Architecting enterprise BPM systems for optimal agility

Architecting enterprise BPM systems for optimal agility Dr Alexander Samarin www.samarin.biz

About me ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],

Overview ,[object Object],[object Object],[object Object],[object Object]

The goal – optimal agility (easy evolution of a BPM system) ,[object Object],[object Object],[object Object]

Challenge of optimal agility (1) ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Challenge of optimal agility (2) ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

BPM and BPM systems ,[object Object],[object Object],[object Object],[object Object],[object Object]

BPM view of the business (1) ,[object Object],[object Object],[object Object],[object Object]

BPM view of the business (2) ,[object Object],[object Object],[object Object]

Architecting an enterprise BPM system (with systems thinking) ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Principal artefacts: services and processes ,[object Object],[object Object],[object Object]

Relationships between services and processes ,[object Object],[object Object],[object Object]

All BPM artefacts ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Main architecting principles ,[object Object],[object Object],[object Object],[object Object]

Improvement of artefacts ,[object Object],[object Object],[object Object],[object Object]

Relationships between artefacts ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Explicit models ,[object Object],[object Object],[object Object]

Executable models ,[object Object]

Synergy between BPM and SOA ,[object Object],[object Object],[object Object]

Role of architecture (1) ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Role of architecture (2) ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

An architectural framework for improving BPM systems ,[object Object],[object Object],[object Object]

Strategy: top managers ,[object Object],[object Object]

Example – a new EA unit ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Business: enterprise architects ,[object Object],Maturity level Technology architecture Application architecture Data architecture Business architecture Enterprise architecture Optimising Managed Defined Under development Initial None

Business: managers ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Business: process owners ,[object Object],[object Object]

Business: super-users ,[object Object],[object Object],[object Object]

Project: managers ,[object Object],[object Object],[object Object],Today Tomorrow

Example – selection of a single tool ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Example – real agility achieved ,[object Object],[object Object],[object Object],[object Object]

Project: business analysts ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Example – early industrialisation of a business system ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

IT: managers ,[object Object],v.1 v.2 v.3 v.4 Life-cycle TCO First BPM/SOA project Further BPM/SOA projects Each subsequent solution is cheaper because it reuses the same tools, the same services, the same architecture Maintenance approx. 80 % Initial development approx. 20 % Typical IT projects

Example – a production system in place for several years ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

IT: enterprise architects ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Example – Solution architecture for “ e-government” (1) ,[object Object],[object Object],[object Object],Gov Internal service Internal application Internal application Integration services e-gov environment External users Collaborative extranet

Example – Solution architecture for “ e-government” (2) ,[object Object]

IT: architects (1) ,[object Object]

IT: architects (2) ,[object Object]

Example – complete redesign of a business system ,[object Object],[object Object],[object Object],[object Object],[object Object]

IT: developers ,[object Object]

Example – typical timing of micro-projects ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

IT: operators ,[object Object],[object Object]

Example – efficient error handling ,[object Object],[object Object],[object Object],[object Object],[object Object]

Summary – Main ways of achieving optimal agility ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Architecting enterprise BPM systems for optimal agility

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (9)

Semelhante a Architecting enterprise BPM systems for optimal agility

Semelhante a Architecting enterprise BPM systems for optimal agility (20)

Mais de Alexander SAMARIN

Mais de Alexander SAMARIN (20)

Último

Último (20)

Architecting enterprise BPM systems for optimal agility