oose.de Dienstleistungen für innovative Informatik GmbH

Activities of the OEP ordered in phases

Legend of activities descriptions

Activities are described as following:

An activity is attached to only one development process (i. e. requirement analysis) and can be included into one or more phases. Each activity has a name, an responsible actor, other actors which participate in the process and results.

You can describe whether the participating actor should work as an active, as a consultant or as an authorized person. You can also define the quantity of participating actors (i.e. "1" or "1...")

If necessary describe the reasons and motivations for the activity, possible triggers, preconditions and the assumption for the activity. If applicable, note counterconditions for the acitivity.

Differ between following activities

iterative activities
These activities will be done in each itaration, or at least in more than one iteration and they produce a partial result in each iteration .
unique activities
These are activities that have to be done unique and closed.
periodical activities
These activities are similar to the iterative activities. They will be done in more than one iteration but they won't be used for the incremental further development of the results, but to test or update results and informations. The reiterationscycle is independent.
accompanying activities
Accompanying acitivities do not produce results that can directly be measured or planned. For example: The activity "Identify attributes" won't have a working order as a direct result, but this task have to be done together with other acitivities. The accompanying acitivities are described to show the responsibilities and for completion.
exceptional activities
These are activities that can't be foreseen, but are connected with incidents that could be entered with a high probability. For example: A mistake happens (trigger) and it has to be clearified (activity).

Furthermore there exist activities that can be classified by their commitment:

obligatory activities (+)
have to be done, otherwise the project can get in trouble. The reason for this are mostly dependencies to other acitivities.
facultatively activities (-)
are only important within definite circumstances or they can be left out without damage.
debitively activities (o)
can be left out, but can cause additional costs and risks. You can leave them out, if the additional costs and risks are justifiable in a concret case and also if higher costs and risks justify to minimize the project duration.