SysML for
Systems Requirements Analysis

Course Description:

This course is aimed at SysML systems analysts and requirements engineers who are tasked with capturing and documenting systems requirements and demonstrating traceability. Practical exercises help to reinforce the theory.

SysML

Duration:

 1 day

Prerequisites:

No prior SysML experience is required.
A background in requirements analysis is helpful.

Equipment:

Webinar

For on-site delivery the customer should provide a suitable training room with a screen or projector to connect to our trainer’s laptop and a whiteboard or flipchart. All delegates require a PC or laptop running Enterprise Architect.

For webinar delivery delegates require a PC or laptop running Enterprise Architect with an Internet connection (a headset can be helpful). If you wish to test your environment join a test WebEx meeting: www.webex.com/test-meeting.html

Course Style:

60% theory, 40% practical.
Each module is accompanied by targeted exercises to allow delegates to apply the theory and become confident with new concepts and notation.

Delegate Handouts:

Each delegate receives a folder containing all the course slides and comprehensive theory notes which form excellent reference material. Folders also contain exercises and suggested solutions. Following successful completion of the course each delegate receives a certificate.

Course Modules:

  • Delegate background and objectives
  • Timetable and course outline

SysML Teaching – 0.5 hour

  • Advantages of graphical notations
  • History of SysML and UML
  • Key SysML diagrams
  • Process and capture requirements
  • System structure and dynamics

SysML Teaching – 0.5 hour

  • Importance of managing requirements
  • Differentiate needs from solutions
  • Requirements traceability
  • Strategies to control scope creep
  • Document requirements
  • Requirements levels and relationships
  • Categorise requirements

UML/SysML Teaching – 0.5 hour

  • What information to gather
  • Sources of information
  • Top 8 requirements elicitation techniques
  • When to use each technique
  • Common problems with elicitation

UML/SysML Teaching – 1 hour

Paper Exercises – 1.5 hours

  • Comparison with traditional requirements
  • Workshops and GUI prototypes
  • Model users as actors
  • External systems and timers
  • Actor definition and notation
  • Actor generalisation
  • Use case and scenario definition
  • Use case notation
  • Use case diagrams

UML/SysML Teaching – 1 hour

Paper Exercises – 1 hour

  • Use case specification
  • Use cases drive development
  • Include relationship
  • Extend relationship
  • Use case inheritance