Ads
  

Background for Requirements Management

Background for Requirements Management

A number of excellent guides to requirements elicitation have been published; therefore, our intention is not to rearticulate them, but to make the reader aware of them and the power of their use. Gerald Weinberg, Roger Pressman, and Barry Boehm have suggested steps to gather and understand the necessary software requirements and prepare them for specifications in the SRS. We do not pretend to know of superior approaches, but we do desire to present a practical description and guide to consolidating the wisdom of these authorities.

In this section we'll talk about "Gather" and "Analyze" from Weinberg's steps shown in Figure 1. We will also reference a set of very high-level models that could help with gathering and analyzing requirements. The majority of modeling activities will take place in the analysis and design phases.

Weinbergs Steps in Analyzing Requirements

From Pressman's requirements engineering steps, shown in Figure 2, we'll cover requirements elicitation (understanding what the customer wants) and requirements analysis and negotiation (analyzing need, negotiating a reasonable solution). Pressman's requirements specification step will be covered in "Developing the Software Requirements Specification". Pressman's system modeling step will be covered in "Analysis and Design Methods".

Pressmans Requirements Engineering Steps

Requirements engineering steps include:

●  Requirements elicitation - understanding what the customer wants;

●  Requirements analysis and negotiation - analyzing need, negotiating a reasonable solution;

●  Requirements specification - specifying the solution unambiguously;

●  System modeling;

●  Requirements validation - validating the specification;

●  Requirements management.

From Boehm's model, shown in Figure 3, win conditions, negotiation, mutual gain, trade-offs, and win-win agreements apply when prioritizing requirements and preparing them for the specification activities.

Boehms Requirements Engineering Steps

Software requirements engineering is the process of determining what is to be produced in a software system. It has the broadly recognized goal of determining the needs for, and the intended external behavior of, a system design. The process of requirements engineering is regarded as one of the most important aspects of building a software system. Within a project, it is a general term used to include all the activities related to requirements. The four particular steps in software requirements engineering are: requirements elicitation, requirements analysis, requirements specification, and requirements validation.


Tags

software system, software requirements, requirements engineering, requirements elicitation
The contents available on this website are copyrighted by TechPlus unless otherwise indicated. All rights are reserved by TechPlus, and content may not be reproduced, published, or transferred in any form or by any means, except with the prior written permission of TechPlus.
Copyright 2018 SPMInfoBlog.
Designed by TechPlus