Content deleted Content added
Jvanreijsen (talk | contribs) m lay-out |
Jvanreijsen (talk | contribs) m temp save |
||
Line 1:
==Overview==
This entry elaborates on the modeling language Object Process Methodology.
Object Process Methodology is an approach to blueprint (commonly) [[information system]]s by depicting them using object models and process models.▼
Little will be spent on the history of the language, continued by explanation of its theory and use.
==Definitions==
▲'''Object Process Methodology''' is an approach to blueprint (commonly) [[information system]]s by depicting them using object models and process models.
An '''object model''' describes the integrity of an object within the analyzed system.
A '''process model''' describes the flow of processes within a specific part of the analyzed system.
==History==
OPM was founded by Dov Dori, researcher at the Technion-Israel Institute of Technology.
Dori published his book "Object-Process Methodology - A Holistics System Paradigm" in 2002, published by Springer.
The common language UML for modeling mainly software systems was in need of a new and simplified approach to model not only software systems, but information systems as well. This is why OPM was created.
OPM intends to answer to the growing complexity in software systems and focusses on lifecycle support as well.
==Elements==
OPM has uses two types of elements: '''entities''' and '''links'''.
Entities are used to express 'physical' elements in a system.
==Usage==
Objects, processes and links between them are depicted by using the '''object process diagram'''. This enables a powerful overview of the analyzed system, as the diagram features folding of components and zooming on the map of objects and processes.
Having only one diagram, this methodology knows no multiplicity in depicting objects and processes, which improves exchangeability between different diagrams and even different methods.
| |||