Each layer is further described by Views, filters showing only the aspects of interest to a stakeholder: for instance, the business layer consists of process, information, strategy, value chains, business models...
The EA framework is built on business Functions, Flows (Processes), Layers and Views components (FFLV) and the GODS (Governance, Operations, Development, Support) structure.
Any Enterprise business structure is shaped by GODS and Value Chains.
GODS describes the top business structure of an Enterprise, the key parts. (G-Governance - coordinates all other, O-Operations - deliver the products, D- Development - develops the products and the organization, S-Support - provides the other functions with technology, people, finance).
GODS structure supplies the Enterprise Architect with a standard capability map.
In the GODS framework this is the horizontal dimension.
Vertically, each GODS function is further described in this proposed EA framework by the People and Technology layers executing the functions.
Any function is fully described by its Business processes, information, rules, strategies... but also by its IT Technology and People implementing them.
Flows describe the processes delivering the products. Here is agraphical representation that can be used as a navigation GUI.

A View, is the graphical representation of all objects in a repository which have been selected for a specific purpose - as for instance the recruitment View.

Each business function consists of at least a process and the technology and organizational roles/units executing the processes.
The Business Reference Map is a standard template used to ease the development for all and everybody. It consists o GODS and a Value Chain such as Planning, Operations (Product delivery), Sales and Service.
A Single Page Architecture is the reference business blueprint for all stakeholders since it describes the basic structure and operation of the Enterprise in one page. It is a key EA delivery.
The extended EA framework also covers metamodel, references maps for business and templates for technology, best practices, development process, EA value assessment, business and operating models, organizational design and alignment, EA design method, security, information and SOA architectures, maturity evaluation, culture, EA architect role and leadership... are all described in my EA book, 3rd edition (Trafford, Amazon...).
So long
Leave a comment