| |
objectives
- gain enough
competence in business modelling to tackle a live
project
- acquire basic UML, a common language for talking
about requirements and design
- understand what major tasks are appropriate
to developing OO models
- know how to produce UML artefacts that can be
used in the software design stage of development
- learn the benefits of separating the business
and software models
overview
Business
modelling is a vital, but often overlooked, step
in your development process. UML
is a flexible tool that can be used to model both
your business and software. The artefacts
from the business model are an invaluable input
into the software design process. To be
of use, it is imperative that your business models
are small and concise. This
course shows how to use the UML notation most
effectively to model your business. The
course provides especially strong coherence between
the different notations used in UML, making it
clear when there are inconsistencies or holes
in the analysis. This saves a lot of money in
the later stages of a project. Working
with your analysts on a project, is the best way
to transfer business modelling skills. We
try to match consultants and mentors who have
extensive project experience within your business
domain.
The course is suitable for business analysts
wishing to develop clear precise methods of discussing
the business and business requirements at a high
level, clear of implementation detail; and managers
and software architects wishing to understand
the strategic issues in migrating to, and getting
the best out of a model-based approach with UML.
Each
section uses numerous small examples and exercises.
Two major examples are followed through
the course: one discussed in class as each point
is introduced, and one developed by participants
in groups. Depending on the background of the
participants, the exercises can be chosen from
commercial or process control areas. The
course is presented by one of our senior consultants,
each of whom has at least ten years' experience
in business analysis and modelling, and at least
three years' experience as a trainer and consultant
in a diverse range of application areas.
content
|
1.
Business modelling
Covers techniques of identifying
business concepts and tasks
- building a business model
- finding use-cases
- connecting use-case and class views
- the dictionary
- uses of business model
- architecture of business process
- context for software requirements
- basis for component interface definition
2. UML basics
Introduces relevant parts of UML
- static models
- objects, types, attributes, snapshots
- subtypes
- dynamics
- use-cases and tasks
- event charts
- state charts
- UML notation review
- documentation style
3.
Requirements engineering
Review of specification of business
requirements, requirement gathering,
and requirements engineering
- 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.
Domain models
A look at existing domain models from
within the participants' areas of
business
|
5.
Development: fundamental tasks
This section reviews the tasks and UML
business model deliverables, involved
in a typical object-oriented development
project.
- the main tasks and artefacts
- business/conceptual modelling
- specification/requirements modelling
- architecture
- design and implementation
- integration and testing
- short-cycle development
- spiral model
- phased development
- role of prototyping
6.
e-business and distributed systems
- architectures
- 3 and n-tier
- from the business model to UML components
- distributed system building tools
7.
Re-engineering existing systems
- business process and existing asset
analysis
- wrapping Vs re-engineering
- low-risk re-engineering path
8. The model-based development process
Shows how business modelling fits
with the rest of the development cycle.
- the main tasks and artefacts
- business/conceptual modelling
- specification/requirements modelling
- architecture
- design, Implementation
- integration and test
- short-cycle development
- spiral model
- phased development
- role of prototyping
|
|
Please
note, when taught at your site, this
course is customizable. Modules
can be adapted, removed, added from
other courses, or even created.
|
|
timings
Day 1
1. Business modelling
2. UML basics
3. Requirements engineering
4. Domain models
Day
2
5.
Development: fundamental tasks
6.
e-business and distributed systems
7. Re-engineering existing systems
8. The Model-based development process
To
book a public or onsite course, please contact Clive Menhinick on +44 (0)161 225 3240, or email: clive@trireme.com. Alternatively, use the booking form.
©
TriReme International Limited 2001-2006. All
rights reserved. |
