The FFLV-GODS Enterprise Architecture framework

Its name is FFLV+GODS EA framework standing for Functions-Flows-Layers-Views + Governance-Operations-Development-Support.

Its purpose is to represent the EA structure on which individual EA elements and artefacts should be plugged-in to form the EA.

The scope: Business, Technology and People/Organisation Architecture. Technology covers more than IT.

FFLV is a meta EA (the architecture of EA) consisting of the interconnected elements that describe an EA:

* the business Functions (capabilities),

* the business Flows (value streams),

* the Layers: Business, Technology and People and

* the Views, the architectures representing aspects of interest to specific stakeholders.

In clear text, any Enterprise can be described by its Functions (structure) and Flows (behaviour) in the business layer, by its Technology and People resource layers, executing the business Functions and Flows, and by any number of Views of the above need by stakeholders.

Information is part of the business Functions and Flows and is represented as data in the Technology Layer.

The FFLV is based on a metamodel that shows the links between Functions, Flows and entities in Layers and Views.

FFLV was built by comparison with the human body anatomy and physiology descrptions you can see in any book. You are already used to it. Body parts are Functions, body flows (end to end vital processes) are business Flows and the nervous or blood system... look like EA Views.

GODS is the functional structure of a generic business consisting of

* Governance: the business Functions coordinating of all other activities

* Operations: the business Functions making and delivering the products/services

* Development Functions developing the products and the enterprise itself

* Support Functions providing technology, financial, HR, transportation, procurement ... support to all other Functions.

GODS aligns to Porter's Value Chain model. Functions are also known as Capabilities and Flows as Value Streams.

Any Business Architecture (the EA business layer), can be built on the GODS template. In addition to Functions GODS describes the key business Flows and the interaction with the customer at all times in the customer experience lifecycle.

The FFLV-GODS framework can be represented tri-dimensionally, as a cube and can be navigated across business flows and functions to analyse performance, executing systems and human resources, the impact of change or for roadmapping and strategy design and implementation purposes.

An extended FFLV-GODS framework is covered in the book "An Enterprise Architecture Development Framework" available on Kindle and elsewhere. It describes an EA development process (many times shorter than TOGAF), best practices, principles, the information architecture built, business and IT architecture templates, EA maturity, value delivery, EA evaluation method, business case, strategic planning with EA, SOA design. It also looks at the EA practice construction, governance, architects skills and selection, the role of culture and even a virtual case study.

The book also describes how to formulate and map strategy and how to do roadmapping. Book reviews at Angry Architect and here Here is an article on the EA value published by IASA.

It is not a stuffy process as TOGAF ADM is. It is much more than a system design taxonomy like Zachman. The framework itself is an onthology. It exhibits an extendable metamodel.

The framework (and metamodel) interconnects all your EA artefacts and offers generic template for business and IT architectures to start with.

FFLV+GODS unifies the EA (and IT) with the Business Process world and business theory.

It is the result of a long effort to understand what frameworks like TOGAF, Zachman, eTOM (Frameworx), DoDAF, FEAF, TEAF... do. From that experience a new framework was built that does all the above and much more.

Enterprise culture, EA governance, roadblocks, architects skills are also discuss in the book and on the web site.

You may post any questions indeed.

Adrian

Adrian Grigoriu is an executive consultant in Enterprise Architecture now living in Sydney, Australia. Shortlisted for the Computer Weekly IT Industry blogger of the year 2011. Former Head of Architecture and EA at OFCOM, the Agency providing regulation to frequency spectrum utilization and broadcasting industry in the United Kingdom. Previously Chief Architect of TMForum, the standards organization providing Frameworx, the Integrated Business Architecture framework for the telecommunications and digital media industries. Adrian also is an Executive Enterprise Strategy and Architecture Consultant and author of "An Enterprise Architecture Development Framework" book available on Amazon and Kindle at Trafford and elsewhere. Reviews of the book are available from BPTrends and the Angry Architect. Here is a short Enterprise Architecture animated slideshow summarising his view. Adrian also offers an EA and business architecture training course on-demand, based on the book. You may get in touch at grigoriu@hotmail.co.uk. His website.

Disclaimer: Blog contents express the viewpoints of their independent authors and
are not reviewed for correctness or accuracy by
Toolbox for IT. Any opinions, comments, solutions or other commentary
expressed by blog authors are not endorsed or recommended by
Toolbox for IT
or any vendor. If you feel a blog entry is inappropriate,
click here to notify
Toolbox for IT.