Architecting the Enterprise

Serge Thorn

Subscribe to Serge Thorn: eMailAlertsEmail Alerts
Get Serge Thorn: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Serge Thorn

For many years I have observed lots of confusion with some basic definitions such as IT and Enterprise Architecture among other terms. I will not try to define the meaning of Enterprise Architecture by myself (despite I have my own view on this) as this is something being right now redefined by the Open Group (which by the way used to call their events “IT Architecture Practitioner Conference” and changed only recently to “Enterprise Architecture Practitioner Conference”). Looking at job definitions related to Architecture positions, I have also identified a clear misunderstanding of “who is supposed to be doing what…”. In addition to that, I’m frequently asked “what’s the difference between an Enterprise Architect and an IT Architect”. First, let’s assume that everyone agrees on the fact that Enterprise Architecture includes -Business Architecture -Information Archit... (more)

Service Management and Enterprise Architecture

Governance is currently a key topic for many IT functions. Its definition varies, but its key themes are true for all companies: effectiveness, efficiency, and reliability. Business value and risk mitigation are also at its center and represent a significant part of enterprise governance overall. Due to the horizontal nature of IT, where almost everyone in the enterprise uses IT assets to complete their responsibilities, the impact of effective IT governance is quite visible throughout an organization. IT governance defines a structure of relationships, processes, and measurement... (more)

Building an Enterprise Architecture value proposition using TOGAF® 9.1. and ArchiMate 2.0

When introducing Enterprise Architecture as a program or initiative, it is regularly done from an IT perspective rarely considering what the costs will be and if there will be any return on investment. This presents a particular challenge to Enterprise Architecture. Generally speaking, IT departments have all sorts of criteria to justify projects and measure their performance. They use measurements and metrics, KPIs. Going to the solution level, they commonly use indicators such as percentage uptime for systems from the System Management team, error rates for applications from th... (more)

Implementing SOA through TOGAF 9.1: the Center Of Excellence

Service-oriented architecture (SOA) has at times been challenged but is now on the verge of mainstream acceptance. It now shows maturity, success and even signs of popularity. Service Oriented Architecture (SOA) is an enterprise scale architecture for linking resources as needed. These resources are represented as business-aligned services which can participate and be composed in a set of choreographed processes to fulfil business needs. The primary structuring element for SOA applications is a service as distinct from subsystems, systems, or components. A service is an autonomous ... (more)

Redefining traceability in Enterprise Architecture and implementing the concept with TOGAF 9.1 and/or ArchiMate 2.0

One of the responsibilities of an Enterprise Architect is to provide complete traceability from requirements analysis and design artefacts, through to implementation and deployment. Along the years, I have found out that the term traceability is not always really considered in the same way by different Enterprise Architects. Let’s start with a definition of traceability. Traceable is an adjective; capable of being traced. Trying to find a definition even from a dictionary is a challenge and the most relevant one I found on Wikipedia which may be used as a reference could be “The ... (more)