Object Process Methodology
From Wikipedia, the free encyclopedia
Object Process Methodology is an approach to designing information systems by depicting them using object models and process models. OPM was founded by Dov Dori, researcher at the Technion-Israel Institute of Technology, in 2002.
Contents |
[edit] Language design
OPM uses two types of elements: entities and links. Entities are used to express 'physical' elements in a system.
The entities used in OPM are objects, states and processes. An object is a thing existing in the system which exists for a set time. A state is a situation an object can be in. A process is a thing that transforms an object (alters the state of the object).
The links used in OPM are structural links and procedural links. A structural link forms a relation between two objects and is persistent. A procedural link is used to link an object to a process and indicates a change in the state of the object.
The model below represents the meta-model of an OPD. The simplicity of the model reflects the simplicity of the OPD itself.
The table below indicates the aggregation of the different links and gives a short explanation per link.
[edit] Cardinality
OPM knows cardinality constraining, meaning a way to indicate to what extent 2 objects can relate to each other. In OPM these constraints are called participation constraints. Constraining can be formulated like:
- 1 to 1 (Example: 1 man can marry 1 woman)
- 1 to many
- 1 to fixed number
- many to many
- fixed number to fixed number
- Optional (expressed as: ?)xx
[edit] Features
[edit] Object Process Diagram
Objects, processes and links between them are depicted by using the object process diagram.
The OPD treats complexity by using three refinement and abstraction mechanisms:
- Zooming in and out
- Folding and Unfolding
- State expression and suppression
Having only one diagram, this methodology knows no multiplicity in depicting objects and processes, which improves exchangeability between different diagrams and even different methods.
[edit] Object Process Language
Another feature of the Object Process Methodology is the Object Process Language - an OPD can be translated in sentences, telling the storyline of the diagram. The power of OPL lies in the fact that it is readable by humans but also interpretable by computers, thus making it an inter-exchangeable language.
[edit] Object-Process Case Tool
Modeling through OPM is possible with a specialized tool called Object-Process Case Tool.[1]
The application has several strong features, which are listed below.
- Syntax checking: The creator of an OPD is immediately warned when an illegal OPD construction is being created. The application refers to the issue and explains the error.
- OPL generator: Modeling an OPD automatically creates the corresponding natural text, formatted in OPL. This way, the creator can use the generated OPL additionally to check his work during the composition of the model.
- Exchangeability with UML: The application has the capability to export an OPD to many UML diagrams, namely:
[edit] See also
- Process-data diagram
- Unified Modeling Language
- Use Case Maps: UCM have some similar goals as OPM.
[edit] References
- ^ The latest version of this tool is called OPCat2 and can be downloaded from http://www.objectprocess.org.
[edit] External links
- OPM Official Web Site
- Methodology - A Holistics System Paradigm (Dov Dori reference book about OPM)
- OPCAT, Inc. was founded in 2005 in order to transfer the scientific knowledge and the powerful technology from academia to industry for the purpose of commercializing the technology and license OPCAT.
- About Use Case Maps
- Bridging the requirements/Design Gap in Dynamic Systems with Use Case Maps (UCMs)