systematic, disciplined, and quantifiable application of approaches to define and manage the purpose and the external behavior of a proposed software product (in the WWW).
Includes:
elicitation set of activities to elicit or discover stakeholder requirements.
Measurables:
- functionality/ business processes (legacy systems)
- content (new, exists, static versus changing, database support)
- structure/navigation (design)
- presentation (layout, design)
- user interaction: operating on presntation elements
- usage/access
- performance
- supportability
Methods:
analysis specification
aspects of good specifications: correct, precise, unambiguous, complete, verifiable, consistent, modifiable, traceable, usable during operation and maintenance, versioning.
1)Gain agreement on the problem being solved
2) identify stakeholders
3) define product boundaries (includes HW/SW requirements, architecture)
4) Identify constraints imposed on product
5) Define priorities, risks, critical features
6) Define performance, reliability, suportability
product = vision of desired solution
managment
manage scope of project
refine product as needed
- produce mock-ups, screen shots
verify results and progress
manage changing requirements
- change request - request made to change as a potential improvement.
- problem report - description of a defect identified that may lead to change for a fix.
