SOW Requirements Management

For more than seven years, MBT- Missile Division at the Israeli Aerospace Industry (IAI), have been managing requirements of project families using Requirements Management (RM) tool infrastructure, including contract requirements, system specifications/subsystem specifications, algorithms, and hardware/software specifications. The benefits of the RM process and requirements reuse was published at IEEE CS SWSTE 2010 conference [1].

While using requirements leveling approach to manage the technical requirements along with reuse of requirements, the RM tool infrastructure was also used for test coverage. As part of the Verification and Validation (V&V) process, the requirements management tests (RMT) tool infrastructure provided traceability between requirements specifications and test requirements. Based on the interface between the RMT (DOORS) and the Test Management Tool (QC), traceability of requirements to tests coverage was achieved in three test levels:
system, subsystem, and software testing. The advantages of this test coverage management was presented at INCOSE-IL conference 2013 [2]

Recently, we began using the RM tool infrastructure for managing non-technical requirements on top of the technical requirements that we are already managing in the RM tool infrastructure. This presentation describes a method of managing the SOW (Statement of Work) requirements based on the requirements leveling approach.

Standard SOW is composed mainly of the following requirements areas: Sytem engineering and development , testing and analysis, HW specifications ,prototypes est. Managerial requirements as milestones, liveries,reviews,documentation,ILS, standards and qualification assurance.

The motivation for managing the SOW requirements via RM tool infrastructure is to achieve control and oversight of the managerial requirements, referred to as non-technical requirements, along with their traceability to the technical requirements and testing deliverables (artifacts). The RM tool infrastructure helps us to classify the SOW requirements to their different areas and trace them to the different subsystems and different sub-contractors that are assigned to build those systems. This traceability of deliverables and responsibilities is most crucial for project management of System of System (SOS) complex projects.

Classifying the requirements in the RM tool makes it fissible to easily produce reports such as milesstones vs. DR's documents and deliverables , Requirements vs. costs, Requirements vs. risks and so on.

Working with the RM tool, in the leveling approach infrastructure, and classifying requirements vs. contractors enables generating SOW's in levels as described before, and linking them to the original SOW, and can be managed in the same manner as system requirements on the RM tool. Moreover these requirements can be linked to the specifications artifacts managed on the same tool.
All rules of traceability and change management can be applied in the same manner.

We shall present a concept of creating such infrustructure in an RM tool describing several

managerial reports, and the process of managing the SOW's.

[1] Goldin L., Matalon M., Lapid J.," Reuse of Requirements Reduces Time to Market ",

The IEEE international Conference on Software – Science, Technology, and Engineering,

Hezeliya, June 2010 (under Methodologies)

[2] Matalon M., “Requirements to Tests Coverage in Project Families", INCOSE-IL 2013,

Hezeliya, March 2013,

(under Requirements Engineering in Complex Systems)

Michal Matalon Beck
Requirements Mangement
Systems Missiles & Space Group