Advanced UML Training Course UK:
|
Who Should Attend
Software professionals trained and experienced in object-oriented techniques,
which need to acquire a thorough understanding of UML 2.0.
Software architects, Senior software developers, Software development team leaders
Prerequisite Skills
The participant must already have the skills to make UML models using reasonable
advanced modelling notation, spanning the main UML diagrams.
Some exposure to UML extensibility elements such as stereotypes and UML profiles
may be beneficial.
Duration
2 days
Course Content
Course content has been developed for real-world, commercial scenarios by our
expert instructors. See below for detailed syllabus, or if you have a technical query email
Requirements gathering.
Tools and techniques for identification and
analysis of requirements.
Volere and FURPS guidelines.
Identifying business objects.
Use-Case driven Requirements analysis.
The supplementary specification.
What goes into the supplementary specification?
Making a Glossary document.
Deciding on a Go/No-Go for the Project.
Service contracts
Fine grained vs coarse grained services
Not everything must be reusable
Mapping Use cases to service types
When to split the domain model.
Criteria to group conceptual classes together.
Using packages to organize the domain model.
Exercise: create service packages.
Linking the domain model to the collaborations.
Wrap up of the Analysis activities.
Communication between team members.
Sharing work between analyst & developer.
The way forward: design tasks for the developer.
Interpreting system sequence diagrams.
The domain model.
Assigning responsibilities to classes and objects.
Extracting operations from a sequence diagram.
Identifying patterns.
The Ying/Yang of modeling.
Detailing object behavior.
The link between message and method.
Message sequencing.
Operations translated in collaboration diagrams.
UML Objects and messages.
Operation contracts.
When to use an operation contract?
The 5 categories for an operation contract.
Detailing pre-and post conditions.
Operation contract guidelines.
From domain model to class diagram.
Adding methods to the class diagram.
Showing temporary visibility.
What about method signatures?
UML profiles, stereotypes and tagged values
When to use object constraint language?
Using inv, context, pre and post.
Using collections.
OCL and executable UML.
Case study of an airline reservation system.
Exercise: create the domain model.
What are subsystems?
Grouping classes into subsystems.
Criteria to group classes into subsystems.
Why a UML profile for frameworks?
Business process modelling
Formal business modelling using UML and the
Eriksson/Penker patterns
Hands on tool-specific exercises
Tracing business models to systems
specifications
Composition and Aggregation.
Association classes.
Qualified associations.
Inheritance and Specializations.
Component interface description
What makes a good component and
interface
Issues in component design
Principles of componentisation
Principles of component design for
reuse/product families, extensibility, etc.
Lessons learned on real-world projects
Subsystem and Component Architectural
Patterns
Concurrency and Resource Management
Patterns
Distribution Design Patterns
Reliability Design Patterns
Deployment Patterns
Key ideas.
Scenario Modelling and Class
Reconstruction
Architecture Specification
Scenario Descriptions
Modes
Operation Effects
Parts and Ports
Tips and tricks for creating code from
classes.
Defining classes with collections.
Order of Implementation.
Creating methods from collaboration
diagrams.
Component document template
Interface specification template
Component examples
How to plan the different phases.
Assigning roles to team members.
Aligning Business and IT.
Project management issues.
SOA and executable UML.
|
|
|