AWebFactory
Requirements Management
Purpose:
- To establish and maintain agreement with the users and other stakeholders on what the system should do.
- To provide system developers with a better understanding of the system requirements.
- To define the boundaries of (delimit) the system (ie. to describe what functionality must be developed).
- To provide a basis for planning the technical contents of iterations.
- To provide a basis for estimating cost and time to develop the system.
- To define a user-interface for the system, focusing on the needs and goals of the users.
This is where the domain of the system is fixed, the syntax and semantics of the system is fixed, at a crossroads comprehensible to natural language readers, while at the same time, consistent (robust) enough to form the basis for Use Case Analysis (the first step beyond What? and into How?); the perfect crossroads for sign-off on the requirements baseline, the perfect crossroads for change management to commence.
Content
Victor Kane (ProjectMaster) and awebfactory.com.arEmail me at info at awebfactory dot com dot ar
Full content (RSS 2.0) and Headlines (RSS 2.0)