This preview has intentionally blurred parts. Sign up to view the full document

View Full Document

Unformatted Document Excerpt

will system have on their business processes and the way that work is done. Once endusers have experience of a system, they will discover new needs and priorities. There are several reasons why change is inevitable: 1. The business and technical environment of the system always changes after installation. New hardware may be introduced, it may be necessary to interface the system with other systems, business priorities may change (with consequent changes in the system support required), and new legislation and regulations may be introduced that the system must necessarily abide by. 2. The people who pay for a system and the users of that system are rarely the same people. System customers impose requirements because of organizational and budgetary constraints. These may conflict with end-user requirements and, after delivery, new features may have to be added for user support if the system is to meet its goals. 3. Large systems usually have a diverse user community, with many users having different requirements and priorities that may be conflicting or contradictory. The final system requirements are inevitably a compromise between them and, with experience, it is often discovered that the balance of support given to different users has to be changed. Requirements management is the process of understanding and controlling changes to system requirements. You need to keep track of individual requirements and maintain links between dependent requirements so that you can assess of the impact requirements changes. You need to establish a formal process for making change proposals and linking these to system requirements. The formal process of requirements management should start as soon as a draft version of the requirements document is available. However, you should start planning how to manage changing requirements during the requirements elicitation process. 4.7.1 Requirements management planning Planning is an essential first stage in the requirements management process. The planning stage establishes the level of requirements management detail that is required. During the requirements management stage, you have to decide on: 4.7 I Requirements management Identified Problem Problem Analysis and Change Specification Change Analysis and Costing Change Implementation 113 Revised Requirements 1. Requirements identification Each requirement must be uniquely identified so that it can be cross-referenced with other requirements and used in traceability assessments. 2. A change management process This is the set of activities that assess the impact and cost of changes. I discuss this process in more detail in the following section. 3. Traceability policies These policies define the relationships between each requirement and between the requirements and the system design that should be recorded. The traceability policy should also define how these records should be maintained. 4. Figure 4.18 Requirements change management Tool support Require... View Full Document

Software Engineering 9 summer

End of Preview

Sign up now to access the rest of the document