Brainstorm and list 10 user stories (title only) You may have fewer than 10 user stories if you can cover the entire system in fewer.
Each person on the team pick 1 user story and fully elaborate it (this is an individual grade, so you do not have to cover for a team mate). This includes the acceptance scenarios.
Team Work
Create login page or some equivalent. Split work.
Create login system not susceptible to easy SQL Injection.
Brainstorm ideas for User Stories on Google Docs.
Grade Rubric
Context diagram covers all actors
10 use cases (or fewer, see above) are listed. They are appropriate and phrased as verb-direct object .....
Android project is created and launches ....
Welcome screen displays (or alternative)....
Welcome screen (or alternative) has controls for login or registration ....
Selecting login brings up screen to enter information ....
Screen displays fields for inputting user name and password ....
Login/Cancel(abort login) has appropriate action
Logout functions correctly
Individual Work (Login / Logout and User Stories)
Each person on the team pick 1 user story and fully elaborate it (this is an individual grade, so you do not have to cover for a team mate). This includes the acceptance scenarios.
Grade Rubric
User story is in correct format
User story complies with INVEST criteria
User story scenarios are in correct format
User story scenarios are complete and cover both success and failure cases
Team Work
Create login page or some equivalent. Split work. Create login system not susceptible to easy SQL Injection. Brainstorm ideas for User Stories on Google Docs.
Grade Rubric
Individual Work (Login / Logout and User Stories)
Each person on the team pick 1 user story and fully elaborate it (this is an individual grade, so you do not have to cover for a team mate). This includes the acceptance scenarios.
Grade Rubric