What is the Architecture Requirements & Strategy deliverable
The applications architecture strategy consists of:the proposed applications architecture,
a comparison of the proposed architecture to the current environment.
The applications architecture partitions the proposed business applications environment into separate applications areas. These applications areas are selected to align to the customer's business processes and to support all customer organizational units.
The main purpose of the Architecture Requirements and Strategy deliverable is to provide a reference at any time for resources working on tasks within the Application and Technical Architecture process in support of the enterprise project.
This document is the source for the application and technical architecture requirements, strategy, approaches, direction, risks, benefits, and assumptions. The document alsocovers the delivery of project and support services to assist the company in the completion of the project. All members of the team should understand and follow the same strategy.
The document describes the key requirements that will underpin the design of information systems architecture. The requirements are a major input into downstream activities within the Applications and Technical Architecture process and will help to identify high-level specifications for the company’s business information systems.
On a practical level, the requirements will have a continuing influence on the scope and content of the architecture design work throughout the project life; therefore, it is important that the list is as complete as possible and agreed on early during the project. The architecture team will need to keep these requirements in mind throughout the project and help create architecture that is compatible with them. Furthermore, if the architecture requirements alter mid-project, the changes should be noted and disseminated in a timely manner.
This document will be distributed to all architecture team members at the process kickoff meeting. Subsequent changes to the architecture scope will be communicated universally before implementation of these changes begins.
The project manager uses this document to understand how the architecture team plans to conduct the architecture work, and how the architecture effort may impact the overall project.