Integration Architecture & Design Competency

Overview

Themes

• It is about designing capabilities

• Patterns of infrastructure

• Infrastructure networks

• Gateways

• Patterns of services

• Functions

• Applications

• Rapid deployment

• Reusability – cost

• Extensibility

• Scalability

Models

• Content – source – models

• Service Models

• Web – loosely coupled

• SOA – app coupling

• Matching Integration solution with business needs

Figure 1 Commonly recognised MOM, EAI messaging patterns

2 Good practices in Static and dynamic design

• Observation of gaps in Static and Dynamic Design templates

• Glossary- Macro, micro - domain class model

• Component Framework

• Channel model

• Application model

• Common Information Model

• Transformation rules

• Source/target

• Message Model

• Interfaces – taxonomy (Patterns)

• Interfaces – Partitioning (rules, framework models )

• Integration of process, app, message (functional operations and data – classes)

• Establishing a Framework of models – logical and how specific programmes will implement specific parts of it

• Verification

• Pattern designs

• Taxonomies and Domain models

• Meta Model

• Services model

• Deployment model

• Use of a Data Dictionary and component dictionary (object based)

• Designs

• Gateways

• Configurators

• Inbound

• Syndicators

• Outbound

• Configurators

• Web services

• Portals

• Integration Platform technology – e.g. JAVA open architecture

• Governance, compliance and enterprise performance management trade-offs

• Change management

• Patterns

• Models

• Can cripple SOA and IT responsiveness

• Interface Contracts - Argos

• Meta Models – Kraft

• SOA Services model – Argos

• Requirements catalogue – alignment – CMM, BSkyB

• Use cases – Testable design – BskyB

• Configurability of changes – without coding – Uis, CMAs

• Domain Platform strategies – Argos , NPower – put logic in SAP, COTS etc.

• Standards based architectures – Argos, SOAP , WS etc

• Joint Application Development JAD - BSkyB

• Use Case Ontology – BskyB

• Test Driven Process Design – BskyB

Some methods for Change deployment

• Common Pattrn Architectures (Argos, Kraft)

• Use of common processes to focus on specific capabilities

• There is a down side to this in governance and speed of deployment and longer term value to company if it does not work well e.g. the BI is “lost” to central areas and taken away from where it is needed at local point of use

• Art of the possible (Diageo)

• Similar to the hot house approach in BT

• Change agents (MOD)

• Use of experts in field to champion change initiatives

3 Some common Patterns to be found in many business architectures

Figure 2 Common Integration patterns

4 The kinds of business architecture that these patterns can be used for:

Figure 3 Common Integration Architecture designs

5 What problems these patterns can be used to solve

Figure 4 Common Integration Architecture problems

6 How do these patterns come together in an Integration Architecture

Figure 5 Common technology Stack patterns

7 Examples of Integration tier patterns in “the flesh”

Figure 6 Integration Tier Pattern Class Model examples

8 How this come together in an Integration Architecture

Figure 7 Architecture layers

9 Operational Questions

- How to do integration better between ERP like systems

- No standard way of defining interfaces

- Need a facade patern of interface design to enable extensibility

- How to reconcile Siebel and Portal functionality

- eCRM strategy

- how to architect self service areas online with Siebel functionality?

- Perferences and promotion

- Profile account management

- How to do better batch data processing and database management?

- consolidation

- What are the things the Integration area need to do better at

- Interface facade pattern design

- Merging different Feeder sources

- Selected different data field sources for composite extract feeds

- standardising interface contracts

- Database consolidation and facade management for internal and external access

- Priorities

- rendering Content to specific channels

- applying common services and content to specific channels

- cross channel coordination

- exposure of content - Meta Model of enterprise

- performance of infrastructure

- Integration patterns

- Service orientated Architecture aspects

- Collaboration networks - portals and gateways

- XML Message collaboration

Scope

- Interface platforms

- Database sources

- Application targets

- Landscape consolidation

- Access and mediation

- Security

- Protocols

- Standards

- Access

- Internal

- External

- Web service methods

- XML-RCP, SOAP

- Integration Frameworks

- ASP.NET; J2EE

- EAI strategy

- Connectivity

- Routing

- Transformation

- Mediation

- Orchestration

- Synchronous and asynchronous strategies

- API management

Notes on Organisation

• Staff skills

• Executive Level

• Direction and needs

• Integration level

• Direction and needs

10 Meta Model Architecture

Figure 8 Meta Model Reference

Mark Skilton

January 2005

#ArchitectureGovernance #SystemsIntegration #IntegrationArchitecture