1. Analyzing the Problem, gain a proper understanding of the problem that a new software system is intended to solve.
2. Understanding User and Stakeholder Needs, elicit requirements from the system users and stakeholders and ability to understand the real needs that the system must address.
3. Defining the System, converts an understanding of the problem and the users’ needs to the initial definition of a system that will address those needs.
4. Managing Scope, managing the scope of the project and  to negotiate an acceptable deliverable before success can be achieved.
5. Refining the System Definition, organize the requirements information and elaborate on the system definition, or refine it to a level suitable to drive design and implementation, so that the entire extended team knows exactly what kind of system it is building.
6. Building the Right System, design assurance, testing, and change management, and  traceability used to help ensure a quality outcome.

This entry was posted on Friday, July 11th, 2008 at 11:57 pm and is filed under Requirements.