Application Architecture Document template

Ministry/Agency Name Complete file/properties to populate fields on this page and in the document headers. To see instructions select Tools/Options Print tab, and make sure that “Hidden Text” is checked. Delete red instructions when filling in the template or select Tools/Options Print tab, and make sure that “Hidden Text” is not checked. Project Name Project #: [###] Application Architecture Document Prepared by: Author's Name Prepared for: [Company Name] Date Submitted: [Date] Project Sponsor: Project Sponsor's Name Client Acceptor: [if different than Sponsor] Project Manager: [Project Manager’s Name] Document Number: 6450-20/[Project Number]/App. Arch. Version: 1.1 Last Updated: November 2, 2004 Creation Date: [Date] Application Architecture Document Project Name Last revised: 2004-11-02 Page 2 of 12 d:\docstoc\working\activepdf\input\$asqapplication architecture document template.doc.doc Table of Contents Table of Contents ................................................................................................................ 2 1. Introduction.................................................................................................................. 3 1.1. Audience .......................................................................................................................3 1.2. Purpose........................................................................................................................3 1.3. Assumptions..................................................................................................................3 1.4. Risks.............................................................................................................................3 2. Technology Framework .............................................................................................. 4 2.1. Structural – Logical Layer and Physical Tier View.........................................................4 2.2. Functional – Component View.......................................................................................4 3. Application Module Design Specification (Design Deliverable List) ..................... 5 4. User Interface (UI) Guidelines .................................................................................... 6 5. Configuration Management Approach ...................................................................... 7 6. Special Considerations............................................................................................... 8 7. APMS Update ............................................................................................................... 9 Revision Log...................................................................................................................... 10 Appendices ........................................................................................................................ 11 Approval ............................................................................................................................. 12 Application Architecture Document Project Name Last revised: 2004-11-02 Page 3 of 12 d:\docstoc\working\activepdf\input\$asqapplication architecture document template.doc.doc 1. Introduction This Application Architecture (AA) document provides an overview of how the required functionality and responsibilities of the system were partitioned and then assigned to subsystems or components. Include a brief description of the underlying framework1 assumed tools, highleeve component interfaces and their respective interaction to satisfy the business requirements. 1.1. Audience The audience for this document includes anyone seeking an understanding for how the applications works within the context of the technological framework adopted. 1.2. Purpose The AA document helps to place into perspective how the application will work and helps to validate: • Design strategies (use of patterns) for functions of the application; • Component classifications (by types); • The mapping of components to the technical architecture; • How/if meta-data is being used; • How the proposed solution satisfies high-level business requirements; and • The application is compatible with the supported operational infrastructure. 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 provide the desired functionality. 1.3. Assumptions Insert text here. 1.4. Risks Insert text here. 1 A framework centralizes different common design-time and runtime resources, allowing developers to concentrate on the unique business logic of the application. (Reference: http://www.ccaforrumorg/overview/framework.html). Application Architecture Document Project Name Last revised: 2004-11-02 Page 4 of 12 d:\docstoc\working\activepdf\input\$asqapplication architecture document template.doc.doc 2. Technology Framework Insert text here. 2.1. Structural – Logical Layer and Physical Tier View Insert text here. 2.2. Functional – Component View Insert text here. Application Architecture Document Project Name Last revised: 2004-11-02 Page 5 of 12 d:\docstoc\working\activepdf\input\$asqapplication architecture document template.doc.doc 3. Application Module Design Specification (Design Deliverable List) Insert text here. Application Architecture Document Project Name Last revised: 2004-11-02 Page 6 of 12 d:\docstoc\working\activepdf\input\$asqapplication architecture document template.doc.doc 4. User Interface (UI) Guidelines Insert text here. Application Architecture Document Project Name Last revised: 2004-11-02 Page 7 of 12 d:\docstoc\working\activepdf\input\$asqapplication architecture document template.doc.doc 5. Configuration Management Approach Insert text here. Application Architecture Document Project Name Last revised: 2004-11-02 Page 8 of 12 d:\docstoc\working\activepdf\input\$asqapplication architecture document template.doc.doc 6. Special Considerations Insert text here. Application Architecture Document Project Name Last revised: 2004-11-02 Page 9 of 12 d:\docstoc\working\activepdf\input\$asqapplication architecture document template.doc.doc 7. APMS Update APMS update required? Yes No APMS updated/to be updated on (date): Comments: Application Architecture Document Project Name Last revised: 2004-11-02 Page 10 of 12 d:\docstoc\working\activepdf\input\$asqapplication architecture document template.doc.doc Revision Log Date Version Change Reference Author Reviewed by [yyyy-mm-dd] 0.1 Application Architecture Document Project Name Last revised: 2004-11-02 Page 11 of 12 d:\docstoc\working\activepdf\input\$asqapplication architecture document template.doc.doc Appendices Enter content here. Application Architecture Document Project Name Last revised: 2004-11-02 Page 12 of 12 d:\docstoc\working\activepdf\input\$asqapplication architecture document template.doc.doc Approval This document has been approved as the official Application Architecture Document for the Project Name project. Following approval of this document, changes will be governed by the project’s change management process, including impact analysis, appropriate reviews and approvals, under the general control of the Master Project Plan and according to Project Support Office policy. Prepared by Signature Date Author's Name [Title] [Organization] Accepted by Signature Date [Client Acceptor’s Name] [Title] [Organization] Approved by Signature Date [Client Approver’s Name] [Title] [Organization] [Client Approver’s Name] [Title] [Organization] [Project Manager’s Name] [Title] [Organization] [IMG Approver’s Name] [Title] [Organization]