requirements analysis

16 Requirements


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).

Syndicate content