Purpose

According to the BABOK® v3 guide, the purpose of the Maintain Requirements task is to do the following:

" … retain requirement accuracy and consistency throughout and beyond the change during the entire requirements life cycle, and to support reuse of requirements in other solutions."

To understand the purpose of this task better, consider the following example:

Consider building a vehicle that is designed to perform at the peak of its group and level, such as a race car.

There are certain specific requirements, for example, rules and regulations around vehicle weight, engine size, and capacity. These are prescribed by the racing industry and must be followed in order for a new car to be eligible to compete.

Thus, in the future, when someone builds a vehicle designed for racing, or they repair an existing vehicle, the rules, regulations, and requirements have been documented and maintained for future use.

A requirement that continues to remain valid or continue, to exist after a project has been completed must be maintained.

In order to maximize the benefits of maintaining and reusing requirements, the requirements should be as follows:

  • Consistently represented
  • Reviewed and approved for maintenance using a standardized process that defines proper access rights and ensures quality 
  • Easily accessible and understandable
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset