In accordance with the Engineering Management programme, it is a firm objective that this Systems Engineering Management Plan shall apply throughout all stages/phases of the project total system life cycle starting with the Concept Exploration phase. This SEMP shall be updated progressively as the work proceeds and the necessity arises.
Prior to contract award involvement in formulating the contract requirements may be required to define performance requirements to promote innovative and cost-effective acquisition requirements and strategies (see MIL-STD-248B). These requirements shall be defined in the 'Statement of Work' (SOW) document and should be prepared by the acquirer of the system with assistance if necessary of the developer.
While the Systems Engineering Management Plan describes the overall management life cycle, policies, principles and objectives, precise methods and processes shall be defined within the specific engineering discipline plans, standards and procedural documents.
Organizations defined within these plans shall be known as "Technical Authorities" and will be responsible for the functional aspects and correct application of their specific specialist disciplines.
Detailed procedures for use within Industry shall be defined in further detail and shall be consistent with this Plan. These shall include the specific specialist standards and plans, which may be the internal to industry documents, procedures and plans. If necessary some of these documents are identified in identify source of local procedures.
Acquisition streamlining in accordance with MIL-STD-248B shall be performed to ensure the project shall be efficient and effective.
Corresponding with these standards and plans, appropriate baselines and build standards shall be established in accordance with the CMP, starting with the Configuration Identification at the start of the Engineering and Manufacturing development stage (see figure 2), including standards, if applicable, for each prototype and production.
System and subsystems shall be specified in the System/Subsystem Specification (and the design detailed in system/subsystem design documents) or Critical/Prime Item Development specifications and shall be produced using the criteria contained in the Data item example text provided in the SSS model text. These specifications shall state all necessary requirements in terms of performance, including test provisions to assure that all requirements are achieved. Essential physical constraints shall be included.
CSCIs shall be developed to the process and requirements contained within the Software Development Standards and Plan(s) documentation that shall be compiled from the software development requirements defined in DOD-STD-2167A/498, RTCA/DO-178B, ISO-12207, DOD-STD-2168, AQAP-13, JSP 188, OB-PROC-42413, and DEF STD 00-31/1 to produce a complete, concise and uniform software development process for all systems.
For software during Engineering and Manufacturing development phase, standards and plans shall be identified within an Software Development Plan (overall) (SDP),* which shall be fully compatible with this SEMP. Each CSCI being developed shall have a CSCI specific SDP which shall confirm adherence to the Software Development Plan (overall) and hence to the comprising Standards and Plans, i.e., SPEP, SCMP, SDOS, SSPM, SQPP. Once becoming available for release to the System, CSCIs shall become subject directly to the procedures defined in this SEMP.
If a user-computer interface is required it shall be developed integrally with the system software. This will result in a maximally useable, operable, reliable and fully integrated with the system and software development process.
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
