I am seeking for some guidance on how can we create and manage Reference Architecture & EA Repository using Hopex. I would like to preserve Ref Architecture diagrams, patterns diagrams and decision tree in the repository.
Was wondering if you could help and guide here.
I would say that any type of model you can make in HOPEX is potentially a Reference Architecture. Logical Application Architectures can be used both as a reference but also to model something that you are planning to implement. If you create a Resource and IT Architecture that is also a Reference Architecture. I would create my Reference Architecture in a specific Library and just use them for reference.. I dont think I would connect the reference architecture to capability maps etc. We are mostly using the capability maps to analyse impacts of the architecture and projects.
@SergeThorn , @aseth this is very timely topic for our company too..
My 2 cents on above response.
BRM, TRM, DRM are "Reference Models" , not Reference Architectures.
These two terms "Reference Architecture" and "Reference Model" are often used interchangibly - but they mean different things.
If you refer to TOGAF 9.2 (Chapter 41 - Repository) you can see Open Group's caution on this.
Reference Models are (a set of unifying concepts about a specific domain/topic)
- Think of a parts list when you buy IKEA furniture.
Reference Architecture are high level patterns ( solutions to a problem in context)
- Think of an IKEA diagram showing how parts fit together to make a chair
- Uses the concepts from the parts list (reference models) and adds relationships
For now, my prefererred approach would be to simply create reference architecture in Archimate - connecting Archimate Capability to the defined concepts in HOPEX capablity map. In Archimate, the viewpoint to chose is "Strategy".
First when we refer to a Reference Architecture, we may associate them to the 4 (or 5) classical architecture domains or layers. It includes a document or set of documents that contains recommendations on the structures and integrations of IT products and services that make up a solution. It encompasses the best practices recognized in the industry, allowing it to suggest the optimal delivery method for this or that technology and in the design stages.
We will refer to generally four models
Enterprise reference architectures are standardized architectures that provide a reference framework for a domain (Business, Data, Application, Technology) or a vertical sector (ex: Banking-Finance, Insurance, Healthcare, etc).
Many domains have their reference architecture definitions.
Key reference architecture examples include:
I’m in the process of developing 2 reference models in Hopex:
Hope this helps.