Frenemies: OPM and SysML Together in an MBSE Model

Abstract

AbstractA Frenemy is “a person with whom one is friendly despite a fundamental dislike or rivalry.” (OED, 2018). The Systems Modeling Language (SysML) and the Object Process Methodology (OPM) are two such frenemies. OPM and SysML are different means of achieving Model‐Based Systems Engineering (MBSE), each with their own benefits, issues, supporters and detractors. The National Defense Industry Association (NDIA) defines MBSE as “an approach to engineering that uses models as an integral part of the technical baseline that includes the requirements, analysis, design, implementation, and verification of a capability, system, and/or product throughout the acquisition life cycle.” (NDIA, 2011) SysML is based on the Unified Modeling Language (UML) and includes diagrams that can be used to specify system requirements, behavior, structure and parametric relationships. SysML provides a means of defining high‐level abstract systems down to detailed physical systems. OPM is a “conceptual modeling language and methodology for capturing knowledge and designing systems. Based on a minimal universal ontology of stateful objects and processes 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.” (ISO, 2015) OPM is used in some systems engineering graduate courses. Students graduating from these institutions are struggling to integrate the differing styles, philosophies, concepts and processes of SysML and OPM. A literature search reveals some papers that contrast SysML and OPM, but none that describe how the two can work together. This paper discusses a synergy of SysML and OPM in a SysML tool rather than promoting one language over another.