Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Add missing stakeholders #69

Closed
sventuerpe opened this issue May 15, 2020 · 5 comments
Closed

Add missing stakeholders #69

sventuerpe opened this issue May 15, 2020 · 5 comments
Labels
documentation Improvements or additions to documentation enhancement Improvement of an existing feature in progress The issue is currently being resolved scoping Issue concerning the scoping document

Comments

@sventuerpe
Copy link

sventuerpe commented May 15, 2020

What is missing

Add the following stakeholders:

  • Local health authorities
  • Coronavirus test centers
  • Responsible system operator

Why should it be included

Important requirements originating from these stakeholders need to be considered.

  • Local health authorities are responsible for contact tracing, quarantine orders, and follow-up actions. For automated contact tracing to be as effective as possible, their efforts need to be integrated with whatever CWA does. Their needs are apparently being ignored so far. Local health authorities also likely play a role in the handling of test results, supervision of testing and general pandemic management.
  • Coronavirus test centers need to enter test results into the system so that app users can be notified about their results. The current scoping document covers only the output side but gives not the slightest hint how test results get into the system in the first place. There are very likely specific requirements pertinent to the input side such as identity and access management, integration with existing processes and systems, and so on.
  • The whole system will have a responsible operator in one way or the other. This operator, in their own right or on behalf of, e.g., the RKI needs to monitor the operation of the system, identify problems and detect abuse, report metrics such as false alarm rates and compliance rates after notification, etc.

Where should it be included

This information belongs in the scoping document, later in the backlog.

@sventuerpe sventuerpe added documentation Improvements or additions to documentation enhancement Improvement of an existing feature labels May 15, 2020
@jarjarbentley
Copy link

We appreciate this suggestion and will be in touch early next week with more comments. Best regards,
JB
Your Corona Warn-App Open Source Team

@sventuerpe
Copy link
Author

@jarjarbentley No need to hurry. Enjoy your weekend, I am sure you deserve it.

@christianbrb
Copy link

@sventuerpe 😊👍🏻

I would call them users instead of stakeholders.

@lukasmasuch lukasmasuch added the scoping Issue concerning the scoping document label May 16, 2020
@aeisenbach
Copy link

Hi @sventuerpe, thank you for this suggestion. We already drafted additional user stories from these perspectives and will add them to the documentation in the next days. BR, Andreas

@jensmuehlner jensmuehlner added the in progress The issue is currently being resolved label May 17, 2020
@jensmuehlner
Copy link
Member

As @aeisenbach from the Scoping-Team confirmed, they will add additional user stories to the documentation in the next days, taking yours into account. Therefore we might close this issue and look at it again after the document is updated, ok?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation enhancement Improvement of an existing feature in progress The issue is currently being resolved scoping Issue concerning the scoping document
Projects
None yet
Development

No branches or pull requests

6 participants