《【能力素质】team方法》由会员分享，可在线阅读，更多相关《【能力素质】team方法（29页珍藏版）》请在金锄头文库上搜索。
1、Technical e-business Architecture MethodTEAMPractice Steps天马行空官方博客：http:/ ；QQ:1318241189；QQ群：175569632The IBM Signature Selling Method and TeAMethod are based upon alignment with the customer buying process天马行空官方博客：http:/ ；QQ:1318241189；QQ群：175569632Signature Selling Method:OutcomesSell Cycle Verifi
2、able OutcomesCustomer and IBM agreement to the value of a relationship.Customer-demonstrated 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 solutio
3、n.Customer Power Sponsors conditional approval of proposed solution.Customer and IBM sign a contract.Customer acknowledges the value of the IBM solution.ldentifiedValidatedQualifiedProposed Won CompletedTEAM:Work Product FormatTitlePurposeSIMethod work product enabledDescriptionCreating the work pro
4、ductSample work productTEAM:Work product Dependency DiagramTEAM:Task FormatTitlePurposeSIMethod task enabledDescriptionAssociated work products/technique papersPhase/Activity/Task(GSMethod Task)/Work Products (GSMethod Work Products)PlanEvaluate Customers Business EnvironmentDefine Business Context,
5、 Validate Business Issues and Goals(Define BusinessContext answers the question:“what are we doing on this project and why?”Helps ensure agreement to the project goalsIdentifies issues early on in the projectProvides a basis for development of the architecturabas solutionSYSTEM CONTEXT DIAGRAM:Ident
6、ifies scope boundariesDefines interface requirementsHelps identify potential interface solutionsUSE CASE MODEL:Provides functional requirements for development of your solutionProvides a process for validating a proposed solution Helps in planning a PoCPrioritizes/categorizes system capabilitiesHelp
7、s define release strategyIdentifies user and system interfacesUse Case Description helps describe(in text)the systems responsibilities.NON-FUNCTIONAL REQUIREMENTS:Documents critical requirements like performance, security, and availability that must be met by the proposed solutionHelps validate the
8、proposed solutionProvides a basis for estimating the size and cost of the proposed systemFirst sign of potential software product requirementsVIABILITY ASSESSMENT:Helps you determine the probability of success for a proposed solutionHighlights issues and risks early on, when they are more easily res
9、olvedARCHITECTURAL DECISIONS:Provides your rationale for including IBM content in the solutionLets you position IBM content to customers within an architectural contextCommunicates the foundation for your choices to the implementors such as IGSARCHITECTURE OVERVIEW DIAGRAM:Communicates the architect
10、ure solution“vision”to all partiesIdentifies the IBM and third-party elements of the proposed solutionProvides input to follow-on design and implementation workThis is where themagichappensUse several views depending on the audienceAVAILABLE ASSET LIST:Helps you justify your choices to customers and
11、 other partiesHelps you keep track of your findings and thought process when researching optionsHelps avoid an RFPMay include assets found in other projects within the same customerCOMPONENT MODEL:Helps document the solution components and their relationshipsIdentifies the components needed on the O
12、perational ModelHelps validate a complex solutionOPERATIONAL MODEL:Helps validate a solution by showing how non-functional requirements are satisfiedHelps provide early cost and sizing estimates for the proposed solutionHelps plan for the implementation of the first project or PoCARCHITECTURE BRIEF:Helps you quickly identify products that fit the customers requirementsHelps you identify product issues that may affect the projectHelps you determine skill requirements that affect your recommendations for products or services
