Aligning Business Process Architecture and Enterprise Architecture: - PowerPoint PPT Presentation

aligning business process architecture and enterprise architecture l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Aligning Business Process Architecture and Enterprise Architecture: PowerPoint Presentation
Download Presentation
Aligning Business Process Architecture and Enterprise Architecture:

play fullscreen
1 / 22
Aligning Business Process Architecture and Enterprise Architecture:
589 Views
Download Presentation
richard_edik
Download Presentation

Aligning Business Process Architecture and Enterprise Architecture:

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Aligning Business Process Architecture and Enterprise Architecture: A Model Driven - Service Oriented Approach Chris Capadouca Business Solutions Architect

  2. Model Manage Enable Repositories Monitor Adaptive Business Process Management Narrow the business-IS Gap Model and simulate cross functional business processes Manage and improve the processes using process metrics Process visibility and exception based interaction Qualitative & Quantitative Feedback Enable & integratehuman and system based business process Reduction in Cycle Time Monitor end-to-end business processes in real-time Adaptability

  3. Model Manage Enable System B System C System A Monitor What are the Challenges? • Challenge • Evolve from siloed functional design and build to a cross functional process focus approach • Challenge • Enable end-to-end monitoring and correlation • Structure around cross functional ownership Process A Process A Process B Process B • Challenge • Enable workflow to cross system boundaries rather than be bound to them • Challenge • Enable visibility to cross functional KPIs, business events, and process states

  4. Historical Perspective • Lack of Alignment • IT centric • Siloed initiatives • Lack Cross-functional process owners • Enterprise Optimization focus is in the wrong place • We get lost in the details

  5. What should the future look like? • Enterprise Architecture is about Business Transformation • Process Modeling is a component of Enterprise Architecture • Cross-functional optimization is the focus • Cross-functional process ownership is obvious and rewarded

  6. What should the future look like? • Strategic Visioning “involves defining the context, identifying strategic drivers, developing a high level business model, establishing principles for the new work system, and packaging for commitment and action.” • “As part of this visioning exercise, key questions for work reengineering need to be explored: What is your business value network? What are the key functions (logical service units) that are closest to delivering value to the customer?” • “Any functional component or service unit can be decomposed into a number of interrelated processes and work activities.” • “Each logical service unit can be modeled to determine the most appropriate business processes and related manual and automated work activities” Excerpts from Paradigm Shift: The New Promise of Information Technology, by Art Caston and Don Tapscott, McGraw-Hill 1993

  7. Why spend the time? Why align Business, IT and Process Architecture? Its about the integrated plan ……..just ask Sarah Winchester Fact: Mrs. Winchester never had a master set of blueprints, but did sketch out individual rooms on paper and even tablecloths!

  8. How do we get there? • Stop viewing Enterprise Architecture as an IT thing! • Create a high level reference framework • Identify & define what we do and the services we provide • Identify & define how we realize the business services • Identify & define how we provide services and who owns them • Publish the plan!

  9. What are the Enablers? • Business Buy-in and ownership • Model Driven Architecture • Describes the enterprise as a set of related models • Enterprise Service Architecture • The business services that need to exist • The services they provide • The capabilities that realize them • It’s not just about the technology • Event Driven Architecture • Describes the enterprise interactions in terms of related events that trigger services Yes, these are complementary!

  10. Model Driven Architecture “A style of enterprise application development and integration based on; using automated tools, to build system independent models, and transform them into efficient implementation”1 1 -Source: Booch, et al, “An MDA Manifesto”, published in the MDA Journal, May 2004

  11. Model Driven Architecture “to build system independent models, and transform them into efficient implementation”1 1 -Source: Booch, et al, “An MDA Manifesto”, published in the MDA Journal, May 2004 A style of enterprise architecture; using a model driven approach,

  12. Reference Models Target Models Deployment Models Strategies Objectives Markets Business Model Channels Brands Locations What What Capabilities Processes Organizations Business Rules Organization Structure Facilities How How Service Functions Services Metrics Operations Model Ref Systems Responsibilities Execution Model Applications Roles Infrastructure People Platform Independent Platform Specific Platforms Model Driven Architecture Approaches demand it! Drive Traceability Reference System and Service Function concepts are extracted from Proact EA Methodology from Proact Business Transformation Inc.

  13. Service Oriented Architecture • “An approach for designing and implementing distributed systems, • that allows a tight correlation between the business model and the IT implementation” Bill Hassell - IBM’s Business Integration Reference Architecture, 2004

  14. Enterprise Services Architecture • An approach for designing and implementing capabilities that realize and leverage services, • that allows a tight correlation between the business model and the physical implementation • Business Perspective • What Services need to exist? • What information do we need? • What Capabilities provide Services? • What Processes realize a Service? • Implementation Perspective • What is the process flow? • What is the information flow? • What composite application functionality realizes as process?

  15. Drive Deployment Models Locations Reference Models Target Models Org Structure Facilities Business Model Strategies Objectives, Markets Infrastructure People Channels, Brands What What Traceability Platforms Operations Model Processes Organizations Business Rules Capabilities Services Metrics How How Customer IT Solutions Delivery Ref Systems, Roles Applications Roles Execution Model Service Function A Solutions Delivery Service Service Desk Platform Independent Platform Specific Service Function B Support Readiness Service Support Reference Modeling • Service Functions1 • What business functions need to exist to sustain the operations of the business • Services • What one Service Function does for another, or an external entity like customer or stakeholder 1) Service Function concepts are extracted from Proact EA Methodology

  16. Customer IT Solutions Delivery Solutions Delivery Service Desk Support Readiness Solutions Support Operational Scenario as a set of Service Functions Solutions Delivery Solutions Support Customer Event 1 Event 2 Release Survey Events Reference Modeling Service Function Model

  17. Drive Deployment Models Locations Reference Models Target Models Org Structure Facilities Business Model Strategies Objectives, Markets Infrastructure People Channels, Brands What What Traceability Platforms Operations Model Processes Organizations Business Rules Capabilities Services Metrics How How Capability Is part of Ref Systems, Roles Applications Roles Execution Model Activity Activity Activity Platform Independent Platform Specific Activity A Activity B Customer Capability Model Event 1 Event 2 Process Model Target Modeling • Capabilities • The collection of activities that realize Service(s) • Process • The sequence of activities that realize Service(s) • Organization • The realization of a set of roles and responsibilities required to perform activities

  18. Is realized by Solutions Delivery Is realized by Release Mgmt Is part of Capability 1 Plan Design Capability nn Test Capability Model Reference to Target Mapping

  19. Operational Scenario as a set of Service Functions Traceability Drive Solutions Delivery Service Support Customer Release Survey Release Mgmt Service Level Mgmt Customer Release Survey Operational Scenario as a set of Capabilities Context basedReference to Target Mapping

  20. Target Process Modeling Operational Scenario as set of Capabilities Release Mgmt Service Level Mgmt Customer Release Survey Drive Implement System Conduct Survey Customer Release Survey Traceability Create Survey Post Survey Notify Participant Complete Survey Publish Survey Results Operational Scenario as a set of process and sub process

  21. Deployment Models Operational Scenario as a set of process and sub process Implement System Conduct Survey Customer Release Survey Create Survey Post Survey Notify Participant Complete Survey Publish Survey Results Web Svc Web Svc Survey System Corporate Portal Messaging System Survey System Mgmt Portal

  22. Adaptive Business Process Management • Enterprise Architecture is about Business Transformation • Process Modeling is a component of the Enterprise Architecture • Modeling the business as a set of interrelated services provides context to Process Modeling An Integrated Roadmap Proact Methodology chart used with Permission