...
| Page Properties | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Goals
- The goals of this requirements page is to document the user stories specifically related to the "Add CCE to Facility" feature. This feature fits within the CCE Reporting and Management epic (
) for the vaccine module and requires a full set of user stories to support development.Jira Legacy server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-571 - While very high-level features were outlined for inclusion in the vaccine module, this page and its sister requirements pages will be used to capture information, stories, background, and processes for the much more specific features.
- Each of these specific features requirements pages should include a business process map to help illustrate the user, system, and administrative aspects of this feature. Not all pieces of the map will translate to specific user stories (e.g. some processes in the map will not involve interaction with the system) but it is still important for us to understand the SOPs that we need to be supporting with this work.
- Scope: This feature should include stories on:
- User processes around viewing CCE catalog and indicating which equipment is at that facility.
- User processes around adding device-specific information to the facility equipment list. (e.g. serial number, brand, vendor)
- User processes around deleting CCE from facility list
- Configuration of pages related to "Add CCE" functionality (e.g. viewing available CCE catalog, UX for user selecting CCE, entering specific info on device to be added)
- ...
- Out of scope for this feature (covered by another page):
- Creating CCE catalog
- Managing CCE alarms & reporting
- Viewing CCE status
- Add CCE that is not in designated catalog (see Open Questions below)
- ...
...