Happy Tree Friends

World Village

Software Architecture Document

Version 1.1 Revision History

Date	Version	Description	Author
10/03/2009	1.0	Architectural Representation, Implementation View	Zhenya Renhart
10/03/2009	1.0	Architectural Goals and Constraints, Use Case View	Vikash Raunyiar
14/03/2009	1.0	Quality, Size, Deployment View	Najam Nazar
15/03/2009	1.0	Introduction, Logical View	Mohsen Anvaari
30/03/2009	1.0	Editing quality and size parts	Najam Nazar
31/03/2009	1.0	Editing Architectural Representation, Implementation View	Zhenya Renhart
3/04/2009	1.0	Editing Architectural Goals and Constraints, Use Case View	Vikash Raunyiar
4/04/2009	1.0	Editing Indroduction, Logical View	Mohsen Anvaari
17/04/2009	1.1	Editing Logical View	Mohsen Anvaari
24/04/2009	1.1	Add package role’s descriptions	Zhenya Renhart
27/04/2009	1.1	Editing Logical View	Mohsen Anvaari

Table of Contents

1. Introduction 5

1.1 Purpose 5

1.2 Scope 5

1.3 Definitions, Acronyms, and Abbreviations 5

1.4 References 5

1.5 Overview 5

2. Architectural Representation 6

3. Architectural Goals and Constraints 6

3.1 Technical Platform 6

3.2 Security 6

3.3 Usability 7

3.4 Availability 7

3.5 Accessibility 7

3.6 Capacity 7

3.7 Suitability 7

3.8 Scalability 7

3.9 Operability 7

3.10 Fault tolerance 7

3.11 Recoverability 7

3.12 Changeability 7

3.13 Stability 8

4. Use-Case View 9

We considered mainly five significant features of our world village project to design and implement, these are as follows: 10

User Management 10

Announcement management 11

Ecopark 12

Entertainment (music, video, movie and picture) 13

5. Logical View 14

5.1 Overview 14

6. Deployment View 16

7. Implementation View 16

7.1 Overview 16

7.2 Layers 18

7.2.1 Presentation Layer 18

7.2.2 HTML Prototypes Layer 18

7.2.3 Control Layer 18

7.2.4 Web Configuration Layer 19

7.2.5 Business Logic Layer 19

7.2.6 Entities layer 19

7.2.7 Hibernate Configuration Layer 19

7.2.8 Database Access Layer 19

7.2.9 Common Elements Layer 20

7.2.10 Database Layer 20

8. Size and Performance 20

9. Quality 20

Software Architecture Document

1. Introduction

   1. Purpose

This document provides a comprehensive architectural overview of the World Village Web Application, using a number of different architectural views to depict different aspects of the system. It is intended to capture and convey the significant architectural decisions which have been made on the system.

In order to depict the software as accurately as possible, the structure of this document is based on the “4+1” model view of architecture [1].

2. Scope

The scope of this document is to describe the architecture of the World Village application and some examples to show how this architecture should be applied in design phase.

3. Definitions, Acronyms, and Abbreviations

RUP: Rational Unified Process

UML:Unified Modeling Language

SAD:Software Architecture Document

4. References

[1] Philippe Kruchten, The “4+1” view model of software architecture, November 1995, http://www3.software.ibm.com/ibmdl/pub/software/rational/web/whitepapers/2003/Pbk4p1.pdf

[2] Use Cases Document of World Village Project

[3] Yoshi Lounge, N-tier Web Applications Using ASP.Net, 11 June 2008

[4] YummiSAD: Software Architecture Document of Yummy Inc : Online Catering Service 1.0

5. Overview

This document contains following sections to document all aspects of the system architecture:

Section “Architectural Representation” describes the use of each view.

Section “Architectural Goals and Constraints” describes the architectural constraints of the system.

Section “Use Case View” describes the most important use cases of the system.

Section “Logical View” describes the layers and subsystems of the application and how design elements should be set on those layers.

Section “Implementation View” describes the decomposition of the software into layers and implementation subsystems in the implementation model.

Section “Deployment View” describes how the system will be deployed.

Section “Size and Performance” describes any performance issues and constraints.

Section “Quality” describes any aspects related to the quality of service (QoS) attributes.