INFO$20172$ Group Project Campus Health Hub SS $2024$

Campus Hub user stories and acceptance criteria

For a smoother transition to the $2$nd half of the course and to allow your $2$nd half profs to prepare for your group project submissions, you are required to complete a draft document showing the user stories, story points and the acceptance criteria for activities of the Campus Health Hub $($details found in the module $>$ Group Project$).$

You will need to provide $15-20$ examples of user requirements which the new system will need to provide to its clients $-$ students, faculty, staff etc. on campus.

Examples may include making an appointment, access to what issues are covered by a medical plan, participating in various health programs$/$initiatives$,$ etc.

As per class discussions:

A user story is a description of a user requirement i$.$e$.$ something that the system must provide, request, complete, document, calculate, etc. and that adds value to the user$$s business needs.

A user requirement is NOT about having a friendly dashboard, having security, being reliable, accessibility across platforms, modifying user preferences, etc. as these concepts are given$/$expected in any credible application system.

Please ensure that your user stories are clear and are NOT just a heading. Use your common sense and your experience from your previous semesters to write credible user stories and acceptance criteria.

Using Chat to do this will not help you during the week $13$ presentations when you will be asked to explain what the user stories mean and how they interact with one another. Chat won$$t be there to help you.

Submission Requirement:

For each of the $15$ to $20$ user stories, add a realistic story point and $2$ acceptance criteria that need to exist in order for the user story to be 'deemed' completed. Acceptance criteria are conditions that the story must fulfill. Each is testable in the real system. Criteria are not $400$ word paragraphs. Criteria clarify the expected outcomes of the user story; it defines when a user story is a success and is considered $$done$.$

$$

Example:

As a teacher, I need a grades report, so that I can compare student progress across different sections.

Possible acceptance criteria:

$1.$ Display the test average as a $\%$ for each section, including the lowest test $\%$ and the highest test $\%$

$2.$ By section, provide the student name, student number and test mark as a $\%$ for each student who is below the test avg $\%.$

$3.$ By section, provide the student name, student number and test mark as a $\%$ for each student who failed the test. By section, include a count of the number of said students and the percent that they represent compared to total students in that section.

Organize your stories as follows:

Story $1$: As a $.....$ I want $......$ in order to $......$

$$As a $[$type of user$],$ I want $[$an action$]$ so that $[$benefit$/$value$].$

Story point: $3$

Acceptance criteria $1$: $.......$

Acceptance criteria $2$: $.......$

User Story $2$: $......$

Etc.