Skip to content

v5.12.0 - OOAD and JDL revised, Language Server (LSP) Architectural Spike
Compare
Choose a tag to compare
@stefan-ka stefan-ka released this 19 May 10:02
v5.12.0
1b2a891

Changes in release v5.12.0:

  • The CML grammar for Use Cases and User Stories has been enhanced in order to generate Entity attributes and references in the OOAD transformations
  • In addition, the grammar supports specifying Use Cases according to the brief or casual template suggested by A. Cockburn.
    • An example Use Case out of his book modelled in CML can be found here.
    • Besides the improved interactions grammar, we added the scope and level attributes.
  • The OOAD transformation step 2 (generating subdomains) generates Entities with attributes and references by using the CML data mentioned above.
  • The input validations on the OOAD transformation dialogs (UIs) have been improved
    • Whitespaces etc. in input names no longer lead to transformation exceptions
  • The PlantUML generator no longer needs a Context Map in the input model.
    • The class diagrams for Bounded Context or subdomains can be generated without Context Map.
    • The generator just needs one of the following inputs:
      • a Bounded Context (with an Aggregate and Entities),
      • a Subdomain (with Entities)
      • a Context Map
  • We introduced a color coding in the PlantUML class diagrams according to the Event Storming colors.
    • Extract of an example:
      image
    • Encoding:
      • Domain Event: orange
      • Command: blue
      • Aggregate: yellow
  • The JDL template for microservice generation uses CML Value Objects as well.
    • Value Objects are mapped to JDL Entities now.
  • The Context Map generation OSGi bundle no longer contains a dependency to javax.annotations
    • Repeatedly caused problems in Eclipse.
  • We implemented a first "Architectural Spike" of our language server based on LSP here:
Assets 17
Loading