Enabling the client-centric world.
Business Architecture
Strategies for transformation and innovation


Day 1 – Strategy, Innovation and Business Architecture

1. The change imperative.
    Challenges of business agility.
• Agility and innovation – what do they really mean?
  - Client and citizen-centric pressures
  - Regulatory and compliance requirements
   -What is your innovation culture?
   -Opportunities for new business models
• The role of strategy for Business Architecture (BA)
   –The 5 P’s of strategic management
   –How strategy is really formed
• Business transformation – an outcome of strategy formation
• BA as catalyst for change: Trailing strategy, values & technology trends
• The constraints to agility - Managing accidental and essential complexity

2.  The Business Architecture manifesto.
     Evolving the enterprise.
• Defining Enterprise Architecture (EA) and Business Architecture (BA)
• Business Architecture mission, deliverables, and target groups
• The Business Architecture ecosphere:
  - Enterprise, information, technology, security and policy architectures
• BA’s critical contributions to Enterprise Architecture
• EA and BA contributions to closing the strategy, design & implementation divide

3. Managing change.
    Fundamentals of enterprise models.
• Bridging the fuzzy front-end
• How architectures, frameworks and models
   tame complexity
• Mapping the future:
  - As-is vs. To-be Business Architectures
• Overview of BA approaches
  - BTEP, MDA, TOGAF and others
• The Business Architect as chameleon:
  - Representing strategic, organizational and IT perspectives

4. Bridging the gap.
    From strategy to Business Architecture.
In this interactive workshop, team members use a real world case study to understand the strategy of introducing a direct self-service channel.
• Understanding strategic direction and stakeholder needs
• Value chain and line-of-business analysis
• Ensuring executive buy-in and participation
• Impact of strategic changes on people, process and technology

5. The reality of priorities.
    Managing the transformation portfolio.
• Roadmap to BA deliverables
• Coverage and granularity factors:
  - Business analysis, project and portfolio management
• Building the right skill set: From BA to IT to change management
• The build-out: From projects to strategic portfolio management

Days 2 & 3
Implementing Business Architecture for
the Client-Centric Enterprise

1. Patterns in the business environment.
    The power of reference models.
• The role of reference models
• From abstraction to generalization
• Government reference models (GSRM and others)
• Industry sector reference models

2. First things first.
    Analysis of business goals.
• Needs, goals, outcomes, outputs, and values
• Enterprise-level business architecture analysis: Identifying strategic drivers
• Value proposition and value chain analysis
• Logic models and strategy maps
• Validating business goals

3. Business services design.
   Modeling for a client-centric world.
• Alignment of strategy and outcomes
• Meeting market or constituency needs
• Co-designing with clients – why does Microsoft hire anthropologists?
• Using product and service patterns
• Modeling valued outputs of the enterprise
• Aligning the outputs with intended outcomes

4. Understanding the value chain.
    Organizational design for Business Architecture.
• The extended enterprise
• Modeling value chains and core processes
• Expressing the impact of strategy on the current value chain
• Abstracting common/shared services in the value chain
• Designing vertical and horizontal accountabilities
• Managing outsourcing
• Building in trust: Security and privacy

5. Getting the semantics right.
    Creating a shared understanding.
• The conceptual business model and its role
• Modeling for the bilingual Business Architect
  - Business and technical language competencies
• Understanding the structural view
• Business components and their relationships
• Input to the enterprise information model

6. The times they are a changing.
    Lifecycle analysis.
• Understanding the behavioral view
• The state transition model:
  - Modeling behavior over time
• Combining semantic and state transition models

7. Living with distributed services.
    Modeling business processes.
• Understanding the functional view
• Businessand distributed use cases
• Implications for applications and service-oriented architecture (SOA)
• Business Architect as lead enterprise designer
• Process and integration standards 

8. Gaining enterprise agility.
    Capturing policy and business rules.
• Environmental implications on strategy
• Impact of strategy changes on business & policy
• Externalizing policies and business rules
• Transparency of business processes
• Modeling business rules
• Business scenarios

9. From over-the-counter to 24/7.
     A world of disintermediation.
• The challenge of conducting business anytime, anywhere with anyone
• Business network model:
  - Implications for the technology architecture
• Workflow architecture
  - Design/simulation of enterprise-wide workflows and business processes

10. Building the business blueprint.
       Achieving the adaptive enterprise.
• Business modeling tools: Managing business design knowledge
• The reality of strategy dynamics:
  - Ongoing adaptation in a client-centric world
  - Sensitivity of Business Architecture artifacts and models to change
• The portfolio of business and IT investments
• Business Architecture governance

Copyright 2007 Intervista Inc.



“I congratulate you on the high caliber of your speakers — they bring a wealth of knowledge to supplement the course material.”
Carol Lachapelle
Director, Information Management
NB Department of Transportation

“Absolutely excellent, current and immediately applicable.”
James Meck
Chief Architect
BAE Systems

“The pragmatic approach is helpful and appreciated.”
Carol Bingaman
Program Manager
Commonwealth of Pensylvania



(Intervista is now offering DAMA & EAIG members a 10% discount on all of our courses)



Group discounts do not apply for customized courses. Educational sessions scheduled outside continental United States and Canada are subject to a 20% surcharge on tuition fees.

back to top


To register for this course, complete our online registration form or call 1-800-397-9744. Outside North America +1 514 937-7130.

Professional Accreditation
Certain professional associations may recognize Intervista courses for credit to satisfy your continuous education requirement. Present the course outline to your board for confirmation. These courses provide approximately 21 hours of advanced instruction.

back to top


Business architecture & modeling bibliography

Architecture and project management
Bloomberg, Jason and Schmeltzer, Ronald, Service Orient or Be Doomed!: How Service Orientation Will Change Your Business, John Wiley & Sons, 2006, A comprehensive survey of key SOA concepts and approaches to implementing SOA. Bloomberg and Schmeltzer are principals at Zapthink, thoughtleaders in the Service Oriented Architecture space. They also teach the Intervista SOA seminar.

Whittle, Ralph,  Myrick, Conrad, Enterprise Business Architecture: The Formal Link between Strategy and Results, CRC Press, 2005. Discusses the value proposition of business architecture and the enterprise model framework required to generate a business architecture along with links to other architectural domains.

Brooks, Frederick P., The Mythical Man-Month: Essays on Software Engineering, 20^th Anniversary Edition, Addison-Wesley, 1995. Chapter 16, No Silver Bullet, Essence and Accident, discusses essential and accidental complexity.

Business objects
Penker & Erikson, Business Modeling with UML: Business Patterns at Work, Penker and Erikson propose a number of UML extensions to support modeling of business processes in UML. They also provide a number of business modeling patterns based on a case study.

Taylor, David, Object Technology: A Managers Guide, 2^nd edition, Addison-Wesley, 1997. The 2^nd edition of David's classic introduction to object technology. In addition to discussing key concepts like objects, classes, and messaging, it covers more recent concepts such as interfaces, components and the applicability of object technology to modeling enterprises as complex adaptive systems.

Taylor, David, Business Engineering with Object Technology, Addison-Wesley, 1995. This book introduces the fundamental concepts of convergent engineering including using objects to model businesses, a business object semantics and responsibility-driven business design.

Fowler, Martin, Analysis Patterns, Reusable Object Models, Addison-Wesley,1997. Fowler extends the pattern approach to the field of business modeling. He has a number of common patterns to model common business problems like representing the structure of a business enterprise, measuring business performance, modeling business agreements, etc. I found it quite helpful when designing the performance and operations management system in its discussion of measurement patterns including unit of measure conversion patterns. He also has an excellent section on architectural layers for multi-tier architectures.

Gale/Eldred, Getting Results with the Object-Oriented Enterprise Model, SIGS Books, 1996. This book relates enterprise modeling to fundamental thinking in general systems theory and current management models like Porter's value chain. It is a pretty thick and earnest book, but I found some quite useful thinking throughout.

Model driven architecture
Frankel, David S, Model Driven Architecture: Applying MDA to enterprise computing, Wiley, 2003 This book looks at modeling languages as programming languages (rather than simply design tools). It looks pragmatically at what can be accomplished with MDA today towards the promise of generating executable code from platform independent business models.

Hubert, Richard, Convergent Architecture: building model-driven J2EE systems with UML, Wiley, 2001. This book relates business architecture and design to systems architecture and design using the concept of “convergent” business components. This is the first practical how-to-guide to applying the concept of model-driven architecture from OMG, an international standards-setting group that established UML as a modeling standard.

Object methodology & technology
Gamma et al, Design Patterns: Elements of Reusable Object-Oriented Software, Addison Wesley, 1995.  This seminal book in the "pattern language of programming" field is indispensable for designers of object based systems who have to work with object developers in producing executable code. It presents a set of generalized patterns to solve and implement common design problems (eg, how to implement fractal objects using the "Composite" pattern or state dependent behavior, using the "State" pattern. It is pretty technical and has sample code fragments in Smalltalk and C++.

Wirfs-Brock, Rebecca, et al, Designing Object-0riented Software, Prentice Hall PTR, 1990. Wirfs-Brock and her associates introduced the responsibility driven design method in this book which applies the technique to the development of a variety of software systems. This book provided much of the inspiration behind the design methodology used in convergent engineering, a precursor to business architecture.

Jacobsen, Ivar, The Object Advantage, Business Process Reengineering with Object Technology, Addison-Wesley, 1995. Jacobsen is a real pioneer in the application of object technology to the development of business systems. His use case methodology and Objectory process are at the heart of the Unified Modeling Language (UML) and the Rational Unified Process (RUP). I find the "uses" and "extends" relationships between use cases to be an excellent way to decompose business requirements. I also use some of his use case scripting techniques as a way to write scenarios.

Schlaer/Mellor, Object Life Cycles, Modeling the World in States, PTR Prentice Hall, 1992. A follow on book to Modeling the World in Data (which proposed a data driven approach to designing objects). The states book provides a very accessible discussion of modeling object life cycles, including events, state transitions and state dependent behaviour. The Schlaer/Mellor methodology has received greatest acceptance in the design and development of real time systems.

Firesmith/Eykholt, Dictionary of Object Technology, The Definitive Desk Reference [DOT], SIGS Books, 1995. This is an indispensable reference book for anyone involved in trying to understand the many, often conflicting uses of terms in object technology by different methodologists.

Complex adaptive systems
Holland, John H., How Adaptation Builds Complexity, Addison-Wesley, 1995. The first two chapters of this book provide an excellent overview of the fundamental elements of complex adaptive systems and the adaptive behaviour of agents. The balance of the book describes attempts to develop computer simulations and a theory of complex adaptive systems.

Websites and Communities
Public Sector Enterprise Architecture Community of Practice is a forum and news group for individuals interested in enterprise architecture and reference models like the Governments of Canada Strategic Reference Model (GSRM). It was established by Gary Doucet (Chief Architect, Government of Canada) and Dave Wallace (CIO, City of Toronto, formerly CTO for the Province of Ontario, and was on executive exchange with Chartwell as VP of the National Public Sector Program). Moderator of the community of practice can be reached at PS_EA_COP-owner@yahoogroups.ca.

Enterprise architecture links: links to a wide range of EA websites can be found at http://www.ewita.com/links/links.htm


© 2007 Intervista Inc.

back to Educational Programs main page
back to top