This blogpost outlines a “big picture” including the components and operating model for Better Architecting With (BAW).
Again, the goals of BAW are:
- to standardise a good set of #entarch common components (viewpoints, artefacts, models, etc.)
- to enable the users to add their own components, if necessary
- to provide formal and repeatable guidance how to achieve unique user’s needs with available components.
- BAW platform;
- a set of ready-to-use popular BAW solutions (consider them as recipes) which you may try as-is and gradually adapt for your unique needs, and
- BAW guidance (including some obvious documentation).
- BAW ontology – a set of about 200 concepts (in my estimation) which are already defined in many sources and needed to be aligned.
- BAW artefacts – a set of about 50 (in my estimation) well-known artefacts to be aligned.
- BAW viewpoints – a user-extendable set of about 20-30 (for now) viewpoints.
- BAW model kinds – a user-extendable set of about 50-70 (for now) model kinds.
- BAW patterns – a user-extendable set of techniques for transforming (not necessary fully automatically) some model kinds into other models kinds.
The BAW solutions comprise the following:
- BAW scenarios – a set of popular architectural works such as designing data-entry application or process-based applications, defining business architecture, formulating IT strategy, etc.
- BAW skeletons – a set of existing #entarch frameworks
Again, the whole BAW must be organised in a way that anyone can add new viewpoints, model kinds, patterns and related documentation to enrich BAW with formalised and repeatable knowledge.