a review of know-how reuse with patterns in model-based … · 2018. 12. 20. · sysml design...

Ce document et les informations qu’il contient sont la propriété de Safran. Ils ne doivent pas être copiés ni communiqués à un tiers sans l’autorisation préalable et écrite de Safran.

A REVIEW OF KNOW-HOW REUSE WITH

PATTERNS IN MODEL-BASED SYSTEMS

ENGINEERING

CSD&M - 18/12/2018

Quentin WU (Safran Aerosystems & Université de Lorraine, CNRS, CRAN) [ +33 1 55 82 50 28 – [email protected] ]

David GOUYON (Université de Lorraine, CNRS, CRAN)

Éric LEVRAT (Université de Lorraine, CNRS, CRAN)

Sophie BOUDAU (Safran Aerosystems)

mailto:[email protected]


AGENDA

Safran Aerosystems / CSD&M 2018 2

1. MOTIVATION

2. CHALLENGES AND RELATED WORKS

3. LITTLE HISTORY OF PATTERNS

4. PATTERNS FOR SYSTEMS ENGINEERING

5. PATTERNS FOR MODEL-BASED SYSTEMS ENGINEERING (MBSE)

6. CONCLUSIONS AND PERSPECTIVES


PR

OB

LE

MS

MOTIVATION


> “Composable design methods will leverage REUSE and validated PATTERNS to configure and integrate components

into system solutions.” (p.28)

> “MBSE has grown in popularity as a way to deal with the limitations of document-based approaches, but is still in

an early stage of MATURITY similar to the early days of CAD/CAE.” (p.38)

(INCOSE SE VISION 2025)

“Formal systems modeling is standard practice for specifying, analyzing, designing, and verifying systems […].” (p.38)

■ How to transfer and manage know-how available for REUSE? > Important to step back and see the “big picture”

■ How to improve CAPITALIZATION ? Are PATTERNS a possible solution? > Formalism adapted to the application domain (p.38)

■ How to overcome the many inhibitors of MBSE adoption? > Gap with the current engineering approach (Vogelsang et al., 2017), (Huldt and Stenius, 2018)

■ How to evaluate MATURITY of a reuse process within a modelling framework? > Confidence in the models/patterns to reuse

Conversion to an MBSE approach is facilitated by the formalization and reuse of know-how in the form of patterns

State of the art about know-how reuse, pattern reuse in a MBSE framework


CHALLENGES AND RELATED WORKS (1/2)


■ Complexity of systems keeps increasing

> Engineers cannot individually have a complete view of the project

○ Knowledge and know-how sharing with other engineers

> Projects are not started “from scratch” ○ Reusing the knowledge and know-how from previous projects

○ To be efficient : save time, money, and resources

> Transferring knowledge and know-how between engineers to foster reuse ○ Static know-how vs Dynamic know-how (Mourtzis et al., 2016)

○ Individuals experience vs Shared information (Miled, 2014)

○ Providing solutions vs Constructing solutions (Gzara et al., 2003)


■ Approaches of reuse

> Opportunistic reuse: when the first project was not developed with reusable capacity. It is the lowest incidence of

reuse (Rockley et al., 2003) because the act of reuse is the responsibility of the engineer's goodwill;

> Planned reuse: when the first project was developed with reusable capacity. In this case, reuse has been integrated in

the development process in order to highlight and foster reusable contents (Rine et al., 1998);

> Variance: use of something already developed during a previous work, in a slightly different form (AFIS CT MBSE,

2018). For example, on a product line, there is a common core model but different options (Niu et al., 2013).

■The concept of pattern

> Proposed generic guides to ease and systematize construction of complex systems (Cochard, 2017)

> Used in all stages of the development cycle (Gzara et al., 2003)

CHALLENGES AND RELATED WORKS (2/2)


Can REUSE of PATTERNS help us counter today's systems rising complexity?


LITTLE HISTORY OF PATTERNS: from Architecture to Systems Engineering


“Each pattern describes a PROBLEM which occurs over

and over again in our ENVIRONMENT, and then describes

the core of the SOLUTION to that problem, in such a way

that you can use this solution a million times over, without

ever doing it the same way twice”

(Alexander et al., 1977)

First works:

proposition for the creation of a SE Pattern Language (Barter, 1998)

proposition of a methodological framework based on the reuse of

patterns during all the lifecycle (Cauvet et al. 1998; Gzara 2000)

proposition to use patterns libraries to support a methodological

framework for the conception of product information system (Conte et al.,

2001)

1977 1995

“Design Patterns: Elements of Reusable Object-Oriented Software.”

(Gamma et al., 1995)

Design Pattern : general, reusable solution to a recurring problem in the

design of object-oriented applications = PROVEN SOLUTIONS

1998 …..

Architecture

Software

Systems Engineering


PATTERNS FOR SYSTEMS ENGINEERING (1/2)


■ CHARACTERISTICS > Patterns "are not created from a blank page; they are mined“ (Hanmer et al., 2004)

○ Individual contributions: used of own experiences or ones from colleagues;

○ Second-hand contributions: interviews with experts or by guiding another person;

○ Workshops/Meeting contributions: groups of people who brainstorm the elements of a patterns.

> Pattern seems to possess an inherent triptych

> Systems Pattern Form (Cloutier et Verma, 2007)

■ EXAMPLES > System Of Interest (SOI)

○ Control-Command (Pfister et al., 2012)

> Systems Engineering Activities (SEA) ○ Reuse process for Innovation (Majchrak et al., 2004)

SE patterns are embedded

in existing designs !

{Context, Problem, Solution}

Patterns needs explicit

documentation

















documentation


■ VALUES AND LIMITS + Patterns allow people to solve complex problems by leveraging experience, knowledge

and know-how from their predecessors ○ In SW : larger the team size was, the greater the use of patterns was for documenting changes

(Hanmer et al., 2004)

○ “should offer the same comfortable learning experience as a conversation with trusted colleagues”

(Haskins, 2005)

+ Patterns are valuable to mitigate risks (Schindel and Peterson, 2013) ○ Not re-experiencing the same mistakes and reworks

○ Handle markets, technologies, environments evolutions

○ “Hero Culture” is not a long term solution

! Patterns are not a magical solution ○ SE Patterns require an adequate notation that allows their documentation (Cloutier et Verma, 2007)

○ A process flow has to be defined to use SE patterns (Cloutier, 2006)

- How to find/mine the right pattern?

- How to store, select, adapt patterns?

- Is the chosen pattern an applicable pattern?

- How are we making engineers aware of patterns they don’t know?

- …



Patterns are not

“silver bullets”

Patterns create a

common lexicon

between engineers


■ REUSE OF MODELS

■MBSE PATTERNS USE CASES

> Guide the development process in a MBSE framework (Schindel and Peterson, 2013)

○ engineers do not need to be expert of modelling methodologies

> Analyze complex systems through patterns mining (Kalawsky, 2013) ○ the discovery of patterns help provide an explicit way to articulate common concepts

W WEAKNESSES

PATTERNS FOR MODEL-BASED SYSTEMS ENGINEERING (MBSE) (1/2)


Patterns helps tailoring

an adequate solution

S STRENGTH

Improve development:

reduce time, improve maturity,

facilitate V&V

Easy to envision:

digital limitations vs physical limitations

Lack of:

expertise on modelling, maturity of

previous version of models

Reuse of models:

developped by providers, customers,…

Intellectual Property transfer O

OPPORTUNITIES

T THREATS


■ EFFORTLESS MODELLING WITH PATTERNS

> Guide the development process (Barbieri et al., 2014)

○ SysML design pattern (package)

○ improve traceability

○ facilitating the impact analysis

> Semi-automatic generation of diagrams (Paydar and Kahani, 2015) ○ candidate patterns

○ manual selection

> Focus on what needs to be modelled and not the aesthetic of the model (Gasser, 2012) ○ resizing of the diagram is automatic (“insert policy”)

○ work in an algorithmic way of thinking

○ focus on the expected behaviour than on the aesthetics

> Patterns as “re-usable models” (PBSE) (Schindel et al., 2015) ○ identify types of “regularities”

○ extend MBSE through configurable models

○ gain the benefits of MBSE without being an expert

PATTERNS FOR MODEL-BASED SYSTEMS ENGINEERING (MBSE) (2/2)



■ PATTERNS FOR MBSE

+ Guide the development to avoid deviation

+ Benefit from the concepts of MBSE without being an expert of modelling methodologies

‒ Syntax and semantics of some modelling languages (RFP SysML 2.0)

‒ Tools interoperability (heterogeneous environment) (Shani and Broodney, 2015)

■ PERSPECTIVES

> Characterization of patterns abstraction level

> Improve the general maturity of reuse approaches ○ Characterize maturity of patterns

○ Define a process of maturation and reuse of patterns

- capitalization, selection, reuse, and update

> Implement the process in a MBSE software tool

CONCLUSIONS AND PERSPECTIVES


Act of capitalization

is not self-evident !


A REVIEW OF KNOW-HOW REUSE WITH

PATTERNS IN MODEL-BASED SYSTEMS

ENGINEERING

CSD&M - 18/12/2018

Quentin WU (Safran Aerosystems & Université de Lorraine, CNRS, CRAN)

David GOUYON (Université de Lorraine, CNRS, CRAN)

Éric LEVRAT (Université de Lorraine, CNRS, CRAN)

Sophie BOUDAU (Safran Aerosystems)


1. AFIS MBSE Technical Comittee, O. Denis, D. Gouyon, D. Lesens, F. Risy, Q. Wu “Reuse & Variant Modeling

Awareness kit”, 2018

2. Alexander, S. Ishikawa, and M. Silverstein, A Pattern Language. Oxford university press, 1977.

3. Barbieri, K. Kernschmidt, C. Fantuzzi, and B. Vogel-Heuser, “A SysML based design pattern for the high-

level development of mechatronic systems to enhance re-usability,” in IFAC Proceedings Volumes (IFAC-

PapersOnline), 2014, vol. 19, no. 3, pp. 3431–3437.

4. Barter, “A Systems Engineering Pattern Language,” in INCOSE International Symposium, 1998, pp. 350–

353.

5. Cloutier and D. Verma, “Applying the concept of patterns to systems architecture,” Syst. Eng., vol. 10, no.

2, pp. 138–154, 2007.

6. Cloutier, “Applicability of patterns to architecting complex systems,” Stevens Institute of Technology,

2006.

7. Cochard, “Contribution à la génération de séquences pour la conduite de systèmes complexes critiques,”

Université de Lorraine, 2017.

8. Gamma, R. Helm, R. Johnson, and J. Vlissides, Design Patterns: Elements of Reusable Object-oriented

Software. Addison-Wesley Longman Publishing Co., Inc., 1995.

9. Gasser, “Structuring activity diagrams,” in 14th IFAC Symposium on Information Control Problems in

Manufacturing, Bucharest, Romania, 2012.

10. Gzara, D. Rieu, and M. Tollenaere, “Product information systems engineering: An approach for building

product models by reuse of patterns,” Robot. Comput. Integr. Manuf., vol. 19, no. 3, pp. 239–261, 2003.

11. Hanmer and K. F. Kocan, “Documenting architectures with patterns,” Bell Labs Tech. J., vol. 9, no. 1, pp.

143–163, 2004.

12. Haskins, “Application of patterns and pattern languages to systems engineering,” in INCOSE International

Symposium, 2005, pp. 1619–1627.

13. Huldt and I. Stenius, “State-of-practice survey of model-based systems engineering,” Syst. Eng., no. July,

pp. 1–12, 2018.

14. INCOSE SE VISION 2025

15. Kalawsky, D. Joannou, Y. Tian, and A. Fayoumi, “Using architecture patterns to architect and analyze

systems of systems,” Procedia Comput. Sci., vol. 16, no. March 2015, pp. 283–292, 2013.

16. Majchrzak, L. P. Cooper, and O. E. Neece, “Knowledge Reuse for Innovation,” Manage. Sci., vol. 50, no. 2,

pp. 174–188, 2004.

17. Miled, “Reusing knowledge based on ontology and organizational model,” Procedia Comput. Sci., vol. 35,

no. C, pp. 766–775, 2014.

18. Mourtzis, M. Doukas, and C. Giannoulis, “An Inference-based Knowledge Reuse Framework for Historical

Product and Production Information Retrieval,” Procedia CIRP, vol. 41, pp. 472–477, 2016.

19. Niu, J. Savolainen, Z. Niu, M. Jin, and J.-R. C. Cheng, “A Systems Approach to Product Line Requirements

Reuse,” IEEE Syst. J., vol. PP, no. 99, pp. 1–10, 2013.

20. Paydar and M. Kahani, “A semi-automated approach to adapt activity diagrams for new use cases,” Inf.

Softw. Technol., vol. 57, no. 1, pp. 543–570, 2015.

21. Pfister, V. Chapurlat, M. Huchard, C. Nebut, and J.-L. Wippler, “A Proposed Meta-Model for Formalizing

Systems Engineering Knowledge, Based on Functional Architecture Patterns,” Syst. Eng., vol. 15, no. 3,

2012.

22. Rine and R. M. Sonnemann, “Investments in reusable software. A study of software reuse investment

success factors,” J. Syst. Softw., vol. 41, no. 1, pp. 17–32, 1998.

23. Rockley, P. Kostur, and S. Manning, Managing Enterprise Content: A Unified Content Strategy. New

Riders, 2003.

24. Schindel and T. Peterson, “Introduction to Pattern-Based Systems Engineering (PBSE): Leveraging MBSE

Techniques,” INCOSE Int. Symp., vol. 23, no. 1, p. 1639, 2013.

25. Schindel, S. A. Lewis, J. J. Sherey, and S. K. Sanyal, “Accelerating MBSE Impacts Across the Enterprise :

Model-Based S * Patterns,” in INCOSE International Symposium, 2015.

26. Shani and H. Broodney, “Reuse in model-based systems engineering,” 9th Annu. IEEE Int. Syst. Conf.

SysCon 2015 - Proc., pp. 77–83, 2015.

27. Vogelsang, T. Amorim, F. Pudlitz, P. Gersing, and J. Philipps, “Should I Stay or Should I Go? On Forces

that Drive and Prevent MBSE Adoption in the Embedded Systems Industry,” 2017.

REFERENCES


a review of know-how reuse with patterns in model-based … · 2018. 12. 20. · sysml design...

Documents