Embedded Systems
Modelling using UML
|
|
|
Course Title |
Embedded Systems Modelling using UML |
|
|
Duration |
3 days |
4-5 days |
|
Format |
50% Lecture, 50% Workshop |
30% Lecture, 70% Workshop |
|
Code |
UMLE3 |
UMLE5 |
|
|
The Unified Modelling Language (UML) is a “Language” for: § Visualising § Specifying § Constructing § Documenting 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. § Systems Analysts, Architects, Designers and Programmers wanting to use the UML standard notation. § Project managers. 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. § Fundamentals of Information Technology § Object Oriented concepts § Embedded Systems modelling experience using other notations (optional) § Knowledge of a pure OO language, such as Java, Eiffel, C# or Smalltalk would be of benefit but is by no means mandatory Before §
Introduction
to Object Orientation |
|
Course Outline
The
UML – an Introduction Class
and Role modelling §
Classes, roles,
entities, things, objects, instances §
The Class
Diagram §
UML for classes
and relationships §
How objects
play various roles §
Attributes §
Associations
and aggregations §
Subclasses and
superclasses, groups of classes §
Invariants and
multiplicity §
Textual
modelling elements §
How to express
constraints. The Object Constraint
Language (OCL) Use
Case modelling §
Use Case §
Actor §
Use Case
Diagram §
<<include>> §
<<extend>> §
Use Case with
Extension Points §
Generalisation §
Using events to
identify use cases §
Use Case
Template §
Use Case
Modelling – The Process State
diagrams Interaction
Diagrams §
Sequence
Diagrams §
Collaboration
Diagrams Packages
and Collaborations Activity
Diagrams Deployment
Diagrams Review,
a conceptual model of the UML §
Building
blocks: things, relationships, diagrams §
Common
mechanisms: specifications, adornments, common divisions, extensibility
mechanisms (stereotypes, tagged values, constraints) Case
Study Lift Control System. *The course will use the client’s
preferred visual modelling tool or alternatively Visual UML. |
|
|
|
|
|
|
Wayland
Informatics Limited -- Home |