Introduction

Technology Component Name:

Initiator:

Problem/Opportunity Definition

This is the problem or opportunity that caused the inception of the project.

Business Drivers

This section contains any business drivers that are associated with this component (if applicable).

High Level Business Requirements

This section provides the “what” of the business need.

Current Situation

Current Architectural Picture

Provide a diagram and associated verbiage that depicts the current architectural picture. The diagram should encompass all impacted systems. Provide text to describe the Architecture.

Proposed Solution

Architectural Design

Provide a diagram that depicts the Architectural Design for the project. The diagram should encompass all impacted systems. Provide text to describe the Architecture and any background information/restrictions/limitations that led to the proposed Architecture.

Business Process to Support Approach

Give a high level description of the Business Processes which will be needed (if necessary) to support the Architectural approach.

Technology

This section should depict any specific technology required (if applicable) in support of the chosen Architectural Approach. In some instances this information will not be known at creation time of the document.

Hardware / Software

This section details any additional hardware or software which must be purchased in support of the chosen solution.

Capacity Needs

This section is optional. It outlines any known capacity needs caused by the Architectural solution, for example, this may be additional disk space, memory or computing power. This information may not be known at creation time of this document.

Issues / Assumptions / Dependencies

Issues

Outline any issues which are known at this time.

Describe the issue.

Owner: Name of Issue Owner

Resolution:

Status:

Open Date:

Target Date:

Assumptions

Outline any assumptions which were made in the process of creating approach.

Dependencies

Outline any dependencies upon other components, items in releases, hardware / technology, or other things.

Business Case

Summary

Summarize the results of the business case.

Cost Savings

This should outline the savings that implementing this project will achieve. It should contain savings from system maintenance, efficiencies in processes, hardware savings, reductions in errors and corrections, reduction in training time, and any other magical things you can think of.

Required Investment

This section should contain the amount of money across the board (including all affected organizations) needed to implement the project. It should essentially be a summarization of the Level of Effort section.

Pay Back Period

This section is an outline or table summary of the time it will take to recoup the investment based on the cost savings

Level of Effort

Include a spreadsheet of the costs by system and / or organization to implement the project.

Implementation Recommendations

This section outlines a recommended approach for phasing of the project, schedule considerations, sequencing of deliveries, and relationships / dependencies to other component areas.

https://www.bestitdocuments.com