Stefan Pappe - Making Soa Operational
- Service Management enabling SOA -
Dr. Stefan Pappe CTO Middleware Services IBM Global Technology Services
© 2008 IBM Corporation
Content
1. Integration of Development and Operations
2. Practitioner point of view
3. Architecture with a vision 4. SOA management 5. Exemplary project approach
6. More best practices
2
Operational SOA
© 2008 IBMCorporation
Every CEO and CIO cares about operational aspects
Partner with the CEO to drive innovation
Enterprise Goals: » Drive top-line revenue
growth Drive IT goals:
Increase the flexibility of the business Deliver new value from existing assets (information and people) Address governance, operational risk and compliance challenges Reduce the cost and complexity of IT operations
»Continue to deliver
bottom-line profit growth
» Run the business while
changing the business
Business depends on quality service delivery
3
Operational SOA
© 2008 IBM Corporation
Integration of the development and operations life cycles
The lack of lifecycle integration between development and operations continues to drive costs up and operational service quality downDevelopment View of IT
Requirements Analysis & Design Implementation Human Factors Architecture Test Packaging Project Mgmt Change Control Documentation Act Surprised Installation Development Testing
Operations View of IT
Help Desk Asset Mgmt Managing Changes IT Strategy Backup / Restore
Deployment Availability Mgmt
System Admin
Throw over Wall Compliance
System Operation Identity MgmtFinancial Mgmt
Risk Mgmt Continuity
Capacity Planning
Security Mgmt
Problem Mgmt
Sometimes Development tends to underestimate Operations (and vice versa)
Most IT organizations spend 7080% on operations
Quality service delivery depends on integration
4
Operational SOA
© 2008 IBM Corporation
Content
1. Integration of Development and Operations
2. Practitionerpoint of view
3. Architecture with a vision 4. SOA management 5. Exemplary project approach
6. More best practices
5
Operational SOA
© 2008 IBM Corporation
SOA Deployment Best Practices & Lessons Learned from 152 projects
Methodical, cross-IBM approach to capture, analyze, feedback SOA deployment experiences
SOA Deployment Lessons Learned / Best Practices Conference executedthrough IBM Academy of Technology Applied standardized Case Study Template
– incl. project information, architecture, project experience, assets&innovation
2007+2008 conferences resulted in 152 case studies, with 950 lessons learned / 870 best practices
Reusable Results
Feedback and reuse in IBM Products and Services White paper for clients with top 5 best practices published at:http://www-935.ibm.com/services/us/its/pdf/wp_five-best-practices-for-deploying-successful-soa.pdf
1. 2. 3. 4. 5.
6
Develop an architecture with a vision for the future Foresee linkages from IT to your business processes Create an organizational culture and skills to support SOA Build a scalable infrastructure Enable operational visibility through governance and service management
OperationalSOA
© 2008 IBM Corporation
Functional and Non-Functional Requirements we typically find in projects confirm the need to focus on infrastructure and operational aspects
16%
5% 21%
Reuse Connectivity Interaction and Collaboration Services Business Process 6% 13% Information as a Service Governance Design Security and Management
5% 2% 3% 10%
8%
Sample NFRs
Availability 3%14%
13%
4%
Flexibility Governance Interoperability
17%
Performance
9%
Sample Functional Requirements
7%
Regulatory
Reliability Reusability
6% 3% 3% 2% 30%
Scalability Security Servicability Standards Technology Usability
7
Operational SOA
© 2008 IBM Corporation
Content
1. Integration of Development and Operations
2. Practitioner point of view
3....
Regístrate para leer el documento completo.