analysis

About Webel IT Australia

Webel - in operation in Australia since 2000 - is a Scientific IT Consultancy specialising in web application development, Content Management System (CMS) web sites, model-based software engineering and systems engineering using technologies such as:

Proprietor Dr Darren welcomes you to Webel IT Australia - the "Elements of the Web"

IT Training

Webel promotes graphical, model-based development and offers Advanced UML and SysML training seminars and workshops, including courses in model-based Java and XML engineering and how to progressively refactor existing systems using reverse-engineering into graphical UML.

Dr Darren is recognised as a leader in graphical software and systems engineering technologies and worked as an expert consultant on MagicDraw UML and the MD SysML Plugin.

The Doctor is in the Webel IT Australia house and available for hire

Just phone +61 (2) 9386 0090 or email Webel consultant Dr Darren in Bondi, Sydney, Australia, to ask about Webel's services for UML™-driven graphical software engineering with Java™ and XML, expert domain and requirements modelling with UML™ Parsing Analysis, graphical systems engineering with SysML, and custom data analysis. Webel also offers PHP-driven Drupal™ Content Management System (CMS) web sites, as well as audio, video, and media services, and unique Pure Data real-time audio and video synthesis services. (That's Dr Darren left working from his Webel office day and night.)

Latest résumé versions

Please visit:


SysML1.2 specification overview using hyperlinked SysML Parsing Analysis [ARCHIVAL]

The content or the technology discussed here is HISTORICAL or ARCHIVAL
The content or the methodology here is OBSOLETE !
Aug 2016: The SysML 1.5 Revision Task Force is in process. SysML has undergone significant changes since SysML1.2 !

This Webel reference and tutorial zone employs the UML™ Parsing Analysis recipe developed by Dr Darren Kelly, which technique exploits graphical and logical «wrapper» Components to relate text "snippets" from technical documents - in this case the OMG's SysML1.2 specification (with change bars) and - to (in this case) SysML model elements.

Please note that the SysML specification does not include the UML Component; the use of «wrapper» Components (which is supported in some tools, such as the SysML Plugin for MagicDraw™ UML) therefore goes beyond official SysML.

The (still incomplete) online trail is structured precisely after the SysML1.2 specification.

All SysML specification text appearing in this online reference trail is quoted, with permission, for educational and conformance analysis purposes only, and to permit convenient web page referencing under Dr Darren Kelly's UML™ Parsing Analysis recipe, and such quoted text remains © Copyright Object Management Group™ (OMG™).

Webel IT Australia maintains © Copyright in all additional UML™ Parsing Analysis models and diagrams of quoted specification text.

Good places to start include:

- Packages (SysML)

- 8.3.2.2 Block

The UML Parsing Analysis meta-process may be represented as stereotypes (from 2005)

The UML Parsing Analysis meta-process may be represented as stereotypes (from 2005)

An attempt to represent an older form of the UML™ Parsing Analysis with stereotypes (freestyle, not strongly bound here to UML Profiles stereotypes or base metaclasses). Note the emphasis on analysis depending on (possibly existing) design, not the other way around.

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

This content area is UNDER CONSTRUCTION or MIGRATION

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.

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
randomness