TEAM方法（英文PPT29頁

1、Technical e-business Architecture MethodTEAMPractice StepsThe IBM Signature Selling Method and TeAMethod are based upon alignment with the customer buying processEvaluateBusinessEnvironmentDevelopBusinessStrategy&InitiativesRecognizeNeedEvaluateOptionsSelectSolutionOptionResolveConcernsand Decid

2、eImplementSolutionand EvaluateSuccessBuying ProcessSignature Selling Method and TeAMethodEvaluateCustomersBusinessEnvironmentDevelop PlansLinked toCustomer sBusinessInitiativesDevelopCustomerInterest.EstablishBuying VisionDemonstrateBusinessBenefits.Capabilitiesand QualifyDevelopSolutionwithCustomer

3、RefineSolution,ResolveConcerns.Close SaleMonitor solutionImplementationand EnsureExpectationsare MetIdentifiedValidatedQualifiedProposedWonCompletedPlanExecuteImplementSignature Selling Method:OutcomesSellCycle Verifiable Outcomes Customer and IBM agreement to the value of a relationship. Customer-d

4、emonstrated interest in working with IBM. Customer-stated business need,buying vision and agreement to support IBM access to Power Sponsor. Customer Power Sponsor and IBM agreement to go forward with a preliminary solution. Customer Power Sponsors conditional approval of proposed solution. Customer

5、and IBM sign a contract. Customer acknowledges the value of the IBM solution. ldentifiedValidatedQualifiedProposedWonCompletedTEAM:Work Product FormatTitlePurposeSIMethod work product enabledDescriptionCreating the work productSample work productTEAM:Work product Dependency DiagramExecute phase work

6、 productsProjectDescriptionSystemContextDiagramNon-FunctionalRequirementsUse CaseModelArchitecture DecisionsArchitecturalOverviewDiagramComponentModelAvailable AssetsOperationalModelViabilityAssessmentP Pl la an n P Ph ha as se e W Wo or rk k P Pr ro od du uc ct ts s: :-Business Context Diagram-Curr

7、ent Organization Descr.-Business Process Roadmap-Envisioned Goals and Issues-IT Standards-Current IT EnvironmentA As ss se et ts s: :-Reference Architecture-Architectural BriefsTEAM:Task FormatTitlePurposeSIMethod task enabledDescriptionAssociated work products/technique papersPhase/Activity/Task(GS

8、Method Task)/Work Products(GSMethod Work Products)PlanEvaluate Customers Business EnvironmentDefine Business Context, Validate Business Issues and Goals(Define Business Context & Validate Business Issues and Goals)Business Context Diagram(Same name)Envisioned Goals and Issues(Envisioned TO-Be Bu

9、siness Goals)Describe Current Organization(Describe Current Organization)Current Organization(none)Develop Plan Linked to Customers Business InitiativesDocument I/T Standards(Document I/T Standards)Information Technology Standards(Same name)Analyze Current IT Infrastructure(Analyze Current IT Infras

10、tructure)Current IT Environment(Current IT Infrastructure, more detailed)Execute(part1)Develop Customer Interest,Establish Buying VisionObtain or Develop Business Roadmap(Business Process Model)Business Process Roadmap(Uses different notation)Gain Sponsorship(none)Project Description(Project Goals,

11、Project Estimates and Risk Assessment)Demonstrate Business Benefits,Capabilities,Qualify OpportunityOutline Solution Requirements(Define and categorize requirements,Develop architecture overview,Establish system context, Identify Key use cases)Non-Functional Requirement(Same name)System Context Diag

12、ram(Same name)Architectural Decisions(Same name)Use Case Model(Same name)Assess Initial Viability(Assess Initial Viability)Viability Assessment(Same name)Phase/Activity/Task(GSMethod Task)/Work Products(GSMethod Work Products)Execute(part2)Develop Solution with CustomerDevelop Architecture Overview(

13、Same name)ArchitectureaL Decisions(Same name)Architecture Overview Diagram(Same name)Survey Available Assets(Same name)Available Asset List(Candidate Asset List)Develop High Level Component Model(Same name)Component Model(Same name)Develop Operational ModelOperational Model(Same name)Refine Viabilit

14、y Assessment(Refine Viability Assessment)Updated Viability Assessment(Same name)Refine Solution, Resolve Concerns, Close SaleAssess Business Impact(Same name)Updated Viability Assessment(Same name)Ensure Client Commitment(Same name)Updated Project Description & Updated Viability Assessment(Proje

15、ct Goals,Project Estimates and Risk Assessment)Evaluate Integrated Solution(Evaluate Integrated Solution,Create Technical Prototype)Updated Project Description & Updated Viability Assessment by the Solution Review recommendations, and the results from a prototype, POC, or performance testPhase/A

16、ctivity/Task(GSMethod Task)/Work Products(GSMethod Work Products)ImplementMonitor Solution Implementation, Ensure Expectations Are MetMonitor Pilot(None)Updated Viability Assessment(Same name)Evaluate success(None)Updated Viability Assessment(Same name)Harvest Assets(None)Phase/Activity/Task(GSMetho

17、d Task)/Work Products(GSMethod Work Products)Value of TeAMethodWork Productsfor SWITAsThe Value of TeAMethodHelps you break a large project into manageable chunksGives you time to thinkHelps transition to other SWITAs, IGS,ITS,AIM Services & Solution AssuranceHelps you remember where you left of

18、f with a customer!BUSINESS CONTEXT DIAGRAM:Helps define the scope of the projectHelps you understand the customers business processes, leading to a better solutionHelps you understand the relationships between the target business entities and processes and other entities/processesIdentifies potentia

19、l system interfaces 111111ProductionschedulingdistributionbillingCustomercurrent statushistoryCURRENT ORGANIZATION:Helps qualify the opportunity:are we in at the right level of the organization?Identifies(potential)sponsors,power sponsors,and enemiesIdentifies persons who should be involved in the s

20、ales process and what their roles should be Identifies additional opportunitiesHelps identify system interfacesBUSINESS PROCESS ROADMAP:Helps you understand the customers current and proposed business processes, leading to a better solutionHelps you build credibility with the customer by demonstrati

21、ng an understanding of their key business processesHelps you more effectively communicate with the customer and the client team regarding the customers business objectivesENVISIONED GOALS & SSUES:Documents you agreement with the customer on their goals, issues, and CSFsProvides a basis for asses

22、sing the success of the projectProvides high-level functional requirements for your use in designing the solutionHelps It see the big picture (theyre usually focused on immediate deliverables)IT STANDARDS:Provides“givens” to be considered in your solutionHelps you eliminate unfeasible options up fro

23、ntIdentifies competitors and opportunities for competitive“replacements”(e.g.Oracle-DB2 UDB)Helps ID skills and education requirementsHelps ID current assetsCURRENT IT ENVIRONMENT:Guides you architecture decisionsIdentifies candidates for re-useProvides a starting point for the to-be architecture pi

24、ctureIdentifies system integration requirementsHelps define transition/release strategy to minimize riskHelps determine the sophistication of environmentPROJECT DESCRIPTION:Communicates the projects goals to all parties; answers the question:“what are we doing on this project and why?”Helps ensure a

25、greement to the project goalsIdentifies issues early on in the projectProvides a basis for development of the architecturabas solutionSYSTEM CONTEXT DIAGRAM:Identifies scope boundariesDefines interface requirementsHelps identify potential interface solutionsUSE CASE MODEL:Provides functional require

26、ments for development of your solutionProvides a process for validating a proposed solution Helps in planning a PoCPrioritizes/categorizes system capabilitiesHelps define release strategyIdentifies user and system interfacesUse Case Description helps describe(in text)the systems responsibilities.NON

27、-FUNCTIONAL REQUIREMENTS:Documents critical requirements like performance, security, and availability that must be met by the proposed solutionHelps validate the proposed solutionProvides a basis for estimating the size and cost of the proposed systemFirst sign of potential software product requirem

28、entsVIABILITY ASSESSMENT:Helps you determine the probability of success for a proposed solutionHighlights issues and risks early on, when they are more easily resolvedARCHITECTURAL DECISIONS:Provides your rationale for including IBM content in the solutionLets you position IBM content to customers w

29、ithin an architectural contextCommunicates the foundation for your choices to the implementors such as IGSARCHITECTURE OVERVIEW DIAGRAM:Communicates the architecture solution“vision”to all partiesIdentifies the IBM and third-party elements of the proposed solutionProvides input to follow-on design and implementation wor