1) Allocate behavior among boundary, entity, and
control objects. Control objects
(controllers) will turn into operations on boundary and/or entity objects, or
may become control objects, such as use case controllers.
2) Show
the detailed interactions that occur over time among the objects associated
with each use cases. Objects interact by
sending messages to each other, for each unit of behavior within a use case you
must identify the necessary messages / methods.
3) Finalize
the distribution of operations among classes.
Most class attributes can be assigned during robustness analysis. In interaction modeling you find appropriate
homes for required operations and update your class diagram.
•