|
|
|
|
|
|
|
|
|
UML Overview (continued) start UML - The Principal Models...Process Model - documented as Activity Diagrams (a special form of Statechart diagrams) these can represent processes at all levels
of the organisation from high-level overviews of core business processes (e.g. how sales orders are filled) to defining exactly how
a single function within a computer system achieves its purpose (e.g. how the monthly repayment on a fixed interest loan is calculated).
Use Case Model - a user-centric textual description of what a user of a computer system must do, and what the computer system will
do in response (but not how that computer system does it) in order to achieve a business goal. Also includes things called
Scenarios based on those use cases. Interaction Model - Sequence and Collaboration diagrams that allow very formal and unambiguous specification
(and documentation) of
how internal elements of the computer system must interact in order to achieve the
outputs the system should generate in response to the user actions specified in the Use
Case Model. State Model - Statechart diagrams that represent the lowest level of control over a system. They define exactly what states a system
can be in (e.g. a bank account can be in the state of being overdrawn or of being in credit) and what the system must
do in response to a change of state and what it can do whilst in a given state.
Class Model - Class diagram that shows the principal entities within a system, their attributes and operations, and the associations
between those entities (e.g. A bank account (entity) has a balance (attribute), can produce a statement (operation) and is associated with
many transactions (entities).
|
Please send mail to
webmaster@quicks.demon.co.uk with
questions or comments about this web site.
|
| Software Development IT Training Courses Workshops Mentoring |
| Home Site Map Services Contact Us Feedback Useful Links |