Relationships and Traceability

A key step under the element of RAA is to explicitly identify relationships and traceability. Relationships are clearly important because the systems engineering team must always be aware of and track requirements interdepen-dencies. For example, one section of a requirements document may refer to the pointing error of an instrument and another section may specify the allowable error for the stabilization and control system for a satellite carrying that instrument. The latter error is very likely to influence the former. The systems engineer must establish such relationships and, as a minimum, annotate the dependency.

Traceability has at least two meanings. The first is the explicit connection between all requirements, through all documentation in which such requirements are stated. The second is the traceability of a requirement through all the life-cycle elements of the systems engineering process. Using the earlier instrument pointing error as an example, the T&E (test and evaluation) element must include traceability back to this requirement. Similarly, the TPM (technical performance measurement) program should include this type of traceability. Thus, traceability involves, as a minimum:

• The interdependence between requirements

• The longitudinal tracking of requirements through the various elements of the systems engineering process as they are applied during the system's life cycle

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