Difference between revisions of "Modeling Standards"

From SEBoK
Jump to navigation Jump to search
(Byline)
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
Different types of [[Model (glossary) | models]] are needed to support the analysis, specification, [[Design (glossary) | design]], and [[Verification (glossary) | verification]] of [[System (glossary) | systems]]. The evolution of modeling standards enables the broad adoption of [[Model-Based Systems Engineering (MBSE) (glossary) | Model-Based Systems Engineering]] (MBSE).  
+
----
 +
'''''Lead Author:''''' ''Sanford Friedenthal'', '''''Contributing Authors:''''' ''Dov Dori, Yaniv Mordecai''
 +
----
 +
Different types of {{Term|Model (glossary)|models}} are needed to support the analysis, specification, {{Term|Design (glossary)|design}}, and {{Term|Verification (glossary)|verification}} of {{Term|System (glossary)|systems}}. The evolution of modeling standards enables the broad adoption of {{Term|Model-Based Systems Engineering (MBSE) (glossary)|Model-Based Systems Engineering}} (MBSE).  
  
 
==Motivation for Modeling Standards==
 
==Motivation for Modeling Standards==
  
−
Modeling standards play an important role in defining agreed-upon system modeling [[Concept (glossary) | concepts]] that can be represented for a particular [[Domain (glossary) | domain]] of interest and enable the [[Integration (glossary) | integration]] of different types of models across domains of interest. Modeling standards are extremely important to support MBSE, which aims to integrate various system aspects across various disciplines, [[Product (glossary) | products]], and technologies.  
+
Modeling standards play an important role in defining agreed-upon system modeling {{Term|Concept (glossary)|concepts}} that can be represented for a particular {{Term|Domain (glossary)|domain}} of interest and enable the {{Term|Integration (glossary)|integration}} of different types of models across domains of interest. Modeling standards are extremely important to support MBSE, which aims to integrate various system aspects across various disciplines, {{Term|Product (glossary)|products}}, and technologies.  
  
−
Standards for system modeling languages can enable cross-discipline, cross-project, and cross-[[Organization (glossary) | organization]] communication. This communication offers the potential to reduce the training [[Requirement (glossary) | requirements]] for practitioners who only need to learn about a particular system and enables the reuse of system artifacts. Standard modeling languages also provide a common foundation for advancing the practice of [[Systems Engineering (glossary) | systems engineering]], as do other [[Systems Engineering Standards | systems engineering standards]].
+
Standards for system modeling languages can enable cross-discipline, cross-project, and cross-{{Term|Organization (glossary)|organization}} communication. This communication offers the potential to reduce the training {{Term|Requirement (glossary)|requirements}} for practitioners who only need to learn about a particular system and enables the reuse of system artifacts. Standard modeling languages also provide a common foundation for advancing the practice of {{Term|Systems Engineering (glossary)|systems engineering}}, as do other [[Systems Engineering Standards | systems engineering standards]].
  
 
==Types of Modeling Standards==
 
==Types of Modeling Standards==
 
   
 
   
−
Many different standards apply to systems modeling. Modeling standards include standards for modeling languages, data exchange between models, and the [[Model Transformation (glossary) | transformation]] of one model to another to achieve [[Semantic Interoperability (glossary) | semantic interoperability]]. Each type of model can be used to represent different aspects of a system, such as representing the set of system [[Component (glossary) | components]] and their interconnections and [[Interface (glossary) | interfaces]], or to represent a system to support performance analysis or [[Reliability (glossary) | reliability]] analysis.  
+
Many different standards apply to systems modeling. Modeling standards include standards for modeling languages, data exchange between models, and the {{Term|Model Transformation (glossary)|transformation}} of one model to another to achieve {{Term|Semantic Interoperability (glossary)|semantic interoperability}}. Each type of model can be used to represent different aspects of a system, such as representing the set of system {{Term|Component (glossary)|components}} and their interconnections and {{Term|Interface (glossary)|interfaces}}, or to represent a system to support performance analysis or {{Term|Reliability (glossary)|reliability}} analysis.  
  
 
The following is a partial list of representative modeling standards, which also includes the common acronym, when applicable, and a reference as to where additional information can be found on the topic.
 
The following is a partial list of representative modeling standards, which also includes the common acronym, when applicable, and a reference as to where additional information can be found on the topic.
Line 19: Line 22:
 
*Object-Process Methodology (OPM) [[http://www.amazon.com/gp/product/3540654712/sr=8-1/qid=1146053424/ref=sr_1_1/104-2484506-3323967?_encoding=UTF8]]  [[http://esml.iem.technion.ac.il/?page_id=874]] (Dori 2002; ISO 19450 PAS - Publicly Available Specification in progress)
 
*Object-Process Methodology (OPM) [[http://www.amazon.com/gp/product/3540654712/sr=8-1/qid=1146053424/ref=sr_1_1/104-2484506-3323967?_encoding=UTF8]]  [[http://esml.iem.technion.ac.il/?page_id=874]] (Dori 2002; ISO 19450 PAS - Publicly Available Specification in progress)
 
*Systems Modeling Language (SysML)(OMG 2010a)
 
*Systems Modeling Language (SysML)(OMG 2010a)
−
*Unified Profile for United States Department of Defense [[Architecture (glossary) | Architecture]] Framework (DoDAF) and United Kingdom Ministry of Defense Architecture Framework (MODAF) (OMG 2011e)
+
*Unified Profile for United States Department of Defense {{Term|Architecture (glossary)|Architecture}} Framework (DoDAF) and United Kingdom Ministry of Defense Architecture Framework (MODAF) (OMG 2011e)
 
*Web ontology language (OWL) (W3C 2004b)
 
*Web ontology language (OWL) (W3C 2004b)
  
−
'''Analytical Models and Simulations''' -  These standards apply to analytical models and [[Simulation (glossary) | simulations]]:
+
'''Analytical Models and Simulations''' -  These standards apply to analytical models and {{Term|Simulation (glossary)|simulations}}:
 
*Distributed Interactive Simulation (DIS) (IEEE 1998)  
 
*Distributed Interactive Simulation (DIS) (IEEE 1998)  
 
*High-Level Architecture (HLA) (IEEE 2010)
 
*High-Level Architecture (HLA) (IEEE 2010)
Line 42: Line 45:
  
 
===General Modeling Standards===
 
===General Modeling Standards===
−
These standards provide general [[Framework (glossary) | frameworks]] for modeling:
+
These standards provide general {{Term|Framework (glossary)|frameworks}} for modeling:
 
*Model-driven architecture (MDA®) (OMG 2003b)
 
*Model-driven architecture (MDA®) (OMG 2003b)
−
*IEEE 1471-2000 - Recommended Practice for Architectural Description of [[Software (glossary) | Software]]-Intensive Systems (ANSI/IEEE 2000) (ISO/IEC 2007)
+
*IEEE 1471-2000 - Recommended Practice for Architectural Description of {{Term|Software (glossary)|Software}}-Intensive Systems (ANSI/IEEE 2000) (ISO/IEC 2007)
  
 
===Other Domain-Specific Modeling Standards===
 
===Other Domain-Specific Modeling Standards===
Line 139: Line 142:
  
 
----
 
----
−
<center>[[Integrating Supporting Aspects into System Models|< Previous Article]] | [[Representing Systems with Models|Parent Article]] | [[Systems Approach Applied to Engineered Systems|Next Article >]]</center>
+
<center>[[Integrating Supporting Aspects into System Models|< Previous Article]] | [[Representing Systems with Models|Parent Article]] | [[Systems Engineering and Management|Next Article (Part 3) >]]</center>
  
−
<center>'''SEBoK v. 1.9.1, released 16 October 2018'''</center>
+
<center>'''SEBoK v. 2.1, released 31 October 2019'''</center>
  
 
[[Category:Part 2]][[Category:Topic]]
 
[[Category:Part 2]][[Category:Topic]]
 
[[Category:Representing Systems with Models]]
 
[[Category:Representing Systems with Models]]

Revision as of 00:56, 26 October 2019

Lead Author: Sanford Friedenthal, Contributing Authors: Dov Dori, Yaniv Mordecai

Different types of modelsmodels are needed to support the analysis, specification, designdesign, and verificationverification of systemssystems. The evolution of modeling standards enables the broad adoption of Model-Based Systems EngineeringModel-Based Systems Engineering (MBSE).

Motivation for Modeling Standards

Modeling standards play an important role in defining agreed-upon system modeling conceptsconcepts that can be represented for a particular domaindomain of interest and enable the integrationintegration of different types of models across domains of interest. Modeling standards are extremely important to support MBSE, which aims to integrate various system aspects across various disciplines, productsproducts, and technologies.

Standards for system modeling languages can enable cross-discipline, cross-project, and cross-organizationorganization communication. This communication offers the potential to reduce the training requirementsrequirements for practitioners who only need to learn about a particular system and enables the reuse of system artifacts. Standard modeling languages also provide a common foundation for advancing the practice of systems engineeringsystems engineering, as do other systems engineering standards.

Types of Modeling Standards

Many different standards apply to systems modeling. Modeling standards include standards for modeling languages, data exchange between models, and the transformationtransformation of one model to another to achieve semantic interoperabilitysemantic interoperability. Each type of model can be used to represent different aspects of a system, such as representing the set of system componentscomponents and their interconnections and interfacesinterfaces, or to represent a system to support performance analysis or reliabilityreliability analysis.

The following is a partial list of representative modeling standards, which also includes the common acronym, when applicable, and a reference as to where additional information can be found on the topic.

Modeling Languages for Systems

Descriptive Models - These standards apply to general descriptive modeling of systems:

  • Functional Flow Block Diagram (FFBD) (Oliver, Kelliher, and Keegan 1997)
  • Integration Definition for Functional Modeling (IDEF0) (NIST 1993)
  • Object-Process Methodology (OPM) [[1]] [[2]] (Dori 2002; ISO 19450 PAS - Publicly Available Specification in progress)
  • Systems Modeling Language (SysML)(OMG 2010a)
  • Unified Profile for United States Department of Defense ArchitectureArchitecture Framework (DoDAF) and United Kingdom Ministry of Defense Architecture Framework (MODAF) (OMG 2011e)
  • Web ontology language (OWL) (W3C 2004b)

Analytical Models and Simulations - These standards apply to analytical models and simulationssimulations:

  • Distributed Interactive Simulation (DIS) (IEEE 1998)
  • High-Level Architecture (HLA) (IEEE 2010)
  • Modelica (Modelica Association 2010)
  • Semantics of a Foundational Subset for Executable Unified Modeling Language (UML) Models (FUML) (OMG 2011d)

Data Exchange Standards

These standards enable the exchange of information between models:

  • Application Protocol for Systems Engineering Data Exchange (ISO 10303-233) (AP-233) (ISO 2005)
  • Requirements Interchange Format (ReqIF) (OMG 2011c)
  • Extensible Mark-Up Language -(XML) Metadata Interchange (XMI) (OMG 2003a)
  • Resource Description Framework (RDF) (W3C 2004a)

Model Transformations

These standards apply to transforming one model to another to support semantic interoperability:

  • Query View Transformations (QVT) (OMG 2011b)
  • Systems Modeling Language (SysML)-Modelica Transformation (OMG 2010c)
  • OPM-to-SysML Transformation (Grobshtein and Dori 2011)

General Modeling Standards

These standards provide general frameworksframeworks for modeling:

  • Model-driven architecture (MDA®) (OMG 2003b)
  • IEEE 1471-2000 - Recommended Practice for Architectural Description of SoftwareSoftware-Intensive Systems (ANSI/IEEE 2000) (ISO/IEC 2007)

Other Domain-Specific Modeling Standards

Software Design Models

These standards apply to modeling application software and/or embedded software design:

  • Architecture Analysis and Design Language (AADL) (SAE 2009)
  • Modeling and Analysis for Real-Time and Embedded Systems (MARTE) (OMG 2009)
  • Unified Modeling Language (UML) (OMG 2010b)

Hardware Design Models

These standards apply to modeling hardware design:

  • Very-High-Speed Integrated Circuit (VHSIC) Hardware Description Language (VHDL) (IEEE 2008)

Business Process Models

These standards apply to modeling business processes:

  • Business Process Modeling Notation (BPMN) (OMG 2011a)

References

Works Cited

ANSI/IEEE. 2000. Recommended Practice for Architectural Description for Software-Intensive Systems. New York, NY: American National Standards Institute (ANSI)/Institute of Electrical and Electronics Engineers (IEEE), ANSI/IEEE 1471-2000.

Grobshtein, Y. and D. Dori. 2011. "Generating SysML Views from an OPM Model: Design and Evaluation." Systems Engineering, 14 (3), Sept. 2011.

IEEE. 1998. Distributed Interactive Simulation (DIS). Washington, DC: Institute for Electrical and Electronic Engineers. IEEE 1278.1-1995. Accessed December 4 2014 at IEEE http://standards.ieee.org/develop/project/1278.2.html.

IEEE. 2008. VHSIC hardware description language (VHDL). Washington, DC: Institute of Electrical and Electronics Engineers. IEEE Standard 1076-2008. Accessed December 4 2014 at IEEE http://standards.ieee.org/findstds/standard/1076-2008.html.

IEEE. 2010. Standard for High Level Architecture. Washington, DC: Institute for Electrical and Electronic Engineers. IEEE Standard 1516. Accessed December 4 2014 at IEEE http://standards.ieee.org/develop/intl/intlstds.html

ISO. 2005. Application Protocol for Systems Engineering Data Exchange. Geneva, Switzerland: International Organization for Standardization. ISO 10303-233. Accessed December 4 2014 at ISO http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=55257.

ISO/IEC/IEEE. 2011. Systems and Software Engineering — Architecture Description. Geneva, Switzerland: International Organization for Standardization/International Electrotechnical Commission/Institute of Electrical and Electronics Engineers. December 1, 2011. ISO/IEC/IEEE 42010:2011. Accessed December 4 2014 at ISO http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?csnumber=50508.

Modelica Association. 2010. Modelica® - A Unified Object-Oriented Language for Physical Systems Modeling, Language Specification, Version 3.2. Modelica Association. Accessed December 4 2014 at Modelica https://www.modelica.org/documents/ModelicaSpec32.pdf.

NIST. 1993. Integration Definition for Functional Modeling (IDEF0). Gaithersburg, MD: National Institute for Standards and Technologies. Accessed December 4 2014 at IDEF http://www.idef.com/IDEF0.htm.

Oliver, D., T. Kelliher, and J. Keegan. 1997. Engineering Complex Systems with Models and Objects. New York, NY, USA: McGraw Hill.

OMG 2003a. XML Metadata Interchange (XMI), Version 1.1. Needham, MA, USA: Object Management Group. Accessed December 4 2014 at OMG http://www.omg.org/spec/XML/.

OMG. 2003b. Model driven architecture (MDA®), Version 1.0.1. Needham, MA, USA: Object Management Group. Accessed December 4 2014 at OMG http://www.omg.org/mda.

OMG. 2009. Modeling and Analysis for Real-Time and Embedded Systems (MARTE), Version 1.0. Object Management Group. Accessed December 4 2014 at OMG http://www.omg.org/spec/MARTE/1.0/.

OMG. 2010a. OMG Systems Modeling Language (SysML), Version 1.2. Needham, MA, USA: Object Management Group. Accessed December 4 2014 at SysML forum http://www.sysml.org/docs/specs/OMGSysML-v1.2-10-06-02.pdf.

OMG. 2010b. Unified Modeling Language™ (UML), Version 2.. Needham, MA, USA: Object Management Group. Accessed December 4 2014 at OMG http://www.omg.org/spec/UML/.

OMG. 2010c. SysML-Modelica Transformation Specification, Beta Version. Needham, MA, USA: Object Management Group. Accessed December 4 2014 at OMG http://www.omg.org/spec/SyM/.

OMG. 2011a. Business Process Modeling Notation (BPMN), Version 2.0. Needham, MA, USA: Object Management Group. Accessed December 4 2014 at OMG http://www.omg.org/spec/BPMN/2.0/

OMG. 2011b. Query View Transformations (QVT), Version 1.1. Needham, MA, USA: Object Management Group. Accessed December 4 2014 at OMG http://www.omg.org/spec/QVT/1.1/.

OMG. 2011c. Requirements Interchange Format (ReqIF), Version 1.0.1. Needham, MA, USA: Object Management Group. Accessed December 4 2014 at OMG http://www.omg.org/spec/ReqIF/.

OMG. 2011d. Semantics of a Foundational Subset for Executable UML Models (FUML), Version 1.0. Needham, MA, USA: Object Management Group. Accessed December 4 2014 at OMG http://www.omg.org/spec/FUML/1.0/.

OMG. 2011e. Unified Profile for DoDAF and MODAF (UPDM), Version 1.1. Needham, MA, USA: Object Management Group. Accessed December 4 2014 at OMG http://www.omg.org/spec/UPDM/.

SAE. 2009. Architecture Analysis & Design Language (AADL). Warrendale, PA, USA: SAE International. Accessed December 4 2014 at Society of Automotive Engineers http://standards.sae.org/as5506a/.

W3C. 2004a. Resource Description Framework (RDF), Version 1.0. World Wide Web Consortium. Accessed December 4 2014 at World Wide Web Consortium http://www.w3.org/RDF/.

W3C. 2004b. Web ontology language. (OWL). World Wide Web Consortium. Accessed December 4 2014 at World Wide Web Consortium http://www.w3.org/2004/OWL.

Primary References

Dori, D. 2002. Object-Process Methodology – A Holistic Systems Paradigm. Berlin, Germany: Heidelberg; New York, NY, USA: Springer Verlag.

Friedenthal, S., A. Moore, R. Steiner, and M. Kaufman. 2012. A Practical Guide to SysML: The Systems Modeling Language, 2nd Edition. Needham, MA, USA: OMG Press.

Additional References

Fritzon, P. 2004. Object-oriented modeling and simulation with Modelica 2.1. New York, NY, USA: Wiley Interscience and IEEE Press.

Bibliowicz, A. and D. Dori. A Graph Grammar-Based Formal Validation of Object-Process Diagrams. Software and Systems Modeling, 11, (2) pp. 287-302, 2012.

Blekhman, A. and D. Dori. "Model-Based Requirements Authoring." INCOSE 2011 – the 6th International conference on System Engineering. March, 2011.

Dori, D., R. Feldman, and A. Sturm. From conceptual models to schemata: An object-process-based data warehouse construction method." Information Systems. 33: 567–593, 2008.

Osorio, C.A., D. Dori, and J. Sussman. COIM: An Object-Process Based Method for Analyzing Architectures of Complex, Interconnected, Large-Scale Socio-Technical Systems. Systems Engineering 14(3), 2011.

Paredis, C.J.J., Y. Bernard, R.M. Burkhart, H-P. de Koning, S. Friedenthal, P. Fritzson, N.F. Rouquette, W. Schamai. 2010. "An overview of the SysML-modelica transformation specification". Proceedings of the 20th Annual International Council on Systems Engineering (INCOSE) International Symposium, 12-15 July 2010, Chicago, IL.

Reinhartz-Berger, I. and D. Dori. "OPM vs. UML—Experimenting with Comprehension and Construction of Web Application Models." Empirical Software Engineering, 10: 57–79, 2005.

Weilkiens, T. 2008. Systems Engineering with SysML/UML. Needham, MA, USA: OMG Press.

< Previous Article | Parent Article | Next Article (Part 3) >
SEBoK v. 2.1, released 31 October 2019
Retrieved from "https://sandbox.sebokwiki.org/index.php?title=Modeling_Standards&oldid=57122"