1、Technical e-business Architecture MethodTEAMPractice Steps.The IBM Signature Selling Method and TeAMethod are based upon alignment with the customer buying process.Signature Selling Method:OutcomesSellCycle Verifiable Outcomes Customer and IBM agreement to the value of a relationship. Customer-demon

2、strated 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 and

3、IBM sign a contract. Customer acknowledges the value of the IBM solution. ldentifiedValidatedQualifiedProposedWonCompleted.TEAM:Work Product FormatTitlePurposeSIMethod work product enabledDescriptionCreating the work productSample work product.TEAM:Work product Dependency Diagram.TEAM:Task FormatTit

4、lePurposeSIMethod task enabledDescriptionAssociated work products/technique papers.Phase/Activity/Task(GSMethod Task)/Work Products(GSMethod Work Products)PlanEvaluate Customers Business EnvironmentDefine Business Context, Validate Business Issues and Goals(Define Business Context & Validate Busines

5、s Issues and Goals)Business Context Diagram(Same name)Envisioned Goals and Issues(Envisioned TO-Be Business Goals)Describe Current Organization(Describe Current Organization)Current Organization(none)Develop Plan Linked to Customers Business InitiativesDocument I/T Standards(Document I/T Standards)I

6、nformation Technology Standards(Same name)Analyze Current IT Infrastructure(Analyze Current IT Infrastructure)Current IT Environment(Current IT Infrastructure, more detailed).Execute(part1)Develop Customer Interest,Establish Buying VisionObtain or Develop Business Roadmap(Business Process Model)Busi

7、ness Process Roadmap(Uses different notation)Gain Sponsorship(none)Project Description(Project Goals, Project Estimates and Risk Assessment)Demonstrate Business Benefits,Capabilities,Qualify OpportunityOutline Solution Requirements(Define and categorize requirements,Develop architecture overview,Est

8、ablish system context, Identify Key use cases)Non-Functional Requirement(Same name)System Context Diagram(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 Prod

9、ucts(GSMethod Work Products).Execute(part2)Develop Solution with CustomerDevelop Architecture Overview(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(S

10、ame name)Component Model(Same name)Develop Operational ModelOperational Model(Same name)Refine Viability Assessment(Refine Viability Assessment)Updated Viability Assessment(Same name)Refine Solution, Resolve Concerns, Close SaleAssess Business Impact(Same name)Updated Viability Assessment(Same name)

11、Ensure Client Commitment(Same name)Updated Project Description & Updated Viability Assessment(Project Goals,Project Estimates and Risk Assessment)Evaluate Integrated Solution(Evaluate Integrated Solution,Create Technical Prototype)Updated Project Description & Updated Viability Assessment by the Sol

12、ution Review recommendations, and the results from a prototype, POC, or performance testPhase/Activity/Task(GSMethod Task)/Work Products(GSMethod Work Products).ImplementMonitor Solution Implementation, Ensure Expectations Are MetMonitor Pilot(None)Updated Viability Assessment(Same name)Evaluate suc

13、cess(None)Updated Viability Assessment(Same name)Harvest Assets(None)Phase/Activity/Task(GSMethod Task)/Work Products(GSMethod Work Products).Value of TeAMethodWork Productsfor SWITAs.The Value of TeAMethodHelps you break a large project into manageable chunksGives you time to thinkHelps transition

14、to other SWITAs, IGS,ITS,AIM Services & Solution AssuranceHelps you remember where you left off 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 bet

15、ween the target business entities and processes and other entities/processesIdentifies potential system interfaces .CURRENT ORGANIZATION:Helps qualify the opportunity:are we in at the right level of the organization?Identifies(potential)sponsors,power sponsors,and enemiesIdentifies persons who shoul

16、d be involved in the sales process and what their roles should be Identifies additional opportunitiesHelps identify system interfaces.BUSINESS PROCESS ROADMAP:Helps you understand the customers current and proposed business processes, leading to a better solutionHelps you build credibility with the

17、customer by demonstrating an understanding of their key business processesHelps you more effectively communicate with the customer and the client team regarding the customers business objectives.ENVISIONED GOALS & SSUES:Documents you agreement with the customer on their goals, issues, and CSFsProvid

18、es a basis for assessing 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 unfea

19、sible options up frontIdentifies competitors and opportunities for competitive“replacements(e.g.Oracle-DB2 UDB)Helps ID skills and education requirementsHelps ID current assets.CURRENT IT ENVIRONMENT:Guides you architecture decisionsIdentifies candidates for re-useProvides a starting point for the t

20、o-be architecture pictureIdentifies system integration requirementsHelps define transition/release strategy to minimize riskHelps determine the sophistication of environment.PROJECT DESCRIPTION:Communicates the projects goals to all parties; answers the question:“what are we doing on this project an

21、d why?Helps ensure agreement to the project goalsIdentifies issues early on in the projectProvides a basis for development of the architecturabas solution.SYSTEM CONTEXT DIAGRAM:Identifies scope boundariesDefines interface requirementsHelps identify potential interface solutions.USE CASE MODEL:Provi

22、des functional requirements 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 system

23、s responsibilities.NON-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 sof

24、tware product requirements.VIABILITY ASSESSMENT:Helps you determine the probability of success for a proposed solutionHighlights issues and risks early on, when they are more easily resolved.ARCHITECTURAL DECISIONS:Provides your rationale for including IBM content in the solutionLets you position IB

25、M content to customers within an architectural contextCommunicates the foundation for your choices to the implementors such as IGS.ARCHITECTURE OVERVIEW DIAGRAM:Communicates the architecture solution“visionto 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 audience.AVAILABLE ASSET LIST:Helps you justify your choic