|
Feature
|
Benefit
|
|
UML™
1.4 modelling using interactive graphical editor
MaxUML
supports the 9 key diagrams defined in UML™ 1.4: Class,
Sequence, Collaboration, Statechart, Activity, Deployment,
Component, Snapshot and Object Diagrams.
|
The
OMG's Unified Modelling Language™ is widely accepted
as the de-facto standard for visual modelling of software
systems. This standard provides a consistent and practical
vocabulary for communication among developers. However UML™
and the techniques needed to address software development
are moving at pace. There is therefore the need for tools
that can be adapted quickly and effectively to an organisation's
best practices. MaxUML offers such a platform for evolution
by tracking standards while offering the possibility of bespoke
extensions and integrations. Its focus is on providing rich
semantic checking in a multi-user environment and dealing
with the practical issues of evolving development methods
- including those incorporating textual notations. |
|
Scenario
& Snapshot (Object Diagrams) support
Scenarios
represent the step-by-step execution of a Use Case or behavioural
element. Each step is characterised by a new system state.
Snapshots capture these states expressed in terms of the
creation / deletion / modification of system variables -
prototypical objects, attributes or relationships. MaxUML
manages the system 'context' propagating variables from
one snapshot to the next.
|
Modelling-by-example
is a powerful technique for accurately capturing behavioural
semantics. Often used by business and systems analysts, scenarios
and snapshots provide a mechanism for visualising and thereby
clarifying the transformations associated with required behaviour.
MaxUML's integrated support for scenarios and snapshots goes
beyond UML™ by allowing for the propagation of 'context'
variables from one snapshot to the next. This greatly simplifies
modelling and endorses consistency across the scenario. |
| Integrated
textual notation support |
While
UML™ supports a wide range of modelling objectives, there
are few methods that do not involve textual notations e.g.
requirements specifications, Use Cases, architectural specifications.
Classically these problems have been solved by providing import/export
mechanisms to text editors. This approach leads rapidly to
inconsistency between the model captured graphically in a
CASE tool and external text documents. MaxUML incorporates
a powerful text editor that ensures text documents and the
model are maintained consistent. |
|
Embedded
navigational paths
All
constraints and notes in diagrams and free-text sections
in documents can contain references to navigational paths,
using the UML™ Object Constraints Language. These are
validated as being consistent at all times. Renames and
deletions are propagated instantaneously providing immediate
visual feedback.
|
MaxUML's
support for the full OCL grammar allows the entry and validation
of business and system rules using the full power of OCL predicate
logic that are maintained consistent through the life of the
project. MaxUML can also be adapted to support other grammars
as required e.g. BPML |
|
Embedded
References
As
well as supporting OCL validated navigation paths, any text
field can contain any number of references to other model
elements.
|
Having
the ability to include hot references to any model element
helps to ensure that specifications remain correct and consistent
as the system specification evolves. |
|
Profile
construction
MaxUML
incorporates a powerful yet simple Profile construction
mechanism that allows an administrator to extend the UML™
meta-model through the use of stereotypes and tagged-values.Using
a standard UML™ meta-type as the base, an administrator
is able to control which constituents from the base meta-type
form part of the new stereotype as well as add additional
fields to it. This control extends to the appearance of
stereotypes on diagrams and documents and control over the
terms used in menus.These changes can then be published
as project standards for use by modellers.
|
Using
profiles an organisation can tailor UML™ to meet its
own specific method and process standards. Profiles form a
key component of the OMG™ Model Driven Architecture (MDAtm)
initiative. MaxUML's support for profiles is intuitive and
highly flexible - not requiring the administrator to learn
new skills such a programming language. Being so simple, the
administrator can experiment with notational extensions (what-ifs)
to quickly establish the most effective notational support
for a programme or project.Profiles are also a key component
of the OMG™ Model Driven Architecture initiative, used
to create a clear separation between the Platform Independent
Model and Platform Specific Model and the transformation between
them. |
| Interactive
Team Working / Multi-user Repository |
While
a check-in/check-out model works well for large-scale distributed
projects, it fails to meet the needs of a closely-knit, agile
development team. Project members often need to share information
in real-time - they cannot afford to go through a process
of reconciling disparate contributions on an intra-day basis.
MaxUML provides a truly seamless team-working approach through
a multi-user, version-managed repository. |
|
Internal
Version Control, Baselining and Transaction Management
The
MaxUML repository has facilities for versioning and baselining
states of the model, and for managing historical transactions.Each
transaction on the repository is recorded and can be retrieved
or rolled backed as required. Versions of the repository
can be defined (baselined) and worked on independently of
each other.Baselines permit particular states of the model
to be identified as key project targets and managed and
maintained as such.
|
The
ability to maintain multiple versions of a model is paramount
when developing products covering multiple delivery platforms,
different versions of operating systems/third-party software
or a historical client base.Similarly it is important that
the tool allow developers to work in their own 'sandbox' and
only when deemed appropriate, publish changes to the team. |
| Integration
with leading third-party configuration management and version
control products |
Large
projects are often physically distributed making interactive
team working problematic. In these scenarios, a check-in/check-out
model of operation is required. Through integration with ClearCase,
Visual Source Safe and other MCSCC-compliant configuration
and version management tools, MaxUML offers a robust integration
platform for physically distributed teams. |
| Export
of UML models through the XMI exchange format |
XMI
is the adopted OMG™ standard for tool information interchange.
MaxUML allows all model-elements to be exported in XMI for
import by other XMI-compliant tools. This provides a powerful
vehicle for integration.However, many existing tools holding
valuable project assets do not yet support XMI. SoftCASE Consulting
provide integration services to allow for such bespoke integration. |
|
Embedding
Files
All
model elements have the ability to own files, either stored
as blobs in the repository or as shortcuts to the external
files. These are version controlled along with the other
elements within the repository.
|
Any
model at any level will consist of many artefacts, a number
of which will be external to the modelling tool (e.g. requirements
documents, company design principles, architectural documents,
etc). Having the ability to either store them in the repository
or to reference them is important for ensuring all aspects
of a project are maintained together. |
|
Meta-Case
Origins
MaxUML
is built on a powerful meta-CASE technology that supports
the definition of both graphical and textual notations underpinned
by a strong semantic model.This same technology has been
used to deliver point solutions to such organisations as
the Swiss Post, BAE Systems, National & Provincial Building
Society supporting methods such as HOOD, Coad-Yourdon OOAD,
SSADM, IDEF0 and OMT.
|
Organisations
having specific methodological notations (graphical or textual)
that they would like to integrate with UML™ can either
call upon SoftCASE to develop these extensions or purchase
ToolBuilder™ development licences. This provides organisations
with maximal flexibility and control over the evolution of
their support tools. Moreover it allows them to leverage unique
competitive advantage through tools that closely track and
effectively support their evolving business and IT processes. |
UML™
& MDA™ are trademarks of the Object Management Group
ToolBuilder™ is a trademark of Critical Path Inc.
MaxUML™ is a trademark of SoftCASE Consulting
|
|