mbse:patterns:patterns
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
mbse:patterns:patterns [2020/03/21 15:45] schindel [References and Download Links] |
mbse:patterns:patterns [2020/09/28 14:06] schindel [Resources, Projects, References by Subject] |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| As used here, System Patterns are configurable, re-usable System Models that would otherwise be like those expected and found in the practice of MBSE (not limited to, but including, SysML models). Through the availability and use of System Patterns, the outcomes targeted by MBSE models are made more accessible, in terms of ease (and skill) of generation and use, associated modeling cost, schedule, risk, completeness, and consistency, etc. Over time, System Patterns become points of accumulation of organizational learning and expertise. Because they are configurable and re-usable models of families or classes of systems, model-based System Patterns involve some additional methods and disciplines that extend the ideas of MBSE (e.g., Pattern Management, Configuration Rules, model minimality, etc.). | As used here, System Patterns are configurable, re-usable System Models that would otherwise be like those expected and found in the practice of MBSE (not limited to, but including, SysML models). Through the availability and use of System Patterns, the outcomes targeted by MBSE models are made more accessible, in terms of ease (and skill) of generation and use, associated modeling cost, schedule, risk, completeness, and consistency, etc. Over time, System Patterns become points of accumulation of organizational learning and expertise. Because they are configurable and re-usable models of families or classes of systems, model-based System Patterns involve some additional methods and disciplines that extend the ideas of MBSE (e.g., Pattern Management, Configuration Rules, model minimality, etc.). | ||
| - | This model-based PBSE approach has been in use for a number of years, applied across enterprises and domains that include mil/aerospace, communications, automotive, medical/health care, advanced manufacturing, consumer products, along with business processes including sales, engineering, production, and general innovation. The first INCOSE PBSE tutorial was provided at IS2005, another given at GLRC2012, another at IS2013, and another at GRLC2013. Attendees at the IS2013 tutorial expressed interest in an ongoing INCOSE PBSE group of some kind. We have also published a number of papers on this approach. | + | This model-based PBSE approach has been in use for a number of years, applied across enterprises and domains that include mil/aerospace, communications, automotive, medical/health care, advanced manufacturing, consumer products, along with business processes including sales, engineering, production, and general innovation. The first INCOSE PBSE tutorial was provided at IS2005, another given at GLRC2012, another at IS2013, and another at GRLC2013. Attendees at the IS2013 tutorial expressed interest in an ongoing INCOSE PBSE group. A number of papers and tutorials on this approach have been published, some reproduced here. |
| 1.2. Specific Challenge: | 1.2. Specific Challenge: | ||
| Line 76: | Line 76: | ||
| - | ===== Resources, Projects, References by Subject (New Section Under Construction) ===== | + | ===== Resources, Projects, References by Subject ===== |
| |**Foundations and Paths to Stronger SE**| //How INCOSE and the systems community are visualizing and reaching out to the future. How the INCOSE MBSE Patterns Working Group is applying a stronger foundation based on the System Phenomenon and the history of patterns in the physical sciences and mathematics to enhance and transform the foundation capabilities of Systems Engineering.// | | |**Foundations and Paths to Stronger SE**| //How INCOSE and the systems community are visualizing and reaching out to the future. How the INCOSE MBSE Patterns Working Group is applying a stronger foundation based on the System Phenomenon and the history of patterns in the physical sciences and mathematics to enhance and transform the foundation capabilities of Systems Engineering.// | | ||
| Line 96: | Line 96: | ||
| | |[[Trusted Model Repository Pattern]]| | | |[[Trusted Model Repository Pattern]]| | ||
| | |[[Verification_&_Validation_of_Models_Project_with_ASME_Stds_Cmtee]]| | | |[[Verification_&_Validation_of_Models_Project_with_ASME_Stds_Cmtee]]| | ||
| - | |**Maps to Frameworks, Schema, Tools**|//There a growing lists of architectural frameworks, reference architectures, ontologies, metamodels, and similar underlying semantic constructs, used as the basis for models of systems, automation tooling, product lines, and otherwise. Mapping the S*Metamodel to these provides an expanded means for understanding and using a given framework, schema, or tool. This includes making S*Models and S*Patterns tool agnostic, portable across modeling languages, and for supporting automated reasoning and more basic queries about models in different systems. // | | + | |**Maps to Frameworks, Schema, Tools**|//There are growing lists of architectural frameworks, reference architectures, ontologies, metamodels, and similar underlying semantic constructs, used as the basis for models of systems, automation tooling, product lines, and otherwise. Mapping the S*Metamodel to these provides an expanded means for understanding and using a given framework, schema, or tool. This includes making S*Models and S*Patterns tool agnostic, portable across modeling languages, and for supporting automated reasoning and more basic queries about models in different systems. // | |
| | |[[Mappings to Frameworks, Schema, and Tools]]| | | |[[Mappings to Frameworks, Schema, and Tools]]| | ||
| | |[[Semantic Technologies]]| | | |[[Semantic Technologies]]| | ||
| |**Domain Patterns**| //S*Patterns are about recurring things within some general or narrow environment, referred to as a domain. The following illustrates S*Patterns across different application domains.// | | |**Domain Patterns**| //S*Patterns are about recurring things within some general or narrow environment, referred to as a domain. The following illustrates S*Patterns across different application domains.// | | ||
| | |[[General Land Vehicle Pattern]]| | | |[[General Land Vehicle Pattern]]| | ||
| + | | |[[mbse:patterns:primary_flight_actuator_pattern_and_automated_verifcation]]| | ||
| | |[[Oil Filter Product Line Pattern]]| | | |[[Oil Filter Product Line Pattern]]| | ||
| | |[[Critical_Infrastructure_Protection_and_Recovery_Patterns_Project_with_CIPR_WG]]| | | |[[Critical_Infrastructure_Protection_and_Recovery_Patterns_Project_with_CIPR_WG]]| | ||
| Line 111: | Line 112: | ||
| | |[[General Mechanical Bracket Pattern]]| | | |[[General Mechanical Bracket Pattern]]| | ||
| | |[[SoS Patterns]]| | | |[[SoS Patterns]]| | ||
| + | |||
| + | ===== Collaborations, Partners, Shared Interest Groups ===== | ||
| + | |||
| + | Most of the projects performed by the INCOSE MBSE Patterns WG are performed jointly with other INCOSE Working Groups or with organizations outside INCOSE, having mutual interests. The matrix below summarizes the different entities we work with, and refers to resulting items in the Resources, Activities, and Projects matrix above. | ||
| + | |||
| + | |||
| + | {{ :mbse:patterns:picture5.jpg?nolink |}} | ||
| + | |||
| + | |||
| + | |||
| ===== Primary Working Group and Partners Meeting Materials--By Event===== | ===== Primary Working Group and Partners Meeting Materials--By Event===== | ||
| + | |||
| + | The following table lists chronological meetings, workshops, and other events participated in by the MBSE Patterns Working Group. The links on the right side of the following table link to event-specific minutes, resources, references, and materials: | ||
| ^Event_Date_._._._^Event_Milestone_._._._._._._._._._._._._._._^Status^Point_of_Contact_._._._._.^Link to References^ | ^Event_Date_._._._^Event_Milestone_._._._._._._._._._._._._._._^Status^Point_of_Contact_._._._._.^Link to References^ | ||
| Line 217: | Line 230: | ||
| CO-chair: Troy Peterson System Strategies, Inc. [email protected] | CO-chair: Troy Peterson System Strategies, Inc. [email protected] | ||
| - | Refer to attached Minutes for current team members, affiliations, and contact information. | + | |
| - | |||
| - | |||
| - | |||
| - | Link to web page with reference files selected from above for download: https://sites.google.com/site/incosepbsewgtempaccess/ | ||
| - | |||
| - | |||
mbse/patterns/patterns.txt ยท Last modified: 2024/04/24 11:00 by schindel
Page Tools
