|
1.
The model-based approach to integration
Introduction to the main ideas
behind the model-based approach to
developing components for enterprise
integration.
- business modelling: concepts and
tasks
- system requirements models
- responsibilities and collaborations
- persistence, GUI, distribution
- component-based design overview
- components and interfaces
- components kits and architecture
- component and reuse culture
- patterns in the process
2.
UML for EAI (Enterprise Application
Integration)
This section introduces those parts
of UML relevant to EAI
- static models
- objects, types, attributes, snapshots
- subtypes
- dynamics
- use-cases and tasks
- event charts
- state charts
- building a business model
- finding use-cases
- connecting use-case and class views
- the dictionary
- UML notation review
- uses of business models
- architecture of business process
- context for software requirements
- basis for component interface definition
- documentation style
3.
Requirements and component specification
This section deals with the specification
of requirements of a software component,
application, or complete system. More
modelling patterns and techniques
are investigated.
- system context models
- high-level operation specs
- state charts for system models
- meaning of 'model'
- how to start abstract and get more
detailed
- event charts: horizontal and vertical
expansion
- elaborating models
- relating the levels of detail
- building a system spec
- system context
- defining system use-case goals
- modelling patterns
4.
Component design
This section covers the key design
stages: assign responsibilities and
collaborations, decouple roles and
components.
- separating core from GUI, persistence,
and other layers
- selection of control objects
- designing system operations with
messages
- decoupling, extensibility, reusability
- dependencies and visibilities
- the class dictionary
- translation to code
|
5.
Domain coupling
The linkage of the 'core(s)' to presentation,
persistence, and other layers.
- GUI
- MVC and reification of use-cases
in UI objects
- persistence: proxy and building
atop object and relational DBs
- networks: layering
6.
Reuse and adaptability
Reuse does not come automatically,
and requires not only appropriate
technology, but also management and
motivation at the corporate level.
- management and economics of reuse
- component repositories
- what's in the repository
- components, frameworks, patterns,
and plans
7.
Pluggability and frameworks
- partial models (views) as reusable
artefacts.
- generalization of two example static
models
- collaborations: generic designs
for interactions
- roles
- synthesis of collaborations
- pluggable code and connector protocols
- component kits and building tools
- component architecture
- common models
- common couplings
- wrapping existing assets
- product Vs component building
- frameworks: generic models
- generalization of two example static
models
- collaborations: generic designs
for interactions
- roles
- synthesis of collaborations
8.
Re-engineering existing systems as
enterprise components
- architectures
- J2EE, CORBA, DCOM
- 3 and n-tier
- EJBs
- defining interfaces in UML
- distributed system building tools
- patterns for distributed systems
- business process and existing asset
analysis
- wrapping Vs re-engineering
- low-risk re-engineering path
|
|
Please
note, when taught at your site, this
course is customizable. Modules
can be adapted, removed, added from
other courses, or even created.
|
