1.1.2 Using Patterns to Share Best Results ‐ A proposal to codify the SEBOK

Haskins, Cecilia

doi:10.1002/j.2334-5837.2003.tb02596.x

Cited by 11 publications

(11 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The third approach is based on the concept of "pattern", described for the first time in architecture by Alexander, Ishikawa, and Silverstein (1977), then promoted in software engineering by Gamma et al (1993) and Bushmann, Meunier, and Rohnert (1996). In the field of systems engineering, Barter (1998) and Haskins (2003), were the first to introduce pattern and pattern language for capturing the engineering knowledge. (Pfister et al 2012) adapted the concept to functional architecture design and describe patterns with an enhanced function flow block diagram (eFFBD), which is translatable into SysML, allowing a bridge with MBSE.…”

Section: State Of the Art Of Knowledge Reusementioning

confidence: 99%

Towards Model‐based Systems Engineering (Mbse) Patterns to Efficiently Reuse Know‐how

Wu¹,

Gouyon²,

Hubert³

et al. 2017

INSIGHT

View full text Add to dashboard Cite

Know‐how reuse is an approach that has been always used by engineers to take advantage of their accumulated knowledge and practices. But, the difficulty to formalize and reuse expert know‐how is increasing alongside the complexity of systems. To deal with this challenge, this paper aims to open the way to new approaches of know‐how reuse, in order to improve engineering activities. For that purpose, it explores the capabilities of three reuse approaches (commercial off‐the‐shelf (COTS), set‐based design, and patterns), and their ability to be linked with a model‐based systems engineering (MBSE) framework.

show abstract

Section: State Of the Art Of Knowledge Reusementioning

confidence: 99%

Towards Model‐based Systems Engineering (Mbse) Patterns to Efficiently Reuse Know‐how

Wu¹,

Gouyon²,

Hubert³

et al. 2017

INSIGHT

View full text Add to dashboard Cite

show abstract

“…Patterns are a proven technique of enhancing the scalability of any model. [9,10,11,12] The universal role of decisions in the system/solution design process implies that decision patterns should be scalable across a broad range of system/solution types, industries and use cases. Even though Decision Management has not yet been recognized as a first-tier Systems Engineering discipline, the scalability of decision patterns has been widely demonstrated across these dimensions.…”

Section: Cross-domain Scalability Of Decision Patternsmentioning

confidence: 99%

2.2.1 Decision Management (DM) as the engine for scalable cross domain Systems Engineering (SE)

Mendonza¹,

Fitch

2012

INCOSE International Symp

View full text Add to dashboard Cite

Decisions create the future in any industry or human endeavor. A robust Decision Management (DM) capability is the key enabler for accelerating the benefits of Systems Engineering (SE) discipline to new domains. Effective Decision Management is comprised of three elements: 1) decision patterns; 2) DM methods engine; 3) decision‐centric information model. INCOSE can leverage DM as an engine for SE outreach to new industries and domains. DM is highly scalable and integrates knowledge from many processes and stakeholders. A “decisions‐first” outreach strategy offers a clear value proposition to the primary stakeholders who must be convinced of the benefits of SE discipline. Existing decision‐makers gain a new set of techniques that improve decision quality, speed and execution. Subject matter experts gain a method for influencing designs with their unique knowledge and preserving their knowledge in the form of decision patterns. Project managers gain the ability to proactively identify and prioritize decisions and manage their impact on project cost/schedule baselines. Solution developers gain a better understanding of the upstream decisions that drive their requirements. Most of the cross‐domain benefits of DM can be demonstrated through rapid‐payback pilots without commitment to wholesale adoption of more comprehensive, complex and costly SE frameworks. The authors propose to engage INCOSE's Decision Analysis working group as the forum for investigating the cross‐domain applicability of DM.

show abstract

“…A pattern is defined as a solution of a specific problem placed in a specific context. Both the (Barter 1998) and (Haskins 2003) papers describe the form of patterns as containing: name, problem statement, forces, context, and a solution. Barter included 'related patterns' as part of a pattern form, whereas Haskins included 'resulting context' as a part of a pattern form "Resulting Context.…”

Section: System Engineering (Se) Patterns Introductionmentioning

confidence: 99%

“…Potential users of the pattern can study this section to weigh the potential costs and benefits. In a pattern language, the resulting context of one pattern often becomes the context for successive patterns that address new issues (tensions)" Haskins (2003).…”

Section: System Engineering (Se) Patterns Introductionmentioning

confidence: 99%

Foundational Systems Engineering (SE) Patterns for a SE Pattern Language

Simpson¹,

Simpson²

2006

INCOSE International Symp

View full text Add to dashboard Cite

Abstract. Patterns are classically used to effectively capture large, complex bodies of information and knowledge. This paper outlines the current state of systems engineering (SE) pattern literature as well as proposing a foundational set of SE patterns for use in SE pattern languages. A pattern is defined as a solution of a specific problem placed in a specific context. A pattern language is a collection of interrelated patterns, with specific relationships binding individual patterns together. A collection of SE pattern relationship types are also introduced in this paper. Language is a fundamental aspect of any technical or scientific activity. The technical language used in technical activities impacts the concepts that can be addressed, the effort to express these concepts, and the precision with which these concepts can be expressed. Therefore it is important to consider the language requirements for conceptual expression and precision when designing a new language. In the case of an SE pattern language, the elements to be considered are the individual patterns and the relationships between the patterns.

show abstract

1.1.2 Using Patterns to Share Best Results ‐ A proposal to codify the SEBOK

Cited by 11 publications

References 8 publications

Towards Model‐based Systems Engineering (Mbse) Patterns to Efficiently Reuse Know‐how

Towards Model‐based Systems Engineering (Mbse) Patterns to Efficiently Reuse Know‐how

2.2.1 Decision Management (DM) as the engine for scalable cross domain Systems Engineering (SE)

Foundational Systems Engineering (SE) Patterns for a SE Pattern Language

Contact Info

Product

Resources

About