Standard Process Models
Saying “standard process models“ we mean detailed processes with specific instructions for those involved in the project. The process is strongly segmented in phases, which may be gone through more than once. In process models with iterative approach, the activities within the phases are run through repetitively to refine the results. In opposition to agile process models, standard process models are very static and provide highly detailed instructions on how and when to create which artifacts within the development process.
Read on to learn about two of the most commonly used standard process models.
V-Modell XT
The process model V-Modell XT (succeeding V-Modell 97) is mainly used in administrations throughout Germany. It is a process-oriented standard for the planning and execution of projects like, for example, development of hardware and software systems. Besides RUP, it is probably the most common standard used in Germany.
What you need to know:
- V-Modell XT is designed in a generic way, which makes it suitable for a great variety of projects with different conditions (subject of the project, customer or contractor within the project, criticality). However, this flexibility makes it necessary to adjust V-Modell to the project´s specific needs.
- For further information on V-Modell XT see:
www.v-modell.iabg.de or www.v-modell-xt.de
RUP (Rational Unified Process ®)
RUP, developed by Rational, is a process model dependent on the method used and strongly linked to UML (Unified Modeling Language). Published in 1997, it has been continuously developed further.
Rational Unified Process focuses on phases, workflows and iterations. Each of the four phases is processed in several iterations, with every workflow being run through with different intensity in each iteration. These workflows consist of one or more separate activities. The activities themselves come with detailed descriptions concerning processes, roles, output artifacts, software modules, components, and interfaces.
What you need to know:
- RUP does not deal with all aspects of software development with the same intensity. There are many aspects only described in a non-specific matter.
- RUP only deals with software development. Thus, it is not directly applicable to systems comprising not only software.
- For further information on RUP see: www.ibm.com