the artefacts
of a software-intensive system, not necessarily Object Oriented.UML is not concerned with the system
development processes, thus it is not a methodology per se.

The UML
standard was adopted in 1997 by the Object
Management Group (OMG).Due to its rigorous definition it became quickly the preferred notation
for any type of software-intensive system, no matter the underlying
technology.

This course
teaches participants how to express their thoughts in well-formed models of a system, using the most recent version of
UML (1.4).By modelling the system,
communication among team members and with the users improves and ideas for
improving the design come easier to mind.

The course
does not teach in a systematic way how to optimise design.

Exercises
throughout the course will help students consolidate the knowledge
acquired.Some exercises and examples
have real time specific, other have information systems specific.

TargetAudience

§Systems Analysts, Architects, Designers and
Programmers wanting to use the UML standard notation.

§Project managers.

Objectives

By the end of
the course participants should be able to:

§understand UML models in order to transpose
them correctly into programs

§enhance their knowledge of UML by self-study

§use the UML in creating well-formed models of
RT/Embedded Systems, under mentoring guidance.