week 2
Topic: Requirements and Use Case
Requirements
.Goals
..Understand the user's needs
..Define the system
..Manage the scope and manage change
..Refine the system definition
..Build the right system
.What is it?
..A goal or objective
..A software capability needed by the user to solve a problem that will achieve an objective.
..A goal for the project that you can check off your list when you are done.
..If you don't write a test case it might not be a req't.
.Characteristics
..Traceable
..Numbered
.The most difficult part of requirements gathering is not the act of recording what the users want. It is the exploratory, developmental activity of helping users figure out what they want.
.McConnell's Process
..1. Identify key users
..2. Interview users to create a preliminary set of req'ts
..3. Create a simple, interactive prototype
more
.Asking
..Clarifying
..Inverviewing
..Interrogating
.Telling
..Asserting
..Explaining
..Dictating
.Generating
..Skillfull discussion
..Dialogue
..Politicking - giving the impression that you listen but are closed mind.
.Stay away from Telling.

Use Cases
Use cases do not include:
- User interface descriptions. This is what hte UI prototype is for.