1. SOA-based Systematic Reuse Key Considerations when building service capabilities Vijay Narayanan Systematic Software Reuse Evangelist http:// www.artofsoftwarereuse.com /

2. SOA-based Systematic Reuse Asking the right questions… Is your dominant metaphor Web Services or Service Orientation? Do you facilitate message exchange patterns beyond synchronous request/reply? Are you leveraging existing assets whilst achieving loose coupling? Are service capabilities aligned with enterprise data standards? Do service contracts use consistent names, namespaces, and reuse types and error codes? Are you trying to build the perfect service? Do you build services in the hope that someone will consume them? Are service capabilities aligned with the organization’s problem domain? Do service capabilities reflect domain concepts and not pursue meaningless abstractions? Ask the hard questions early and often! Legacy Asset Leverage MEPs Sample Fill Domain Alignment Agility Lightweight Governance Development Metaphor Legacy Asset Leverage

9. SOA-based Reuse Isn’t an Island… SOA needs to co-exist with the enterprise’s overall systematic reuse strategy and needs to evolve in conjunction with existing components, frameworks, patterns, and other assets as part of a holistic approach to achieving reuse. Regardless of particular approach, the goals of systematic reuse – quicker time to market, higher quality, ability to create new solutions, and reducing development costs – remain the same. Systematic Reuse Strategy Components Domain specific Assets Frameworks Services Domain agnostic Assets