top header
top gradation HOME top vertical line top vertical line top vertical line top vertical line top vertical line top vertical line top vertical line menu gray
black line 2
menu gray tab More About ATI
menu blue ATI — Who We Are
white line
menu blue Contact ATI Courses
white line
menu blue List Of ATI Courses
white line
menu blue Attendees Testimonials
white line
menu blue The ATI FAQ Sheet
white line
menu blue Suggestions/Wait List
white line
menu blue New Courses
white line
menu blue Become an ATI Instructor
menu gray tab site resources
menu blue Acoustics & Sonar
white line
menu blue Rockets & Space
white line
menu blue GPS Technology
white line
menu blue ATI Blog
white line
menu blue ATI Space News
white line
menu blue ATI Site Map
white line
menu blue ATI Staff Tutorials
white line
menu blue ATI Sampler Page
white line
menu gray tab bar
menu gray tab courses
white line
menu blue Current Schedule
white line
menu blue Onsite Courses
white line
menu blue Register Online
white line
menu blue Request Brochure
white line
menu blue Free On-Site Price Quote
white line
menu blue Download Catalog
white line
menu blue Distance Learning
black line

System Architecting with SysML


Share |

Summary:

Technical Training Short On Site Course Quote

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.

Instructors:

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.

Dr. Scott Workinger

has led innovative technology development efforts in complex, risk-laden environments for 30 years in the fields of manufacturing (automotive, glass, optical fiber), engineering and construction (nuclear, pulp & paper), and information technology (expert systems, operations analysis, CAD, collaboration technology). He currently teaches courses on program management and engineering and consults on strategic management and technology issues. Scott has a B.S in Engineering Physics from Lehigh University, an M.S. in Systems Engineering from the University of Arizona, and a Ph.D. in Civil and Environment Engineering from Stanford University.

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 Requirements Modeling (2:00) Modeling technical requirements; the relationships between operations and requirements; how to document requirements and their relationships using SysML. Requirements, their forms and uses. Requirements diagrams to show relationships among requirements. Types of requirement relationships and how to show them in SysML. Requirements rationale in SysML. Constraints as a part of requirements; the constraint block. Parametric diagrams to define constraints. Constraint blocks to modify flows. Representing trade-offs. Modeling requirements verification.
  5. System Logical Architecting and Analysis (3:00) Requirements analysis using logical constructs; understanding the requirements better as a step toward physical system design; the logical architecture. Logical vs. physical architecture. Functional design vs. object-oriented design; how SysML supports either. The concept of a state; state transitions, triggers, guards, and effects. State hierarchies and operation calls. State Machine diagrams to analyze and document the event-based behaviors. Sequence diagrams to analyze and document the message-passing behaviors. Lifelines and interactions in sequences
  6. 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
  7. 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
  8. 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.
  9. 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

Tuition:

    Tuition for this three-day course is $1790 per person at one of our scheduled public courses. Onsite pricing is available. Please call us at 410-956-8805 or send an email to ati@aticourses.com.

spacer