Object Process Methodology: Difference between revisions

Revision as of 09:00, 16 September 2006

Revision as of 16:44, 27 September 2006

Line 1:

{{wikify-date|May 2006}}

'''Object Process Methodology''' is an approach to blueprint (commonly)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]].

==Language design==

The common language [[Unified Modeling 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.

OPM was founded by [[Dov Dori]], researcher at the Technion-Israel Institute of Technology, in [[2002]].

==Object Process Methodology Meta-Model==

OPM uses two types of elements: '''entities''' and '''links'''. Entities are used to express 'physical' elements in a system.

Line 21 ⟶ 18:

The model below represents the meta-model of an OPD.

The simplicity of the model reflects the simplicity of the OPD itself.

<!-- Unsourced image removed: [[Image:OPM-Metamodel.gif]] -->

The table below indicates the aggregation of the different links and gives a short explanation per link.

<!-- Unsourced image removed: [[Image:OPM-Links.gif]] -->

==Cardinality==

Line 48 ⟶ 42:

==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.

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.

==Object-Process Case Tool==

Line 66 ⟶ 58:

** Deployment Diagram

** Activity Diagram

==Example: Marriage==

The example below demonstrates the modeling of the concept marriage in an OPD.

<!-- Unsourced image removed: [[Image:OPD-Marriage.gif]] -->

This example indicates how the states of the objects 'man' and 'woman' can transform from being 'single' to being 'married' by the process called 'marrying'.

* The result/consumption link takes the status 'single' of the objects 'man' and 'woman' through the process 'marrying' to the state 'married'.

* The process forms the object 'couple', which consists of the objects 'man' and 'woman'.

* The object 'couple' has the object 'wedding date' as a characterization through an exhibition/characterization link.

* John is a 'man' and Jane is a 'woman', due to the generalization/specialization link.

As a result of this example, the object-process case tool created the OPL data that corresponds with the OPD. The OPL is given below.

<!-- Unsourced image removed: [[Image:OPL-Marriage.gif]] -->

The example explains itself. The colors of the text correspond with the elements in the OPD example.

==See Also==