Ecore model, graph nodes, and processors for architecture - architecture elements/building blocks, ... This model is intended to be a "physical" "reference implementation" of the TOGAF model containing helper classes and refinements.
For example, TOGAF defines a ViewPoint and a View. This model may define RepresentationSpec and Representation as parts of ViewPoint and View respectively. A representation by itself (e.g. a chart, a diagram, a list, or a table) might not be enough to address a stakeholder concern - it may need additional representations and textual description. So, a View is a unit or addressing stakeholder concerns by providing multiple related representations to the stakeholder.
The model shall be usable to define architectures and generate documentation. It also can be used as a starting point to create organization-specific architecture repositories, which contain structures reflecting existing organizaion ways of working. E.g. how people are organized, how information systems are tracked.
Use case: Load and publish the baseline model for analysis and to build new architectures on top:
- Use GitLab to scan org's source repositories
- Use Maven model to load
pom.xmlin the repositories - Use Java model to load
module-info.javain the repositories - Use Azure model to load information about the cloud runtime
- Use Excel model to load information from Excel spreadsheets
- Use org-specific models to load information from internal systems
- Resolve cross-references. E.g. Maven developer to a person in the organization directory
- Use the resulting model for analysis, solution generation, and generation of reports and web sites. ECharts model and ECharts Java can be used to generate visualizations