Effective Techniques for Requirements Gathering and Prototyping in Software Development
This guide covers essential techniques for gathering requirements, including user and domain insights, task analysis, and user interface design. It delves into prototyping methods such as throwaway and evolutionary prototyping, highlighting their roles in validating requirements and delivering functional systems to users. The text discusses the advantages and disadvantages of various prototypes, including high-fidelity and Wizard of Oz prototypes, providing a comprehensive overview for software developers and project managers.
Effective Techniques for Requirements Gathering and Prototyping in Software Development
E N D
Presentation Transcript
Part 2d: Requirements Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain Chapter 4: Finding Out about Tasks and Work Chapter 5: Requirements Gathering: Knowledge of the User Interface Design Chapter 6: Thinking about Requirements and Describing Them Chapter 7: Case Study on Requirements, Part 1 Video: Paper Prototyping
Prototypes The quickest way to build something is, first to build something else Most frequently used modern method for communicating, getting feedback, and evaluating design of new software products
Two major types of prototyping • Throwaway Prototyping • Also known as Rapid Prototyping • The objective of throw-away prototyping is to validate or derive the system requirements. • Start with those requirements which are poorly understood • Evolutionary Prototyping • The objective of evolutionary prototyping is to deliver a working system to end-users. • Start with those requirements which are best understood.
Discussion • What are some disadvantages of high-fidelity prototypes • Wizard of Oz prototypes