1. Introduction

This Application Architecture (AA) document provides an overview of how the business needs (functionality and responsibilities) as defined during the business requirements phase are to be implemented.

1.1. Audience

The audience for this document includes anyone seeking an understanding for how the applications works to support the business needs within the context of the technological framework supported by the Ministry.

1.2. Purpose

The AA document is a perspective on how the application will work and helps to validate:

· Design strategies (use of patterns) used in establishing business process/services;

· The mapping of components (business services) to the technical architecture;

· How/if meta-data is being used;

The purpose of this document is to gain an understanding of how and why the system was decomposed, and how the individual parts work together to fulfill the business needs.

1.3. Assumptions

Assumptions supporting the proposed Architecture include references to current standards referenced, tools and expected revision levels of supported API’s.

If the recommended tools or technologies include proprietary metadata, describe how this metadata will be handled and used in the following respects:

1.4. Risks

Any perceived risks associated with the architecture, potential areas of risk may include:

·Suitability of framework to support business requirements; and

·Support for emerging technology.

Insert text here.