Global Company SOA Landscape Recommendations By eFlix Architects Group, LLC

eFlix Architects Group, LLC EAG Team Members Andrew Bond – Principal Design Architect Jai Mathaiyan – Chief Technical Architect Oleg Shnayderman – Distinguished Lead Architect

eFlix Architects Group, LLC About the group Formed in 2010, we are a dynamic team of professionals, working in close collaboration to deliver custom SOA software projects to a variety of specialized clientele. With years of experience working with a variety of corporations across the spectrum of industries and markets, we deliver solutions that exceed customer expectations. We specialize in: Assessment of existing IT architectures Identify SOA solutions that provide maximum value SOA migration planning and execution Implementing agile software development methodologies

eFlix Architects Group, LLC Past projects, references 2011 – San Jose Mineta Airport – Provided SOA consulting as part of a $6.5 million upgrade from the existing Sperry Univac 1100/2200 based Airport Management System (AMS) to a modern SOA infrastructure allowing Federal TSA system integration, flexible/scalable IT management, coordinated flight information, scheduling and airline database integration.$6.5 million upgrade Sperry Univac 1100/ – eJinni, a project to design a system for small businesses that loan, rent and sell entertainment media and equipment from a retail store, to help them compete with features offered by larger and online competitors, with the flexibility to include online shopping and order shipment options. Incorporating modern SOA techniques, with modular, flexible design allowing quick analysis and debugging of defects, and technical issueseJinni

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

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 Customer Support Operation

Customer Support Outline of Findings Global’s customer support group is located in high-wage, high-cost region (SF Bay area), while Magento support is off-shore (Bangalore) The support process requires relatively low- medium skilled workers, requiring about 6 months train-up period for a worker to be fully productive Recommendation – Workforce restructuring of Global Customer Service staff after a 6 month integration period where the Magento staff can prepare and train-up

Operations Outline of Findings Magento and Global Operation staff are both currently located in high-wage, high-cost region (SF Bay area) Recommendation Magento and Global Operations staff should remain in place for the next 1-2 fiscal years, at least until after a full integration of Magento and Global systems are complete, and the architecture for migration of IT platforms to CloudShare is complete.

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…