We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

Enterprise Architecture Matters

Adrian Grigoriu

An Enterprise Architecture framework, FFLV-GODS

Vote 0 Votes
FFLV-GODS is an EA methodology (or extended framework...) that integrates the many existing frameworks concepts, classifies them in four different aspects, and integrates them in this framework whole.

FFLV-GODS consists of:

- 1. The Framework itself 
describing the EA structure (its layers, views, nodes...). 
It looks like the contents page of a book. It illustrates its structure but pages have to be still read or filled in.
A metamodel, constructed on the framework, describes the relationships between the EA structural elements.  
Most existing frameworks offer layers (typically  business/applications/...). 
In this category of frameworks partly enter metamodel like "frameworks" such as Archimate.

FFLV covers the Functions (nodes), Flows (links), Layers (business/technology/people) and  Views (stakeholders architectures), their relationships and navigation and the metamodel.

- 2. The Process 
describes the development phases that realise the target EA. Typically good practices such as methods to measure progress and value, to evaluate risks... or in more general terms, to properly conduct a project, are included in the process. 
Governance comes in here: principles, decision boards etc
FFLV covers: the EA Setup phase followed by iterations of EA Discovery, Planning, Implementation and Exploitation. 
TOGAF falls into this category.
Still a car cannot be described by using a process alone. The end result could be anything that moves. 

- 3. The Model, the reference models that streamline the EA documentation and design.
In this category may fall TM Forum's Frameworx (NGOSS) consisting of templates for a process framework (eTOM), an application framework (TAM) and an information network (SID).
GODS describes the key parts of a business, the key Functions and Flows (Value Streams). FFLV-GODS also provides a capability map, the One Page EA, the IT application, information, infrastructure... architecture models. 
But you still need the above transformation Process and Framework.

- 4. The Design, i.e. a synoptic view of the EA design process and diagrams.
There are standard techniques to describe the EA artefacts for system structure (taxonomies), behaviour (sequence charts, activity diagrams...), dynamic systems (state diagrams), information (ERD/class diagrams), organisation charts... 
There are also typical dependencies and relationships between these representations. 
DODAF and versions, for instance, excel at Design through the views concept.
The FFLV Design poster shows the relationships between key artefacts.

These four posters at http://www.enterprise-architecture-matters.co.uk illustrate the methodology.

Last but not least, to develop an EA you need to cover All Four aspects. Neither the Framework, the Process, the Model or the Design, taken separately, would be sufficient to devise the EA.
In other words, a combination like  ArchimateTOGAF, Frameworx (TM Forum) and DoDAF is necessary.  
FFLV-GODS, cover all these aspects in a single a unified methodology.

Leave a comment

Adrian Grigoriu blogs about everything relating to enterprise and business architecture, SOA, frameworks, design, planning, execution, organization and related issues.

Adrian Grigoriu

Adrian is an executive consultant in enterprise architecture, former head of enterprise architecture at Ofcom, the spectrum and broadcasting U.K. regulatory agency and chief architect at TM Forum, an organization providing a reference integrated business architecture framework, best practices and standards for the telecommunications and digital media industries. He also was a high technology, enterprise architecture and strategy senior manager at Accenture and Vodafone, and a principal consultant and lead architect at Qantas, Logica, Lucent Bell Labs and Nokia. He is the author of two books on enterprise architecture development available on Kindle and published articles with BPTrends, the Microsoft Architecture Journal and the EI magazine. Shortlisted by Computer Weekly for the IT Industry blogger of the year 2011.

Recently Commented On

Monthly Archives