Systems Engineering Master Schedule

The information provided here shall provide details for general guidance on the 'Systems Engineering Master Schedule' (SEMS).

Overview

The SEMS is the top-level process control and progress measurement tool for the systems engineering effort.
It shall provide visibility for in-process verification. The SEMS shall provide visibility of the accomplishments of the technical factors.
The events shall provide visibility into the progress and to assess risk.
The SEMS shall be developed to address specific project needs and the technical effort to be accomplished. The SEMS shall provide overall visibility into the accomplishments necessary to ensure the requirements. Each SEMS will identify the project specific aspects relative to demonstrations and risk reductions to project success.

The SEMS is a technical events plan, i.e., driven by events, not date driven, or time constrained; it is in general process controlled Basic process model.
It is not driven by dates and time. The events in the SEMS are key demonstration, progress assessment, decision points, or other events identified by the tasking activity (SOW).
These events shall be acquirer/supplier reviews, e.g., System Requirements Review(s) Formal Reviews major verification efforts, or other technical events.

For an SEMS example SEMS Click here.

The SEMS has four critical elements:

• Events
• the required accomplishments
• the criteria for each accomplishment
• the event sequencing (or "time-line")

Additionally, a numbering scheme should be used to simplify tracking of events, accomplishments, and accomplishment criteria to tasking statements, work breakdown structure, and the 'systems engineering detailed schedule'.

• Events - events in the SEMS can include reviews and other key progress demonstration points. The SEMS is not date driven, however, a limited number of events may be date related based on availability or other constraints;
• SEMS Accomplishments - SEMS accomplishments define interim and final steps to defining and producing the system. The accomplishments shall be sequenced and organized around the product and event they support.
  Typical examples are:
  • architectural design complete
  • interface documented;
  • etc.
• Defining the scope of accomplishments is a factor critical to the success of the SEMS. If accomplishments are too narrow, the flexibility in executing the technical effort can be curtailed. For example, defining accomplishments that represent only a couple of months effort is probably too detailed for most program applications.
  Accessibility to the SEDS should provide the needed visibility into the performing activities technical progress. Alternatively, accomplishments that are too broad (for example, if they span multiple events) need to be decomposed into manageable parts.
• Accomplishment criteria - The accomplishment criteria shall be measurable and useful. The statement 'Test Plan complete' is measurable and useful. 'Test Plan 85% complete' is not measurable (the last 15%may take 85% of the time).

rest 'under construction'

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