【正文】
on their goals, issues, and CSFs167。 Provides highlevel functional requirements for your use in designing the solution167。 Provides“givens” to be considered in your solution167。 Identifies petitors and opportunities for petitive“replacements”(DB2 UDB)167。 Helps ID current assetsCURRENT IT ENVIRONMENT:167。 Identifies candidates for reuse167。 Identifies system integration requirements167。 Helps determine the sophistication of environmentPROJECT DESCRIPTION:167。 answers the question:“what are we doing on this project and why?”167。 Identifies issues early on in the project167。 Identifies scope boundaries167。 Helps identify potential interface solutionsUSE CASE MODEL:167。 Provides a process for validating a proposed solution 167。 Prioritizes/categorizes system capabilities167。 Identifies user and system interfaces167。 Documents critical requirements like performance, security, and availability that must be met by the proposed solution167。 Provides a basis for estimating the size and cost of the proposed system167。 Helps you determine the probability of success for a proposed solution167。 Provides your rationale for including IBM content in the solution167。 Communicates the foundation for your choices to the implementors such as IGSARCHITECTURE OVERVIEW DIAGRAM:167。 Identifies the IBM and thirdparty elements of the proposed solution167。 This is where the‘magic’happens167。 Helps you justify your choices to customers and other parties167。 Helps avoid an RFP167。 Helps document the solution ponents and their relationships167。 Helps validate a plex solutionOPERATIONAL MODEL:167。 Helps provide early cost and sizing estimates for the proposed solution167。 Helps you quickly identify products that fit the customer’s requirements167。 Helps you determine skill requirements that affect your remendations for products or services