You are on page 1of 2


A requirements engineering management plan (REMP) should not be created without taking a
holistic look at other processes associated with systems development. A typical mistake when setting up
a REMP is to ignore upstream and downstream processes. They are very necessary to understand the
context of any RM processes put in place.
Requirements can be managed using spreadsheets. One technique we use is to periodically
query the database, retrieving statistics on how well the fields are being filled in. By observing quality
field values over time, an organization can monitor improvements in requirements elicitation and
analysis. Another technique that can be used to reduce the manual effort in defining requirement
attributes is to automatically propagate attribute values from parent to derive or from derived to
Product lines, their processes, and their artifacts have been well documented.
The most challenging aspect of managing product line requirements is the multidimensional nature of
some of the requirement attributes.
Table 7.10: Tips for Effective Requirements Management


Only possible to review 4–
10 requirements per hour

Conduct reviews at the highest level possible. As the requirements
become more detailed, the reviews should have fewer participants
and be less formal.

Toolsets not integrated

Create a full metamodel for the environment. Use the metamodel to
plan and implement a tool integration strategy.

Navigation of text

Use web pages with hyperlinks. Associate documents with
keywords. Use nontraditional techniques like Wikipedia’s or webbased visual models, with text behind the symbols.

Difficulty managing traces

Use metamodels to define and automate a tracing strategy. If
possible, use advanced dynamic tracing tools to minimize manual
effort and eliminate problems associated with traces breaking.

Very large, complex product

Use formal modeling techniques instead of pure text. Minimize the
number of documents by keeping the text in the model symbols and
generate documents on the fly.

Large numbers of

Use requirement attributes in the database for levels and types of
requirements to ensure that a query does not bring back too much.

 Plan for navigational facilities. with algorithms to compute the “satisfice” level and to do tradeoff studies. low cost.10: Tips for Effective Requirements Management Issue Suggestion Quality assurance of requirements Put the quality attributes for requirements in the database. Difficulty managing nonfunctional requirements Use formal goal models to visualize NFRs and their large-scale projects.  Carefully define the requirements database schema. Lots of rework due to major discrepancies Be sure to do a root cause analysis on discrepancy sets to determine if there are any weaknesses in the requirements processes. Best Practices The following practices can help with medium.  Create a glossary of terms and use the terms consistently throughout the project.. trace problems Use automated techniques to generate requirements from use cases. Difficulty understanding extensibility requirements Use feature/variability models to formally define exactly what features are given to which clients.  Create a project metamodel or artifact model at project initiation. Generate skeleton test plans semiautomatically from the programmatically linked product map/feature model. e. Difficulty getting reviews done because of the volume of material Use visual/graphical techniques and do online reviews with a web conferencing tool. quality vs. and process models are much easier to review than large amounts of text. Feature.g.Table 7.  Requirements hierarchies should be well defined. Use automated scripts to propagate quality attributes up to parents or down to children. goal. Lots of use case documentation. .