1

BPM14 – Enterprise Architecture Modeling as a Framework to Model Driven DevelopmentSteven Strutz Tamura Hinojosa

Primary objective was to be able to “reason” about the impact of changeImpact Analysis Requirements ManagementTraceability Continuity – Conformance – Consistency

So, where is that place and how will I move the earth…

2

Common Architectural ComponentsOrganizationCollectionsCollaborationGovernance

Architecture provides the basis and context within which to reason about transformationsFocus on perspectives

Architecture provides the framework within which to consider proper placement of components The definitions for Architecture provide our first clue…Architecture facilitates reasoning about…

3

Enterprise Architecture provides the framework within which to…Visualize the proper placement of Information Technology assets

- Connective tissue between business and information technology assets that satisfy the business needsVisualize the proper context and relationships of Information Technology assets

Enterprise Architecture provides the roadmap for Information Technology investments Meets the needs of business and technology constituents by providing subject matter expertise to envision new

and improved ways of performing business operations and functions by utilizing technology in new and improved waysVis-à-vis the Operating Model for the Business

4

5

Strategic Planning Assumption: Through 2006, vendors, users and trade press will continue to use the term SOA in ways that are incompatible or incorrect (0.8 probability).

Enterprise Architecture enables Information Technology to help solve the “right” business problemsReasoningDecision-making

Significantly change and expand the role of the Enterprise Architecture team to provide facilitation, leadership, and guidance by taking a holistic view of business and technology processes and information

Transform designs seamlessly from business constituents to Information Technology personnel using model-driven approaches that clearly communicate approach, technology components, and design requirements

Enterprise Architecture positioned to become strategic differentiator TraceabilityImpact Analysis Reason about…

The Enterprise Architecture Model framework to manage requirements Turning Goals Into RealitiesThe Enterprise Architecture specifies the common set of Information Technology standards and goals,

establishes common objectives for decision makers, facilitates governance and conformance to standards, and provides for compatible interfaces through four main components:- Business Processes: Architected (not designed) to produce repeatable, reliable, transparent results across

the enterprise. - Software Applications and Components: Defining overall structures, interfaces, policies, priorities and

standards leads to consistent decisions about automation, resource allocation, and which applications should be supported by third-party software or custom development.

- Data Resources: Standards help define the responsibility for data acquisition, ownership and maintenance, and help avoid redundancy and inconsistency. Data required by one part of the enterprise can also be shared with minimal translation, reformatting and bandwidth expenditure.

- Technology: Includes software applications, middleware, software development and maintenance tools, operating software, hardware platforms and communications facilities. Defining rules and standards for component selection, placement and ownership can ensure seamless communication among applications in different parts of the enterprise.

13/06/2015

IBM Confidential 6

The Enterprise Architecture Model framework to manage requirements Turning Goals Into RealitiesThe Enterprise Architecture specifies the common set of Information Technology standards and goals,

establishes common objectives for decision makers, facilitates governance and conformance to standards, and provides for compatible interfaces through four main components:- Business Processes: Architected (not designed) to produce repeatable, reliable, transparent results across

the enterprise. - Software Applications and Components: Defining overall structures, interfaces, policies, priorities and

standards leads to consistent decisions about automation, resource allocation, and which applications should be supported by third-party software or custom development.

- Data Resources: Standards help define the responsibility for data acquisition, ownership and maintenance, and help avoid redundancy and inconsistency. Data required by one part of the enterprise can also be shared with minimal translation, reformatting and bandwidth expenditure.

- Technology: Includes software applications, middleware, software development and maintenance tools, operating software, hardware platforms and communications facilities. Defining rules and standards for component selection, placement and ownership can ensure seamless communication among applications in different parts of the enterprise.

13/06/2015

IBM Confidential 7

Make the “right” decision Make the “enforceable” decisions Properly ascertain the impact of any decision on the enterprise or application portfolio

So, exactly how does the Enterprise Architect make this happen?

8

Initially developed to address and focus on software development However, the framework extends to allow for its incorporation into an enterprise architecture model Provides variousViewpointsLevels of Abstraction

Flows directly into…Model-driven Software DevelopmentUse Case FlowdownConceptually the same

- Black box versus white box - Views- Recursive drill-down

9

Triggered by need to manage requirements encompassed by implementation of Oracle ERP and numerous COTS packages

Another thought:Use “Collaborative Environment” to specify process flows for ERP-related “accelerators” and “configurations”

- Enable automated reuse when changing applications in the future- Possible competitive advantage or differentiator

10

Basic Enterprise Architecture Model developed as a framework with which to manage business requirements and

reason about the impact of change.

An ecosystem, if you will…

Solves the problems of…

- Throwing “it” over the wall

BEAM facilitates requirements management incorporating viewpoints from various competing perspectives in an

environment that promotes collaboration, continuity, conformance and traceability among the artifacts and models

that represent the layers of abstraction necessary to succinctly and clearly articulate business requirements.

Behavior and requisite information – hand-in-hand

The framework emanated from the need to provide an easily understood instantiation of the SDLC and its model-

11

driven approach.

The framework provides a mechanism for guiding and promoting Information Technology maturity.

Semantics

Tribal Knowledge

Virtual Representation

Component of Enterprise Environment

11

Levels of Abstractions ViewpointsPerspectivesDimensions

12

Transformation Tactic

13

The key to this framework is the collaborative environment within which it becomes easier to reason about the changes affecting business requirements, behaviors, and the information associated with those behaviors.

Architectural KnowledgebaseCollaborative Environment

The collaborative environment comprises the IBM Rational Tool StackRequisiteProRational Software Modeler (RSM)Rational Software Architect (RSA)Rational Application Developer (RAD)Rational Data Architect (RDA)ClearCaseClearQuest

The IBM Rational Tool Stack provides the instantiation of the framework and facilitates impact analysis, traceability, and continuity of business requirements.

14

Collaborative Environment component compliment

15

Collaborative Environment component compliment

16

Employed Industry Best practices for managing Enterprise Architecture activities and collaborations with projects There are other activities to do when coding software…

Enterprise Architecture PhasesFeasibilityInceptionElaborationBusiness-as-Usual

Enterprise Architecture Discipline – a la Charles EdwardsArchitecture

- Business- Information- Technology

Management- Risk- Issues- People

Foundation- Change control- Configuration- Processes and Tools

17

18

Strategic Planning Assumption: Through 2006, vendors, users and trade press will continue to use the term SOA in ways that are incompatible or incorrect (0.8 probability).

“Bridge the gap” between the different “languages” spoken and used by business and technology personnel Establish and maintain relationships with key business constituents Collaborate with project teams Work with business and technology constituents to identify and examine business issues and improvement

opportunities separating “feasible or reasonable” requests and opportunities from “infeasible or unreasonable” Analyze and model current-state business processes and systems as needed to understand and communicate

capabilities, limitations, and issues Identify and develop improved business processes and information management capabilities to meet business

needs Analyze opportunities for using technology capabilities effectively to simplify and improve business operations

19

Strategic Planning Assumption: Through 2006, vendors, users and trade press will continue to use the term SOA in ways that are incompatible or incorrect (0.8 probability).

Support the acquisition and maintenance of information technology investments Develop and maintain the Enterprise Architecture Models Develop and maintain the inventory of architectural artifacts – applications, data, components, infrastructure, etc.

The framework emanated from the need to provide an easily understood instantiation of the SDLC and its model-driven approach.

The framework provides a mechanism for guiding and promoting Information Technology maturity. There are a number of initiatives that demonstrate the framework and the supporting IBM Rational Tools:Collaborative EnvironmentEnterprise Information ManagementRequirements ManagementImpact Analysis

These projects form the foundational prototypes of our IBM Rational investment and implementation.

20

21

22

23

24

25

26

27

28

This is not revolutionaryBased on time-tested Frameworks and Patterns

- Zachman- TOGAF- RUP- AgileEA- Ambler- Fowler- Martin- Gang of Four (Gamma, et. al.)

Based on Industry Best Practices- Years of consulting experience and practice- As expressed by Gartner, Forrester, et. al.

Based on Common Sense- Variety of flavors and colors- Collaboration

What is revolutionary:If someone actually employed the framework

- Unfortunately, RUP and Agile are used as excuses for not doing requisite activities- The failure is that we are unable to ascertain the impact of proposed changes to the catalog of applications

- A catalog that grows in complexity every day…

29

Simply to reason about the impact of changes…

30

31

With the impending transformation from legacy (anything today) to web-enabled, role-playing, or software-as-a-service paradigms facilitated by service-oriented architectures, corporate proprietary algorithms require proper placement among the enterprise architectures to ensure gaining the most from their capabilitiesVis-à-vis

- Operating Model Technology Models One of the newer paradigms for people entering corporate America today…

32

33

34