Activity

[Work on own experiences/completions]

Requirement Analysis

A-230 UML-business-class-model

Develop a UML-business-class model per subsystem. Describe all attributes and operations of all identified business classes.

Activity has to be run in Elaboration Phase (Iterative Activity)
Activity has to be run in Construction Phase (Iterative Activity)


Develop a UML-business-class-model per identified subsystem.
Describe all structural relations between all important technical entities as a business class model. Find all important entities in the system use cases. List all identified business classes and develope a first rough business-class-model.

Define all class names in the glossary as a technical term. Later you can specify these terms in the design-model. Define the technical relevant attributes, associations, constraints and operations (not only get-/set-operations).

In following iterations or if a business-class-model already exists, work on it and add new knowledge by restructuring.

Analyse only the technical relevant classes, that are business classes and use only a fix quantity of them - only the most important ones. Classes that are found by abstraction, base classes, technical classes, interfaces or other ones shouldn't be analysed in a business-class-model.

If reference models exist, use them to find information or solution concepts to structure the application domain.

When you describe a business class model, keep your eyes on the associations (incl. the special forms aggregation and composition). Note names of roles and relationships, multiplicities and constraints if they are known. Model only inheritance relationships if they are necessary. It is not important to search after generalization/specialization and detailed inheritance relationships.

Try to identify attributes and operations and describe them. Use the system use cases to find candidates.


Reasons:

Trigger:

Precondition:

A subsystem-model and a final business-class-model already exists. The first requirement workshop was successful.

Documents:

E-115 UML-Business-Class-Model
E-6 Essence of Use Cases

Countercondition:

Results:

E-115 UML-Business-Class-Model
E-58 Sub System

Special tools:


Responsible person:

.System Analyst

Involved persons:

.Domain related Architect
.System Analyst

Postcondition:

A-232 Develop a design class modell and an evaluated sub system model
A-251 Consolidate the UML-business-class-models

OEP - Object Engineering Process, v3.0, 06.11.2006 11:07:51, Copyright © 2006 by oose Innovative Informatik eG