Layered Architecture for Mobile Web Based Application: A Case Study of FNU Student Registration System

Layered Architecture for Mobile Web Based Application: A Case Study of FNU Student Registration System

Bimal Aklesh Kumar (Fiji National University, Lautoka, Fiji)
Copyright: © 2016 |Pages: 14
DOI: 10.4018/IJSI.2016070104
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

Mobile and other PDA devices allow us to access the World Wide Web anytime and anywhere using fully functional mobile web browsers. This study utilizes the mobile web to deliver services to register students for courses at Fiji National University (FNU). Developing dynamic web based applications for mobile devices is a challenging task, because these devices have limited processing power and physical memory. In order to overcome these limitations, the author proposed layered architecture for the development of this system. This paper describes the architecture, design and implementation of the new system. Experimental results demonstrate that proposed architecture can effectively reduce the client side resource utilization (processing power and physical memory) of dynamic mobile web based systems. Furthermore the author conclude this paper by outlining future work for research in this area.
Article Preview

Research Background

Software architecture of a computing system is the structure or structures of the system, which comprises software elements, the externally visible properties of those elements and the relationships among them (Bass et al., 2003). Like any other complex structure, software must be built on solid foundation. Failing to consider key scenarios, failing to design for common problems, or failing to appreciate the long-term consequences of key decisions can put your application at risk. Modern tools and platform helps you to simplify the task of building applications but they do not replace the need to design your application carefully, based on your specific scenario and requirements. The risks exposed by poor architecture include software that is unstable, is unable to support existing and future business requirements or is difficult to deploy and manage in the production environment (Chaudhary, 2009).

Layer can be defined as one of the two or more rows, levels or ranks arranged one above another, hence the definition for Multi-Layer being any number of levels arranged above another, each serving distinct and separate tasks (Ruzinoor, 2011). From the beginning of computer science, the industry has been practicing a simple form of client/server computing, since the inception of the mainframe with a configuration that had directly connected to the host an unintelligent terminal constituting the one-layer or monolithic system (Christian, 2010). The simplest client/server model involves only two layers interacting with each other called the 2-Layer architecture, varying from low scalability architectures with fat clients, handling transformations on data retrieved from a simple file or database server, to solutions with fat servers offering lightweight client modules in exchange for increased complexity on server-side. The successors of 2-Layer architectures, the 3-Layer architectures imply the insertion of an additional layer called the middle layer, morphing the other two entities from the 2-Layer architecture into the front end and backend. Front end mostly contains logic responsible for presentation, delivered as client side code, whereas the backend deals with access to dedicated services such as a database server to the middle layer. The philosophy is that direct access for the front end to the back-end without the middle layer acting as an intermediate is not permitted. Following the pattern, 3-Layer architectures can be extended with additional layers ending up obtaining the generalized structure of the multi-layer architecture.

Complete Article List

Search this Journal:
Reset
Open Access Articles: Forthcoming
Volume 6: 4 Issues (2018): 1 Released, 3 Forthcoming
Volume 5: 4 Issues (2017)
Volume 4: 4 Issues (2016)
Volume 3: 4 Issues (2015)
Volume 2: 4 Issues (2014)
Volume 1: 4 Issues (2013)
View Complete Journal Contents Listing