UML & SysML modelling languages

Expertise and blog articles on UML, SysML, and Enterprise Architect modelling tool

version francaiseTwitterVideos UMLChannel SparxSystems EA YouTubeLinkedIn

VISEO EA UML to JHipster Generator MDG Technology

This article shares an MDG Technology that integrates Sparx Enterprise Architect UML models with the free and open source JHipster RAD (Rapid Application Development) framework.

VISEO EA UML to JHipster Generator MDG produces JDL (JHipster Domain Language) content from UML models maintained in Enterprise Architect. This output can be used with JHipster to create the application's entities, including properties and relations.

Not being able to find a suitable tool that generates JHipster entities from UML models, I started such integration for a software application that has been implemented with JHipster 2. This work has been tested and used by VISEO JHipster experts and developers.

Update (31/10/2017): this project is now available from GitHub (MDG-Sparx-EA-UML-JHipster Github project) and will evolve to support new JHipster JDL definitions.

Note: a french version of this article is available here (version FR).

Please click here for more information.

This article is intended to introduce and share tailored searches for SysML Requirements in Sparx Enterprise Architect modelling tool.

Enterprise Architect built-in requirements have been customized by Sparx Systems according to the OMG SysML specifications by adding the following properties:

  • text: The textual representation or a reference to the textual representation of the requirement.
  • id: The unique id of the requirement.

Text and id are available as tagged values, illustrated below.

sysml requirement id text tagged values sparx enterprise architect

When standard (non-SysML) requirements are used, it is common practice to run searches on the title, alias (reference) and notes (description). When possible, a systems project team can choose to use these fields in SysML requirements as an alternative to the OMG "id" and "text" properties.

Instead if the id et text tagged values must be used, there can be issues in running searches based on Enterprise Architect default installation.

That's why I ended up defining the following SysML searches, available via the UMLChannel MDG Technology.