This training course teaches the Model-Based approach to Systems Engineering (MBSE) using the SysML modelling language and Sparx Systems Enterprise Architect modelling tool. It is aimed at systems engineers, mechanical, electrical and electronis engineers, system architects and developers who want to produce a detailed model of the structure and behaviour of real world systems sufficient to form the detailed specification, architecture and design of equipment for industrial, automotive, nuclear, military and aerospace applications. The industry best practice model-based systems engineering (MBSE) techniques are based on the Systems Modelling Language SysML v1.5 and are taught within the context of systems engineering disciplines including specification, analysis, architecture, design, validation, verification and testing.
Students produce a model of their own system, or one from within their own domain, using the Sparx Systems Enterprise Architect SysML modelling tool in interactive modelling sessions guided by the intructor.
The models produced are sufficiently detailed to form the basis for the design of systems using a mixture of mechanical, hydraulic, electrical, electronic, firmware and software, real-time and embedded systems architectures. Each technique is taught to the level required for competence on a real project.
Systems Engineers, Mechanical Engineers, Requirements Gatherers, System Architects, Analysts and Developers with at least 2 years experience. This workshop is not suitable for those seeking certification as a step towards a qualification. See the Certification Policy for a detailed discussion.
The client is advised to provide adequate documentation regarding the overall project goals and functionality of the project to be modelled, under non-disclosure if necessary, at least 2 weeks prior to the start of the training, if possible. If no project documentation is available, then a stakeholder with a suitable knowledge of the problem domain should be available to take part in the workshop sessions. Stakeholder involvement in problem domain modelling sessions is always encouraged.
Courses normally start at 9.30am on the first day, 9.00am on subsequent days and finish at 5.00pm each day with an hour for lunch and a 15 minute break in the morning and again in the afternoon. Course attendance is normally limited to 12 students.
The client is expected to provide an appropriate venue, refreshments, high resolution projector or large screen, whiteboard or flipchart and at least one computer per two students loaded with at least the evaluation version of Enterprise Architect or another suitable modelling tool. For a discussion of the use of modelling tools, please see Modelling Tool Use on Courses. A printed course manual with copies of all presentations, exercises and solutions will be provided for each student. For a full discussion of on-site course logistics please see On-Site Course and Workshop Logistics.
The client is expected to provide an appropriate conferencing service that allows the instructor to join the online meeting, share their screen, talk to each and every student on the course and view their screen if necessary to support their individual modelling work. They should also provide a computer for each student loaded with at least the evaluation version of Enterprise Architect or another suitable modelling tool. For a discussion of the use of modelling tools, please see Modelling Tool Use on Courses. Copies of all presentations, exercises and solutions will be provided electronically. For a full discussion of remote course logistics please see Remote Course and Workshop Logistics.
A firm quotation for this course or workshop, delivered either onsite (in-house) at your UK-based premises or remotely (online), can be obtained from one of the Course and Workshop Price Calculators available on the CRaG Systems site. For on-site courses outside the UK, custom courses, or classes of greater than 12 students, please email: firstname.lastname@example.org or call +44 (0)1782 785045.
|Training Course Outline|
IntroductionPeople - Course Structure - Modelling - Systems Engineering - System Modelling Language SysML
Requirements ModellingRequirements Diagrams, Requirements and Hierarchy - Derived, Copy, Satisfy and Trace Dependencies - Test Cases - Problems, Rationale, Allocations and Callouts - Generating Documents - Managing Traceability - Repositories
Requirements Modelling Workshop
Specifying Functional Requirements with Use CasesSystem Use Cases and Actors - Primitive Use Cases and the Basic Course - Writing Effective Use Case Descriptions - Writing Sub-flows and Alternate Flows - 'Include' and 'Extend' Relationships - Modelling Timing Constraints
System Use Case Workshop
Block Definition DiagramsBlocks - Block Definition Diagrams - Namespace and Structure Compartments - Value Types, QuantityKind, Units - Enumerations - Stereotypes - Instance Specifications - Dependency - Reference Associations, Part and Shared Associations - Containment - Generalization
Block Definition Diagrams Workshop
Internal Block DiagramsParts and Properties - Internal Block Diagrams - Connectors and Item Flows - Ports, Connectors and Item Flows - Blocks and Value Types to Specify Ports and Item Flows - Interface Blocks and Blocks as Function and Data Types - Proxy and Full Ports - Signals to Specify Events and Messages
Internal Block Diagrams Workshop
Parametric ModellingConstraint Blocks - Parametric Diagrams - Constraint Properties
Parametric Modelling Workshop
Modelling Behaviour as ActivityActivity Diagrams - Activities, Activity Parameters, Parameter Sets - Actions, Action Pins, Control and Stream Pins - Objects - Control and Object Flows - Events, Signals and Interruptible Regions - Control Operator, Call Behavior Action - Control Nodes: Initial, Final, Decision, Merge, Fork and Join - Partition and Allocation - Hierarchy with Structured Activities
Activity Modelling Workshop
Modelling Interaction and MessagingInteractions, Messages, Operations and Methods - Sequence Diagrams - Diagram Links - Synchronous and Asynchronous Messages - Selection and Iteration - Execution Specification - Creation and Destruction - Timing Constraints
Interaction Modelling Workshop
Modelling State Dependant BehaviourThe Meaning of the State Model - State Machine Diagrams - States and Transitions - Events and Conditions - Actions and Activities - Hierarchy and Concurrency - Actions on a State - Consistency with Other Diagrams - Direct Implementation
State Modelling Workshop
Should the content of the available SysML courses not fit your exact requirements, then CRaG Systems can create a custom course for you. Please either email or call us to discuss your particular needs.
UML, BPMN, SysML and the corresponding logos are trademarks of the Object Management Group
Enterprise Architect, Sparx Systems and the corresponding logos are trademarks of Sparx Systems
CRaG Systems (UK) email@example.com 01782 785045
MBSE with SysML and Enterprise Architect Hands-On Workshop Training Course - 4 Days