You are on page 1of 4


System Architectural Design

1. Overall System Architecture

The system reallize heavily on client-server archtecture and SOA pattern to deliver services to its users. Data will be transfer through the internet using some common protocols There are 4 entities that is mentioned in the diagram. They are described details as follow
y Database: this is the database storage where all the data for website application is stored. Database server can be distributed another dedicate server for hosting SQL or on the same machine that host the webapplication. viBooks database will use SQL Server 2008 in order to ultilize the features provided by Microsoft.NET framework y Application Server:this is the IIS server that will host the main web system. Web system consists of the 2 components: - Web Application and Web Services. Web Appication is responsible for creating and serving web pages. Which will be developed in ASP.NET Webplatform using ASP.NET MVC 3 framework. - Web Services provides some advanced features, interface and API that supporting the main Web Application system. The services are consumed by mobile application, browser extension and other websites. It shoulb be clearly noted that this Web Services will not be included in the scope of this first realase of the project. However the system architecture must be very flexible and extensible in order to support and implement this feature in the very near future

y Servi e Providers:the e are severeal serv ce prov ers that v Book makes use of in order to provide user with the usability They can be roughfully categorized into 2 sections - Google Translate API: provide translation ability help system s users to translate a piece of te t into chosen language with ease - 3rd login system: provi e additional credential and utilities to viBook login system y Clients:are the devices that connects directly or indirectly to out viBook system. They can be either personal computer with browsers (Opera, IE, Chrome, Firefox,etc.) connect to system usinbg HTTP/ HTTPS protocols or mobile devices that connect using SOA pattern. It s remarkble that viBooks aims to support browser crossing, however, this is not within the project s scope

2. Web Applic io Arc i ec ure

The architecture for the main web application isdepicted as the following diagram:

2.2 ViBook.Resources Co ponent This components contains the static resource for the system that is localized strings, images, style sheet, javascript,ect. 2.3 ViBook.Business Co ponent Thiscomponets contains all the business rules and busisness implementation of t e system (not just h Web application).There are ORM classes, business classes, data access layer, business interface


ViBook.Co o Co po ent As its name, this component provide the very common service that is used by other componets, or throuout the whole system as Caching, Logging, Cryptography and Helpers


The objective that is aimed when design this components is to make it independent and reusable by all other future components All other components that depends exiply or inexitply will access this component via its interface

2.4 ViBook.Web Co ponent This component is reposible for accepting request from users and provices back-end service to users. It is developed in Microsoft.NET MVC3 framework. MVC consists of 3 main elements as describled followed

y y y

Model:Contains the main core object and entity of the application. It also holds and define all the validation rules View:Encapsulate the presentation layer of an application. In ASP.NET, this ismere HTML markup and Javascript logic Controller: control the data-flow of the application. It interacts witth model and view to direct the flow and execution

The overall architecture of the Web component is depicted as the following diagram:


y y y

ActionFilter: provides utilites and cross-cuting experience Helpers: These are utilities classes that encapsulate reusable methods Framework: Contain the core framework to build web application