Information & Technology Management Standards

---

Analysis, Design & Architecture Document

The Analysis Design and Architecture (ADA) document consolidates the documentation requirements for short-term "low risk" category of applications. Typically these types of applications have easily definable goals that can be described in terms of how the system will be used and do not require more than two iterative design/development cycles.

This document represents a consolidated view of key technical and architectural features associated with an application. An emphasis has been placed on detailing information processing capabilities (functional specifications) and maintenance support requirements.

The ADA document consolidates the core documentation requirements represented by the following standard Application Development Environment (ADE) deliverables:

• Technical Architecture Document;
• Application Architecture Document;
• Implementation Plan; and
• Operations and Support Guide

The purpose of this document is to ensure a minimum level of information is delivered for projects with a scope and duration that do not warrant submitting each of the standard ADE templates listed above.

Two submission/acceptance points are associated with the delivery of this document. The first submission occurs at the end of the design phase and the final "as built" revision occurs towards the end of the project.

Template		Contact
	Analysis, Design & Architecture Document Template		Senior Application Analyst

Deliverable Reviewers

IMG Reviewers		Other Typical Reviewers
	Application Analyst		Business Lead
	Data Architect		Business Sponsor
	Database Administrator		ITMB Application Support
	Technical Architect		ITMB Business Analyst
	Web Tier Lead

Related Deliverables

Prerequisite Deliverables		Successor Deliverables
	Master Project Plan (Lite)		Application Source Code
			Application Run-Time Code

Standards

	The Application Architecture Document should conform to the Ministry template and must include: User interface style, including sample screen mock-ups, Design strategy for functions of the application, Classification of the components by types, A mapping of the components to the technical architecture, Use of patterns and use of meta data, Design deliverables list, Performance issues, Configuration Management for meta data and components or packages.
	Guidelines for the Location of Transient Data. Transient data will be located in its own data area on the middle tier. This data area will not be backed up. For the purpose of this guideline, transient data is defined as follows: Transient data can be reproduced from the source data in a reasonable amount of time. Transient data is not backed up as the data can be reproduced from others sources if needed. Transient data should not have a shelf life greater then one year. Examples of transient data would include: Static reports. A phone list that is generated from another source
	The Implementation Plan should conform to the Ministry template.
	Standards and Guidelines for Development/Delivery of J2EE Applications. (Revised standards are in development).
	User Interface Style Definition Minimum Standards
	User Interface Style Definition Standards
	Web Applications User Interface Guidelines

NOTE: Acrobat Reader needed to view or print PDF versions.