SOA Landscape Recommendations By >

Who we are  Team Members  Company History  Current & Past Client Projects  Note: have fun here. Make up your history. Add “logos” of your past client projects

Agenda  Overview  Current Landscape  Future Landscape  Governance Recommendations  Appendix (*) (*) Technical Details for IT and Development Team

Overview

Purpose & Scope  Analyze existing systems and design interaction behavior between the Global Company, Magento store and Cyber security to build a single service oriented application.  The business goals for this application

Purpose & Scope - Business goals  Credit card authorization and payment should be automated by integrating with Cyber Security. However credits will continue to be manual.  Reuse the Magneto's storefront with Global company's UI. However the brand names have to be separate because Magento could possibly sell products by itself in future  Orders have to be fulfilled and shipped automatically. Provision to apply certain rules on orders and process them manually if required. For e.g. orders > $1000 should be processed manually.  Add UPS shipment service for automated shipping.  Integration with Twitter for sales announcements.  RAM, Disk storage and Environments can be increased/decreased automatically with integration with Cloudshare services.

Purpose & Scope - Technology goals  Global company's current investment in Oracle SOA should be kept. However recommendations for service inventory and upgrade to 11g is desirable.  The Global company's SOA services should be used for Cloudshare's credit card processing and recurring billing  Replace the current store based tax calculation with online real-time shipment and tax calculation.

Overview of Business Units  Global  Magento  CloudShare  Note: describe what each business does and est. annual revenue (make numbers for revenue!)

Users Interviewed  Note: for each business units

Outline of Findings  I.E. Abstract of key findings and recommendations  Sets the Stage for the rest of the presentation  Note: also useful as a “short version” of presentation giving CEO’s key findings without getting into the details.

Current Landscape

As-Is Business Processes  Diagrams (about a few slides each as needed):  Use Case Overview Diagram  Global & Magento Business Process Model  Order Fulfillment  Order Returns  Back Office Systems  CloudShare Business Process Model  New Subscription  Payment Processing  Use Case Scenarios  End-to-end sequence diagrams for key Use Cases

As-Is SOA Landscape  SOA Architecture Logical Component Diagram  List of Core Services and Key Contracts  Highlight “hot spots” where changes are needed  Identify Key Challenges  Note: stick to problem definition here. Do not discuss solutions yet – that’s for the next section.

Future Landscape

To-Be Business Processes  Diagrams (highlight changes in a different color):  Use Case Overview Diagram  Global & Magento Business Process Model  Order Fulfillment  Order Returns  Back Office Systems  CloudShare Business Process Model  New Subscription  Payment Processing  Use Case Scenarios  End-to-end sequence diagrams for key Use Cases

To-Be SOA Landscape  SOA Architecture Logical Component Diagram  List of New Services and Contracts  Highlight Key Changes which addresses the Challenges identified in As-Is State  Include:  Integration of PCI Compliant Payment Service  Integration of new shipping service(s)  Other recommended services  Note: don’t put details here (put them in the appendix)

Governance Recommendations

Governance Notes:  Management Policy Changes  Policy Table  Recommended Service Granularity Approach (Ref: SOA Governance Patterns)  PCI Compliance Validation  SOA Architecture Maintenance  Web Service Versioning of Key Contracts (Ref: Service Life Cycle)  Change Management around Data Models  Infrastructure Upgrade Roadmap  Move to Hybrid Cloud?  Upgrade to SOA Suite 11g

Appendix

Appendix:  Include  Any Design Design Details (i.e. explain “why”)  Architecture Prototypes (that support recommendations)  Web Service Contracts (request/response examples) used in analysis leading to recommendations  UI Screenshots of recommended changes  Etc…