domain analysis

ecoSmart Building Pty Ltd

Type of organisation
Sydney, Australia
IT Consultant, software engineer, systems engineer, software architect, web developer

UML: TIPS: Analysis vs. Design: how to organise your UML models


In this Webel tutorial, anything that is not forward or reverse engineered is defined as an "analysis" element, and ONLy elements that are forward or reverse engineered to code are considered "design". The emphasis is on reuse of existing design elements, rather than on developing and forward engineering designs AFTER creation of analysis elements.

Dr Darren says that the name of the game is to:

Define analysis at a high level of abstraction (using, for example, «wrapper» Components as systems specifications) and then "go and find" existing designs that can be combined to do the job.

Tutorial: the UML Parsing Analysis recipe(s)

Before studying this tutorial trail readers should first examine some examples of «wrapper» Components. You should familiarise yourself with the wrapper concept, and with the difference between logical grouping, graphical grouping, and physical ownership (packaging).

Service: UML Parsing Analysis of technical documents and digital texts into graphical UML models

Webel - the home of Dr Darren's UML™ Parsing Analysis recipe - is delighted to offer a unique service, the translation of digital texts into UML models capturing requirements, systems analysis, systems architecture, and designs as graphical Unified Modeling Language™ (UML™) models.

What comes in ?

Technical documents from your domain, preferrably as digital text, however the conversion of older documents such as printed materials and scans into digital text is also offered as part of the service.

Candidate source text documents include:

What comes out ?

Professional UML™ Parsing Analysis models and diagrams corresponding to every sentence of the source document, together with overview diagrams generated from the union of those diagrams, including Package and Model overview diagrams, Use Case diagrams, systems and architecture diagrams, and professional reports.

In the case where the domain involves scientific or engineering topics with flows, port-based engineering diagrams employing Systems Modeling Language™ (SysML™) can be provided to supplement traditional software engineering diagrams.

Does it run ?

Where there is appropriate correspondence between the domain and software engineering elements, the analysis layer can be related to a design layer of reverse-engineered Java components from existing APIs, or forward engineered to the Eclipse Modeling Framework (EMF).

UML Parsing Analysis zone

Dr Darren explains:

I use the term UML™ Parsing Analysis to refer to a recipe I develop for parsing digital texts into graphical form and interpreting them as Unified Modeling Language™ (UML™) and Systems Modeling Language™ (SysML™) model elements, and as navigable, cross-referenced UML™ diagrams.

The UML™ Parsing Analysis approach is closely related to other recipes for modelling and diagramming domain ontologies with UML or OWL, however it is specifically designed to efficiently guide UML modellers in the sentence-by-sentence creation of highly navigable, easily traceable, graphically robust domain, systems- and analysis-models - in modern UML tools - from technical documents such as engineering design manuals and scientific articles.

This Webel zones feature explanations of the UML™ Parsing Analysis recipe(s), guidelines for interpreting text as UML™ and SysML, and many examples of applications of the technique to a wide range of domains, including software engineering, systems engineering, science, language, art, and of course the very UML specification itself !

The UML™ Parsing Analysis recipe has undergone significant evolution and improvement since 2000, from the naive use of text boxes and UML notes (0th order), then stereotyped Comment elements as «source» text containers related to analysis elements by loose handles (1st order), and eventually to the novel use of Classifiers (such as Components) with Relationships (such as Dependencies and Associations) to analysis model elements (2nd order). Readers should orient themselves primarily on the most recent examples, however the older examples are still of educational value.

The advanced form of the UML™ Parsing Analysis recipe achieves robust model element management using UML Model and Package elements for ownership, while using parasitic «wrapper» Components for convenient logical and graphical grouping of related elements - without disturbing the "physical" ownership structure - and for capturing the context provided by a snippet of «source» text. This also promotes easy navigation between diagrams in tools supporting hyperlinking of models elements to diagrams.

Syndicate content