CIS 3750 Lecture Notes - Lecture 3: User Story, Jargon, Sept
19 Oct 2018
School
Department
Course
Professor
Document Summary
Is incredibly di cult to do with accuracy. You are working on a new problem domain. You don"t have a rm design and many implementation details ironed out. User stories de ne a feature that a speci c user would like to see in the project and why, requirements are more general and de ned using the user stories. Requirements need to explain what makes something easy for a user. The best requirements are concise and unambiguous. Ex: the system must respond to a search query in less than 2 seconds to provide a list of the 50 most relevant results . To make this requirement statement better we should include a why. The system must respond to a search query in less than 2 seconds so the emergency dispatcher can quickly con rm the address of the caller . Its important that we know why the system needs something so that we can evaluate the requirement ourselves.
