Development Phases

The execution of the project runs in different phases. Each phase has its own objectives and is a temporal or logical section of a project.

A phase summarizes a set of acitivities and results into a planning and controlling unit. Each phase ends with a mile stone, that defines the results which have to be achieved within the phase.

A mile stone defines a date. At this date a set of results should be completely and verifabely available with defined details and formally described .

The individual phases can subdivided into iterations or timeboxes to achieve an iterativ process.

Following phases are defined:

Inception Phase

The inception phase helps to get orientation and to make a first draft about the project planning.

The requirements on the new system are analysed as far as possible, to be able to give a first statement about the efforts, the project duration, necessary ressources, dates of the mile stones and that a first subdivision into separate iterations is possible.

The inception phase is not responsible to describe the requirements completely and in detail, to restrict the problem field and also not to develop solutions. The inception phase rather deals to clarify the scope of the project and supports to get a decision to start the project.

The most important result of the inception phase is the decision, whether and under what conditions the project should be run or not. With that are other decisions connected, for example the decisions about the start and final date, ressources and budget, to name the projectleader, project members, client, steering board etc.

The inception phase is run

Uncertainties of realization can be checked by explorative prototypes.

If the execution of the whole project hasn't been decided or a high degree of uncertainties exists, the preliminary study would come into focus of the inception phase, to clarify the realization, usefulness and possible alternatives.

If a clear decision for the execution of the inception phase exists, all activities concentrate on the concretization and restriction of the project contents and conditions.

The most important results of the inception phase are:
The preliminary study is the basis to decide whether the elaboration phase should run or not.

The inception phase lasts typical ca. 3 - 6 week.

Activities of Inception Phase (Overview)


Elaboration Phase

The elaboration phase deals with the analysis of basic functional and non-functional requirements on the product, the development of a stabil domain related and technical architecture and the clarification of basic risks.

The technical connections and requirements have to be determined in detail, the domain related and technical architecture have to be developed and the project planning have to be detailed. A first draft of solution concepts have to be developed.

The most important results of the elaboration phase are:

First parts of the system with a high priority have to be developed, domain related or technical risks have to be analysed, by developing relevant prototypes, which go over into suitable solutions and measurements, if necessary.

All requirements (100 % that are known should be identified (i.e. in struture of system use cases with name, trigger and results). The most important system use cases have to be described on an abstract level, for example as descriptions of essential system use cases. It has to be taken into consideration that probably not all requirements are known by this time (maybe only 80 %) and that futher requirements will be known in the construction phase.

At the end of the elaboration phase a mile stone review has to be run. At this time the project management can decide whether a risky project should go on or not.

After the elaboration phase all basic conditions exist, to devide the project into several teams, which run concurrently to scale a project.

The duration of the elaboration phase lasts usually in 1 - 3 iterations. During two iterations the phase should last two until four months.

Activities of Elaboration Phase (Overview)


Construction Phase

The construction phase deals with the incremental development of sub systems and their regular integration into a (temporary) product.

The sub systems, which are described in the sub system model, have to be implemented by parallel working development teams. Changes of requirements can be flow into the development process at that moment, by using the change management process. The construction phase has two until seven iterations (projects with normal growth). Depending on the duration of an iteration the phase goes on about two until 14 months. Within one iteration all requirements with the highest priority in analysis, design, implemention and test have to be realized. The scope of the functions and partly the quality of the product grow incrementally for, iteration to iteration. The most important results of the phase are:

The end of the construction phase leads into the finished product .

Activities of Construction Phase (Overview)


Transition Phase

The transition phase deals with the test and the acceptance of the complete application, the delivery and installation, also the training of the users.

The developed and finished product will be installed in the test environment and will be tested under realistic conditions. Arising problems and bugs will be corrected maybe updates have to be installed in the test evironment. The users can be trained to handle the new product. Under circumstances the training documents have to be defined and the trainer has also to be trained. The development documentation of the project will be finished. Staff for the maintenance have to be trained, if necessary. If the transition is combined with a difficult process the transition phase can be subdivided into several iterations. The duration of the phase is between one and six months. The transition phase is finished, if the product is installed in the productions environment and is workable.

Activities of Transition Phase (Overview)


Operation Phase

The operation phase deals with the application of the finished product.

The operation phase is the most important aim of the project. Configurations and other very small changes of the product can be done. The training and the coaching of the users will be continued. Larger changes of the requirements have to be identified and defined separately to the project and collected for a futher change request. The responsibility for the maintenance of the product can pass into other hands as the hands of the developer.

Activities of Operation Phase (Overview)


OEP - Object Engineering Process, v2.0, 06.11.2006 11:05:13, Copyright © 2003 by eG