1. ProblemProblem Statement: Currently most web applications use the standard http file browse and upload service provided with the <input type="file"> form field.
2. UsersCatalina and Christy are some of the users whose needs we primarily considered when designing the Uploader. Fluid 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: Where in the systems we support is an Uploader being used currently?
Functional Requirements: What use cases does the Uploader component support? Primary & Secondary Scenarios: In what scenarios would the Uploader be used? |
4. SolutionWireframes: What does the Uploader look like and how does it behave? Storyboards: How, when, and where would the user use an Uploader?
Comprehensive File Upload Design Pattern: Design advice for performing a "comprehensive" (complex) file upload. 5. Uploader User TestingUploader User Testing: Summary of all user testing performed on the Uploader component. User Testing Protocol: Describes how the user testing of the Uploader will be carried out.
User Testing Results: Describes how the users interacted with the Uploader prototype and what improvements can be made. 6. Preparing for ImplementationStorycards: Decomposes the Uploader into small implementable chunks
Functional Specification: Development specification containing interaction details such as "interesting moments." |