Layout style

Predefined Color Shemes


Blogs

7 useful concepts to get a better understanding of Enterprise Architecture

1. Service Oriented Architecture
TOGAF 9 on SOA
CBDI-SAE
2. Total Cost of Ownership
3. Services
4. Architecture Building Blocks

5. Service Areas and Service Categories
6. Service layers
7. Component Based Development

1. Service Oriented Architecture

Service Oriented Architecture (SOA) is a common basis for the future state Architecture for an enterprise.
Generally this is seen as a technical issue where the focus is on designing Application Services as SOAP or REST based Web Services.
However organisations usually need to first understand what a Service is and think in terms of Business Services from a a business perspective before designing Application Services from an application or infrastructure perspective.

The Enterprise Architecture language ArchiMate is good in this respect since it has a strong focus on Services at all levels and on integrating concepts in the Business layer, Application layer and infrastructure Layer.

TOGAF 9 on SOA

TOGAF 9 has also a similar meta model stressing the centrality of Services although it's definitions are not yet fully aligned with ArchiMate definitions.

TOGAF also now has a page on Using TOGAF to Define & Govern SOAs.
The Open Group's SOA Working Group has published a collection of source material for use by enterprise architects working with Service-Oriented Architecture at Open Group SOA Source Book.

CBDI-SAE

CBDI-SAE has a detailed SOA Reference Architecture Framework, meta-model for SOA, service life cycle and SOA principles.

2. Total Cost of Ownership

Total Cost of Ownership (TCO) is a concept by which all costs associated with the purchase of a hardware or software product over a given time period are accounted for.
These costs include the purchasing, owning, operating and support costs. The TCO is useful in optimising and consolidating products.

3. Services

A Services Based Architecture is a IT management and architectural approach that classifies services and the service components that implement them, with respect to how they support business and architecture objectives.
Service Based Architecture is an idea that focuses on delivering effective, reliable and flexible IT services as a way to controlling their costs and efficiency. It changes the IT department from running as a cost centre into one running as a mini business unit.
Service Based Architecture is not just a view of IT services seen from a technology perspective, but is a different business model for supporting the business users.
Instead of simply being seen as delivering off the shelf products and developing new bespoke applications, the IT department is now providing a complete service in the same way as an organisation may interact with a software product vendor.

  4. Architecture Building Blocks

Architecture Building Blocks are large granularity pre-defined Service Components. TOGAF focuses on Architecture Building Blocks.

  • A Service Component a package of functionality defined to meet the Service needed by a System.
  • A Service Component has published interfaces to access the services it provides.
  • A Service Component may inter-operate with other, interdependent Service Components.
  • A Service Component has already been implemented and has a well defined context and guide to its usage and is already supported by technology and support staff.
  • A Service Component will be assembled from other Service Components and Infrastructure Service Components.

Ideally a Service Component is reusable in many different contexts.
A Service Component may have multiple implementations over time but will still provide the same Service.

5. Service Areas and Service Categories

The Service Areas and Service Categories enable the structured definition of standardised Service based applications and products.
They can be viewed as a set of layers (or 'Technology Stack') that structures the Application and Technical Architecture models from the presentation layer through the application services and application platform components to the underlying operating system, hardware and infrastructure.
The Service Areas and Service Categories are defined in the Technical Reference Model.

6. Service layers

Business Actors -> User Interfaces -> Business Services -> Business Processes -> Application Services -> Applications -> Application Data -> Technology and Infrastructure

7. Component Based Development

A system development process that places components and services at the heart of the development activities, with explicit reuse of services and components governed by the Enterprise Architecture.

Credit to the author : Adrian Campbell

Infrography credit : created by Gerald Wildmoser from Noun Project

More Blog Entries

We were at the Enterprise Architecture Forum in Saudi Arabia

The "Enterprise Architecture Forum" took place on Monday, May 27, 2013 at King...

What you need to know about Information Architecture

It includes: Business Object Models Application Data Models Data management...

0 Comments

Recent Bloggers

JR
Jamie Roberts
Posts: 5
Stars: 0
Date: 1/30/18
AC
Adrian Campbell
Posts: 3
Stars: 0
Date: 1/11/18
MC
Morgane Canal
Posts: 21
Stars: 0
Date: 10/15/16

TextSlider

Latest news

  • 25/09/2015 - GCloud 7 Supplier

    Enterprise Architects are now providing all services through our government Service Catalogue. Please visit link

  • 16/2/2016 - Digital Outcomes & Specialists Supplier

    Enterprise Architects are now providing services through the Digital Outcomes and Specialists Supplier framework. Please visit:

    link

  • 05/04/2015 - New Office Location MENA

    Enterprise Architects are now located at a new address in Dubai:

    MENA office - Dubai 
    Level 14, boulevard plaza tower 1
    Sheikh Mohamed Bin Rashid Boulevard
    Downtown, Dubai
    United Arab Emirates