3 days.

To provide delegates with a sound understanding of the principles and process for using the Model Driven Architecture strategy to build Domain-based Platform Independent Models using UML.  To allow delegates to perform large-scale integration of such models to form a coherent set of components to use as the basis for platform-specific design and implementation.

This course is tool agnostic, and the techniques presented are applicable to all mainstream UML tools.

Technical Managers, Analysts, System Designers, Implementers, Testers

None

The course content covers the key elements of UML for describing the system architecture and for platform-independent domain modelling.  It incorporates real-world examples to illustrate how the various models are constructed and organised.  Delegates will consolidate their understanding through a series of practical group exercises.

Gives an overall picture of the Model Driven Architecture (MDA) process, and the primary UML artefacts produced by that process.

Deals with all aspects of modelling classes, associations, generalisations and attributes, using a variety of exercises.  The UML Class Diagram is the primary notation used.  Delegates gain confidence in class modelling using a variety of exercises, most based upon aerospace systems.

Explains the principles of partitioning a system into separate domains, and provides proven techniques for finding and defining a coherent set of domains.  The UML Package Diagram is introduced as a means of representing the domains and their dependencies.

Explains how use case analysis can be used to draw out and organise the system-level and domain-level requirements that will drive the architecture design process.

Covers the process of defining operations and building UML Statechart Diagrams for the classes in each domain.  It emphasises the importance of establishing the overall interaction pattern using UML Sequence Diagrams prior to construction of the individual Statechart Diagrams.

Shows how UML Sequence Diagrams can be used to understand how the system will operate and to link use cases to a set of components making up a system.

Provides illustrations of a number of common patterns used in platform independent models.  In each case, delegates are given guidelines about when to apply the pattern, and the benefits achieved. Delegates practice applying these patterns during a number of exercises based upon aerospace systems.

Explains how to integrate a system of domains.  It illustrates specification of domain interfaces, domain bridges and counterpart relationships.

Brings out the benefits of translation-based development using the Model Driven Architecture strategy.  It contrasts this approach with the more traditional elaborative methodologies.  It explains the strategies and principles behind model translation with real-world examples.

Brings together the key aspects of MDA and UML, and provides references to additional information.