Docstoc

Application Architecture Document template

Document Sample
Application Architecture Document template Powered By Docstoc
					                       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



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




Last revised: 2011-10-18                                                                                                                    Page 2 of 12
d:\docstoc\working\pdf\0885e795-1670-4b58-9682-5d4d939f9c7e.doc
Application Architecture Document                                                           Project Name



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
                                                                          1
or components. Include a brief description of the underlying framework assumed tools, high-
level 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.cca-
forum.org/overview/framework.html).

Last revised: 2011-10-18                                                                     Page 3 of 12
d:\docstoc\working\pdf\0885e795-1670-4b58-9682-5d4d939f9c7e.doc
Application Architecture Document                                 Project Name



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.




Last revised: 2011-10-18                                          Page 4 of 12
d:\docstoc\working\pdf\0885e795-1670-4b58-9682-5d4d939f9c7e.doc
Application Architecture Document                                 Project Name



3.      Application Module Design Specification
        (Design Deliverable List)

Insert text here.




Last revised: 2011-10-18                                          Page 5 of 12
d:\docstoc\working\pdf\0885e795-1670-4b58-9682-5d4d939f9c7e.doc
Application Architecture Document                                 Project Name



4.      User Interface (UI) Guidelines

Insert text here.




Last revised: 2011-10-18                                          Page 6 of 12
d:\docstoc\working\pdf\0885e795-1670-4b58-9682-5d4d939f9c7e.doc
Application Architecture Document                                 Project Name



5.      Configuration Management Approach

Insert text here.




Last revised: 2011-10-18                                          Page 7 of 12
d:\docstoc\working\pdf\0885e795-1670-4b58-9682-5d4d939f9c7e.doc
Application Architecture Document                                 Project Name



6.      Special Considerations

Insert text here.




Last revised: 2011-10-18                                          Page 8 of 12
d:\docstoc\working\pdf\0885e795-1670-4b58-9682-5d4d939f9c7e.doc
Application Architecture Document                                 Project Name



7.      APMS Update

        APMS update required?               Yes             No

        APMS updated/to be updated on (date):

        Comments:




Last revised: 2011-10-18                                          Page 9 of 12
d:\docstoc\working\pdf\0885e795-1670-4b58-9682-5d4d939f9c7e.doc
Application Architecture Document                                         Project Name



Revision Log

Date            Version     Change Reference                 Author   Reviewed by
[yyyy-mm-dd]    0.1




Last revised: 2011-10-18                                                 Page 10 of 12
d:\docstoc\working\pdf\0885e795-1670-4b58-9682-5d4d939f9c7e.doc
Application Architecture Document                                 Project Name



Appendices

Enter content here.




Last revised: 2011-10-18                                          Page 11 of 12
d:\docstoc\working\pdf\0885e795-1670-4b58-9682-5d4d939f9c7e.doc
Application Architecture Document                                                  Project Name



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]




Last revised: 2011-10-18                                                           Page 12 of 12
d:\docstoc\working\pdf\0885e795-1670-4b58-9682-5d4d939f9c7e.doc

				
DOCUMENT INFO
Shared By:
Tags:
Stats:
views:4227
posted:1/6/2008
language:English
pages:12
ocak ocak
About