Description

The discipline of systems engineering (SE) is transforming, with much of the design information now captured in graphical models. System Modeling Language (SysML) is the primary tool used to create and retain this design information. Design information in SysML includes operational (stakeholder) definition, technical requirements, architectural analysis/structure, parametric definition, and test information, which together represent nearly the entirety of SE artifacts. An underlying database holds the SysML information so that data from one diagram appears synchronized on other diagrams. The benefits to the system architect are extensive.

This course shows how to architect and maintain a system definition using SysML. The course is filled with graphic examples from SysML models, but it is unlike other SysML courses in that the spotlight is on the system architecting. Students do not work on a computer during class, so that they can focus on the concepts rather than on use of a specific software tool. The course flows through familiar SE processes while teaching how the SysML models and structures support and enhance each task. We cover every SE activity and every SysML diagram, from Use Case and Activity diagrams to define operations; through State Machine, Sequence and Parametric diagrams to define system requirements; to Block Definition, Internal Block, and Requirements diagrams to define architectural structure. By the completion of this course, you will be able to apply SysML effectively in your own work.

In addition to our complete course materials, students also receive a copy of the seminal textbook A Practical Guide to SysML by Friedenthal, Moore, and Steiner.

Who Should Attend:

• Systems engineers
• Design engineers
• Technical team leaders
• System support leaders
• Others who participate in defining and developing complex systems.

Course Outline:

1. Systems Architecting and Engineering (1:30) – How systems architecting and systems engineering fit together; how model-based systems engineering (MBSE) has developed and what benefits it offers. A systems engineering model based on ISO-15288 and the INCOSE Handbook. What is an architecture? What is architecting? Six principles of MBSE. Survey of current SysML tools.
2. Basic SysML Concepts (1:30) – Where SysML came from; its purpose within the SE paradigms; the basic constructs of SysML. SysML underlying concepts; the information database; correct vs. complete. The SysML language. SysML and UML. The nine SysML diagram types. Common diagram structures: frames, headers, keywords, node symbols, path symbols, icons, notes.
3. Operational Definition and Analysis (3:00) – Understanding stakeholder views of the problem and the system; stakeholder requirements; using SysML to analyze and document the operational architecture. The concept of a use case (scenario). System boundaries and external actors. Use Case diagrams to define functionality. Activity diagrams to elaborate the behavior of a use case.
4. System Physical Architecting (3:00) – System physical design; how to use SysML to show the physical architecture; the end-state of architecting. The block as a representation of systems, components, or flow items. Block relationship types: association, composite, reference, generalization. Block Definition diagrams to depict structural block relationships. Internal Block diagrams to depict dynamic block relationships. Quantifiable characteristics in a block. Modeling interfaces using ports and flows. Modeling block behavior. Modeling classifications and variants. Requirements diagrams to show hierarchical requirements allocations. Requirements allocations in the block diagrams.
5. Additional SysML Constructs (1:30) – Some remaining features of SysML for better architecting; organizing the model; allocating relationships. Package diagrams to organize the model; types of organization; namespaces; imports and dependencies. Requirements containment hierarchies. Allocation between model constructs. Alternate constructs in SysML. Customizing SysML for projects or enterprises; SysML profiles; stereotypes
6. Architecting Challenge Exercise (5:00) – Student group work in four segments to practice the major aspects of architecting with SysML; creating the SysML model diagrams to define a system. Introduction to the remotely-piloted aircraft system. Part A: Operational definition with use cases and activities. Part B: Logical architecting with state machines, sequences, and parameters. Part C: Physical architecting and alternatives with block diagrams. Part D: Requirements allocation and package diagrams.
7. Summary (0:30) – Review of the important points of the course. Interactive discussion of participant experiences that add to the material. Continuing Education: This course qualifies for 2.1 CEUs or 21 PDUs

Instructor(s):

Glen Francisco (CSEP, PMP) received his Engineering Bachelor’s degree Aero/Astro Engineering from RPI (Troy NY) in ‘75, Engineering MS Aero/Astro Engineering from MIT (Cambridge MA) in ‘76 and MBA Information & Business Technology from FIT (Melbourne FL) in ‘86.

Mr. Francisco has supported military programs for the U.S. Army, Navy, Air-Force and Marine since 1976 as well as developed products for domestic & international commercial markets to include Instrumentation, Automotive, Aviation, Firefighting, Police, Law Enforcement and Security Surveillance since 2000.

Mr. Francisco remains certified as a practicing PMI PMP and INCOSE CSEP, as well as an ASIS certified Security CPP. He also is a National Registry EMT First Responder Medic and Commissioned Firefighter, Driver/Operator and Firefighter Instructor I & II. As a Commissioned Instructor, Mr. Francisco has demonstrated his proficiency of material knowledge, material development and dynamic presentation techniques to train others as well as creating classroom didactic and practical hands-on training techniques meeting specific learning objectives and teaching materials that can be effectively used by other instructors. Mr. Francisco has served as a staff Instructor to multiple local, county, state and federal agencies/facilities for over 18 years serving as a recognized practitioner, researcher, consultant and instructor successfully crossing the chasm between paid career and volunteer professionals.

William “Bill” Fournier is Principal Acquisition Systems Engineering with over 35 years of experience. Mr. Fournier taught DoD Systems Engineering full time for over three years at DSMC/DAU as a Professor of Engineering Management. Mr. Fournier has taught Systems Engineering at least part time for more than the last 25 years. Mr. Fournier holds a MBA and BS Industrial Engineering / Operations Research and is DOORS trained. He is a certified CSEP, CSEP DoD Acquisition, LSS GB and XPMP. He is a contributor to DAU/DSMC, defense contractor internal Systems Engineering Courses and Process, and INCOSE publications. Currently, He Is working for DoD Mission Engineering / Systems Engineering office supporting Space and Missile Defense Programs. Bill has written and assessed ~20 SEP/SEMPs.

The course was developed by Dr. Eric Honour, CSEP, international consultant and lecturer, has a 40-year career of complex systems development & operation. Former President of INCOSE, selected as Fellow and as Founder. He has led the development of 18 major systems, including the Air Combat Maneuvering Instrumentation systems and the Battle Group Passive Horizon Extension System. BSSE (Systems Engineering), US Naval Academy; MSEE, Naval Postgraduate School; and PhD, University of South Australia.