Services Engineering Process - SOA Blueprint · • Design, development & build tools •...
22
Services Engineering Process Yogish Pai Bl htt // t h bl t Blog: http://entarch.blogspot.com © Copyright 2007 – Yogish Pai The author grants a non-exclusive license to everyone to publish this document in full or part by acknowledging the source Any other usage is prohibited without the express source. Any other usage is prohibited without the express permission of the authors. © Copyright 2008 – Yogish Pai
Transcript of Services Engineering Process - SOA Blueprint · • Design, development & build tools •...
Services Engineering Process
Yogish PaiBl htt // t h bl tBlog: http://entarch.blogspot.com© Copyright 2007 – Yogish PaiThe author grants a non-exclusive license to everyone to publish this document in full or part by acknowledging the source Any other usage is prohibited without the expresssource. Any other usage is prohibited without the express permission of the authors.
© Copyright 2008 – Yogish Pai
Agenda
Introduction
Services Engineering Process
Deliverables by Stages
Services Lifecycle requires seamless flow of information between the three areas of responsibilities
Business Requirements
1 1. Accurately capture the business requirements
information between the three areas of responsibilities
Service Repositor
business requirements 2. Develop the IT solutions to
business requirementsSolution DevelopmentService
Operations
y2
33. Deploy and maintain the
service to business requirements
Initial Priority
Accurately capture the business requirements not only the business capabilities but • Accurately capture the business requirements, not only the business capabilities but also the operations needs
• Eliminate the communication gap between the business and development team, enabling the development team providing business with exactly what they requested as well as reduce cost by reusing servicesy g
• Provide capability to build out the operations infrastructure on an as needed basis
High-Level requirements for each of the three areas of responsibilitiesArea of Responsibility Requirements Potential Tools
• Visually map business process starting from Level 0 down D fi h f th b i
• Business Process MappingR i t C t
responsibilities
• Define each of the business process• Identify business owners for each of the processes• Identify objectives and current business services gaps• Map Input and Output data elements• Prioritize business process and business services• Capture all aspects of business service definitions• Simulate user interface and/or business processes
Line-Of-Business (LOB)
• Requirements Capture• Simulation: User
Experience• Simulation: Business
Process
• Review requirements and identify alternatives for each of the business process
• Design and estimate each of the components for the business services, examples are Portal Services, Integration Services, Infrastructure Services, Data Services, policy service and business (logic) servicesId tif t iti f b i i
Solution Development
• Accept and estimate rqmts.• Identify Business Service
Components: Portal Services, Integration Services, etc.
• Service RepositoryB i S i P tf li • Identify reuse opportunities for business services
• Develop and execute to detailed project plan• Track and report progress to Business & IT Management• Obtain business sign-off of delivery of each of the business
services
• Review requirements and identify infrastructure needs• Establish systems environment consisting of development, system
• Business Services – Portfolio Management
• Design, development & build tools
• QA/Testing tools
• Capacity Planning• Environment management y g p , y
integrations testing, performance testing, user acceptance and product environments
• Assist solutions development teams in systems/application configuration, periodic builds, capacity planning, etc.
• Track and manage dependencies between services and • Deploy and manage business services in production• Provide application support for business services based on business
Service (IT) Operations
g• Business Service
Provisioning and configuration
• Monitoring and dependency management
priority
Review Requirements
Review
Architecture ReviewLine of Business (LOB)
Solutions Development
IT Operations
Prioritize Business Services
Map high-level Business
Processes
Capture Business Services
Requirements
Prioritize and add to
Solutions Portfolio
Review Alternatives & Estimate effort
Propose Solution
Requirements and Analysis
Assign Resources to
Solutions
Design solutions –
Develop, QA and conduct
UAT for
Design and Development
Solutions Development
Team
identify reuse opportunity
UAT for business solution
IT Operations
Assign Resources to
Service Operations
Teams
Identify infrastructure needs
and establish systems
environment
Deploy business solution
Maintain Solution to Business
Requirements
IT Operations
Agenda
Introduction
Services Engineering Process
Deliverables by Stages
Service Engineering Process
Business Requirements
Capture and document high-level business requirements
Business
Business Process Map the business requirements to the business process
Business Services
Map existing business services to the business process
SOA Repository
process
Repository
Service Engineering Process
Business Requirements
Business Every business services could be implemented as one or multiple physical / business services as
Business Process
Business Services
one or multiple physical / business services as illustrated
Biz /Phy
Re-use existing Physical/ Business services wherever possible
SOA Repository
Service Logic
Biz./Phy. Services
Service Assets
Develop missing services
Repository Service Assets
Requirements / Use caseDesign SpecificationsInputs & Outputs Data Elements RequiredDependent on servicesSe ice sed b
Submit developed Service used byVersionsSource code (location)Builds (location)Product Type
services
Portal
ESB
Product AProduct BProduct C
Product 1Product 2
Every service has assets associated with it ESB
Data Services
Infrastructure
Product 2
EII
ETLI&AM
DQ
associated with it
Service Engineering Process
Business Requirements
Business
Business Process
Business Services
Executable
Generate the Service Assembly Model which includes creating the
SOA Repository
Service Logic
Executable Services
Service Assets
Develop missing services
includes creating the logical deployment model
Repository Service Assets
Requirements / Use caseDesign SpecificationsInputs & Outputs Data Elements RequiredDependent on servicesSe ice sed b
Submit developed The Service A bl M d l Service Assembly
Service used byVersionsSource code (location)Builds (location)Product Type
services
Portal
ESB
Product AProduct BProduct C
Product 1Product 2
Approved Services
Assembly Model shall consist only of the approved services
Product Domain Models
ESB
Data Services
Infrastructure
Product 2
EII
ETLI&AM
DQ
Service Engineering Process
Business Requirements
Business
Business Process
Business Services
Executable
Services Assembled is deployed in production by the operations teams
Service Repository
Service Logic
Executable Services
Service Assets
Develop missing services
Service Matrix
Repository Service Assets
Requirements / Use caseDesign SpecificationsInputs & Outputs Data elements requiredDependent on servicesSe ice sed b
Submit developed
Service Deployment
Service used byVersionsSource code (location)Builds (location)Product Type
services
Portal
ESB
Product AProduct BProduct C
Product 1Product 2
Service Assembly
Approved Services
Each of the deployed services is monitored to map back to business services ESB
Data Services
Infrastructure
Product 2
EII
ETLI&AM
DQ
Product Domain Models
business services
Service Engineering Process
Business Requirements
Business
Business Process
Business Services
Executable
BAM
SOA Repository
Service Logic
Executable Services
Service Assets
Develop missing services
Service Matrix
Repository Service Assets
Requirements / Use caseDesign SpecificationsInputs & Outputs Data elements requiredDependent on servicesSe ice sed b
Submit developed
Service Deployment
Service used byVersionsSource code (location)Builds (location)Product Type
services
Approved Services
Service Assembly
Porttal
ESB
Product AProduct BProduct C
Product 1Product 2
Product Domain Models
ESB
Data Services
Infrastructure
Product 2
EII
ETL
DQ
I&AM
Storage
Service Engineering Process: Information M d lModel
Business Requirements
Business
Information Model
Business Services
Map existing business services to the business process
SOA Repository
process
Repository
Sample representation of an Information Model (data flow) by mapping the input, output and the entities (data elements) to p ( )each of the business processes
Service Engineering Process: Information M d lModel
Business Requirements
Business The information model in translated into the data flow for further development and could also be
Information Model
Business Services
flow for further development and could also be mapped to the business processes.
Biz /Phy
Re-use existing Physical/ Business services wherever possible
SOA Repository
Data Flow
Biz./Phy. Services
Service Assets
Develop missing services
The rest of the process remains the same
Repository Service Assets
Submit developed services
Mapping data services to business processes facilitates developing /developing / identifying shared data servicesDetailed data matrix
Services Lifecycle: Actors/RolesActors Actors
C
I
EA
A
C
CIO
R
R
PMO
&
I
C
LOB
I
Dev
I
RM
C
IT Oper
IT Governance
Application Portfolio Management
Capabilities
I
I
BA
C
I
PM
C
A
LOB/IT
I
I
C
C
R
C
C R
I
Req
uir
em
en
ts &
An
aly
sis
C
C
C
C
C
C
I
I
I
I
I
R
Application Portfolio Management
Requirements Gathering
Business Process Modeling
User Experience Simulation
Data Flow Modeling
Business Activity Monitoring
I
R
R
R
C
C
I
R
A
A
A
A
A
A
C
C
C
C
Ap
plica
tio
n
Desi
gn
Applications / Systems / Services Blueprint
Architecture Frameworks / Standards
Service Orchestration Modeling
Service Assembly Modeling*
Service Network Modeling (Deployment Architecture)
I C CCA R
C CI I I CICC AR
I ICAR
I C RI A
I IC I R CICC A
Assign Service Composition/Development
Dev Service Composition
Service Development
Composite Applications: Debugging and testing
CRA C
ARCI C
ARCI C
C ARCI C
Deployment Management and Configuration I II C R ARR C
Op
er
p y g g
Monitoring and Management
Business Activity Management
AI RA
A CI RCR C
R esponsible A ccountable C onsulted I nformed
© Copyright 2008, Pai Systems, LLC
Agenda
Introduction
Services Engineering Process
Deliverables by Stages
Deliverables by Application Lifecycle stages
Feasibility Req. Design Dev QA ReleaseAnalysis Analysis Design Dev. QA Release
Feasibility Analysis
Activities • Organize business owners and establish project sponsorship• Define full set of requirements
Exit Criteria
• Fully funded project• Assigned resources for the entire
duration of the projectq• Iterate on technical and cost feasibility until final scope is
determined• Create project work plan and identify delivery date• Obtain signoff on requirements, schedule and costDeliverables
A li ti R i t
duration of the project
• Application Requirements• Project Scope
© Copyright 2008, Pai Systems, LLC
Deliverables by Application Lifecycle stages
Feasibility Req. Design Dev QA ReleaseAnalysis Analysis Design Dev. QA Release
Requirements Analysis
Activities • Create functional specifications that define how the application will
behave
Exit Criteria
• Business signoff on requirements and delivery date
• Program signoff on Infrastructure• Complete the User Interface design and site map• Revise project plan as necessary based on design• Obtain business signoff on functional specificationDeliverables• Functional Specification
Program signoff on Infrastructure usage
• Program commitment to delivery date
• Architecture Review Board signoff (technical team accepting requirements)
© Copyright 2008, Pai Systems, LLC
Deliverables by Application Lifecycle stages
Feasibility Req. Design Dev QA ReleaseAnalysis Analysis Design Dev. QA Release
Development
Activities • Application Design• Data Model
Exit Criteria
• Architecture Signoff:• Infrastructure• Database
• Design patterns and componentsDeliverables• Technical design document
Database• Network
• User Interface signoff• Development Environment Ready• Architecture Review Board signoff
© Copyright 2008, Pai Systems, LLC
Deliverables by Application Lifecycle stages
Feasibility Req. Design Dev QA ReleaseAnalysis Analysis Design Dev. QA Release
Development
Activities • Complete development• Perform unit level testing
Exit Criteria
• Unit level testing cleared • Code complete for all functionality• Business Analyst documented allg
Deliverables• Development assets• Configuration Documentation
Business Analyst documented all use/test cases
• Architecture Review Board signoff
© Copyright 2008, Pai Systems, LLC
Deliverables by Application Lifecycle stages
Feasibility Req. Design Dev QA ReleaseAnalysis Analysis Design Dev. QA Release
Design
Activities • Plan application testing (System, User, Performance) • Execute System Test
Exit Criteria
• Business signoff on application• User Acceptance Test cleared• Program signoff on performancey
• Execute User Acceptance Test• Complete Performance test• Obtain business signoff for launchDeliverables• Business Approved Application
Program signoff on performance and release plan
© Copyright 2008, Pai Systems, LLC
Deliverables by Application Lifecycle stages
Feasibility Req. Design Dev QA ReleaseAnalysis Analysis Design Dev. QA Release
Design
Activities • Complete detailed release plan and schedule• Prepare production environment for launch of new application
Exit Criteria
• Support Team and processes in place
• Live Applicationp p pp• Create Post-Production support matrix and coordinate with myBEA
Production Support• Train users• Obtain final signoff• Go LiveD li bl
Live Application
Deliverables• Support Matrix• Released Application
© Copyright 2008, Pai Systems, LLC
Thank You
Yogish Pai© Copyright 2007 Yogish Pai© Copyright 2007 – Yogish PaiThe author grants a non-exclusive license to everyone to publish this document in full or part by acknowledging the source. Any other usage is prohibited without the express permission of the authors.
