The objectives of this activity are to:

o Identify and document functional requirements related to potential systems,

o Identify and document data requirements related to potential systems,

o Identify and document technical requirements related to potential systems,

o Identify and document integration requirements related to potential systems,

o Identify and document communications requirements related to potential systems,

o Prioritize the new requirements, identifying strategic opportunities.

Tips and Hints

Some requirements will have been identified as part of the current information technology assessment. These requirements must be understood and documented.

o Emphasize what the organization needs, not what currently exists. Keep the analysis at a high level, focusing on the processes that must be supported to meet the business objectives. Do not try to re-engineer the business process itself within the scope of the study. Identify where the processes are more likely to be reshaped and streamlined, and the requirements that could flow from the reshaping.

Activity – Identify Technology Requirements

Identify the requirements that will affect the selection of the technology components for the solution.

Review the corporate technical direction. Assess the current technology in use. Consider the likely future direction (e.g., industry direction, technology trends). Consider specific requirements such as disaster recovery and network and systems management.

Activity – Confirm Coverage of Requirements

To assemble the traceability matrix sections for both the application and the technical architecture and confirm that the stated requirements are met.

Activity – Model Technical Requirements

This activity defines the technical requirements of the data warehousing project. Specific objectives are to:

o Define user access needs,

o Define storage requirements,

o Define system availability and performance requirements,

o Define data management and load strategies,

o Define data and process placement strategies,

o Define new requirements and/or upgrades to the technical platform and SME,

o Define access control and security requirements,

o Present the technical requirements to the Acceptor and obtain approval to continue.

An evaluation of current data infrastructure including the following:

o Data Infrastructure Overview

Prepare a brief description of the key entities (e.g., the current databases) for the organization. Provide the following:

o Name of the data component,

o Type of data (e.g., input, output, file, database),

o Where data is used (e.g., source/destination of data),

o Medium used to store or transmit the data,

o Location of the data,

o A brief description of the data.

o Strengths, Weaknesses, and Opportunities

Present observations addressing problems, strengths, requested improvements, and opportunities to be explored. Indicate the urgency of any changes.

If there are any recommendations that can be made at this point in time on the future of the data, present the recommendation. For example, if the data is of high quality, extremely valuable to the organization and recently implemented at a significant cost to the organization, it may be prudent to document this here and recommend that the data component be included “as-is” in the future data architecture.

Size and Format

Prepare the following:

o A one to two page overview of the current data infrastructure,

o A one page conceptual model, identifying which applications access the data and where the data is located,

o A one to two page summary table, organized around a functional view of the data, detailing strengths, weaknesses, and new requirements,

o A one page list of recommendations.

Tips and Hints

Document only the highlights that are key to understanding the scope of the new system. Data models and process models are typically not necessary to document the observations. A single page conceptual model showing data location is recommended.

https://www.bestitdocuments.com/Samples