Class 1 Lecture - Model-Based Systems Engineering PDF

Class #1: Introduction to Model-Based Systems Engineering EMSE 6817 Model-based Systems Engineering Dr. Ben Stirgwolt Class #1 Outline 1. Welcome & Self-Introductions 2. Introduction to EMSE 6817 3. Introduction to Model-Based Systems Engineering (MBSE) 4. Introductio...

Class #1: Introduction to Model-Based Systems Engineering EMSE 6817 Model-based Systems Engineering Dr. Ben Stirgwolt Class #1 Outline 1. Welcome & Self-Introductions 2. Introduction to EMSE 6817 3. Introduction to Model-Based Systems Engineering (MBSE) 4. Introduction to the Systems Modeling Language (SysML) EMSE 6817 - Class 1 - Slide 2 Introduction to Dr. Stirgwolt BS – Aeronautical/Astronautical Engineering – Purdue University MEng – Systems Engineering – Penn State University PhD – Systems Engineering – George Washington University INCOSE CSEP & OMG Certified System Modeling Professional Currently Director of MBSE at Belcan, an engineering services company. Previously SE Manager at Lockheed Martin. Live in OH. Enjoy DIY home projects and trying to skateboard. EMSE 6817 - Class 1 - Slide 3 Self-Introductions Name Location Undergraduate degree Place of employment / current role Experience with MBSE EMSE 6817 - Class 1 - Slide 4 Introduction to EMSE 6817 Course Objectives 1. Articulate the motivation for and value of model-based systems engineering 2. Describe the various languages, methodologies, and frameworks associated with MBSE 3. Represent the behavior, structure, and requirements of a system using foundational elements of SysML 4. Perform mathematical analysis as an integrated part of the system architecture development process 5. Extend SysML to support a range of system modeling domains and stakeholder concerns EMSE 6817 - Class 1 - Slide 6 Course Logistics Class Live class Saturdays 9:00 am – 12:10 pm EST; Nov 9 – Jan 25 Lectures will be recorded, but please make every effort to attend the live session 5-10 minute break every ~1 hour Office Hours 3 hrs of office hours / week gwu-edu.zoom.us/my/ben.stirgwolt Monday 8-9 PM EST, Thursday 7:30 - 9:30 PM EST Feel free to email throughout the week EMSE 6817 - Class 1 - Slide 7 Textbook & Grading Textbook SysML Distilled: A Brief Guide to the Systems Modeling Language, 1st Edition, by Delligatti, ISBN-13: 978-0-321-92786-6 E-book available through GWU library Grading Grades are determined by weight average values and based on a standard curve relative to the class average HW: 30%, Midterm: 35%, Final: 35% EMSE 6817 - Class 1 - Slide 8 Class Schedule Class Topic/Activity Assignment Due Course Introduction None 1 Introduction to Model-Based Systems Engineering Introduction to the Systems Modeling Language Introduction to languages, frameworks, processes, & tools Read Ch 1, 2 2 HW 1 due 9:00am 11/16 Model preparation, organization, & management Read Ch. 5, 10, 11 3 Use cases & requirements modeling HW 2 due 9:00am 11/23 Structural modeling Read Ch. 3, 4 4 HW 3 due 9:00 am 12/7 Behavioral modeling, part 1 Read Ch. 6 5 HW4 due 9:00am 12/14 EMSE 6817 - Class 1 - Slide 9 Class Schedule, cont. Class Topic/Activity Assignment Due Behavioral modeling, part 2 Read Ch. 7, 8 6 HW5 due 9:00am 12/21 7 Parametric analysis, Verification & Validation Read Ch. 9 Cross-cutting concepts Read Ch. 12 8 Extensions of SysML HW6 due 9:00am 1/11 Specialty engineering integration Deployment & application of MBSE HW7 9 Trade studies & product line engineering with MBSE SysML 2.0 HW8 10 Research, trends, & challenges in MBSE EMSE 6817 - Class 1 - Slide 10 Homework Assignments Worth 30% of the final grade 8 assignments due Saturdays at 9:00 am EST Homework files will be submitted via Blackboard HW 1, 2, 7, 8 are free response (submit Word or PDF file) HW 3, 4, 5, 6 are models (submit mdzip file) Late submissions are penalized 20%; no late assignments accepted after 1 week EMSE 6817 - Class 1 - Slide 11 Exams Any variation of multiple choice, multiple answer, true/false, FITB, short answer and short essay Midterm (35% of grade): Covers all material from Weeks 1-5 Opens 8 PM EST Saturday, Dec. 21, due 8 PM EST Monday, Dec. 23 Final (35% of grade): Focus is on Weeks 6-10 (which incorporate concepts from Weeks 1-5) Opens 8 PM EST Saturday, Jan. 25, due 8 PM EST Monday, Jan. 27 There will be no exceptions in the exam window If there’s a risk of a real or possible conflict, mitigate the conflict If a conflict comes up near exam time, mitigate the conflict EMSE 6817 - Class 1 - Slide 12 Honorlock Testing Minor: Radio/TV in the background Honorlock exam policy Someone enters the room Sit at a clean desk or table in a quiet area Sitting on a couch Students may use only native calculators on the PC or Mac (you won’t Out of camera view briefly (less need one) than 5 minutes total) Only use one computer monitor Second monitor (off) on the desk Students may use one formula sheet 8.5 x 11 (letter size, front and Improper lighting back) Using headphones Not properly adhering to these parameters will result in significant Wearing hats, sunglasses, etc. number of violations of Honorlock exam policy Honorlock violations will be reviewed following the exam to Major: determine Browsing the web Number and nature of minor violations Using a phone Second screen Number and nature of major violations Out of camera view for more Violations will be reported to the SEAS Online office, who will than 5 minutes determine the appropriate sanctions Communicating with another A practice exam is available now to ensure functionality of the system. individual by any means EMSE 6817 - Class 1 - Slide 13 Questions? Introduction to MBSE MBSE - Decomposed Model-Based Systems Engineering EMSE 6817 - Class 1 - Slide 16 MBSE - Decomposed Model-Based Systems Engineering What is a system??? EMSE 6817 - Class 1 - Slide 17 Definitions of ‘system’ Several definitions, with common themes: “A system is a set of interacting elements that work together to accomplish some purpose” “A system is an assemblage or combination of functionally related elements or parts forming a unitary whole” “A system is a set of interrelated components functioning together toward some common objective(s) or purpose(s).” When designing a system, define the purpose of the system so that the system components can be engineered to provide the desired functions Borky, John & Bradley, Thomas. (2019). Effective Model-Based Systems Engineering. 10.1007/978-3-319-95669-5. Blanchard, B. S., & Fabrycky, W. J. (2011). Systems engineering and analysis. Upper Saddle River, N.J: Pearson Prentice Hall. EMSE 6817 - Class 1 - Slide 18 Aspects of a System Aspect Description Components The parts of the system Attributes Properties of the components and of the system as a whole Relationships Links or connections between pairs of components as a result of engineering the attributes of both components so that the pair operates effectively together in order https://en.wikipedia.org/wiki/Gas- fired_power_plant#/media/File:Berlin-mitte_heizkraftwerk- to achieve the purpose of the system mitte_20060605_629.jpg When designing a system, define the system of interest by specifying its limits, boundaries, or scope. Blanchard, B. S., & Fabrycky, W. J. (2011). Systems engineering and analysis. Upper Saddle River, N.J: Pearson Prentice Hall. EMSE 6817 - Class 1 - Slide 19 System or Not A System? https://www.istockphoto.com/ EMSE 6817 - Class 1 - Slide 20 Complexity, Technological Growth & Change Technological growth is happening continuously and rapidly (think about the technology you’re using now compared to 10 years ago, compared to 20 years ago) Development of systems blurs boundaries between engineering disciplines and necessitates a team with individuals aware of the relationships between the specialties Additional factors to consider beyond technical and business: environmental, political, social, cultural, etc. Demand for better, more efficient systems EMSE 6817 - Class 1 - Slide 21 MBSE - Decomposed Model-Based Systems Engineering What is systems engineering??? EMSE 6817 - Class 1 - Slide 22 Systems Thinking In order to create systems, it is necessary Environment to engage in ‘systems thinking’ An approach for dealing with complexity Input Output System Systems thinking is a perspective based on systems theory where one is aware of the whole of the system and how the parts within that system interrelate. Environment Systems thinking starts with the system as a black box and how it interacts with the Input Output environment. System Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities. 4 Edited by David D. Walden, Garry J. Roedler, Kevin Forsberg, R. Douglas Hamelin and Thomas M. Shortell. Hoboken, NJ: Wiley, 2015. Blanchard, B. S., & Fabrycky, W. J. (2011). Systems engineering and analysis. Upper Saddle River, N.J: Pearson Prentice Hall. EMSE 6817 - Class 1 - Slide 23 Origins of Systems Engineering 1930s/40s: Origins of modern SE British multidisciplinary analysis of air defense system Bell Labs NIKE missile development 1950s: RAND Corp recommends adoption of term ‘systems engineering’ 1960s: Formulation of the field of study known as ‘general systems theory’ Central tenant: A conceptual framework based on the principle that the component parts of a system can best be understood in context of the relationships with each other and with other systems, rather than in isolation. 1990: National Council on Systems Engineering established SE emerged as a discipline as an effective way to manage complexity and change. Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities. 4 Edited by David D. Walden, Garry J. Roedler, Kevin Forsberg, R. Douglas Hamelin and Thomas M. Shortell. Hoboken, NJ: Wiley, 2015. EMSE 6817 - Class 1 - Slide 24 What is Systems Engineering? A variety of definitions exist; one from SE Handbook v4 provided below: “…an interdisciplinary approach and means to enable the realization of successful systems. It focuses on defining customer needs and required functionality early in the development cycle, documenting requirements, and then proceeding with design synthesis and system validation while considering the complete problem: operations, cost and schedule, performance, training and support, test, manufacturing, and disposal. Systems engineering integrates all the disciplines and specialty groups into a team effort forming a structured development process that proceeds from concept to production to operation…” (p.11) Systems engineering is an interdisciplinary approach for bringing systems into being. Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities. 4 Edited by David D. Walden, Garry J. Roedler, Kevin Forsberg, R. Douglas Hamelin and Thomas M. Shortell. Hoboken, NJ: Wiley, 2015. EMSE 6817 - Class 1 - Slide 25 Systems Engineering Areas of Emphasis 1) Top-down approach: viewing the system as a whole 2) Life-cycle oriented: address all phases of the system, beginning to end 3) Initial definition of system requirements 4) Interdisciplinary throughout Blanchard, B. S., & Fabrycky, W. J. (2011). Systems engineering and analysis. Upper Saddle River, N.J: Pearson Prentice Hall. EMSE 6817 - Class 1 - Slide 26 The Systems Engineering “Vee” Conceptual Operation/ Development Maintenance Requirements Verification/ Validation Architecture Integration/Test Design/Implementation EMSE 6817 - Class 1 - Slide 27 MBSE - Decomposed Model-Based Systems Engineering EMSE 6817 - Class 1 - Slide 28 What is a model? Again, a variety of definitions: A model is an abstraction of a system -> a simplification of the actual system “A simplification of reality intended to promote understanding” https://www.motor1.com/news/398825/detailed-audi- It cannot contain every possible piece of information rs7-diecast-model-car/ about the system. Model is not necessarily wrong or incomplete so long as it contains the relevant and necessary information. https://www.simscale.com/blog/2016/03/what- everybody-ought-to-know-about-cfd/ Holt, J. Systems Engineering Demystified: A practitioner's handbook for developing complex systems using a model-based approach. 2021. Packt Publishing Bellinger, Gene. 2004. Mental Model Musings. https://www.systems-thinking.org/simulation/model.htm EMSE 6817 - Class 1 - Slide 29 MBSE - Decomposed Model-Based Systems Engineering EMSE 6817 - Class 1 - Slide 30 What does it mean to be ‘model-based’? In the context of engineering design… A model or set of models is central repository for an analysis or for design decisions The model is the definitive authority of information Example: Model-based design - model contains annotated 3D geometry with product manufacturing information, unifying design, manufacturing, quality. EMSE 6817 - Class 1 - Slide 31 MBSE - Decomposed Model-Based Systems Engineering EMSE 6817 - Class 1 - Slide 32  What is Model-Based Systems Engineering? “The formalized application of modeling to support system requirements, design, analysis, verification, and validation activities, beginning in the conceptual design phase and continuing throughout development and later life cycle phases” A system model constitutes the primary artifact of the systems engineering process Shift in focus from producing/controlling documentation about the system to managing/controlling a model of the system MBSE is not a subset of systems engineering The goal of MBSE is the same as the goal of systems engineering: to realize successful systems. INCOSE Systems Engineering Vision 2020 (2007) EMSE 6817 - Class 1 - Slide 33 Discussion Question Based on the definition of MBSE, what would you expect some of the benefits of MBSE to be? Or stated differently, what are the motivations for MBSE? EMSE 6817 - Class 1 - Slide 34 Motivation/Expected Benefits of MBSE Improved communication Increased ability to manage system complexity Improved product quality Enhanced knowledge capture Reduced development risk Increased productivity EMSE 6817 - Class 1 - Slide 35 Brief History of MBSE 1993 – Wayne Wymore’s book introducing mathematical foundation for MBSE 1995 – Unified Modeling Language created 2003 – Requirements released by OMG to extend UML to support systems modeling 2006 – SysML specification adopted by OMG 2007 – INCOSE introduced the MBSE Initiative in January 2007 – SysML 1.0 released in September 2009 – First edition of ‘A Practical Guide to SysML’ 2014 – ‘SysML Distilled’ released 2017 – RFP for SysML v2 released 2022 – SysML 1.7 released 2023 – SysML 2.0 Beta spec released EMSE 6817 - Class 1 - Slide 36 Google Trends: MBSE https://trends.google.com/trends/explore?date=all&geo=US&q=mbse EMSE 6817 - Class 1 - Slide 37 MBSE Throughout the Lifecycle Conceptual Development Use model to support dialog with stakeholders Assess alternative system concepts Model operational scenarios Requirements Capture requirements, decompose requirements, perform requirements analysis Allocate requirements, create traceability The primary output of MBSE is a model of the system under development. EMSE 6817 - Class 1 - Slide 38 MBSE Throughout the Lifecycle, cont. Architecture Describe components/subsystems of system Describe interfaces (internal & external) Describe behaviors Create traceability to requirements Design/Implementation Capture baseline design Support analyses & trade studies EMSE 6817 - Class 1 - Slide 39 MBSE Throughout the Lifecycle, cont. Integration/Test Integrate system in accordance with system architecture Verification/Validation Verify requirements with test cases specified in the system model Operation/Maintenance Operate system in accordance with conceptual model Maintain, upgrade system based on attributes described in system model EMSE 6817 - Class 1 - Slide 40  Process, Methods, Tools, Environment J. N. Martin, Systems Engineering Guidebook: A Process for Developing Systems and Products, CRC Press, Inc.: Boca Raton, FL, 1996. Estefan J.A., Weilkiens T. (2022) MBSE Methodologies. In: Madni A.M., Augustine N., Sievers M. (eds) Handbook of Model-Based Systems Engineering. Springer, Cham. EMSE 6817 - Class 1 - Slide 41 Discussion Questions Describe a time when technology made your systems engineering efforts more challenging. --Or-- Describe any challenges that you may have faced in your organization’s culture as you’ve tried to implement MBSE (or a similar change). EMSE 6817 - Class 1 - Slide 42 Three Pillars of MBSE Modeling Language Modeling Method Modeling Tool Defines kinds of How the system modeler Means for creating model elements or modeling team Complies with rules of Relationships between performs design tasks to modeling language elements create a system model Vary in cost, capability, Notations you can use to Ensures model and compliance with display elements and consistency language their relations Ensures team is working to common objective Examples: Cameo, Examples: SysML, UML, Examples: OOSEM, Rhapsody, Enterprise BPMN Harmony, MagicGrid Architect EMSE 6817 - Class 1 - Slide 43 Discussion Question Why do we use a modeling tool in systems engineering? Why not use Visio or the diagramming capabilities of Power Point? EMSE 6817 - Class 1 - Slide 44 Model Scope and Purpose Just as was the case in ‘traditional’ SE, the model must have a scope and purpose. Model purpose: What are the short- and long- term uses of the model? Who are the stakeholders? Components of the scope of a model: Breadth: which parts of the system need to be modeled? Depth: how many levels down the system hierarchy must you model? Fidelity: how detailed does the model need to be? EMSE 6817 - Class 1 - Slide 45 Note about this course & textbook Focus of this class SysML MBSE Focus of your textbook EMSE 6817 - Class 1 - Slide 46 Introduction to SysML What is SysML? Officially the OMG Systems Modeling Language (OMG SysML®), but SysML for short Object Management Group (OMG) is the standards development organization that owns/maintains the SysML standard “SysML is a general-purpose graphical modeling language that supports the analysis, specification, design, verification, and validation of complex systems that may include hardware, software, information, personnel, procedures, and facilities” https://www.omgsysml.org/what- Intended to facilitate the creation of a cohesive and is-sysml.htm consistent model SysML is not MBSE. SysML is a commonly used language that is part of an MBSE solution. https://www.omgsysml.org/what-is-sysml.htm EMSE 6817 - Class 1 - Slide 48 SysML Evolution SysML Request for Proposals (RFP) developed jointly by OMG and INCOSE and issued by the OMG Version Date in March 2003. 1.0 September 2007 The RFP specified the requirements for 1.1 November 2008 extending UML to support the needs of the 1.2 June 2010 systems engineering community. 1.3 June 2012 The SysML Specification was developed in 1.4 August 2015 response to these requirements by the diverse 1.5 May 2017 group of tool vendors, end users, academia, 1.6 December 2019 and government representatives. 1.7 December 2022 The Object Management Group announced the 2.0 (beta) July 2023 adoption on July 6, 2006 and the availability of OMG SysML v1.0 in September 2007. [https://www.omgsysml.org/what-is-sysml.htm EMSE 6817 - Class 1 - Slide 49  SysML Evolution SysML “represents a subset of UML 2 with extensions needed to satisfy the requirements of the UML for Systems Engineering RFP” Some rules of SysML are defined in the UML specification Examples: The SysML ‘NestedConnectorEnd’ is an extension of the UML ‘ConnectorEnd’ and the SysML ‘ValueType’ is an extension of the UML ‘DataType’ https://www.omgsysml.org/what-is-sysml.htm https://www.omgsysml.org/what-is-sysml.htm EMSE 6817 - Class 1 - Slide 50 Diagram vs. Model Diagrams are used to present a Model – all elements view of the model; there must be a specific purpose. Diagram – selected elements Only some elements of a model are shown on a given diagram. A model element could appear on zero, one, or many diagrams. Model elements may be visualized on diagrams or in tables / matrices. Changes in the model are propagated to all diagrams Elements removed from diagram remain in the model Elements removed from the model are removed from all diagrams EMSE 6817 - Class 1 - Slide 51 Diagram Frames, Header, & Content Diagram Header Every SysML diagram must have a Diagram Type [model element type] model element name [diagram name] diagram frame which encloses the content Diagram header contains: Diagram Content Area Diagram kind (abbreviated) Model element kind Model element name Diagram name Diagram content area graphically shows the model elements of interest. Diagram Frame EMSE 6817 - Class 1 - Slide 52 Kinds of model elements by diagram Each diagram represents a model Diagram Valid model element types element; there are restrictions on what can be represented by each Block Definition Package, model, model library, view, block, diagram. constraint block The model element type and name Internal block Block represent the ‘namespace.’ Activity Activity The namespace is a model element Sequence Interaction that is allowed to contain other State Machine State machine elements Use Case Package, model, model library, view Namespace Requirement Package, model, model library, view, requirement Parametric Block, constraint block Package Package, model, model library, view, profile EMSE 6817 - Class 1 - Slide 53 SysML Diagram Taxonomy 9 types of diagrams in SysML, which fall in 4 categories: 1. Behavior Sometimes 2. Structure referred to as the 3. Requirements ‘pillars of SysML’ 4. Parametrics Carry-over, modified, and new diagrams from UML 2. SysML has abbreviations for each diagram type https://www.omgsysml.org/what-is-sysml.htm A diagram is a presentation of a collection of elements from the system model. EMSE 6817 - Class 1 - Slide 54 Diagram Types – Package (pkg) Used for presenting the organization of the model. Packages are the fundamental unit of model organization Models are a kind of package Packages can be hierarchical Packages can be reused from model to model Diagram from Cameo Enterprise Architecture Sample Model – Hybrid Sport Utility Vehicle EMSE 6817 - Class 1 - Slide 55 Diagram Types – Requirement (req) Used for showing requirements and their hierarchies Requirement elements have a name, ID, and a text property at a minimum but could include other properties Shows how a requirement is satisfied, verified, refined, etc. Specification generally captured in packages. Diagram from Cameo Enterprise Architecture Sample Model – Hybrid Sport Utility Vehicle EMSE 6817 - Class 1 - Slide 56 Tables & Matrices Tables & matrices – not a type of diagram, but still allowed by SysML Non-graphical approach for efficiently showing large amounts of information Tables are useful for showing requirements Matrices are useful for showing relationships between model elements Images from Cameo Enterprise Architecture Sample Model – Hybrid Sport Utility Vehicle EMSE 6817 - Class 1 - Slide 57 Discussion Question If we use a system modeling tool to perform requirements analysis, do we need a requirements management tool like DOORS? Why or why not? EMSE 6817 - Class 1 - Slide 58 Diagram Types – Activity (act) Type of behavioral diagram used for modeling flow An activity is a controlled sequence of actions Activity diagram shows the actions of an activity as well as the inputs/outputs and control flows Control nodes allow flows to be split or joined in various ways Diagram from Cameo Enterprise Architecture Sample Model – Hybrid Sport Utility Vehicle EMSE 6817 - Class 1 - Slide 59 Diagram Types – Sequence (seq) Behavioral diagram showing the interactions between elements of the model as a sequence of message exchanges Structural elements are represented by ‘lifelines’ on the sequence diagram Different kinds of messages depending on the behavior being modeled Diagram from Cameo Enterprise Architecture Sample Model – Hybrid Sport Utility Vehicle EMSE 6817 - Class 1 - Slide 60 Diagram Types – State Machine (stm) Behavioral diagram used to show how elements of a system respond to internal and external events. Depicts the states of a system element and how it transitions from one state to another. Used in conjunction with other behavioral diagrams. Diagram from Cameo Enterprise Architecture Sample Model – Hybrid Sport Utility Vehicle EMSE 6817 - Class 1 - Slide 61 Diagram Types – Use Case (uc) Behavioral diagram showing the functionality of the system in terms of how it’s used to realize the objectives of its users (or entities that interact with the system) Functionality described in diagram is further elaborated using other behavioral diagrams Diagram from Cameo Enterprise Architecture Sample Model – Hybrid Sport Utility Vehicle EMSE 6817 - Class 1 - Slide 62 Diagram Types – Block Definition (bdd) Structural diagram used for defining blocks and their features and their relationships Blocks are the basic unit of structure in SysML Properties are the primary structural feature of blocks, including parts, references, and values. Diagram from Cameo Enterprise Architecture Sample Model – Hybrid Sport Utility Vehicle EMSE 6817 - Class 1 - Slide 63 Diagram Types – Internal Block (ibd) Structural diagram showing how the parts of a system are connected Connectors show there is an interface between two parts of a system Ports can be included to describe an interaction/ connection point. Diagram from Cameo Enterprise Architecture Sample Model – Hybrid Sport Utility Vehicle EMSE 6817 - Class 1 - Slide 64 Diagram Types – Parametric (par) Used for creating equations that constrain the properties of blocks Shows how constraint properties are connected Support a wide range of analyses, including trade studies Diagram from Cameo Enterprise Architecture Sample Model – Hybrid Sport Utility Vehicle EMSE 6817 - Class 1 - Slide 65 Diagram Interrelationships MBSE is not the diagrams – it’s about the model of the system! The diagrams are used to expose a view of the model. The model is a collection of information, and the diagrams show a portion of that information Relationships exist between the elements of the model, whether they are shown on a diagram or not. Relationships span the types of diagrams. Benjamin W. Stirgwolt, Thomas A. Mazzuchi & Shahram Sarkani (2022) A model-based systems engineering approach for developing modular system architectures, Journal of Engineering Design, 33:2, 95-119 EMSE 6817 - Class 1 - Slide 66  Views of a model A view is a container (a SysML package) of model content that is of concern to a particular stakeholder Holt suggests asking the following when considering if certain information should be in the model: Who wants to look at the view? Why do they want to look at the view? What information is needed in the view? What language should be used? Image from Holt Holt. (2021). Systems Engineering Demystified: A Practitioner’s Handbook for Developing Complex Systems Using a Model-Based Approach. Packt Publishing, Limited. EMSE 6817 - Class 1 - Slide 67  Diagrams in context of views A notation represents the means (language) for communicating with stakeholders Diagrams use the notation to communicate information Notation and diagrams used to visualize the different views of a model Image from Holt Holt. (2021). Systems Engineering Demystified: A Practitioner’s Handbook for Developing Complex Systems Using a Model-Based Approach. Packt Publishing, Limited. EMSE 6817 - Class 1 - Slide 68  Viewpoints A viewpoint is ‘a specification of the conventions and rules for producing artifacts that offer customized presentations of information contained in a SysML model’ A viewpoint specifies: stakeholders, concerns, purpose, language, method, and presentation (note: ‘presentation’ is not included in your textbook) Image adapted from Friedenthal, S., Moore, A., & Steiner, R. (2015). A practical guide to SysML: The systems modeling language. Holt. (2021). Systems Engineering Demystified: A Practitioner’s Handbook for Developing Complex Systems Using a Model-Based Approach. Packt Publishing, Limited. EMSE 6817 - Class 1 - Slide 69  Viewpoints Views of the model The System Aerodynamicist Mass Properties Engineer Propulsion Engineer EMSE 6817 - Class 1 - Slide 70 SysML View/Viewpoint Example https://mbse4u.com/2014/10/02/whats-new-in-sysml-1-4-view-and-viewpoint/ EMSE 6817 - Class 1 - Slide 71 Summary & Looking Forward Key Ideas from Today’s Lecture This is a course about MBSE, and I’m glad you’re here! MBSE is the future (or the current state?) of SE MBSE is not SysML, and SysML is not MBSE MBSE is focused on creating a model of a system A model must have a clear scope and purpose A model is not a diagram or set of diagrams Diagrams are views of the model There are 9 types of SysML diagrams, which focus on structure, behavior, requirements, and parametrics (analysis) Stakeholders have different viewpoints; the model must address each viewpoint EMSE 6817 - Class 1 - Slide 73 Coming Up… Next Lecture: Modeling frameworks, methodologies, tools, and other languages What you need to do: Read Ch. 1 (MBSE Overview), Ch. 2 (SysML Overview) HW 1 due Saturday 11/16/24 at 9:00 AM ET Take the ‘practice exam’ to ensure Honorlock works for you. EMSE 6817 - Class 1 - Slide 74