How are these Degrees of Obligation Implemented in a Project?

All phases required by stdSEM must be executed
The phases required by SEM are a minimum requirement for standard projects and must therefore always be executed. This naturally does not apply to special cases (e.g. if the project is aborted or if no Operations phase is required). The frame phases (Initiation and Termination) must always be executed.
Subphases generally constitute a group of associated activities which provide a useful subdivision for a phase (in particular technical activities which pursue specific subgoals). If required, additional subphases can be defined on a project-specific basis.

Documents do not necessarily need to comply with stdSEM requirements 1:1
The required contents must exist, but the required documents do not necessarily have to exist as individual documents. The stdSEM subdivision is seen as a proposal for "standard projects". Project execution can nevertheless deviate from this proposal if required. An example: In the case of small projects, it may be quite expedient to combine planning documents (e.g. project plan, CM plan and RR plan). In large projects, on the other hand, it may be expedient to divide up some documents into subdocuments (e.g. several detailed design specifications or test specifications). Refer to the next page for the degree of obligation of subdivisions.

The stdSEM specifications relate first and foremost to results
The stdSEM specifications relate first and foremost to results which must/should/may be available. It is not important when executing a phase to execute all the specifications (descriptions of activities) down to the very last word, but rather to ensure an expedient implementation in the project. The document checklists and examples should be used in particular to demonstrate the meaningfulness of measures so that the latter can be implemented - suitably adapted if necessary - in the project.

What is left as the "hard core"?
What remains are the "must" results as defined in stdSEM!
The "must" results which apply for each phase can be found in the Phase Orientation!

How to use additional specifications within a project
In principle, additional specifications - as far as is expedient - are possible within a project. Method-related measures which are not required or recommended by stdSEM must nevertheless be checked to ensure non-contradiction to stdSEM and must be recorded in the project's QA plan (e.g. check of CASE tools for their suitability in meeting all the requirements made on the project configuration management).


Siemens AG Österreich, Program and Systems Engineering PSE
Contact: stdSEM Webmaster
Last modified: 08/27/98 15:41
Copyright © Siemens AG Österreich 1997. All rights reserved.