2. Analysis - the purpose of the analysis is get of the description of the task, it should be full, consistent, suitable for reading and reviewing by all interested sides, really checked. The analysis is concentrated not on the form, and on behaviour and should explain what the system does, instead of how it does. Designing should answer a question "how". The full analysis prior to the beginning of designing not only is impossible, but also undesirable. To execute the full analysis of all primary elements and some secondary enough that will allow to track a course of performance of the project. As a result of the analysis we should receive the description of a system designated purpose with the help of scripts, diagrams of objects, diagrams of classes for demonstration of relations between classes and diagrams of conditions for demonstration of life cycle of the major objects also are allowable. Besides in the analysis we should specify such requirements to system as efficiency, reliability, security, portability, an estimation of risk (dangerous places exposure).

3. Designing - is necessary for creation of architecture of developing realization and production of uniform tactical receptions for various elements of system. For the description of architecture it is important to show grouping of classes in a category of classes (for logic architecture) and grouping of modules in subsystems (for physical architecture). The architectural release of system represents the vertical cut of architecture transmitting major (but not full) semantics of essential categories and subsystems and is a basis of evolution of system. The architectural release should be working program that allows to measure, study and estimate architecture. The general tactical receptions are the located mechanisms which are shown everywhere in system, such as principles of detection and processing of mistakes, management of memory, storage and data presentation, approaches to management.

4. Evolution - the basic purpose of evolution - to increase and change realization, consistently improving it, finally, to create ready system. Evolution at realization of software product is better, than the monolithic set of receptions helps to determine, what restrictions are essential, and what are not present. Analyzing behaviour of each new release, using histograms and to that similar technics, we can better understand how to adjust system. Evolution is a process of development of the program. At this stage we to the full use microprocess. Result of evolution is a series of executable releases representing iterative improvements of primary architectural model. This stage comes to the end with release of a ready product and its delivery in operation.

5. Support is an activity on management of evolution of a product during its operation. During this stage corrections of old mistakes and the located changes arising in process of the account of new requirements are made. Results of this step are similar to results at a stage of evolution except that to them work with the list of improvements and corrections is added.