What about Maintenance and Non-Software Projects?

Maintenance projects
A project is termed a maintenance project if it involves performing work on an existing product. There can be three reasons for changing an existing product:
  • Eliminating errors
  • Performing functional changes (extensions, adaptations)
  • Performing non-functional changes (porting, optimizations).

Virtually all maintenance projects are dealt with using the evolutionary development model. Each shipment results in a new product version (following error elimination, incorporation of change requests or optimizations). Since a maintenance project is always based on an existing product, the software code is accompanied by documents generated during earlier versions.

Every phase contains information which is particularly relevant for maintenance projects in this phase. To obtain information, simply click the "What about maintenance projects?" icon on the Phase Orientation page (can be accessed from the Phase Overview).
Non-SW projects
All activities and results required by stdSEM must also be applied for non-SW development work (services, consultancy, orgware, etc.; the eeSEM instance exists for HW development).
This can be applied directly for some activities (e.g. kick-off activities, reviews, etc.). With other activities and results, however, the requirements as per stdSEM must be applied analogously (e.g. specifications, tests, etc.).
Every phase contains information which is particularly relevant for non-SW projects in this phase. To obtain information, simply click the "What about non-SW development?" icon on the Phase Orientation page (can be accessed from the Phase Overview).

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.