Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Object-modeling technique
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Short description|Object modeling approach for software modeling}} [[Image:OMT object diagram.png|thumb|240px|OMT object diagram]] [[Image:OMT state diagram.png|thumb|360px|OMT [[state diagram]]]] The '''object-modeling technique''' ('''OMT''') is an [[object modeling language|object modeling]] approach for [[Computer software|software]] modeling and designing. It was developed around 1991 by [[James Rumbaugh|Rumbaugh]], Blaha, Premerlani, Eddy and Lorensen as a method to develop [[Object-oriented analysis and design|object-oriented systems]] and to support [[object-oriented programming]]. OMT describes object model or static structure of the system. OMT was developed as an approach to [[software development]]. The purposes of modeling according to Rumbaugh are:<ref>Rumbaugh et al. (1991:15)</ref><ref name="Tot97">Terje Totland (1997). [http://www.idi.ntnu.no/grupper/su/publ/html/totland/ch0527.htm 5.2.7 Object Modeling Technique (OMT)] Thesis, Norwegian University of Science and Technology (NTNU), Trondheim.</ref> * testing physical entities before building them (simulation), * communication with customers, * visualization (alternative presentation of information), and * reduction of complexity. OMT has proposed three main types of models: * ''Object model'': The object model represents the static and most stable phenomena in the modeled domain.<ref>(Rumbaugh et al.,1991:21)</ref> Main concepts are classes and associations with attributes and operations. Aggregation and generalization (with multiple inheritance) are predefined relationships.<ref name="Tot97"/> * ''Dynamic model'': The dynamic model represents a state/transition view on the model. Main concepts are states, transitions between states, and events to trigger transitions. Actions can be modeled as occurring within states. Generalization and aggregation (concurrency) are predefined relationships.<ref name="Tot97"/> * ''Functional model'': The functional model handles the process perspective of the model, corresponding roughly to data flow diagrams. Main concepts are process, data store, data flow, and actors.<ref name="Tot97"/> OMT is a predecessor of the [[Unified Modeling Language]] (UML). Many OMT modeling elements are common to UML. Functional Model in OMT: In brief, a functional model in OMT defines the function of the whole internal processes in a model with the help of "Data Flow Diagrams (DFDs)". It details how processes are performed independently.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)