Post on 24-Feb-2016
description
Specialists in Service Oriented Application Modernization
www.everware-cbdi.com
12th Federal SOA for eGov ConferenceOctober 11, 2011
Presented by
Dave Mayo (dmayo@everware-cbdi.com) Denzil Wasson (dwasson@everware-cbdi.com )
What is a Composable Service?
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
Topics
State of SOA in Federal Government History of Federal Sharing Initiatives Shared Services vs. SOA Composable Services
Demo: Composable Services in Agile IT – Denzil Wasson
SOA Model-Driven Development
2
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
State of SOA in Federal Government
The Good Guidance & direction from OMB & CIO Council – the pressure is building Most agencies recognize the need for SOA as a best practice and are taking
steps to adopt it Business/mission side is getting more involved
Cloud computing is driving interest in SOA Some successes in implementing SOA
The Bad Many still consider SOA to be an integration technology Some have tried and hit the wall – mostly because they did not consider all
of the CSFs for SOA (Roadmap planning, Governance, SOA Maturity) Many services sit in the registry and are not consumed due to poor service
specs and lack of defined policies (governance) SDLCs do not incorporate service discovery and consumption steps
Confusion between Shared Services and SOA
3
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
History of Federal Sharing Initiatives
4
Quicksilver2001
Cloud-First2010
E-Government Act2002
Clinger-Cohen1996
E-Gov InitiativesInitial 25
2003
Lines of BusinessInitial 5 (HR, GM, FM, FHA,CM)
2004
Lines of BusinessRound 2 (Geo, BFE, ITI, ISS)
2006
Payroll Consolidation Completes
2009
GAO Report: Opportunities to Reduce Potential Duplication
2011
E-Gov InitiativesRound 2 (DAIP, ITDS, IAD-Loans/Grants)2008
Shared Services2011
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
What is a Shared Service?
5
Roles: Provider, Producer, Consumer Sources: Internal or external to the agency
(government or commercial).
Shared ServiceProducer ConsumersProvider
OMB Definition: Mission or support function that is provided by one business unit to multiple business units.
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
CIO Executive Board Survey – Shared Services
Survey of 50 large corporations Only 40% of businesses able to capture the cost-saving
benefits of shared services Inadequate set of services or services hard to use Lack of customer focus and service skills No long-term plan to ensure continued cost savings (TCO)
Best organizations generated: Strategic benefits (eg, agility) Significant cost savings
Conclusion “Best shared service organizations understand that service
orientation and long-term strategy are the most critical components for success.”
In other words – Service Oriented Architecture!
6
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
What is Service Oriented Architecture
7
“Service” – Independent unit of functionality that is accessed via a well-defined interface; consumer needs are met by provider capabilities
“Oriented” – Beyond a single service; covers a business domain & includes governance, management, and administration of the services in the domain
“Architecture” – Critical factor in managing complexity; ensures that all components work together and boundaries are clearly defined
SOA Principles Loose coupling Service abstraction Statelessness Discoverability Interoperability Autonomy Standard service contract Composability
It’s Not SOA, if there is no ARCHITECTURE!
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
Shared Services vs. SOA
8
Shared Service, but not SOA
Shared Service
Silos, Unstructured code, Point-to-point Shared Service with SOA
Shared Service
Layered Service Model
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
Benefits of Services
9
Business Agility Time to Market –
Speed! Customer
responsiveness IT flexibility
Reuse Cost savings Consistency Collaboration &
interoperability Skills transfer
Service OrientedArchitecture
Shared Services
SOA is an Architecture; Shared Services is a collection of services (eg, JBOWS)
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
Composable Services
10
Shared services must be architected for consumption Well defined interface; well encapsulated; highly independent Discoverable (catalog) – good description/specification Standards for integration, interoperability, semantics, security Functional boundaries determined by architecture
Solution architecture & requirements must consider available services Product Line Approach (SEI)
A software product line (SPL) is a set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way.
Product Line Benefits: Reduction of code size; higher quality code. Uniform look and feel. Common technological platform and code
style. Easier reuse, maintenance and integration Shorter development schedules Lower development and upgrade costs
Lower total ownership costs
Support for an incremental development model
Shared technology costs Best-in-class COTS/government off-the-
shelf (GOTS) components Continuous technology insertion
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
Summary
Composable Services are Shared Services that are designed and architected to work together
In a manner similar to a Software Product Line approach
Adhere to the SOA principles
11
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
Composability Demo: Service Oriented Application Modernization
12
Combines: SOA, Model-Driven Development & Agile Methods
SOAM
SOA
MDA
Agile Methods(SCRUM)
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
Themes for Demo
Services are the composable building blocks Services provide important architectural articulation
points MDD makes it visible, manageable and productive Agile is a good fit
Defined scope Contract driven Early value
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
Business process (snippet)
login Pick an application
Review an application(options)
Submit an application
Review pricing Pay
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
SOA (snippet)
Applicant portal
Security (auth/auth)
Rules
AWS Simple DB
PM App
Payment processor
PaymentsPersistence
process
core
underlying
solution
utility
Examiner portal
Fees
AD AS
D.App
AR
Inbox
AD = Application DraftingAS = Application SubmissionAR = Application ReviewPM = Profile ManagementD.App = Draft ApplicationApp = Application
© 2011 Everware-CBDI IncV2011.1012 www.everware-cbdi.com
Technical Architecture (overview)
JSF web examiner
portal
JSF web applicant
portal
POJO channel
delegates
Service Endpoints
POJO Service implementations
Cloud Services
presentation integration application data
tomcat servicemix Jvm / Amazon (AWS) Amazon (AWS)
OTS Components
Service
ServiceMix ESB
Specialists in Service Oriented Application Modernization
www.everware-cbdi.com
Dave Mayodmayo@everware-cbdi.com
(703) 564-0263
Denzil Wassondwasson@everware-cbdi.com