UML & SysML modelling languages

This article provides a feedback about Sparx Enterprise Architect model transformation and XML Schema generation (XSD, JSON), involving the Schema Composer (introduced in Sparx EA v12).

Having a business class model in Enterprise Architect, I moved to the definition of the message structure for the application's services (purpose was to exchange data with another application involved in the overall process). I took the opportunity to assess EA model transformation and XML schema files generation based on the associated benefits:

• The existing Business Class diagram content can be reused to start the design.
• Traceability between the Business and Design models would enable impact analysis in the long run, whereas relevant information identified whilst carrying the design could be pushed to the business model.
• Enterprise Architect would facilitate publishing and sharing a model alongside XSD files with the dev team in charge of implementing the interfaced application. This step was required to agree on the exchanged data and associated services between both applications.
• Document generation features would facilitate producing Service Contract specifications.

This article illustrates the model transformation from a PIM to PSM, a custom model transformation template, and the use of the Schema Composer to generate an XSD File.