Derived Requirements

A critical part of requirements analysis is the construction of derived requirements. These are a set of requirements derived from the original requirements specification but are not actually a part of the specification itself. In other words, such requirements flow from the systems engineering analysis and must be formulated to proceed constructively with the design of the system.

An example can be seen by correcting the requirement for availability cited Section 8.5.2. This requirement is restated as:

• The overall system shall have an operational availability of 0.988 with an MTBF of 500 hours and an MDT of 6 hours.

The issue here is that requirements for the subsystems have to be derived from this overall system requirement in order to design the subsystems. Such derived requirements are not part of the requirements document; it is up to the systems engineering team to derive them. Thus, the team has to annotate all cases for which top-level system requirements must be analyzed in greater detail to develop a set of derived requirements. Such derived requirements are then ''allocated'' to the subsystems to give guidance to the subsystem design teams. More specific examples of how this might be done are explored in the next section.

Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Post a comment