MY BOOK REVIEW

OBJECT ORIENTED ANALYSIS and DESIGN

Book

Edward Yourdon and Carl Argila

Author

QA 76.64 Y68 1996

Reference no.

CHAPTER 9

Marriage must be a relation either of sympathy or of conquest.

                                                                                                                        - George Eliot

                                                                                                      (nee Marian Evans Cross)

The concept of a role has been applied to distributed systems management, agents, and robots. In addition, role theory has been used to analyze collaboration and coordination in various contexts. However, it has been difficult to realize these role representations in automated systems, due to the lack of adequate formalisms and the corresponding abstractions in software. Role models are relatively new concepts in object-oriented software engineering that emphasize patterns of interaction and therefore rectify this situation for software analysis and design. This article provides examples of agent role models and explains how role modeling can be used to facilitate agent system analysis and design. The author also discusses role model implementations based on two approaches: the Role Object pattern and aspect-oriented programming (AOP).

Although there are numerous books on object-oriented programming, few go beyond a presentation of terminology, notation and the structure of a unique model. Written by a co-developer of one of the most popular OOA/OOD methods, this exceptionally practical and authoritative casebook shows how object-oriented analysis and design are actually practiced in developing real systems-i.e., shows the insight rather than the technique that was applied at each step in a solution-false starts and all. Presents two very realistic case studies-one with a predominant reactive view and one with a predominant data view-and shows how the principles of object-oriented analysis and design are applied to them.

Instances connections are part of the Attribute Layer together with attributes.

Instances connection are show only if they are meaningful within the application domain and capture an application domain constraint or business rule.

Redundant instance connections are usually not shown.

Many-to-many instance connections are permitted in the OOA model.

The existence of a many-to-many instance connection may suggest the existence of a new associative object. Such an object, however, must be meaningful within the application domain.