- follow the UML Components development process
- model the necessary UML business artefacts
- create enterprise component specifications
- design enterprise component implementations
- design with adaptability as key motivator
This course is aimed at the software architect
who wants to use the UML Components process to
develop enterprise components. The course
also provides material for the project manager
responsible for the development of a component
architecture. UML Components is a software
development process aimed specifically at creating
component architectures, and enterprise components
such as EJBs.
The course is suitable for analysts
and designers, as well as project managers.
This is a pencil-and-paper course, with
group exercises. We can demonstrate a variety
of support tools (such as Rose, Select, or Rhapsody).
However, we do not recommend using tools
for the exercises, as the details of driving them
distracts from the main issues of the process
and techniques; and they do not promote team working
in the class. The course is presented by
one of our senior consultants, each of whom has
at least ten years' experience in software development,
and at least three years' experience as a trainer
and consultant in a diverse range of application
UML Components software development
Overview of UML Components - a model-based
approach to developing enterprise
- business modelling: concepts and
- system requirements models
- responsibilities and collaborations
component-based design overview
- components and interfaces
- components and adaptability
Introduction to those parts of UML
used in the UML Components process.
- static models
- use-cases and tasks
- business models
- architecture of business process
- context for software requirements
- basis for component interface definition
System and component specifications
Specification of a software component,
application, or complete system.
- building a system specification
- system context
- defining system use-case goals
This section covers the key design
stages: assign responsibilities and
collaborations; then decouple roles
- designing system operations with
- decoupling, extensibility, reusability
- dependencies and visibilities
- translation to code [EJB examples]
Artefacts of component architecture,
and rules to guarantee flexibility.
- component architecture
- common models
- common couplings
- federated architectures
- component repositories
- what's in the repository
6. Component implementations
The final stage is to implement
components and apply current component
- pluggable code and connector
- synthesis of collaborations
Covers the available component standards.
- enterprise infrastructure
- J2EE, CORBA, DCOM
- 3 and n-tier
- defining interfaces in UML
- distributed system building tools
Summary of the main tasks and artefacts
of the UML Components process.
- business/conceptual modelling
- specification/requirements modelling
- design and implementation
- integration and test
- how to apply a management process:
note, when taught at your site, this
course is customizable. Modules
can be adapted, removed, added from
other courses, or even created.
1. UML Components software development process
3. System and component specifications
4. Component design
5. Component architectures
6. Component implementations
7. Enterprise components
8. Process review
book a public or onsite course, please contact
Clive Menhinick on +44 (0)161 225 3240, or email: email@example.com. Alternatively, use the booking form.
TriReme International Limited 2001-2006.
All rights reserved.