Deleted from Module 6

Refine the system definition

Module 5 described how you use requirement attributes and views to organize project requirements. Now we look at some of the activities that you must perform to refine the system definition and manage changing requirements.

Refining the system definition includes two key considerations: developing more detailed descriptions of the high-level system definition and verifying that the system will comply with stakeholder needs and behave as described. Early in system definition, decisions are made on what constitutes a requirement, documentation format, language formality, degree of requirements, request priority and estimated effort, technical and management risks, and scope. Part of this activity may include early prototypes and design models directly related to the most important stakeholder requests.

The activities include the following: Refinement continues throughout the project lifecycle. It is important to establish a change control or approval process, requiring all proposed changes to be reviewed by designated team members. Sometimes this single channel of change control is called a Change Control Board (CCB). ************
Requirements can be easily modified or edited at any time after their initial creation. RequisitePro records the current site of the requirement in the system-generated attribute entitled "Location." This attribute indicates whether the requirement is contained in a document as well as the database. (Remember, ALL requirements are contained in your database regardless of their current location.) This attribute becomes important when editing or modifying a requirement. Requirements that are in a document can be edited by default only in the document.