User Stories
End-User Emma is a typical user that seeks to gather information for medical cases to enter into a form so that it can be studied by other end-users.
Arnold Admin is an administrator that has all of the entitlements of an end-user, while also having elevated access for case creation, assignments, and validation.
As End-user Emma, I want to be able to create an account and log in.
As End-user Emma, I want to be able to see my account information.
As End-user Emma, I want to be able to see a list of case studies that I have access to.
As End-user Emma, I want to be able to see open case studies.
As End-user Emma, I want to be able to see the case study information in varying formats and input information about the cases into a form.
As Arnold Admin, I want to be able to see case studies of different formats (e.g. PDF’s, web pages, HTML documents, etc).
As Arnold Admin, I want to be able to create case studies.
As Arnold Admin, I want to be able to assign cases to different users.
As Arnold Admin, I want to be able to see user-inputted information about case studies and create a validated output.
Requirements
Functional
- Definite
- The application must allow account creation and login as either a standard user or administrator.
- The application must display a list of cases assigned to the user in PDF, HTML document or hyperlink format.
- The application must display a form where the user can populate the appropriate fields using the data from the assigned case.
- The application must allow submission of the form where it can be stored and later reviewed by other users.
- The application must allow administrators to create and edit case studies.
- The application must allow administrators to assign cases to different registered users on the platform.
- The application must allow administrators to view and validate user submissions.
- Perhaps
- The application must have a search feature for finding specific cases.
- Improbable
- The application must have a payment system to reward work on case studies.
- The application must use a language model to auto-fill forms.
Nonfunctional
- Definite
- The application must have a separate admin UI from non-admin users.
- The application must be compatible on desktop.
- The application must be easily navigable using a menu.
- The application must have clear separation of case studies and their sub-elements.
- The application must load everything within 2 seconds, otherwise display a loading screen.
- The application must have the ability to scroll through case studies that do not fit on the screen.
- The application must have clearly legible and distinguishable elements.
- The application must be able to display PDF, HTML, and other file types.
- The application must provide a help screen/useful tips for unfamiliar users.
- The application must be able to display error messages.
- The application must not expose any of the underlying code.
- The application must display success/failure messages upon submission of form.
- Perhaps
- The application must be accessible on mobile devices.
- The application must have a verification system for account creation.
- Improbable
- The application must have partial use without the internet.