View Source

Target release	3.3
Epic
Document status
Document owner	Sam Im (Deactivated)
Technical Lead	Technical Lead who reviews or supports document

Goals/Scope

Configure Program Settings such as:
- Customize the requisition template
- Enable skipped periods
- Show Non Full Supply tab
- Edit Program code and name
- Create new programs and associate facilities to supported program
- Create and edit Reasons
- Create and associated Processing Schedules

Background

Are there any country specific features that should be noted? Who are the personas? Who are the users that will be interacting with this functionality? What are their challenges, responsibilities, and level of connectivity? These personas are intended to be representative archetypes of the key stakeholders who will participate in theses workflows/scenarios.

Screenshot from Version 2:

OpenLMIS > Program Settings > Screen Shot 2017-05-25 at 3.35.54 PM.png

Assumptions

Version 2 functionality for Equipment Tracking, Budgeting, and Price Schedule are not included.
Changing Program status to Inactive
Audit logging for changes

User Stories

Short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.

#	Title	User Story	Label	Importance
1	Edit Program Settings	As an admin I want to edit program settings so that control these settings at the program level. View program settings Enable or disable skipping periods Select show non full supply or hide non full supply tabs	Relevant labels to distinguish source. From which system, or which country?	Must Have
2	Add New Program	As an admin I want to add a new program so that I can associate them with the required information to use in the requisition process. Admin can create new program and enter required program settings details Admin can create new R&R template for the new program
3	Create Reason	This was part of Stock Management epic The purpose of this ticket is to consolidate Program specific configuration into one section of the Administration tab.
4	Create Processing Schedules	Create & associate processing schedules to a program
5	Configure R&R Template	This was part of Requisition epic
6	Edit Reason	Edit an existing Reason

Diagrams

Include any business process mapping, mockups, diagrams or visual designs relating to these requirements. Describes the tasks and the personas who perform those activities. The diagram provides the context for the user stories and serves as a focal point for achieving clarity and agreement among stakeholders. Looks like a standard flow chart.

Dependencies

Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.

Description	Link
Name of story or release	Link to JIRA

Open Questions

Initial communication between stakeholders and the development team to help understand scope and estimates.

Below is a list of questions to be addressed as a result of this requirements document:

#	Question	Outcome	Status
1	(e.g. How we make users more aware of this feature?)	Communicate the decision reached	Open, In Progress, Closed, and date of closure

Out of Scope

List the features discussed which are out of scope or might be revisited in a later release.