We considered mainly five significant features of our world village project to design and implement, these are as follows:
User Management
Announcement Management
Upload Management
Ecopark and
Entertainment
User Management
Figure 1: User management
Announcement management
Figure 2: Announcement management
Ecopark
Figure 3: Ecopark
Entertainment (music, video, movie and picture)
Figure 4: Entertainment
For more details of each use case scenarios: Use the “Use Case Document” of World Village Project.
Logical View
Overview
The World Village web application is divided into layers based on N-tier architecture:
The dependencies of architectural layers will be explained and shown in Deployment View section. Now we will describe responsibility of each layer and its significant packages:
Presentation Layer: This is a front-end component, which is responsible for providing portable presentation logic. This layer works with the results/output of the business logic layer and transforms the results into something usable and readable by the end user. [3]
Model: This component holds the data, which should be displayed to the user or which the user enters. It also interacts with business logic layer.
View: Displays the model on the screen.
Controller: Responds to user input by modifying the model. It sends requests to model when user performs some activities on the page.
Business Logic Layer:Allows users to share and control business logic by isolating it from the other layers of the application. The business layer functions between the presentation layer and data access layer, sending the client's data requests to the database layer through the data access layer. [3]
Data Manager: This component encapsulates the business logic of the application. It works with entities or objects containing information of what is needed from database. It is responsible for forming these objects and sending them to data access layer.
Data Access Layer:Provides access to the database by executing a set of SQL statements or stored procedures. As the name suggests, the data access layer contains no business rules or data manipulation/transformation logic. It is merely a reusable interface to the database. [3]
ORM: This component is responsible for generating SQL requests from objects it gets from business logic layer. SQL requests are sent to database and then the response is converted to entities.
Database Layer:Provides the mechanism to store and retrieve data. [3]
Common Layer:
Entities: These are domain objects that contain their properties and relationships between each other. These objects are used by all layers. Presentation layer may use them as model representation. Business logic layer will work with them to perform business logic operations. And finally, data access layer (ORM) maps entities to the database.
Figure below shows Architecture Analysis Model Overview of the system. User Interface Package corresponds to Presentation Layer, Controller relates to Business Logic Layer, Data Access Package corresponds to Data Access Layer and Database relates to Database Layer. Entity package is in common section of architecture.
