• Like
Business Architecture
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Business Architecture

  • 2,279 views
Published

 

Published in Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,279
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
242
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Good Day Ladies and Gentlemen, My name is Gary Doucet and I am the Chief Architect for the GC within the CIO Branch of the Treasury Board Secretariat.

Transcript

  • 1. Business Architecture and SOA for Business Gary Doucet Chief Architect, Government of Canada Treasury Board of Canada, Secretariat RDIMS#528292 Statistics Canada Information Technology (IT) Conference 2007 April 4-5, 2007
  • 2. Agenda
    • Canada and Change
    • Enterprise Architecture
    • Business Architecture
    • SOA - Service Oriented Architecture
    • SOA for Business and Technology
  • 3. Canada and Change
    • Change Agenda for Canada:
    • Political Priorities – Accountability and more..
    • Internal Services – Finance, Human Resources, Procurement,…
    • Service Delivery – Common Standards, Shared Providers
    • Technology Services – Common Distributed Computing Plus..
    • Role of the CIO – Moving beyond technology…
    • Government Services Overall – Who does what and why?
    • Policy - Simplify and Reduce
    • Plus, plus, plus…
  • 4. Enterprise Architecture
    • Formal Definition
    • The fundamental organization of an enterprise (i.e. government); outlining its components, their relationships to each other and the environment, along with the principles governing its design and evolution. Adapted from ANSI / IEEE Std 1471-2000
    • Informal Explanation
    • An Enterprise Architecture is the collection of things which describe the Enterprise. This includes: legislation, policies & instruments, business plans, service descriptions, process descriptions, org charts, job descriptions ….and (of course) information and technology descriptions. Together, it is confusing, but it IS the description of the enterprise. EA seeks to add structure to that description so the collection can make sense and be analyzed for improved management, effectiveness, ever-greening, agility, public policy alignment, …. essentially better knowledge of the enterprise. THE key tool for decision support!
    Enterprise Architecture: A tool for change management…
  • 5. Enterprise Architecture
    • Role of the Chief Architect…
    • Lead discipline of Enterprise Architecture (How)
      • All Domains (Business, Information, Technology …)
      • All requirements (Security, Privacy, Accessibility, …)
    • Capture, hold, and publish architectures (What)
      • Domain visions, strategy’s, and designs
      • Enterprise Architectures (Roadmap)
    • Responsible for Business Transformation Enablement Program
        • “ www.cio-dpi.gc.ca/btep-pto/index_e.asp”
    • Standards Program (From IT to Business Design)
  • 6. Enterprise Architecture
    • … Role of the Chief Architect
    • Emerging trends such as Open Source, XML, Open File Formats, Digital Rights Management, Identity Management,…
    • Investment Plans
    • Strategic Projects (lead and support)
      • Grants and Contributions
      • Oversight Improvement
      • Expenditure Management Renewal
    • Chief Architect Passions
      • Integration and Interoperability
      • Ensure Business is part of EA (Like water is a part of the ocean)
      • Consumer Centric Architecture
  • 7. Enterprise Architecture
    • The SFO (Senior Financial Officer) provides rules and tools on how to do accounting and makes sure it’s done right
    • The SFO provides integrated accounting results to DM based on the results of departmental efforts
    • The SFO stewards the GC fiscal plans and safeguards the enterprise’s financial health
    • Proper financial controls is something built into all of our daily business processes
    • The Chart of Accounts is our authoritative classification for fiscal data
    • The larger the enterprise, the more robust the financial controls are likely to be
    • The CA (Chief Architect) provides rules and tools on how to do EA and makes sure it’s done right
    • The CA provides integrated architecture views (‘as is’ and ‘to be’) to the DM based on the results of departmental efforts
    • The CA stewards the GC enterprise architecture to safeguard and align the strategic plans and designs
    • EA is a pervasive element of all planning, design, management and transformation activates
    • The GSRM is our authoritative classification for all program and service information
    • The larger the enterprise, the more vital the need for an architected approach
    Accounting Enterprise Architecture WHAT 200v1
  • 8.
    • Traditional versus New Business Architecture
    • Traditional Business Architecture:
    • Capturing business requirements to properly align business process and business systems to the business. Uses things like use cases, process maps, etc.
    • New Business Architecture
    • Capturing the business purpose and then designing the business to deliver the desired business outcomes. Supports better service design, org charts, job descriptions, …
    • Traditional BA results in solutions aligned to business.
    • New BA results in business aligned to purpose …
    • … and prioritized outcomes (performance objectives).
    Business Architecture Think Business “Purpose” not just Business “Process”
  • 9.
    • New Business Architecture
    • It is not:
      • Just a new name for business process reengineering/mapping.
      • only focused on getting technology to work better for business
      • Only practiced by IT specialists
      • About ‘capturing’ business (aka business Modeling)
    • It is:
      • Public Outcome Value Chains, Performance Logic Models, Outcomes, Services, Target Groups and their Needs
      • Business Information Models
      • Business Blueprinting
      • About Program portfolio management, both horizontal and vertical
      • About ‘changing’ business (aka Business Design)
    Business Architecture
  • 10. Business Architecture GSRM: Governments of Canada Strategic Reference Model
    • GSRM Includes:
    • Standard Set of Business Components & Definitions
    • Standard Set of Integrated Business Models & Methods
    • Reusable Business Design Patterns
    GSRM 120v3 Common Language and Design Constructs Target Group
  • 11. Business Architecture GSRM: Governments of Canada Strategic Reference Model
    • GSRM Includes:
    • Standard Set of Business Components & Definitions
    • Standard Set of Integrated Business Models & Methods
    • Reusable Business Design Patterns
    GSRM 120v3 Common Language and Design Constructs Target Group
  • 12. Business Architecture
    • GSRM Quick Facts:
    • G overnment s of Canada S trategic R eference M odel
    • Experience with MRM and PSRM
    • GSRM “v1”: 1998-2002
    • GSRM “v2”: 2003-2004
    • Business Concepts, Language and Design Constructs (construction models)
    • Reference Patterns and Metrics
    • Multi-jurisdictional
    BTEP/GSRM Background and History
  • 13. Business Architecture
    • GSRM: Quick facts
    • A common language (for policy, transformation and operations).
    • Holistic for all public sectors & jurisdictions in Canada. Started in cities and then provinces years ago. Federal Government simply added to the existing model.
    • An essential tool for:
      • Context & guidance;
      • Integrated business planning;
      • Work assignments;
      • Accountability; and
      • Governance.
    • Aligning with and extending existing GOC performance model
    20 Oct. 2004
  • 14. Business Architecture BTEP/GSRM Mgmt – Sharing and Engagement GSRM: Quick facts - Working with jurisdictions on common standard …‘xRM’ Alignment
  • 15. Business Architecture BTEP/GSRM Mgmt – Status and Change GSRM Levels of Change
  • 16. Business Architecture Packaged together, these provide powerful business transformation capability to help achieve alignment across Canada’s business strategies. S et of core enablers that provide strategic horizontal capabilities to increase business integration GSRM used as the Transformation framework that defines and organizes all elements of a business Government Strategic Reference Models containing authoritative business designs and patterns Methodology for transformation Transformation governance model Roadmap for transformation Website: www.cio-dpi.gc.ca/btep-pto 20 Oct. 2004 An Open Toolkit for Transformation BTEP: Business Transformation Enablement Program
  • 17.
    • BTEP developed 2002-2004
    • Sponsored and developed by team within Treasury Board Secretariat (TBS)
    • BTEP “V1” – early adopter projects
    • BTEP V2.0: September 2004:
      • Published set of five documents with templates
      • Release and promotional campaign (2004-2005)
    Business Architecture BTEP/GSRM Background and History BTEP: History
  • 18. Business Architecture 2004 BTEP/GSRM Mgmt – Status and Change BTEP/GSRM Suite and Release Management BTEP Handbook for Practitioners BTEP SD&P Guide BTEP: GSRM Service Reference Patterns BTEP: Executive Summary BTEP Glossary BTEP: Templates GSRM Foundation Model GSRM Bus Ref Model Specification V2.1 GSRM Bus Ref Model Handbook GSRM Meta - Model UN/CEFACT UMM Spec (External) GSRM Configuration, Change and Release Management GSRM Tech Ref Model Specification GSRM Info Ref Model Specification 2007 2008 TBD TBD 2007 2007 2007 GSRM Tech Ref Model Specification GSRM Tech Ref Model Specification TBD TBD
  • 19. Business Architecture
    • Establish/Publish GSRM business reference model V2.1 baseline
    • Establish NGO stewardship for BTEP and GSRM products
    • Governance: Configuration, Change and Release Management for BTEP and GSRM
    • Community Engagement Strategy
    Next Steps
  • 20. Business Architecture
    • Gartner Research Publication
    • “ Application of the Canadian BTEP produces highly strategic, breakthrough improvement opportunities for more-citizen-centric government.”
    • “ The methodology must have the participation and buy-in of key business stakeholders. The initial learning curve is steep for getting participants familiar and comfortable with the methodology and for acquiring the common vocabulary needed to work together across organizational boundaries. Success requires strong facilitation skills and a gradual introduction of more-detailed materials as the participants come to grips with what transformation means to them and their organizations”
    WHAT 140v1
  • 21. SOA – Service Oriented Architecture
    • Everyone is doing it …
      • IT Organizations: IBM, Microsoft, BEA Systems Inc., Oracle Corp., SAP, SUN, HP, …
      • Other Organizations: Boeing, Lockheed Martin, Fujitsu, NASA,…
      • Most Governments
    • “ 80% of software development projects will be based on SOA by 2008” … Gartner
    SOA seems to be the answer … But what was the question?
  • 22. SOA – Service Oriented Architecture
    • Technology Needs
    • IT has not always grown in-step with an organization’s mission
    • Lack of agility, redundancy, inefficient interactions, and increasing costs
    SOA is solving some of these issues.
    • Increased need for intra and inter organization information sharing
    • Difficult to determine “what exists” & “what data means”. Duplicate applications and data
    • Inability of apps to interoperate due to platform incompatibility
    Interoperability
    • Current IT assets cannot be quickly repositioned.
    • Decision cycles are unnecessarily lengthened by vertical stovepipes
    • More time spent patching systems together than adding mission critical capabilities
    Agility
    • Integrating data & process stovepipes is expensive & wasteful
    • Operations costs are a rising percentage of the budget
    • Duplicate data entry and manual data reconciliation create higher labor costs
    Costs
    • Systems and organizations duplicate work
    • Data used across an organization is often inconsistent and potentially inaccurate
    • Information stovepipes require point-to-point integrations that limit flexibility and create process overhead
    Process & Data
  • 23. SOA – Service Oriented Architecture
    • SOA of today:
    • is predominantly IT focused. You could say it is really Service Oriented (Technology) Architecture. SOTA aims to:
    • Ease integration between IT systems.
    • Enable reuse of IT assets.
    • Reduce cost of IT overall.
    • Unify business with technology.
    • It does this by ensuring (technical) services are:
    • Agnostic (i.e. Context Adaptive)
    • Loosely coupled
    • Layered
    • Standardized
    • Even in the tech realm the real issues are business related:
    • Who pays for what?
    • Governance
  • 24. SOA – Service Oriented Architecture SOA: Clients, Services, Middleware and a Registry Gartner Reference Service in a SOA Business software component, designed to be invokable by name from external contexts via a well-defined, programmatic interface. Service Interface Service Implementation SOA Software design pattern consisting of any number of registered services and service consumers (clients) in loosely coupled relationships. Interface Proxy Service Consumer (Client) Registry Repository Service Enterprise Service Bus (ESB)
  • 25. SOA – Service Oriented Architecture Source: Gartner - Hype Cycle for Web Technologies, 2006 - (July 2006): Authors: Gene Phifer et al
  • 26. SOA – Service Oriented Architecture Example: Secure Channel Moving from this... From a web of duplicated services and user registration… IVR kiosk www e-mail e-mail IVR www www e-mail kiosk Clients of Government services - Individuals - Businesses Government services Government services Data Data Data
  • 27. SOA – Service Oriented Architecture Example: Secure Channel ... to this Programs CPP EI Tax credits SIN Tax status changes Vital Statistics
    • Birth
    • Death
    • Marriage
    Gov’t services Gov’t services Service Integration via the Secure Channel Service integration Translation of data Directory of Services Acquiring Data Clients of Gov’t services
  • 28. SOA – Service Oriented Architecture ISSUE: A Silo’ed solution to an integration problem? How many service exchange communities does ‘A’ belong to? TAX Community SOA Solution Programs A EI Tax credits SIN Tax status changes Vital Statistics
    • Birth
    • Death
    • Marriage
    Secure Channel SOA Solution Programs A EI Tax credits SIN Tax status changes Vital Statistics
    • Birth
    • Death
    • Marriage
    Health Community SOA Solution Programs A EI Tax credits SIN Tax status changes Vital Statistics
    • Birth
    • Death
    • Marriage
    Market Place SOA Solution Programs A EI Tax credits SIN Tax status changes Vital Statistics
    • Birth
    • Death
    • Marriage
    Will the Semantic, Contract, Technology, Registry and Governance models agree or interoperate?
  • 29. SOA for Business and Technology Business & IT: Common SOA Solution
    • Service Oriented Technology Architecture (SOTA)
    • is well underway with things like Web Services
    • Service Oriented Business Architecture (SOBA)
    • is on the move with things like GSRM and BTEP
    WHAT 140v1 How do these relate?
  • 30. SOA for Business and Technology Business & IT: Many Parallel Needs
    • Reuse business services
    • Service Level Agreements
    • Service catalogue
    • Ability to inter-operate with other jurisdictions and service delivery partners seamlessly
    • Program & Departmental autonomy
    • Deliver value (in discrete and measurable units)
    • Reuse system components
    • Interface specifications
    • Service registry/repository
    • Loosely coupled interoperable components acts as discrete “building blocks”
    • Self-contained and abstracted
    • Services are “stateless”
    Business Needs Technical Parallel
  • 31. SOA for Business and Technology SOA:The Business View
    • SOA can be applied to business irrespective of technology .
    • Service Oriented (Business) Architecture aims to:
    • Ease integration between Business entities.
    • Enable reuse of business assets.
    • Reduce cost of business overall.
    • Unify business with business . (e.g. Joined-up Program services)
    • It does this by ensuring (business) services are:
    • Agnostic (i.e. Context Adaptive)
    • Loosely coupled
    • Layered
    • Standardized
    • As with the tech realm the real issues are business related:
    • Who pays for what?
    • Governance
  • 32. SOA – Service Oriented Architecture SOA:The Technology View Service Oriented (Technology) Architecture How does SOTA look against our views of the GC? Perspectives Policy - Citizen Demand - Problem Definition, - Goals & Outcomes Programs - Program Performance - Program Alignment Services - Service Definitions - Metrics & Measurement Processes - Process Maps - Work Definitions Resources - Human, Technical - Financial, Information { { { { { } } } } }
    • Examples
      • Policy & Legislation
      • - National Security Policy
      • - Privacy Policies
      • - Government Security Policy
      • Programs
      • - Health,Public Safety
      • - Information Management
      • Services
      • - Inspection
      • - Income Security Funds
      • Processes
      • - Application for benefit
      • - Financial mgmt processes
      • Resources
      • - Technical Ref Model
      • - Specifications
      • - SOAP, XML, etc.
  • 33. SOA for Business and Technology SOA:The Business View Service Oriented (Business) Architecture How does SOBA look against our views of the GC? Perspectives Policy - Citizen Demand - Problem Definition, - Goals & Outcomes Programs - Program Performance - Program Alignment Services - Service Definitions - Metrics & Measurement Processes - Process Maps - Work Definitions Resources - Human, Technical - Financial, Information { { { { { } } } } }
    • Examples
      • Policy & Legislation
      • - National Security Policy
      • - Privacy Policies
      • - Government Security Policy
      • Programs
      • - Health,Public Safety
      • - Information Management
      • Services
      • - Inspection
      • - Income Security Funds
      • Processes
      • - Application for benefit
      • - Financial mgmt processes
      • Resources
      • - Technical Ref Model
      • - Specifications
      • - SOAP, XML, etc.
  • 34. SOA for Business and Technology * Common language between business, information & technology based on SERVICES. Perspectives Policy - Citizen Demand - Problem Definition, - Goals & Outcomes Programs - Program Performance - Program Alignment Services - Service Definitions - Metrics & Measurement Processes - Process Maps - Work Definitions Resources - Human, Technical - Financial, Information { { { { { } } } } }
    • Examples
      • Policy & Legislation
      • - National Security Policy
      • - Privacy Policies
      • - Government Security Policy
      • Programs
      • - Health,Public Safety
      • - Information Management
      • Services
      • - Inspection
      • - Income Security Funds
      • Processes
      • - Application for benefit
      • - Financial mgmt processes
      • Resources
      • - Technical Ref Model
      • - Specifications
      • - SOAP, XML, etc.
    SOTA SOBA * Service Orientation
  • 35.
    • Enterprise Architecture is need for successful change.
    • Business Architecture is needed for successful business change.
    • Service Orientation should be viewed as a useful general model. One which can be applied to technology and/or business.
    • It’s a new way to think of things but ‘we won’t solve today’s problems with the same thinking that created them.’ - Einstein
    Conclusion
  • 36. “ Maybe we can show government how to operate better as a result of better architecture. …”* Frank Lloyd Wright -1939 * - http://www.giga-usa.com/quotes/authors/frank_lloyd_wright_a001.htm
  • 37. Contacts
    • Rick Bryson
    • Deputy Chief Architect
    • Government of Canada
    • Treasury Board of Canada Secretariat
    • Chief Information Officer Branch
    • 2745 Iris Street 6 th Floor
    • Ottawa, Ontario, Canada K1A 0R5
    • Email : [email_address]
    • Gary Doucet
    • Chief Architect
    • Government of Canada
    • Treasury Board of Canada Secretariat
    • Chief Information Officer Branch
    • 2745 Iris Street 6 th Floor
    • Ottawa, Ontario, Canada K1A 0R5 Email : [email_address]
    Q: “Who do I talk to regarding BTEP/GSRM?” A: The contacts for BTEP and GSRM are: Contacts and Questions
  • 38. Questions? Contacts and Questions
  • 39.  
  • 40. BTEP/GSRM Management Sharing and Engagement
    • Q: “What are the ‘feds’ doing with the GSRM?”
    • A: Intent is for TBS to transfer GSRM Business Reference Model to a public sector non-governmental organization for stewardship as quickly as possible.
    • Q: “What tools and instruments do you have for BTEP/GSRM?”
    • A: We are developing a GSRM Meta-Model Specification Version 2 using the Universal Meta-Model (UMM) from the UN/CEFACT – using UML allows for GSRM designs and artifacts to be implemented (e.g. Process and below) by information systems professionals.
    • Q: “How do I get hold of some of the work done so far?”
    • A: The Treasury Board CIOB website will be updated to provide available GSRM artefacts, and supporting documents, templates, etc. We will be pursuing a federated repository. (see following slides)
    BTEP/GSRM Mgmt – Sharing and Engagement
  • 41. BTEP/GSRM FAQ’s
    • Q: “BTEP V2.0 – looks good but what do we do now?”
    • Q: “How do I get BTEP/GSRM changed?”
    • Q: “So what EXACTLY is the GSRM anyway?”
    • Q: “Who is using BTEP/GSRM out there?”
    • Q: “I have a methodology that does what BTEP does, how do I work GSRM into the mix?”
    • Q: “I don’t need the whole meal (BTEP SD&P) – I just want a salad!”
    • Q: “What are the ‘feds’ doing with the GSRM?”
    • Q: “What tools and instruments do you have for BTEP/GSRM?”
    • Q: “How do I get hold of some of the work done so far?”
    • Q: “Who do I talk to regarding BTEP/GSRM?”
    BTEP/GSRM FAQ’s
  • 42. BTEP/GSRM Management Status and Change
    • Q: “BTEP V2.0 – looks good but what do we do now?”
    • A: What we are doing now is:
    • Establishing a baseline of BTEP/GSRM products
    • Establishing GSRM Foundation Model
    • Updating our website with newer products and artifacts
    • Introducing New EA products
    • Q: “How do I get BTEP/GSRM changed?”
    • A: We are creating an initial Configuration, Change and Release structure to manage BTEP/GSRM products
    • Q: “So what EXACTLY is the GSRM anyway?”
    • A: We are currently creating:
    • A GSRM Business Reference Model (BRM) as a separate product specification (initially to be Version 2.1)
    BTEP/GSRM Mgmt – Status and Change
  • 43. BTEP/GSRM Management Communities of Practice
    • Q: “Who is using BTEP/GSRM out there?”
    • A: BTEP/GSRM is and will be used by:
    • Public Sector forums
      • Public Sector CIO Council
      • Public Sector Service Delivery Council
    • Government of Canada Departments
    • Provincial, Regional, Municipal and Aboriginal governments
    • Industry - public sector service consultants
    • Industry - public sector IM and IT professionals
    • Industry vendors (tools) for public sector
    • International users
    • Enterprise Architecture Community of Practice (representing all of the above)
    BTEP/GSRM Mgmt – Communities of Practice
  • 44. BTEP/GSRM Management Communities of Practice
    • Q: “I have a methodology that does what BTEP does, how do I work GSRM into the mix?”
    • A: The development of a GSRM Practitioner’s Handbook
    • Q: “I don’t need the whole meal (BTEP SD&P) – I just want a salad!”
    • A: Need to engage an active EA Community of Practice to incorporate “lessons-learned” (already have received some) – and principles based tailoring guidance and methodology mapping guidance into the BTEP suite of documents including the Handbook for Practitioner’s and SD&P guide.
    BTEP/GSRM Mgmt – Communities of Practice