System Engineering Management Plan
Section 4.3 - Model Text

4.3 Allocation.

Each capability function and sub-function shall be allocated a set of performance and design requirements. These requirements shall be derived concurrently with the development of capabilities, time-line analyses, synthesis of system design, and evaluation performed through trade-off studies and system/cost effectiveness analysis.

Time requirements which are prerequisites for a capability or set of capabilities affecting mission success, safety, and availability shall be derived. The derived requirements shall be tested in sufficient detail for allocation to hardware (HWCIs), Computer software (CSCIs), procedural data, facilities, and personnel.

When necessary, special skills or peculiar requirements shall be identified. Allocated requirements shall be traceable through the analysis by which they were derived to the system requirement they are designed to fulfil.

All HWCIs and CSCIs that comprise the system shall be identified in the System/subsystem specification(s) and/or any Prime/Critical Item specifications.

A system/subsystem design document shall be used to describe the design of a system or subsystem and its operational and support environments as specified by a system/subsystem specification.

Development specifications shall define the design, engineering, and manufacturing development of a product during the Engineering and Manufacturing phase and shall be prepared in sufficient detail to specify effectively the characteristics that the item is to achieve to evolve into a production item.

Development specifications shall cover the design and engineering development of a product (CSCI, HWCI, etc.,) during the Engineering and Manufacturing phase and shall be prepared in sufficient detail to describe effectively the characteristics that the configuration item is to achieve so that it will in due course develop into a production item.

It is essential that innovation is an integral part of the process of design and development, and that requirements must always be so framed that ideas and concepts are not inhibited.

For details of example model texts of Development Specifications see:

4.3.1 Technical requirements.

Development specifications shall define the requirements in terms of performance, reliability, design constraints, functional interfaces, etc., that are necessary to assure a practical and reasonable development effort. The specifications may include design goals in addition to the mandatory minimum requirements, but in these cases a distinction between the two must be made to avoid confusion. Only essential design constraints shall be included as requirements (e.g., restriction of use of certain materials due to toxicity, dimensional, or functional restrictions).


Back to Home page MANAGING STANDARDS Home page

Please send any beneficial comments or identification of errors using the following form to: kenr@wysywig.airtime.co.uk

Copyright © Ken Rigby 1996, 1997, 1998