文本课件文稿1

1、Mattel SOA PlaybookStep 5: Build Services and Composite ApplicationsApr. 4th, 2012AgendaTIBCO SOA Execution Model and Step 5Step 5 Process FlowCreate Architecture and DesignSequencing of Key Architecture IssuesImplement, Deploy, and TestCode Review CriteriaUpdate Planning Documents and Provide Feedb

2、ackDocuments Templates Walk-throughQuestions?Whats next?TIBCO SOA Execution ModelProven approach to building a strategic SOA/ESB programGovernance and methodology in Mattel Playbook is derived from TIBCO SOA Execution ModelOperate theBusinessDevelop Vision,High-LevelArchitecture,& RoadmapDefine &Imp

3、lement Organization & GovernanceDefine &ImplementTechnical Infrastructure & Standards poseProcessesinto ServicesBuild Services& CompositeApplicationsStep 1Step 2Step 3Step 4Step 5Step 6Output of steps 1-3provides basis for effectivelyperforming steps 4-6Step 5: Build Services and Composite Applicati

4、ons1. TRANSFORM PROCESS BY DELIVERING PROJECTS EACH WITH ITS OWN ROIEstablish development and test environmentsArchitect and design selected servicesImplement, test, and deploy new business services and applicationsUpdate the Projects Services Roadmap2. PERFORM POST-DEPLOYMENT ACTIVITIESDocument fol

5、low-on required actionsPrepare Project Lessons Learned Report input to next iteration of Steps 4 & 5Update Projects Services Roadmap to reflect additional services developed and their utilization by other projectsUpdate Services Portfolio PlanBus ProcessPlanning Organization InfrastructureVisionBus

6、ProcessTransformationStep 5 ProcessFlowKey Tasks performed in Step 5Create architecture and designImplement, Deploy and TestUpdate planning documents and provide feedbackWork stream delineated btw Project and ICE teamIterative and collaborative (e.g., “Architect and Design Services”)Completion of ac

7、tivity (i.e., rounded rectangle) is panied with artifactsSystems Architecture Doc (Solution)Service Design Doc (Service/Integration)Test PlanDeployment and Operations ManualStep 5 Create Architecture and DesignICE ResponsibilityProvide service/integration/ESB standards, templates, and guidance (Step

8、 3, 4 5 artifacts)Review and approve systems architecture and service/integration designProject Team ResponsibilityEstablish project environments (i.e. SCM) Deployed code runs on shared ESB env owned by ICECreate Systems Architecture Contains overall solution architectureCreate service/integration d

9、esign Narrower in scopeCovers specific functionalityCreate Test PlanStep 5 Create Architecture and Design Sequencing of Key Architecture/Design Issues To Be Addressed Top-Level Architecture: major components and services, assign responsibility, where will they reside?Communications: communication tr

10、ansport, adapters?, data representations and content transformationData: determine systems of record, CDM?, identifier mapping, info replication?Coordination: business process breakdown detection, how processes will be monitored and managedHA, FT, and LB: are these needed and what mechanism to use?S

11、ecurity: authentication, authorization, encryption, and audit logs. Who does it?Monitoring: what needs to be monitored and how. For business process and component levelTesting: how business process and system to be tested. Modifying design to facilitate testingStep 5 Implement, Deploy, and TestArtif

12、acts Created in This StepDeployable UnitsBW EAR and initial setup/configuration fileInit scripts for EMSDDL and DML scriptsThird-party/custom libraryChanges for backend system as necessaryDeployment/Operations ManualPrerequisites Deployable Artifact inventoryDeployment InstructionsOperations: lifecy

13、cle management and troubleshootingStep 5 Implement, Deploy, and TestCode Review CriteriaAdherence of ICE best practicesAdoption and usage of appropriate integration approaches and design patternsAdoption and usage of existing services: foundational technical and business serviceAdoption and usage of

14、 common development artifactsBW project templateBW development library/stubs (i.e. CLE client library rather than direct call to CLE)Quality Validation of ESB process and service/integration implementationOverall artifact organization and modularityFlexibility (Support for future changes, global var

15、iables)ScalabilityPerformance and resource utilization (local variable, non-persistent mode for req/rep?)Naming standards and best practicesHandling and support of guaranteed message delivery (acknowledgement/delivery mode used, duplicate message?)Readability (meaningful component name and inline co

16、mment/notes)Step 5 Update Planning Documents and Provide Feedback Artifacts Created/Updated in This StepUpdated Project Services Roadmap Latest additions and status changes (i.e. new business service deployed)Follow-on Actions/Lessons Learned DocManagement and quality processesMethods, tools, standards, best practicesAnalysis of project issues and results mendations for future enhancementMeasurements on e