User Story
Note: Definitions for "quickly" as used below are drawn from Performance metrics and expectations
User can quickly log-in and get to their dashboard.
User can quickly see any detail screen with data in it, especially a system with 600K to millions of records.
User can quickly see list of objects or records and pagination, especially a system with 600K to millions of records.
User can quickly navigate through system.
User can quickly review and utilize search results, especially a system with 600K to millions of records.
User can quickly enter and save data.
User can quickly enter, update and save relationships among things.
See also: Performance metrics and expectations for further optimization goals.
Related User Stories:
- <link to a related User Story>
- <link to a related User Story>
- ...
Derived Stories:
These related stories are created or derived from the User Story described on this page. For example, Service Stories describe bits of functionality that a service might need to provide in order for the User Story requirement to be fulfilled. These stories are used to create, plan, and track specific development tasks in JIRA. If development has begun on one of these stories, there should be a link into JIRA describing the story and the related development tasks.
Service Layer Stories
Service Story: <Describe a bit of functionality from the perspective of the service consumer.>
Service Story: <Describe a bit of functionality from the perspective of the service consumer.>
Application Layer Stories
Application Story: <Describe a bit of functionality required by the UI layer components as clients.>
Application Story: <Describe a bit of functionality required by the UI layer components as clients.>
UI Layer Stories
UI Story: <Describe a bit of end-user functionality and interaction with UI components.>
UI Story: <Describe a bit of end-user functionality and interaction with UI components.>
0 Comments