Presenter

Joost van der Vlies, Technology Consultant, IT Architect, Hewlett Packard

For over 12 years Joost has been working in the IT industry on software development, IT architecture and (international) course facilitation.

He works as technology consultant and IT architect at HP Shanghai, China, specializing in SOA. His education includes a technical degree in Software Engineering and Masters in Social Science Informatics.

Experience:-

• He facilitated courses on IT architecture within Capgemini France, India and China (2006 - 2008)
• He ran workshops SOA for Capgemini Oracle professionals, Utrecht, 2008.
• He has been guest lecturer on ŒLarge projects and outsourcing, behind the scenes at the College of Advanced Technology, Leeuwarden, 2006
• He supplied chain integration in social security, aCapgemini event, Utrecht, 2006
• He conducted a workshop on Service Oriented Architecture with focus on technology platform, Capgemini CxO event, 2005

Presentation

Using TOGAF 9 Architecture Content Framework within SOA Related Engagements

In the TOGAF 9 document the Service Oriented Architecture (SOA) style is explicitly mentioned in a specific chapter and the Architecture Content Framework (ACF) is updated with extensions that facilitate this style. This presentation will focus on the usage of the ACF in the two aspects of a SOA related engagement, accompanied by examples from actual projects.

Within a SOA related engagement two architectural aspects can be distinguished. The first aspect is the SOA based (enterprise integrated) technology architecture that is needed to facilitate and support the SOA style (like an enterprise services bus, business process management, services registry, portal, etc.). The second aspect are the services itself, both from a business perspective (business services) and from an information system perspective (IS service). 

The SOA based technology architecture is described in the Technology architecture (with additional views combining the application architecture). Using logical application (technology) components to describe the needed architecture (vendor agnostic model) and the physical technology components to chose the desired product technology. The use of SOA reference architectures will be discussed which can facilitate this process and make sure an SOA style can be used together with other architectural styles (which is the case is most organizations). An example of an architecture for a large international bank will be presented.

The services and components which represent business functionality will be described in the business and information systems architecture. The granularity of these services depends on the purpose of the architecture engagement. Low granularity may be needed in case the purpose is business planning so high level building blocks will be sufficient, whilst higher granularity may be needed if the purpose is the identification of multiple IT projects.  The relation between Business, Process and IS services will be discussed, together with granularity and cardinality aspects. Especially within SOA engagements a clear line between the architecture and the projects (realizing the identified IT) is necessary. An example of a project at an Airline company will be presented, with the focus on the granularity of services (from business to IS to software service realizing in projects).

Within SOA related engagements, two aspects can be identified: The SOA based technology architecture and the SOA based services itself. Both aspects are presented and discussed, with additional examples given from actual projects.