1
0
mirror of https://github.com/corona-warn-app/cwa-documentation synced 2024-10-31 22:58:48 +01:00
Commit Graph

22 Commits

Author SHA1 Message Date
Henning Femmer
3562e21612
Resolves https://github.com/corona-warn-app/cwa-documentation/pull/241#discussion_r441028490 2020-06-18 20:41:56 +02:00
Henning Femmer
2668f96096
Response to https://github.com/corona-warn-app/cwa-documentation/pull/241#discussion_r441029404 2020-06-18 20:09:20 +02:00
Henning Femmer
ff2ba6848d
Changed app users to user consistently and added clarification at the beginning 2020-06-18 20:07:10 +02:00
Henning Femmer
7b29d9cdb3
Phone number must not only be stored, but also visible to the user. 2020-06-14 23:03:38 +02:00
Henning Femmer
c838ee1de5
Update scoping_document.md
- consistency: application -> app, user -> app user
- replacing pronouns for ease of reading
- minor grammatical issues
2020-06-14 23:01:22 +02:00
Henning Femmer
dcf55b9971
Clarified language, removed "should" from non-requirements
"Must, shall, should" are triggers indicating legal requirements. In this case they were not, so I clarified and also improved the sentence on the way.
2020-06-14 22:42:35 +02:00
Henning Femmer
6fcda23378
Took the precise name of the format
see https://en.wikipedia.org/wiki/User_story#Common_templates
2020-06-14 22:32:42 +02:00
Henning Femmer
d6371c5f71
Removed unverifiable acceptance criterion and added an explicit one
This seems to be the major case, so better add a AC for it. Even better, improve with future languages.
2020-06-14 22:29:02 +02:00
Henning Femmer
36f94d3498
Remove "might" for clarity
Additional comment: Most functionality of the system is not for everyone. There is no need for optionality in the "reason" part
2020-06-14 22:23:58 +02:00
Henning Femmer
dfca9d4502
Removed "various", since it does not carry any additional meaning or is ambiguous. 2020-06-14 22:20:28 +02:00
Henning Femmer
12926a56b0
"at any time" is either imprecise or unnecessary
The acceptance criteria does not really make it better. Should it say something like from any part of the app with just one step?
2020-06-14 22:18:51 +02:00
Henning Femmer
272ffaed98
more improved wording on slashes 2020-06-14 22:14:08 +02:00
Henning Femmer
9dd4ec2a6e
Fixed dangerous (potentially ambiguous) slashes 2020-06-14 22:09:52 +02:00
Henning Femmer
abd74ad6d7
Added rationale for E06.02 2020-06-14 21:53:44 +02:00
Henning Femmer
ab28f6220f
Added rationale for E02.05 2020-06-14 21:49:36 +02:00
Henning Femmer
946d119be0
Added Rationale for E01.01 2020-06-14 21:47:09 +02:00
Sebastian Wolf
b90b67dbff
docs: New revision of scoping document (DE,EN) 2020-06-05 15:47:19 +02:00
benekuehn
6819d4ef50
Update scoping_document.md
deleted the apostrophe as requested in pr #150
2020-05-26 14:20:16 +02:00
benekuehn
b8786a2823
Update scoping_document.md
Line 77 only wrote "publish pseudonymized warn ID" but has to be "publish pseudonymized warn ID's" as each user will have generated more than one ID during the use of the app, as also stated later in line 156 correctly.
2020-05-26 14:12:36 +02:00
Henning Femmer
1c1bc27229
Made the User stories consistent with User Story Template
The template defined at the beginning was used inconsistently, so I made it consistent. I also used the common Pattern: As a, I want, so that (cf. Mike Cohn: https://www.mountaingoatsoftware.com/agile/user-stories)
2020-05-20 15:41:10 +02:00
Henning Femmer
e290ab4451
Replaced <> with &lt; and &gt;
Brackets were read as html tags and not displayed in markdown. I used &lt; and &gt; instead
2020-05-20 15:27:54 +02:00
Sebastian Wolf
bdd8f103e6
docs: Add English version of Scoping Document 2020-05-14 19:40:25 +02:00