IBM--TeAM方法（英文版）.pptVIP

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. 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 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 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 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 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 COMPONENT MODEL: Helps document the solution components and their relationships Identifies the components needed on the Operational Model Helps validate a complex solution 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