User Tools

Site Tools


mbse:pbse

This is an old revision of the document!


Pattern-Based Systems Engineering (PBSE), Based On S*MBSE Models

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

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

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 Eclipse Process Framework (EPF) version of OOSEM exists.
  • 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 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 INCOSE Connect site under the INCOSE OOSEM WG page. Note: Access requires INCOSE membership.
  • 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.

Resources

  • Friedenthal, Moore, Steiner, “A Practical Guide to SysML,“ (Refer to Chapter 16), Morgan Kaufmann OMG Press, 2009.
  • 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.

Return to List of MBSE Methodologies

mbse/pbse.1438205058.txt.gz · Last modified: 2015/07/29 17:24 by jcwatson