1. Technical e-business Architecture Method TEAM Practice Steps

2. The IBM Signature Selling Method and TeAMethod are based upon alignment with the customer buying process

3. Signature Selling Method:Outcomes Sell Cycle Verifiable Outcomes Customer 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 solution. Customer Power Sponsor ’ s conditional approval of proposed solution. Customer and IBM sign a contract. Customer acknowledges the value of the IBM solution. ldentified Validated Qualified Proposed Won Completed

4. TEAM:Work Product Format  Title  Purpose  SIMethod work product enabled  Description  Creating the work product  Sample work product

5. TEAM:Work product Dependency Diagram

6. TEAM:Task Format  Title  Purpose  SIMethod task enabled  Description  Associated work products/technique papers

7. Phase/Activity/Task(GSMethod Task)/Work Products (GSMethod Work Products)  Plan  Evaluate Customer ’ s Business Environment Define 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 Business Goals) Describe Current Organization(Describe Current Organization) Current Organization(none)  Develop Plan Linked to Customer ’ s Business Initiatives Document I/T Standards(Document I/T Standards) Information Technology Standards(Same name) Analyze Current IT Infrastructure(Analyze Current IT Infrastructure) Current IT Environment(Current IT Infrastructure, more detailed)

8.  Execute(part1)  Develop Customer Interest,Establish Buying Vision Obtain or Develop Business Roadmap(Business Process Model) Business Process Roadmap(Uses different notation) Gain Sponsorship(none) Project Description(Project Goals, Project Estimates and Risk Assessment)  Demonstrate Business Benefits,Capabilities,Qualify Opportunity Outline Solution Requirements(Define and categorize requirements,Develop architecture overview,Establish 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 Products (GSMethod Work Products)

9.  Execute(part2)  Develop Solution with Customer Develop 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(Same name) Component Model(Same name) Develop Operational Model Operational Model(Same name) Refine Viability Assessment(Refine Viability Assessment) Updated Viability Assessment(Same name)  Refine Solution, Resolve Concerns, Close Sale Assess Business Impact(Same name) Updated Viability Assessment(Same name) 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 Solution Review recommendations, and the results from a prototype, POC, or performance test Phase/Activity/Task(GSMethod Task)/Work Products (GSMethod Work Products)

10.  Implement  Monitor Solution Implementation, Ensure Expectations Are Met Monitor Pilot(None) Updated Viability Assessment(Same name) Evaluate success(None) Updated Viability Assessment(Same name) Harvest Assets(None) Phase/Activity/Task(GSMethod Task)/Work Products (GSMethod Work Products)

11. Value of TeAMethod Work Products for SWITAs

12. The Value of TeAMethod  Helps you break a large project into manageable ‘ chunks ’  Gives you time to think  Helps transition to other SWITAs, IGS,ITS ’,AIM Services & Solution Assurance  Helps you remember where you left off with a customer!

13. BUSINESS CONTEXT DIAGRAM:  Helps define the scope of the project  Helps you understand the customer ’ s business processes, leading to a better solution  Helps you understand the relationships between the target business entities and processes and other entities/processes  Identifies potential system interfaces

14. CURRENT ORGANIZATION:  Helps qualify the opportunity:are we in at the right level of the organization?  Identifies(potential)sponsors,power sponsors,and enemies  Identifies persons who should be involved in the sales process and what their roles should be  Identifies additional opportunities  Helps identify system interfaces

15. BUSINESS PROCESS ROADMAP:  Helps you understand the customer ’ s current and proposed business processes, leading to a better solution  Helps you build credibility with the customer by demonstrating an understanding of their key business processes  Helps you more effectively communicate with the customer and the client team regarding the customer ’ s business objectives

16. ENVISIONED GOALS & SSUES:  Documents you agreement with the customer on their goals, issues, and CSFs  Provides a basis for assessing the success of the project  Provides high-level functional requirements for your use in designing the solution  Helps It see the big picture (they ’ re usually focused on immediate deliverables)

17. IT STANDARDS:  Provides “ givens ” to be considered in your solution  Helps you eliminate unfeasible options up front  Identifies competitors and opportunities for competitive “ replacements ” (e.g.Oracle->DB2 UDB)  Helps ID skills and education requirements  Helps ID current assets

18. CURRENT IT ENVIRONMENT:  Guides you architecture decisions  Identifies candidates for re-use  Provides a starting point for the to-be architecture picture  Identifies system integration requirements  Helps define transition/release strategy to minimize risk  Helps determine the sophistication of environment

19. PROJECT DESCRIPTION:  Communicates the project ’ s goals to all parties; answers the question: “ what are we doing on this project and why? ”  Helps ensure agreement to the project goals  Identifies issues early on in the project  Provides a basis for development of the architecturabas solution

20. SYSTEM CONTEXT DIAGRAM:  Identifies scope boundaries  Defines interface requirements  Helps identify potential interface solutions

21. USE CASE MODEL:  Provides functional requirements for development of your solution  Provides a process for validating a proposed solution  Helps in planning a PoC  Prioritizes/categorizes system capabilities  Helps define release strategy  Identifies user and system interfaces  Use Case Description helps describe(in text)the system ’ s responsibilities.

22. NON-FUNCTIONAL REQUIREMENTS:  Documents critical requirements like performance, security, and availability that must be met by the proposed solution  Helps validate the proposed solution  Provides a basis for estimating the size and cost of the proposed system  First sign of potential software product requirements

23. VIABILITY ASSESSMENT:  Helps you determine the probability of success for a proposed solution  Highlights issues and risks early on, when they are more easily resolved

24. ARCHITECTURAL DECISIONS:  Provides your rationale for including IBM content in the solution  Lets you position IBM content to customers within an architectural context  Communicates the foundation for your choices to the implementors such as IGS

25. ARCHITECTURE OVERVIEW DIAGRAM:  Communicates the architecture solution “ vision ” to all parties  Identifies the IBM and third-party elements of the proposed solution  Provides input to follow-on design and implementation work  This is where the ‘ magic ’ happens  Use several views depending on the audience

26. AVAILABLE ASSET LIST:  Helps you justify your choices to customers and other parties  Helps you keep track of your findings and thought process when researching options  Helps avoid an RFP  May include assets found in other projects within the same customer

27. COMPONENT MODEL:  Helps document the solution components and their relationships  Identifies the components needed on the Operational Model  Helps validate a complex solution

28. OPERATIONAL MODEL:  Helps validate a solution by showing how non-functional requirements are satisfied  Helps provide early cost and sizing estimates for the proposed solution  Helps plan for the implementation of the first project or PoC

29. ARCHITECTURE BRIEF:  Helps you quickly identify products that fit the customer ’ s requirements  Helps you identify product issues that may affect the project  Helps you determine skill requirements that affect your recommendations for products or services