Building the Analysis Object Model

Building the analysis object model is a combination of three sub-processes:

The ECB Pattern

The analysis model usually implements the Entity-Control-Boundary Pattern.

The Entity-Control-Boundary Pattern partitions objects into three categories (stereotypes):

<<entity>> = a domain-specific object such as a bank account or employee

<<control>> = an object that excutes user commands

<<boundary>> = an interface between an actor and a control. A control panel, for example.

Boundary objects can be described using prototypes or mock-ups.

Identifying entity objects (also called domain or business objects) is the goal of the analysis model.

Identifying the control objects comes down to specifying the behavior of the system. This is the goal of the dynamic model.