ARTiSAN Logo Prodotti     Download     Centro UML     Società     Clienti     Contattaci     Home

Novità     Eventi     Partner     Lavoro     Training     Supporto     Mappa Sito

Fornitore Leader di strumenti software di sviluppo UML tecnologicamente avanzati

[Sito in lingua inglese]
English

Training

Sommario
Corsi
Nord America
Europa
Libri
Home
Mappa sito
Contattaci
Mailing List
Parla di noi a un amico

Systems Engineering Using UML

Se siete interessati all'effettuazione del seguente corso d'addestramento presso i Vostri uffici in Italia, per favore mandate una email a .

EUROPE REGISTRATION     US REGISTRATION

Course Description

Designed specifically for real-time systems engineers, this training course shows the relevance of UML modeling techniques and ARTiSAN’s modeling extensions for system engineering activities on real-time or embedded system projects. Many UML courses are for software engineers and focus on software design techniques for object-oriented systems. Very few cover the ‘front-end’ system development activities that are of concern to the systems engineer. This course has been specifically designed to present a pragmatic approach, based on the de facto object-oriented modeling language, UML, for the definitions of system architecture, functionality and structure that are necessary for the production of high quality real-time/embedded systems. Examples and exercises are all based on real-time applications.

Course Objectives

  • Provide an understanding of the principles of object technology as they relate to systems engineers.
  • Enable attendees to apply UML and ARTiSAN extended modeling techniques to systems engineering.
  • Illustrate how the application of the these techniques can lead to better system definition, resulting in improved project control and enhanced product quality.

Attendees Will Learn

  • Essential object-oriented concepts, terminology and notation.
  • Object-oriented modeling techniques using UML.
  • How UML techniques can be applied to the definition and partitioning of real-time/embedded systems.
  • How ARTiSAN’s extended modeling techniques supplement UML to provide a more complete and consistent systems engineering view of the system.
  • How system definition information is used in software design and how to trace between definition and design.

Pre-requisites

  • Some understanding of real-time software characteristics and development.

Who Should Attend

  • Real-time systems engineers embarking on a project using object-oriented analysis and design for the first time.
  • Anyone on the project who needs to understand how UML-based modeling can be successfully applied to systems engineering activities.

Duration

3 days

Attendees Receive

  • An annotated copy of all course presentation material.
  • All course exercises and solutions.
  • A certificate of attendance.

Course Format

Presentations and discussion are used to convey concepts, techniques and notation. Case study exercises allow practical application of the techniques. Attendees work in small groups to complete a number of worked examples, providing hands-on experience of applying the techniques and familiarity with the concepts. Use is made of ARTiSAN’s Real-time Studio to facilitate an understanding of the relationship between the various models that comprise the system definition as well as these and the design models. All the examples are based on real-world, real-time and embedded systems.

Related Courses

Developing Real-time Systems using UML – this 5 day course provides a more in-depth understanding of UML-based software design for software engineers.

Course Outline

Introduction to Real-time Systems

  • Object-orientated and UML concepts.
  • Modeling and process overview.
  • Real-time systems and object-orientation.
  • UML and Real-time Studio - why are ARTiSAN's real-time modeling extensions necessary for a complete solution.

System Definition

  • Define System Scope –specifying the system scope and the I/O context.
  • Document the System Usage – specifying functionality through use cases and system interaction.
  • Document the System Modes – relating events and use cases.
  • Specify System Constraints – defining non-functional requirements.
  • Activity Diagrams – subsystem communication and other activities.
  • Partitioning the problem - components and packages.

Object Design Issues

  • Understanding software objects – typical real-time objects and how they can be derived from the system definition.
  • Object interaction – mapping use case system interaction to objects.
  • Classes and class relationships – why these are important.
  • Object dynamics – object lifecycle and behavior

System and Software Architecture

  • Architecture modeling – defining the hardware topology to ensure a complete and correct hardware/software mapping.
  • Concurrency Modeling – tasks and inter task communication.
  • Mapping the Software Architecture to the System Architecture.

Process Issues

  • Waterfall and incremental development approaches.
  • Adapting models for specific life cycle requirements.
  • Managing product and process change.