Procedure model
A process model, V-model, is initially quite generally the organization of a process into different, structured phases, which in turn are assigned specific methods of organization. In this process, the tasks underlying the process and corresponding activities are linked with each other in a logical order. In terms of software processes, a process model defines a set of rules from planning, through realization, to implementation and maintenance, which supports and controls the necessary phases. Depending upon the model used thereby different points of view can be taken as well as specific aspects particularly stressed. Procedure models are to support a structured and at any time transparent realization of software projects, in order to avoid so risks, time delays as well as unnecessary costs and to maximize the software quality.
A goal of the procedure models
An optimal goal of procedure models in the software development process is the covering of the ranges:
Project management, qualitymanagement, configuration management, change management, software engineering and project controlling.
The central range forms thereby the software development, which is supported by the quality management with test and Reviews. Configuration management organizes software version management and change management regulates the management of modifications (change requests). Project management has an overview of all these areas. Their tasks are the planning, assignment, monitoring and control of processes. For larger and more complex software projects, a project controlling system is defined that is superordinate to all areas for monitoring and controlling.
Procedure models as framework for software projects
Procedure models give a framework for the realization of software projects and stress depending upon the selected model different points of view. They recommend guidelines for roles (responsibilities), individual phases, specific activities and activities to be derived from them, as well as methods and standards for documentation. The analysis, design, implementation and test phases are an integral part of each model, which then usually provides for specific, optimizing additions.
In this connection the following classical procedure models for the development of software are to be mentioned:
Waterfall model Rigid structure of sequentially running phases. Iterations are only allowed between two successive phases
Rational Unified Process (RUP) Very intensive process model based on the Unified Modeling Language( UML), which covers the complete software life cycle
Spiral Model Iterative and incremental phase model that is no longer linear in structure
V model The V-model is considered the standard for the organization and implementation of IT projects. It is differentiated into the phases of project management, quality assurance, software development and configuration management.
Agile software development The model provides for a reduction of the general project effort using as few rules as possible
Object Engineering Process (OEP) Defines an iterative-incremental, agile, use case-driven, and architecture-centric development process.
Extreme Programming (XP) The model is based on an agile and iterative approach to the process of developing software.