Tutorials.

Transcription

1 Tutorials T1 Model-Based Systems Engineering (MBSE) goes digital: How digitalization and Industry 4.0 will affect systems engineering (SE) Prof. St. Rudolph (University of Stuttgart) Conventional Model-Based Systems Engineering (MBSE) and the V-Model in the near future will have to enclose in their digital twins technological achievements such as: - digital, machine-executable, re-usable and machine-readable knowledge representations in form of modeling languages - fully semantic interoperability of methods, tools and processes along the digital product life-cycle due to language properties - software tool independency to separate the corporate design knowledge (company DNA) in an abstract language to avoid costly software vendor lock-in The tutorial will present an integrated solution approach and a research prototype implementation based on design languages in UML which allow to express and execute a digital V-model. The approach will not only focus on engineering design, but also on code generation and the integration of the digital factory into such a fully digital modeling and simulation framework. Three use-cases from aerospace and the automotive industry will be used to illustrate the digital modeling approach. Awareness for the driving questions in the upcoming digitalization and Industry 4.0 in engineering and manufacturing. Familiarity with abbreviations and like CAD, MBS, FEM, CFD from engineering and concepts of MDA, M2M, M2T from computer science and MBSE and V-Model from SE will help, but are not mandatory. EMEASEC 2018 Tutorials, Issue 1 Page 1/9

2 T2 Challenges of System Safety and how Systems Engineering can help to tackle them? Dr. A. Rudolph (Continental) Tutorial shall provide common working session on Safety and how Systems Engineering can help to achieve Safety in the presence of new and poorly understood challenges at the systems and at the operational level. An attempt to look in a visionary future shall be taken. Guidance and instruction coming from the Safety WG of INCOSE: Structure: Sec. 1 - Brainstorming: What are current challenges of System Safety? Which of them are new and where are they from? Sec. 2 - Summary: How could we identify common challenges across domains and industries? How can we define safety (purpose, discipline, contributions)? Sec. 3a Justification: How can Systems Engineering as a whole help? How can Systems Engineers help? How do they differ from the safety folks? Sec. 3b - Justification: How can INCOSE as a council help? Sec. 4 - Brainstorming: Which Systems Engineering aspects can be used to help (viewpoints, processes, etc.)? Sec 5 - Defining: Can we as Systems Engineering community define a vision for Systems Safety Engineering that we can believe in? Sec. 6 Inviting: Introduction to the INCOSE SAFETY WG and welcome to participate None EMEASEC 2018 Tutorials, Issue 1 Page 2/9

3 T3 Modeling in Early Project Phases Using the NATO Architecture Framework (NAF) Dr. M. Becker (Fraunhofer IESE) The tutorial will provide an introduction to the practical application of an enterprise architecture framework (NAF v3.1) in interdisciplinary projects. With guidance, the participants will use the example exercise Planetary Defense System to model different views of the framework. The example exercise covers a wide variety of modeling aspects in an early project phase. These include identification and modeling of the project context and the interfaces to external systems and/or stakeholders, description of the main functions and the systems / subsystems, and requirements modeling. The example exercise is complex, yet easy to understand. It covers different disciplines (e.g. software, hardware) and can be described very well in functional terms. In addition to the architecture framework, a fundamental modeling methodology will also be demonstrated and its practical implementation in the modeling tool (Sparx Enterprise Architect) will be explained. The participants will learn Best Practices from various projects (defense sector), especially with regard to architectural scoping and required modeling depth. Basic knowledge of SysML or UML Initial experience with at least one established modeling tool (e.g., Sparx EA, No Magic! MagicDraw, IBM Rhapsody) EMEASEC 2018 Tutorials, Issue 1 Page 3/9

4 T4 How to design product lines by means of MBSE Prof. Dr. C. Zuccaro (University of Applied Sciences Munich) Almost all systems exist as product lines. Model-based product line engineering (MBPLE) extends SysML-based MBSE to take product variability into account. One valid approach is based on orthogonal variability modelling (OVM) according to ISO In this tutorial we consider what is expected by modelers: - Model product lines by combining variability modelling and system modelling - Assure consistency with other design artifacts - Consistency of product line and variability model - Create product models based on variability decisions - Design for variability with the target to reduce internal variability without impacting external variability - Support design of product lines by suitable business processes We will show how to tackle these needs, apply them on exemplary models and discuss case studies Basic knowledge of MBSE based on SysML is helpful EMEASEC 2018 Tutorials, Issue 1 Page 4/9

5 T5 Model-Based Requirements Management (MBRQM) Dr. M. Di Maio (Projectglobe.com) Model-Based Requirements Management (MBRQM) The objective of the tutorial is to better understand the role of MBSE in supporting Requirements Management (RQM). Using a case study from product development, the students are split into two groups to generate different system models: one in SysML, the other in the semantic graph of Model-Driven Engineering (MDE). 1) Recap I: RQM in Product Development - definitions, objectives, principles, and comments. 2) Recap II: MBSE and SysML - basics, objectives, and comments. 3) Recap III: Model-Driven Engineering (MDE) - basics, graph model, objectives, and comments. 4) Case Study: Introducing a simple complex product. 5) Group Work: Develop an RQM-Model for the Case Study using MDE (Group A) and SysML (Group B). 6) Discussion: Comparing the two approaches and identifying pros and cons. Working Knowledge of SE and basic understanding of Modelling. EMEASEC 2018 Tutorials, Issue 1 Page 5/9

6 T6 Model-Based Functional Safety with SysMLÉ T. Weilkiens (oose Innovative Informatik eg) Keywords xxxxxx System safety analysis must be integrated in system development. Therefore, when modeling a system, functional safety aspects must be considered from the very beginning. In this tutorial current approaches how to integrate system safety aspects in SysMLÉ are presented. The tutorial is based mainly on the safety profile that is currently developed by OMGÉ. As a member of the working group involved in developing the safety profile we can provide first-hand information. None EMEASEC 2018 Tutorials, Issue 1 Page 6/9

7 T7 Fear no more! Essential Model-Based Product Line Systems Engineering at your reach Dr. H. G. ChalÑ GÖngora (Thales) Title Come and learn how to take control of the model-based chaos and improve your business by applying efficient architectural design principles in a Product Line Engineering (PLE) context. When combined effectively, MBSE and PLE can lead to extremely efficient and capable product systems engineering. However, an integrated approach combining effective processes and practices is crucial to achieve a broad adoption. This, along with efficient supporting tools, is essential to obtain the full benefits of Model-Based Product Line Systems Engineering (MBPLSE). This hands-on tutorial will walk you through the essential practices of systems engineering, architectural design and Model-Based SE in a PLE perspective. The tutorial will also give you an opportunity to demystify model-based approaches thanks to a practical methodology supported by an open MBPLSE solution General knowledge on systems engineering, modeling tools or languages and PLE is recommended Practitioners having a first experience in system architecting or modelling (in general) or MBSE. EMEASEC 2018 Tutorials, Issue 1 Page 7/9

8 Best Practices Circle (BPC) (Limited to producing industries of highly complex cybertronic systems) Several from Industry The SE-BPC (Systems Engineering Best Practice Circle) is an industry working group and a communication platform in the GfSE for practitioners from different industry sectors across the D-A-CH region (Germany, Austria and Switzerland) producing industries of highly complex cybertronic systems, in particular OEMs and suppliers from automotive, rail, utility and farming vehicles, machinery and plant engineering, aerospace, medical, defense and more. The trustful cooperation is predominant within this group. SE-BPC work product releases and status communication is only done after the reconcilement and clearance or approval of it through the SE-BPC participants and through the GfSE. The agreed language of the SE-BPC is German. Consultancies, tool vendors and universities are not participating. They may be invited for specific issues and presentations. The SE-BPC is focussed on the evolvement of the core methods on Systems Engineering (SE) and Model-Based Systems Engineering (MBSE). The link to the state of the art and method support is given by the Fraunhofer IEM, Paderborn. They coordinate and organise the SE-BPC and ensure the communication into the GfSE e.v. as well as to other subject relevant organisations like ProSTEP ivip and the BMBF-Spitzencluster, like its-owl. Limited to producing industries of highly complex cybertronic systems EMEASEC 2018 Tutorials, Issue 1 Page 8/9

9 SEP TEST (INCOSE Exam) INCOSE Keywords Certification CSEP, Certification Exam Individuals, who are not currently INCOSE ASEPs, CSEP, or ESEPs, are invited to take the INCOSE Certification knowledge exam at the International Workshop. There is no fee for this exam. There are, however, some differences from the exam offered at computer testing facilities. The exam at the IW will be taken on paper rather than a computer. Results will be sent by within four weeks of the exam completion. Those who pass the exam will be allowed to use their results toward INCOSE ASEP or CSEP certification if they apply for that certification within a year. No test participants are required to apply for certification, but those who do apply will have to pay all standard application fees and be INCOSE individual members. On exam day, participants will need to provide photo identification and confirm their address. No talking or reference materials are allowed during the exam, except for a translation dictionary for those whose mother tongue is a language other than English. Candidates whose mother tongue is not English may also have an additional thirty minutes to take the exam. They must request this extra time before the exam begins. Information about the INCOSE knowledge exam based on the INCOSE Handbook version 4 was presented at IS 2015 and is published here. Additional details about the INCOSE Certification Program are here. See INCOSE website EMEASEC 2018 Tutorials, Issue 1 Page 9/9