...
- Demo data (20 items)
- More depth in problem statement and user stories
Presentation Outline:
The Product Committee meetings 9/27 at 9am PST
We will have 20 minutes to:
- Introduction and describe Summer of Code
- Describe what you have done
- Explain the goal of this mobile prototype
- Demo the prototype
- Ask questions to the Product Committee (because if they ask questions, the meeting might never end)
- What are the next steps for picking up the design work
Problem Statement
Stock clerks have the difficult task of tracking the inventory at a clinic. These clinics can range in size from a district hospital to a rural health outpost.
We have chosen to focus primarily on doing a physical inventory in the OpenLMIS system, and using that to refine the OpenLMIS-UI design to support mobile navigation and data entry.
9/21 Mary Jo thoughts
- We don't use grouped products like we have in requisitions
- Navigation could use accordion/sliding menu all the way until you get to the products
- For a mobile device, its probably going to be used in a small clinic —
- How do you see the summary page so you can check your work before you submit
- What does an error message look like
- If you didn't add an adjustment reason to an item – what does that look like
- Missing Adjustment Reasons feature
PC presentation should include
- Explain what they did
- What was your goal
- What are the next steps for the community picking up this design work
9/17 Draft Feedback
The following feedback is from Nick Reid (Deactivated) and Alfred Mchau
...