1. ProblemProblem Statement: 2. UsersFluid Personas are a collection of various types of important users whose needs we need to consider throughout the design process. 3. Users' needsContexts of Use: In what contexts would the user need a Pager? What activities do they undertake in these contexts? Functional Requirements: What use cases does the Pager component support? Primary & Secondary Scenarios: In context, what are the primary and secondary user needs are we meeting? |
4. SolutionWireframes: Visual representation of design iterations and final designs. Storyboards: How, when, and where would the user use a Pager? Design Pattern
Accessibility Considerations: 5. User TestingPager User Testing: Summary of all user testing performed on the Pager component. User Testing Protocols: Describes how the user testing of Pager will be carried out. User Testing Results: Describes how the users interacted with the Pager prototype and what improvements can be made. 6. Preparing for ImplementationStorycards: Decomposes the Pager into small implementable chunks. Functional Specification: Development specification containing interaction details such as "interesting moments." |