Differences

This shows you the differences between two versions of the page.

--- mbse:pbse [2015/07/29 17:24]
jcwatson created
+++ mbse:pbse [2015/07/30 13:08] (current)
jcwatson
@@ Line 1: / Line 1: @@
-==== Pattern-Based Systems Engineering (PBSE), Based On S*MBSE Models ====
+{{:mbse:methodology:pbse_title3.jpg|}}
 === Overview ===
-== Pattern-Based Systems Engineering (PBSE) Methodology is a form of Model-Based Systems Engineering (MBSE) based on use of the S*Metamodel. In this approach, re-usable, configurable S*Models (which are MBSE models conforming to the S*Metamodel, in any modeling language or toolset) are created, then used and re-used across a range of different system configurations or family members, and improved over time as the point of distillation of learning. These re-usable, configurable S*Models are called S*Patterns to emphasize their recurring use, and are model-based substantial extensions of earlier, pre-MBSE engineering patterns. ==
+Pattern-Based Systems Engineering (PBSE) Methodology is a form of Model-Based Systems Engineering (MBSE) based on use of the S*Metamodel. In this approach, re-usable, configurable S*Models (which are MBSE models conforming to the S*Metamodel, in any modeling language or toolset) are created, then used and re-used across a range of different system configurations or family members, and improved over time as the point of distillation of learning. These re-usable, configurable S*Models are called S*Patterns to emphasize their recurring use, and are model-based substantial extensions of earlier, pre-MBSE engineering patterns.
-== S*Models and S*Patterns contain Features, Interactions, Roles, States, Design Components, Interfaces, Requirements, Attributes thereof, couplings between them, and more. S*Patterns are constructed to cover a system configuration space bigger than single system model instances, and are sufficiently parameterized and abstracted to be configurable to more specific S*Models, and thereby reusable. S*Patterns are models of platforms, reference architectures, product lines, or system families: ==
+S*Models and S*Patterns contain Features, Interactions, Roles, States, Design Components, Interfaces, Requirements, Attributes thereof, couplings between them, and more. S*Patterns are constructed to cover a system configuration space bigger than single system model instances, and are sufficiently parameterized and abstracted to be configurable to more specific S*Models, and thereby reusable. S*Patterns are models of platforms, reference architectures, product lines, or system families:
-== {{:mbse:s_patterns_fg1.jpg|}} ==
+{{:mbse:methodology:s_patterns_fg1.jpg|}}
+S*Models and S*Patterns may be expressed in any system modeling language (e.g., SysML, IDEF, etc.) and managed in any COTS system modeling tool or repository, by an S*Metamodel mapping or profile.
-== S*Models and S*Patterns may be expressed in any system modeling language (e.g., SysML, IDEF, etc.) and managed in any COTS system modeling tool or repository, by an S*Metamodel mapping or profile.
+PBSE builds on long historical work in patterns, now improved as MBSE models (many historical engineering patterns were not explicit MBSE models), expansion of pattern scope to whole system families, platforms, and domains (as opposed to smaller-scale localized patterns). An explicit foundation based on a stronger MBSE metamodel expresses systemic phenomena, critical to engineering applications needing a clearer connection to scientific understanding of systems phenomena.
-PBSE builds on long historical work in patterns, now improved as MBSE models (many historical engineering patterns were not explicit MBSE models), expansion of pattern scope to whole system families, platforms, and domains (as opposed to smaller-scale localized patterns). An explicit foundation based on a stronger MBSE metamodel expresses systemic phenomena, critical to engineering applications needing a clearer connection to scientific understanding of systems phenomena. ==
+{{:mbse:methodology:s_patterns_fg2.jpg|}}
+//Organizational/Learning Gains://
+  * Reduced recurring cost of modeling, along with shift of emphasis, from “learn how to model” (an abstract skill) to “learn the model (pattern)” in use by an enterprise, a more concrete knowledge of the enterprise’s products, simplifying the introduction of MBSE methods.
+  * A structured means of representing and accessing learning across organizational boundaries and different languages—technical, marketing, customer, production, life cycle support.
+  * Strong expression of fitness landscapes as the basis for selection, trades, improvements, decisions, innovations, configuration, and understanding of risk and failure.
-=== Tool Support ===
-  * INCOSE OOSEM was created as tool- and vendor-neutral, model-based methodology.  A dedicated process framework tool for OOSEM does not exist; however, there has been discussion (J.D. Baker, private communication) that an [[http://www.eclipse.org/epf/|Eclipse Process Framework (EPF)]] version of OOSEM exists.
+//Foundational Engineering Improvements://
+  * Explication of the System Phenomenon as a real world-based science and math foundation for systems engineering, amenable to systems science, connected to historical math/science models of engineering disciplines, encouraging discovery and expression of higher-level systemic phenomena.
-  * Tool support for OOSEM can be provided by COTS-based OMG SysML tools and associated requirements management tools. Other tools required to support the full system lifecycle should be integrated with the SysML and requirements management tools, such as configuration management, performance modeling, and verification tools.  Note, however, this is true for any methodology.
+  * A detailed MBSE approach to Platform Management for system families and product lines and support of emerging standards and interests in product line engineering, reference architectures, architectural frameworks, ontologies.
+  * Strengthened semantic integration of system requirements with the rest of the model.
+//Engineering Process and Automation://
+  * Expression of key patterns in both Engineered Systems and Systems of Engineering, including the Embedded Intelligence (Management) Pattern, the Systems of Innovation Pattern generalization of ISO 15288, and its Agile Systems Life Cycle Pattern form.
+  * Very rapid generation of first draft configured system requirements and other fundamental systems engineering artifacts, of higher quality and completeness.
+  * Rapid generation of D-FMEA, A-FMEA, P-FMEA, and FTA analyses of risks on a more systematic and complete basis, more deeply integrated with the rest of the system model.
+//Compatibility / Ease of Integration//
+  * Compatibility with contemporary modeling language standards.
+  * Direct mapping into contemporary modeling tools, PLM information systems, and other COTS and enterprise systems, increasing the value of existing information technologies.
+  * Deeper support for federated data across differing information systems, for integration with emerging open systems life cycle (OSLC) standard technologies.
+  * Strong expression of life cycle and operational states of systems
+Applied in award-winning INCOSE papers, S*MBSE models have been practiced for two decades, across a variety of domains in commercial, defense, and institutional environments:
+{{:mbse:methodology:s_patterns_fg3.jpg|}}
+=== Tool Support ===
+PBSE and its supporting S*Metamodel are tool-independent by intention. Substantially any COTS modeling, engineering, or PLM tool can be made to support PBSE by the use of an S*Metamodel Map for the specific COTS tool. Such mappings have already been created for a number of tools, including IBM/Rational DOORS™, Siemens Team Center™ Systems Engineering, Dassault Systemes ENOVIA™, Sparx Enterprise Architect™ for SysML®, IBM Rhapsody for SysML®, generic standard SysML, and others. Each such mapping is a detail specification of the formal mapping of S*Metamodel classes, relationships, and attributes into a specific schema native to the target tool or information system, along with supporting configuration information.
-  * A more complete set of OOSEM tool requirements is provided in the referenced OOSEM tutorial (see Resources for this methodology below).
 === Offering/Availability ===
-  * The OOSEM tutorial and training materials are available on the [[http://connect.incose.org/default.aspx|INCOSE Connect]] site under the [[https://connect.incose.org/tb/tote/oosem/default.aspx|INCOSE OOSEM WG]] page.  **Note:**  Access requires INCOSE membership.
+The general PBSE approach to enhanced MBSE is being shared through and explored by the members of the Patterns Working Group of the INCOSE MBSE Initiative. This cross-industries team has been and continues pursuing a number of PBSE applications and projects (including joint projects with other INCOSE working groups) which are shared through the INCOSE MBSE Challenge Team’s MBSE wiki / web site posted resources, reference, and information assets. Refer to the Resources below.
-  * Unlike other industry-provided MBSE methodologies, OOSEM is not a formal offering that can be purchased from any specific vendor, including professional services. Support services may be available by contacting representatives of the INCOSE OOSEM Working Group.
+Where commercial support may be requested, ICTT System Sciences and its partners provide related services, and the third party COTS tools noted above are supported by their commercial suppliers. S*Modeling elements are also taught as systems competencies for engineering undergraduates at Rose-Hulman Institute of Technology, the original academic parent of ICTT.
 === Resources ===
-  * Estefan, Jeff A., “[[http://www.incose.org/ProductsPubs/pdf/techdata/MTTC/MBSE_Methodology_Survey_2008-0610_RevB-JAE2.pdf|Survey of Model-Based Systems Engineering (MBSE) Methodologies]],” Rev. B, INCOSE Technical Publication, Document No.: INCOSE-TD-2007-003-01, International Council on Systems Engineering, San Diego, CA, June 10, 2008.\\
+// __Summary of PBSE Methodology:__//
+  - Schindel, W., et al, “Pattern-Based Systems Engineering (PBSE) Based on S*MBSE Models” INCOSE MBSE Patterns Working Group, 2015. (Click {{:mbse:methodology:pbse_extension_of_mbse--methodology_summary_v1.5.5a.pdf|here}} for this article, and more references, examples.)
+//__Applications of PBSE:__//
+  - Bradley, J., Hughes, M., and Schindel, W., “Optimizing Delivery of Global Pharmaceutical Packaging Solutions, Using Systems Engineering Patterns” Proceedings of the INCOSE 2010 International Symposium, 2010.
+  - Cook, D., and Schindel, W., “Utilizing MBSE Patterns to Accelerate System Verification”, in Proc. of the INCOSE 2015 International Symposium, Seattle, WA, July, 2015.
+  - Peterson, T., and Schindel, W., “Pattern-Based Systems Engineering: Leveraging Model-Based Systems Engineering for Cyber-Physical Systems”, Proc. of NDIA GVSETS Conference, 2014.
+  - Schindel, W., and Smith, V., “Results of applying a families-of-systems approach to systems engineering of product line families”, SAE International, Technical Report 2002-01-3086, 2002.
+  - Schindel, W., and Peterson, T., “Introduction to Pattern-Based Systems Engineering (PBSE): Leveraging MBSE Techniques”, in Proc. of INCOSE 2013 International Symposium, Tutorial, June, 2013.
+  - Schindel, W., Lewis, S., Sherey, J., Sanyal, S., “Accelerating MBSE Impacts Across the Enterprise: Model-Based S*Patterns”, in Proc. of INCOSE 2015 International Symposium, July, 2015.
+//__Impact of Formal Interaction Models:__//
+  - Schindel, W., “Requirements Statements Are Transfer Functions: An Insight From Model-Based Systems Engineering”, Proceedings of INCOSE 2005 International Symposium, 2005.
+  - Schindel, W., “System Interactions: Making the Heart of Systems More Visible”, Proc. of INCOSE Great Lakes Regional Conference, 2013.
+  - Simoni, M., et al, “Practicing and Assessing Formal Systems Competencies in ECE Senior Design”, in Proc. of American Society for Engineering Education 2014 Conference, 2014.
-  * Friedenthal, Moore, Steiner, “A Practical Guide to SysML," (Refer to Chapter 16), Morgan Kaufmann OMG Press, 2009.\\
+//__The INCOSE MBSE Patterns Working Group__//
+  - MBSE wiki / web site of Patterns Challenge Team:
+    * http://www.omgwiki.org/MBSE/doku.php?id=mbse:patterns:patterns
+  - Schindel, W., “Failure Analysis: Insights from Model-Based Systems Engineering”, Proc. of INCOSE International Symposium, 2010.
+  - Schindel, W., “What Is the Smallest Model of a System?”, Proc. of the INCOSE 2011 International Symposium, International Council on Systems Engineering (2011).
-  * Lykins, Howard, Friedenthal, Sanford and Abraham Meilich, “Adapting UML for an Object-Oriented Systems Engineering Method (OOSEM),” //Proceedings of the INCOSE 2000 International Symposium//, Minneapolis, MN, Jul. 2000.
-  * Friedenthal, Sanford, “Object Oriented Systems Engineering,” //Process Integration for 2000 and Beyond: Systems Engineering and Software Symposium//, New Orleans, LA, Lockheed Martin Corporation, 1998.
-  * “Object-Oriented Systems Engineering Method (OOSEM) Tutorial,” Ver. 02.42.00, Lockheed Martin Corporation and INCOSE OOSEM Working Group, Apr. 2006.

MBSE Wiki

User Tools

Site Tools

Differences

Page Tools