Object Oriented Role Analysis Method
Encyclopedia
The Object Oriented Role Analysis and Modeling (OOram) is a method, based on the concept of role, for performing object-oriented modeling. OOram is a precursor for the Unified Modeling Language
(UML).
Originally (1989) coined Object Oriented Role Analysis, Synthesis and Structuring (OORASS), the method focuses on describing patterns of interaction without connecting the interaction to particular objects/instances. OOram was originally developed by Trygve Reenskaug
(1996), a professor at the University of Oslo and the founder of the Norwegian IT company Taskon
.
Enterprise models created according to OOram may have a number of views, with each view presenting certain aspects of a model. The following ten views are proposed:
OOram suggests a varied mix of formal and informal notations and languages for representing and communicating models. Which view to use depends upon the needs in a particular situation.
Unified Modeling Language
Unified Modeling Language is a standardized general-purpose modeling language in the field of object-oriented software engineering. The standard is managed, and was created, by the Object Management Group...
(UML).
Originally (1989) coined Object Oriented Role Analysis, Synthesis and Structuring (OORASS), the method focuses on describing patterns of interaction without connecting the interaction to particular objects/instances. OOram was originally developed by Trygve Reenskaug
Trygve Reenskaug
Trygve Mikkjel Heyerdahl Reenskaug is a Norwegian computer scientist and professor emeritus of the University of Oslo. He formulated the model-view-controller pattern for Graphic User Interface software design in 1979 while visiting the Xerox Palo Alto Research Center...
(1996), a professor at the University of Oslo and the founder of the Norwegian IT company Taskon
Kantega
Kantega is a Norwegian software corporation founded in 2003 with headquarters in Oslo. Kantega primarily develops bespoke software based on Java and lightweight application frameworks, identity management and digital signature solutions based on PKI and Web Services technology.Kantega is a sponsor...
.
Enterprise models created according to OOram may have a number of views, with each view presenting certain aspects of a model. The following ten views are proposed:
- Area of concern view: Textual description of a phenomenon represented in the role model.
- Stimulus-response view: Describes how environment roles may trigger activities in the organization (stimulus), together with the effect (response).
- Role list view: List describing all roles of a role model together with attributes and textual explanation.
- Semantic view: Describes meaning of roles and relationships between roles.
- Collaboration view: Describes patterns of roles and message paths.
- Interface view: Describes all messages that can be sent along a message path.
- Scenario view: Provides a sample sequence of messages flowing between roles (a concrete example).
- Process view: Describes data flow between roles and associated activities performed by the roles.
- State diagram view: For each role, the legal states can be described together with messages that triggers transitions.
- Method specification view: Describes what messages to send for each method belonging to a role. May also specify procedures to perform.
OOram suggests a varied mix of formal and informal notations and languages for representing and communicating models. Which view to use depends upon the needs in a particular situation.
Further reading
- Rebecca J. Wirfs-Brock and Ralph E. Johnson (1990). Surveying Current Research in Object-Oriented Design. Communications of the ACM, vol. 33, no. 9 (September 1990), pp. 105–124. OORASS on pp. 113–116.