What is Metamodel?
In Archipeg, you can have multiple projects for different initiatives, workloads, or teams. A project has a metamodel that you select when creating it. A metamodel is an underlying schema that describes the project's preferred approach or methodology. This schema controls what you can do within a project, including the shapes of objects and associations.
Each project having a separate metamodel allows organizing parallel workstreams with distinct approaches and methodologies.
Currently, Archipeg supports the following metamodels:
- Application Portfolio Management
- Application Portfolio Management (APM) is a practice that attempts to justify and measure the financial benefits of each application in comparison to the costs of the application's maintenance and operations.
- Archipeg EA
- Archipeg EA Framework is a simplistic model of a digital twin of most enterprises. It allows capturing data about applications, products, services, customers, org structures, technologies, vendors, etc.
- C4 Model
- The C4 model is an easy to learn, developer friendly approach to software architecture diagramming. Good software architecture diagrams assist with communication inside/outside of software development/product teams, efficient onboarding of new staff, architecture reviews/evaluations, risk identification, threat modelling, etc.
- Domain-Driven Design
- Domain-Driven Design (DDD) is an approach to software development for complex businesses and other domains. DDD tackles that complexity by focusing the team's attention on knowledge of the domain, picking apart the most tricky, intricate problems with models, and shaping the software around those models.
Can't Find a Suitable Metamodel?
You can submit your feedback or proposal if your preferred metamodel is not listed above.