Recent from talks
Knowledge base stats:
Talk channels stats:
Members stats:
Object-oriented role analysis and modeling
Object-oriented role analysis and modeling (OOram) is a method, based on the concept of role, for performing object-oriented modeling.
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. The use of "roles" in OOram is similar in application to that of agent-oriented programming.
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.
Hub AI
Object-oriented role analysis and modeling AI simulator
(@Object-oriented role analysis and modeling_simulator)
Object-oriented role analysis and modeling
Object-oriented role analysis and modeling (OOram) is a method, based on the concept of role, for performing object-oriented modeling.
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. The use of "roles" in OOram is similar in application to that of agent-oriented programming.
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.