Software Product Lines (Pattern instantiation) with Drawio Java API

[pvlasov]

• Architects create diagrams capturing patterns, security and other relevant parties review the diagrams, diagrams are digitally signed and published to a searchable pattern catalog.
• When a pattern needs to be instantiated it can be done in a pipeline:
  • Networking/infrastructure takes a published pattern diagram and creates networking infrastructure, adds configuration details to the diagram or supporting files - it can be done automatically (executable diagrams) or manually.
  • Then the diagram is passed to development - it can be used to generate documentation with infrastructure details or it can also be used to generate code, e.g. initial "Hello World" microservices, CI/CD pipelines. Generation results, e.g. build jobs and source repositories URL's are also stored in the diagram and supporting files.
  • Development progress is pulled from an issue tacking system and is displayed on the diagram - completed pieces are shown in green, in progress in some other color, components with risks or behind schedule are shown in amber or red.
  • When development is completed and the solution is deployed the diagram is updated with deployment information and a production support site is generated from it. The site generation process pulls solution health information from monitoring systems and shows it on the diagram and on diagram element pages. For example, an overloaded component may be shown in amber, broken in red, and scheduled maintenance in grey.