Is there any guidance on how to properly capture the model/architecture of a solution? I understand how to assign technology product roles to a technology build. The editor doesn't seem to account for components to be defined like front-end, back-end and then to assign Technology Provider Usage to those components.
I believe this is the class relationship:
Composite Application Provider -> Application Deployment (Production) -> Technology Product Build -> Technology Build Architecture -> Technology Provider Usage
What I'm hoping to capture:
Application A -> Application A Deployment -> Front end -> Technology in the front end
Application A -> Application A Deployment -> Back end -> Technology in the back end
Dependency relationship between the front-end and back-end
I've tried deciphering the online docs for weeks and don't understand. I'm also trying to use the technology tab on the application editor, seems to only allow the Technology Provider Usages to be captured.
Thanks for any insight or clarify you can provide.
Solution Modeling
The meta-model already supports this requirement, but we do not currently have a high-level Editor for it. Prior to the upcoming introduction of our diagramming framework, this would have do be done using the back-end Capture screen.
More specifically:
Step 1
Create the instances of the Technology Composite class (change names as you see fit) that represent the roles that Technology Platforms (Technology Product Builds) can play in your architecture. For example
- Front End Platform
- Back End Platform
- Data Management Platform
Step 2
For each deployment of an Application, depending on its architecture,
- Create separate instances of Technology Product Build for the platform layers that support them (e.g. 2, 3, n tier) together with their underlying architectures (i.e. the Technology Product Roles that comprise them). Or, if you have some technology platforms that are shared across Applications, create them and their underlying architectures.
- Map these Technology Product Builds to the previously created Technology Composites to defined the roles that they play. For example:
- <Application A - Production> Front End as Front End Platform
- <Application B - Production> Back End Platform as Back End Platform
- MyCompany Shared Production No-Code Platform as Back End Platform
Step 3
For each deployment of an Application, create an instance of Technology Product Build that represents the overall Technology Platform supporting the Application and then and then add and link the previously create Technology Product Build Roles as required (see attached diagrams).
More specifically:
Step 1
Create the instances of the Technology Composite class (change names as you see fit) that represent the roles that Technology Platforms (Technology Product Builds) can play in your architecture. For example
- Front End Platform
- Back End Platform
- Data Management Platform
Step 2
For each deployment of an Application, depending on its architecture,
- Create separate instances of Technology Product Build for the platform layers that support them (e.g. 2, 3, n tier) together with their underlying architectures (i.e. the Technology Product Roles that comprise them). Or, if you have some technology platforms that are shared across Applications, create them and their underlying architectures.
- Map these Technology Product Builds to the previously created Technology Composites to defined the roles that they play. For example:
- <Application A - Production> Front End as Front End Platform
- <Application B - Production> Back End Platform as Back End Platform
- MyCompany Shared Production No-Code Platform as Back End Platform
Step 3
For each deployment of an Application, create an instance of Technology Product Build that represents the overall Technology Platform supporting the Application and then and then add and link the previously create Technology Product Build Roles as required (see attached diagrams).
You do not have the required permissions to view the files attached to this post.
