Object Process Methodology: Difference between revisions

Content deleted Content added
Common nouns are not capitalised in English
Citation bot (talk | contribs)
Altered journal. | Use this bot. Report bugs. | Suggested by Headbomb | Linked from Wikipedia:WikiProject_Academic_Journals/Journals_cited_by_Wikipedia/Sandbox | #UCB_webform_linked 934/990
 
(5 intermediate revisions by 5 users not shown)
Line 18:
Object process methodology (OPM) is a conceptual modeling language and methodology for capturing knowledge and designing systems. Based on a minimal universal [[Ontology (computer science)|ontology]] of [[stateful]] [[Object (computer science)|object]]s and [[Process theory|process]]es that transform them, OPM can be used to formally specify the function, structure, and behavior of artificial and natural systems in a large variety of domains. Catering to human cognitive abilities, an OPM model represents the system under design or study bimodally in both graphics and text for improved representation, understanding, communication, and learning.
 
In OPM, an ''object'' is anything that does or does not exist. Objects are [[stateful]]—they may have states, such that at each point in time, the object is at one of its states or in transition between states. A ''process'' is a thing that transforms an object by creating or consuming it, or by changing its state.
 
OPM is bimodal; it is expressed both visually/graphically in object-process diagrams (OPD) and verbally/textually in Object-Process Language (OPL), a set of automatically generated sentences in a subset of English. A patented software package called OPCAT, for generating OPD and OPL, is freely available.<ref name="OPCAT">{{cite web |url=http://esml.iem.technion.ac.il/opcat-installation/ |title=Enterprise Systems Modeling Laboratory » OPCAT installation |website=technion.ac.il |access-date=3 May 2017}}</ref>
Line 42:
In 1997, [[Unified Modeling Language]] (UML), by the [[Object Management Group]] (OMG), became the de facto standard for software design. UML 1.1 was submitted to the OMG in August 1997 and adopted by the OMG in November 1997.
 
The first book on OPM, ''Object-Process Methodology: a Holistic Systems Paradigm'', was published in 2002,<ref name="Object-Process Methodology – A Holistic Systems Paradigm">{{cite book |last=Dori |first=Dov |author-link=Dov Dori |title=Object-Process Methodology: A Holistic Systems Paradigm |date=2002 |publisher=[[Springer-Verlag]] |___location=Berlin, Heidelberg, New York |isbn=978-3540654711 |doi=10.1007/978-3-642-56209-9 |s2cid=13600128 }}</ref> and OPM has since been applied in many domains.<ref>{{cite book |last1=Perelman |first1=Valeria |last2=Somekh |first2=Judith |last3=Dori |first3=Dov |title=Model verification framework with application to molecular biology |series=TMS-Devs '11 |date=2011 |publisher=Society for Computer Simulation International |pages=140–145 |url=http://dl.acm.org/citation.cfm?id=2048494 |ref=MolecularBiology}}</ref><ref>{{cite journal |last1=Fischer |first1=Amit |last2=Nolan |first2=Mike |last3=Friedenthal |first3=Sanford |last4=Loeffler |first4=Michael |last5=Sampson |first5=Mark |last6=Bajaj |first6=Manas |last7=VanZandt |first7=Lonnie |last8=Hovey |first8=Krista |last9=Palmer |first9=John |last10=Hart |first10=Laura |title=3.1.1 Model Lifecycle Management for MBSE |journal=INCOSEIncose International Symposium |date=2014 |volume=24 |pages=207–229 |doi=10.1002/j.2334-5837.2014.tb03145.x|s2cid=106677531 }}</ref>
 
In August 2014, the ISO adopted OPM as ISO/PAS 19450.<ref name="ISO19450" />
Line 52:
Object-Process Methodology (OPM) is a systems modeling paradigm that integrates two aspects inherent in any system: its structure and its behavior. Structure is represented via objects and structural relations among them, such as aggregation-participation (whole-part relation) and generalization-specialization ("is-a" relation). Behavior is represented by processes and how they transform objects: How they create or consume objects, or how they change the states of an object.<ref name="Model-Based"/>{{rp|2}}
 
OPM offers a way to model systems of almost any ___domain, be it artificial or natural.<ref name="Model-Based"/>{{rp|x}}<ref>See also: {{cite journal |last1=Herre |first1=Heinrich |last2=Heller |first2=Barbara |last3=Burek |first3=Patryk |last4=Hoehndorf |first4=Robert |last5=Loebe |first5=Frank |last6=Michalek |first6=Hannes |date=July 2006 |title=General formal ontology (GFO): a foundational ontology integrating objects and processes: part I: basic principles |journal=Onto-Med Report |volume=8 |page=3 |url=http://www.onto-med.de/publications/2006/herre-h-2006-a.pdf |quote=Current languages in use for conceptual modeling like the [[Unified Modeling Language]] (UML), [[entity–relationship model]]ing in the database field, or the Object-Process Methodology can be examined according to their ontological commitments. |archive-date=2016-03-28 |access-date=2017-05-04 |archive-url=https://web.archive.org/web/20160328133208/http://www.onto-med.de/publications/2006/herre-h-2006-a.pdf |url-status=dead }}</ref>
 
===Modeling===
Line 58:
 
; Object process diagram (OPD)
OPD is the one and only kind of diagram of OPM. This uniqueness of diagram kind is a major contributor to OPM's simplicity, and it is in sharp contrast to UML, which has 14 kinds of diagrams, and to SysML, which has nine such kinds.<ref name="SysMLvsOPM">{{cite book |last1=Grobshtein |first1=Yariv |last2=Perelman |first2=Valeriya |last3=Safra |first3=Eliyahu |last4=Dori |first4=Dov |title=Systems Modeling Languages: OPM Versus SysML |date=2007 |publisher=IEEE |___location=Haifa, Israel |isbn=978-1-4244-0770-5 |pages=102–109 |url=https://ieeexplore.ieee.org/document/424372 |archive-url=https://web.archive.org/web/20200218141326/https://ieeexplore.ieee.org/document/424372 |url-status=dead |archive-date=February 18, 2020 |access-date=15 November 2018 |ref=SysMLvsOPM}}</ref> An OPD graphically describes objects, processes and links among them. Links can be structural and procedural. Structural links connect objects to objects or processes to processes, expressing the static system aspect—how the system is structured. Procedural links connect objects to processes, expressing the dynamic system aspect—how the system changes over time. The entire system is represented by a set of hierarchically organized OPDs, such that the root OPD, called the systems diagram (SD), specifies the "bird's eye" view of the system, and lower-level OPDs specify the system in increasing levels of detail. All the OPDs in the system's OPD set are "aware" of each other, with each showing the system, or part of it, at some level of detail. The entire system is specified in its entirety by the union of the details (model facts) appearing in all the OPDs.
 
; Object process language (OPL)
Line 343:
 
===ISO and OPM===
In June 2008, Richard Martin approached [[Dov Dori]] after his presentation at the [[International Council on Systems Engineering|INCOSE]] International Symposium in Utrecht, the Netherlands, to inquire about the possibility of creating an International Standard for OPM.{{Citation<ref needed|datename=May":0" 2017}}/> Martin, convener of ISO TC184/SC5/WG1 for automation systems interoperability architecture and modelling, had for some time been searching for methodologies offering more than static information and process modeling.{{Citation needed|date=May 2017}} He provided Dori with a simple example to model that could demonstrate both the modelling capability of OPM and its dynamic simulation opportunity.{{Citation needed|date=May 2017}}
 
In May 2010, Dori presented a brief overview of OPM and his demonstration model at the ISO Technical Committee 184/Sub-Committee 5 (TC184/SC5) plenary meeting, which then adopted a resolution to create an OPM Study Group for the purpose of examining the potential for OPM to enhance the standards created by SC5.<ref>{{cite web |last1=Dori |first1=Dov |last2=Howes |first2=David |last3=Blekhman |first3=Alex |last4=Martin |first4=Richard |title=OPM as a Basis for Model - Based Enterprise Standards, Report of the ISO TC184/SC5 OPM Working Group to the Plenary ISO TC184/SC5Meeting, Tokyo 26, 2010 |url=http://esml.iem.technion.ac.il/wp-content/uploads/2011/05/OPM_WG_Report_to_TC184-SC5_Tokyo_March_26_2010.pdf |access-date=18 November 2018}}</ref>
 
The OPM Study Group began its work in October 2010 and issued an interim report for the 2011 SC5 Plenary.<ref name=":0">{{cite web |last1=Blekhman |first1=Alex |last2=Dori |first2=Dov |last3=Martin |first3=Richard |title=Model-Based Standards Authoring |url=http://esml.iem.technion.ac.il/wp-content/uploads/2011/07/Model-Based-Standards-Authoring-March-2011.pdf |access-date=18 November 2018}}</ref> The report included several uses of OPM to model existing SC5 standards and led to an initial motivation for the standardization of OPM with the realization that being text-based, ISO standards are prone to suffer from inconsistencies and incomplete information. This deficiency could be significantly reduced if the standards were model-based rather than text-based, and OPM offered a useful underlying modeling paradigm for this purpose.
 
A final OPM Study Group Report and a draft for a metamodel for model-based standards authoring document were delivered at the 2012 SC5 Plenary.<ref>{{cite web |last1=SC 5 PLENARY MEETING |title=Meeting Report |url=http://esml.iem.technion.ac.il/wp-content/uploads/2011/05/ISO-TC184-SC5_N1185_2012_SC5_Plenary_Meeting_Report_-_Haifa_.pdf |access-date=18 November 2018}}</ref> As the OPM Study Group effort progressed, it became obvious that OPM could also serve as a solid and comprehensive basis for model-based systems engineering (MBSE) and for modeling both natural and man-made systems.{{Citation needed|date=May 2017}}