6 the role of the architect zapthink · the power of the soa center of excellence • soa experts...
TRANSCRIPT
1
Copyright © 2006, ZapThink, LLC 1
The Role of the Architect
Jason BloombergSenior AnalystZapThink, LLC
Take Credit Code: ROLEARCH
Copyright © 2006, ZapThink, LLC 2
The Role of the Architect
Governance
Project Management
Design
Organizational Issues
2
Copyright © 2006, ZapThink, LLC 3
Challenge: SOA is Architecture
Copyright © 2006, ZapThink, LLC 4
What is Architecture?
The fundamental organization of a system embodied by its components, their relationships to each other and to the environment and the principles guiding its design and evolution. (IEEE P1471/D5.3)
3
Copyright © 2006, ZapThink, LLC 5
The SOA Metamodel
• SOA Metamodel is a model of models: Business Model, Service Model, & Implementation Models
• Service model is abstract representation of– Requirements for Services– Services in production
• Model actualized in Service contracts and other Service metadata
Service Metadata
Service Model
Business ModelImplementation
Models
Copyright © 2006, ZapThink, LLC 6
Service Model Drives Contract-First Development
• Service contracts specify required functionality to IT and provided functionality to the business
• Service model represents the clearinghouse for information about IT environment
• Contracts go beyond WSDL:– Usage policies– Security policies– Consumer delivery contracts– Service-level agreements, etc.
4
Copyright © 2006, ZapThink, LLC 7
SOA Foundation: The 4+1 View Model
Logical ViewFunctional requirements
Deployment ViewPlatforms
Process ViewProcesses
Implementation ViewComponents
Use Case ViewSOAs
Data View
Information View
Copyright © 2006, ZapThink, LLC 8
SOA Foundation: The Zachman Framework
5
Copyright © 2006, ZapThink, LLC 9
The Zachman Framework (cont.)
Copyright © 2006, ZapThink, LLC 10
SOA & Zachman
DATA FUNCTION NETWORK
SOA
6
Copyright © 2006, ZapThink, LLC 11
SOA & Zachman (cont.)
SemanticModel
Messages
Events
GovernanceFramework
Policies
RulesPhysical
DataModel
BusinessStrategy
ServiceLifecycle
ServiceNetwork
UIServices
ServiceConsumers
Users
ServiceModel
ProcessModel
SystemArchitecture
ServiceInfra-
structure
BusinessEntities
ComponentArchitecture
LogicalDataModel
SOBAsThe
OrganizationThe
InternetBusinessChange
IdentitiesNetworkNodes
ComponentsSchemas AssertionsElements
Copyright © 2006, ZapThink, LLC 12
The Service Model: Processes
Source: IBM
7
Copyright © 2006, ZapThink, LLC 13
The Service Model: Building Business Services
Source: IBM
Copyright © 2006, ZapThink, LLC 14
Organizational Issues
8
Copyright © 2006, ZapThink, LLC 15
Building the right SOA team
• Shared Services cross organizational boundaries
• Siloed IT management styles are becoming obsolete
• The new role for enterprise architects
Copyright © 2006, ZapThink, LLC 16
Where Do You Find Enterprise Architects?
• Enterprise Architects (EAs) must have the big picture of the relationship between business & technology
• Some are more technical, some are more business-oriented, many organizations put both types together on a team
• Typically rise through ranks internally, because of need for intimate knowledge of business
• Supplement EA team with consultants, but don’t let consultants drive EA
9
Copyright © 2006, ZapThink, LLC 17
Building Support for SOA
• Find your champion– May be LOB manager, CIO, management-
level architect, or other architect
• Build the business case– Solve business problems while
transitioning to new architecture
• Tackle project iteratively within context of overall plan
Copyright © 2006, ZapThink, LLC 18
Change Management Issues
• Organizational change more challenging than technological change
• Keep business focused on TCO
• Focus on human aspects of change management (education, etc.)
10
Copyright © 2006, ZapThink, LLC 19
The “Ivory Tower” Problem
• Architects create design and other artifacts, but don’t have the authority or mandate to require their use
• Development team considers them optional
• Business likes idea of architecture in principle, but short-term needs trump best practices
• When architects are external consultants, the “not invented here” syndrome makes the Ivory Tower worse
Copyright © 2006, ZapThink, LLC 20
The Power of the SOA Center of Excellence
• SOA experts who maintain a knowledge base of best practices– General and company-specific– Design time and runtime
• Drives SOA policy (either explicitly or implicitly)
• Can unify approaches across a large organization
11
Copyright © 2006, ZapThink, LLC 21
Enabling Service Domains
• A Service Domain is a logical grouping of shared Services with a common business context
• Examples: customer-facing Services,purchasing-related Services
• Manage Services by managingthe Domains
• Move away from traditional IT silos for the purposes of managingServices, but retain technical teamsas needed
Copyright © 2006, ZapThink, LLC 22
The Roles of SOA
Use Case ViewSOAs
Use Case ViewSOAs
Use Case ViewSOAs
Logical ViewFunctional requirements
BusinessStakeholders
Information View
InformationSpecialists
Business AnalystsLOB Experts
Process ViewProcess ViewProcesses
Use Case ViewSOAs
Enterprise Architects
Deployment ViewPlatforms
Systems Experts
Data View
Data Experts
Implementation ViewComponents
Component ArchitectsDevelopers
Copyright (C) 2004, ZapThink, LLC
12
Copyright © 2006, ZapThink, LLC 23
The Role of the Architect:Governance
Copyright © 2006, ZapThink, LLC 24
SOA Governance “in the Narrow”
• Governance of SOA initiative
• Design time governance– Are developers and other personnel
following the policies that apply to Services?
• Runtime governance– Are running Services and SOBAs conforming
to runtime policies?
13
Copyright © 2006, ZapThink, LLC 25
SOA Governance “in the Broad”
–Policy management• SOA configured & controlled via metadata,
including policy
–Visibility• Services abstract heterogeneous data sources,
providing necessary business intelligence
–Flexibility• Ability to build Services that address compliance
issues and adjust them as regulations or business needs change
Not just governance of SOANot just governance of SOA……governance in the context of SOAgovernance in the context of SOA
Copyright © 2006, ZapThink, LLC 26
Project Management
14
Copyright © 2006, ZapThink, LLC 27
IT Governance Feedback Loop
Source: LogicLibrary
> Delivery of architectural guidelines and supporting materials
> Governance over project-specific selection of architectural materials
> Traceability of architectural materials used within a project
> Feedback on effectiveness of architectural materials
> Delivery of architectural guidelines and supporting materials
> Governance over project-specific selection of architectural materials
> Traceability of architectural materials used within a project
> Feedback on effectiveness of architectural materials
Copyright © 2006, ZapThink, LLC 28
Project Management for an SOA Project
• Pilot project much like a standard IT project, because business Services not yet in place.
• As your SOA matures, you must shift to a more agile, model-driven approach that requires more flexible project management.
• Basics of project management won’t change (resource management, client management, schedule/dependency management).
• Project managers will have to deal with larger, more diverse teams.
• Maintaining agility requires the project manager to change the project plans over time more frequently.
• Key to keeping SOA projects on track: measurement of key indicators– Quality indicators– Governance indicators– Other indicators
15
Copyright © 2006, ZapThink, LLC 29
The Relationship with Portfolio Management
• SOA rollout projects vs. ongoing Service lifecycleprojects– Break up SOA rollout into individual
projects, based on iterative approach showing business value at each step
• Plan for ongoing change– New Services– New versions of Services– Ongoing reconfiguration of SOBAs,
policies, etc.
Copyright © 2006, ZapThink, LLC 30
Architectural Visioning Session
• Attendees: architecture team, business analysts responsible for business processes
• Provide the SOA perspective
• Processes drive the Services, Services drive the technology
• Split into two initiatives: process definition followed by Service definition
• Balance “big picture” with realistic pilot starting point
16
Copyright © 2006, ZapThink, LLC 31
Key Elements of Successful SOA Projects
• Building the right SOA team– A diverse group that bring different perspectives and
wide-ranging support to the implementation
• Handling organizational/people issues– Human resistance to change more challenging than
the technical issues
• Tackling the project iteratively– Won’t have full spec as you get started
• Managing the Service lifecycle– Very different from the traditional software
development lifecycle (SDLC)
Copyright © 2006, ZapThink, LLC 32
Thank You!
ZapThink is an advisory, analysis, & influence firm focused exclusively on Service-Oriented Architecture, Web Services, & XML.
Read our new book, Service Orient or Be Doomed! How Service Orientation Will Change Your Business.
Jason Bloomberg