-
Notifications
You must be signed in to change notification settings - Fork 0
scenario 3
alpervv edited this page Feb 19, 2026
·
14 revisions
![]() |
Jack Smithson Vietnam Veteran Male Army retiree living in New York City He is a Veteran He wants American youth to leanr NYC history |
|---|
- Wants to post his cultural heritance so that young people can learn the history of places
- Telling a story of his on a platform where others can view and read
- Wants to view how many people have viewed his postings
- Wants to store his memories in a secure public place in case he forgets them or gets caught to alzheimer
- Some people are already using the applicaiton
- The user must have a google account or an email address
- Opens the website and clicks sign up
- Signs up using his gmail
- Types his first and last name, a username is generated from these fields and displayed in the bottom available for editing
- He proceeds without editing his username
- Clicks the "Post" button on top right
- Chooses the option "Post to specific location"
- Drags the maps to point to the location he wants to tell a story about
- He clicks record a story button and start telling the story by talking
- Audio is transcribed and displayed to him for his review
- He approves the transcription without edits
- He clicks Post button
- First post badge appears on the screen
- He clicks the close button
- As users view and comment on his post, he can view the stats on his dashboard
- 1.1.1.2.1 Contributors shall be able to create nodes.
- 1.1.1.2.7 Contributors shall be able to link their nodes with existing nodes.
- 1.1.1.2.8 Contributors shall be able to track the progress of their work and edit them.
- 1.1.2.1 Contributors shall be able to send a collaboration request to another contributor.
- 1.1.2.2 Contributors shall be able to accept or reject a collaboration request.
- 1.1.3.1 Users shall provide their real names, e-mail adresses, passwords to sign up.
- 1.1.3.2 E-mail addresses shall be unique.
- 1.1.3.3 User passwords shall meet safety criteria
- 1.1.3.4 E-mail addresses shall be confirmed.
- 1.1.3.5 Users shall provide some documentation that demonstrates their proficiency in order to contribute to a scientific field.
- 1.1.3.6 Documentation shall be verified.
- 1.2.5.1.2 The platform shall allow users to semantically search for nodes.
See Requirements.
</div>
Team Members
- Lab 1 Report (12/02/2026)
- Lab 2 Report (19/02/2026)
- Lab 3 Report (26/02/2026)
- Lab 4 Report (05/03/2026)
- Lab 5 Report (12/03/2026)
- Lab 6 Report (26/03/2026)
- Lab 7 Report (02/04/2026)
- Lab 8 Report (16/04/2026)
- Lab 9 Report (30/04/2026)
- Lab 10 Report (07/05/2026)
- Weekly Meeting 1 (14.02.2026)
- Weekly Meeting 2 (21.02.2026)
- Weekly Meeting 3 (28.02.2026)
- Weekly Meeting 4 (07.03.2026)
- Weekly Meeting 5 (14.03.2026)
- Weekly Meeting 6 (19.03.2026)
- Weekly Meeting 7 (28.03.2026)
- Weekly Meeting 8 (05.04.2026)
- Weekly Meeting 9 (11.04.2026)
- Weekly Meeting 10 (18.04.2026)
- Weekly Meeting 11 (02.05.2026)
- Weekly Meeting 12 (09.05.2026)
- Customer Meeting 1 (18.02.2026)
- Stakeholder Meeting 1 (09.03.2026)
- Milestone Review Meeting (05.04.2026)
- MVP Test Meeting (08.04.2026)
- Customer Meeting 2 (30.04.2026)
