Topic: Itinerary Website (Web Development Document) Module: Web Application Design and Modeling Mark: 78% Date: Jan 2012 Sheffield Hallam University

1. DEVELOPMENT CONCEPT
AND DESIGN PATTERN
FOR
TRAVEL ITINERARY PROJECT
Created by Team Members
Reviewed by Team Members
Module: Web Application Design and Modeling (WDAM)
Created Date 10 Jan 2012
Assignment: Final Assignment (Itinerary 2012 project) Revised Date 12 Jan 2012
Revision No. 1.0
Team Name: As a Whole
Document Name D01-002
1

2. 2 OBJECTIVE OF THIS DOCUMENT
1. To propose our design pattern
based on well-known framework
and architecture.
2. To prevent if our application
cannot run in different
environment properly.
3. To explain how we used object-
oriented and development
concept applied for this project.

3. We separated code into three tiers OUR DEVELOPMENT CONCEPT
FOLLOWING OO & DESIGN PATTERN
Presentation Layer
Web Browser
Web Application (JSP)
JSP JSP JSP JSP JSP JSP JSP
page#1 page#2 page#3 page#4 page#4 page#6 page#n
Business Logic Layer Services
Itineary.Model, utils, mail
Itinerary Itin_Item Privacy Note FriendGroup
Services User
Itinerary. Itineary.U Transport Activity
Trip
mail til Manager
Admin
Flight
Itinerary.Model
Data Model Layer Itinerary.Controller
Applied abstraction, inheritance and and
ORM (Mapper) Abstract
polymorphism concept. Therefore,
Controller
code can be reused in each layer.
Trip Friend
Itinerary Flight Transport Activity Note Privacy User
Manager Group
Controller Controller Controller Controller Controller Controller Controller
Controller Controller
JDBC
Database (Microsoft Access)
Applied from Kuali Application Architecturehttps://wiki.kuali.org/display/KULRICE/Architecture+(Archive+from+Original+KTC+Work), Last accessed 7 Jan 2012

4. A P P LIED MV C (MO DEL V IEW C O N T R O LLER)
4
O N IT IN ER A RY P R O J EC T.
MS Access database
Update
Update Data
presentation Abstract Controller Class
Data Model Layer
Entity Specific Controller Class
Get Data
Calss1 .. Class n
The Controller Concept
Main functions of our Controller Class
1. Support CRUD Operation between DBMS(persistent layer) and Benefits for this concept.
Data model layer. ( C=Create, R=retrieval, U=Update, D=
Delete )
1. Encapsulate DBMS and SQL Language
2. Map database and tables into Objects. So, a user programmer
doesn’t need to learn about database backend behind 2. Flexible to change DBMS
application. Also, SQL syntax is encapsulated from the
application layer.
Applied from http://www.asp.net/mvc/tutorials/overview/asp-net-mvc-overview, last accessed 11 Jan 2012

5. EX . SO U R C E C O DE A N D IMP L EMEN TAT IO N
5
C O N C EP T IN C O N T R O LLER PA G K A GE
Ex. Abstract Methods in our AbstractController Class Ex. Superclass Methods in our AbstractController Class
// 1) Find And return Single Object by Primary key Value
public Object FindObject(String PKValue)
// 2) Retrieve Object by specific Field Name and Value
// Tell controller what is the table's Primary Key Field Name public Object FindObjectByField(String FieldName,String FieldValue)
public abstract String getPKFieldName();
// 3) Save Your Object to databases
// Tell controller What is the table Name to Store Object public void SaveObject(Object obj)
public abstract String getTableName(); // 4) Retrieve all objects in table
//Tell controller How to Load data from Database to object public ArrayList<Object> getObjectList()
protected abstract Object CreateFromResultSet() // 5) Retrieve objects with conditions
public ArrayList<Object> QueryObjects(String Condition)
// Tell controller How to Store object to databases
protected abstract void SaveToResultSet(Object obj) // 6) retrieve Objects with specific query
public ArrayList<Object> CustomQueryObjects(String SelQuery)
Abstraction, Inheritance and Polymorphism concepts are // 7) delete Object by Primarykey Value
also applied in this AbstractController. public boolean DeleteByPKValue(String PKValue) throws SQLException
Regarding with our abstract class, programmer can Benefits:
implement a subclass as following;
1. Separate characteristic of each subclass which has same
1) Create Class and Inherit from Abstract Controller Class. concept of the abstract class.
2) Override the Abstract Methods to Implement the Controller 2. Code is the same pattern. It is easy to maintain and delegate
class. work.

6. EX . C O MP L ET ED DESIG N IN MO DEL PA C K A GE
6
(R EDU C E R EC O MP L IN G C O DE)
Ex Method in Itinerary.Model Ex Method in Itinerary.User
//1) Create Itinerary //1) Create User Profile
CreateItinerary():boolean CreateProfile():boolean
//2) Update Itineary //2) Update User Profile
UpdateItinerary():boolean UpdateProfile():boolean
//3) Delete Itinerary
//3) Delete User
RemoveItinerary():boolean
RemoveUser():boolean
//==================================
//4) Search Itinerary by Condition
//ex. ItinNo = ‘T01’ and UserName = ‘john’ //==================================
//Function will return array list following condition //4) Search User by Condition
//================================== //ex. UserName = ‘abc’ and FirstName = ‘john’
SearchItinerary(String condition):ArrayList<Itinerary> //Function will return Array list following condition
//==================================
//5) Search by ItinNo SearchUser(String condition):ArrayList<User>
//Return Object of Itinerary
SearchByPk():Itinerary //5) Search by UserName
//Return Object of user JSP is flexible to operate data objects
//Search Shared Itineraries (Needs to check privacy) SearchByPk():User and reduce needs to add more
SearchSharedViewItinerary(String UserName):ArrayList<Itinerary> methods in model classes.
As can be seen, model classes have five main methods.
1. Presentation layer (JSP) can operate inserting, updating,
Benefits:
deleting and retrieving data objects following these main
methods. 1. Flexible to operate creating, updating, deleting and retrieving data
2. We add some methods in model classes for specific needs ex. without recompiling java.
SearchSharedViewItinerary because this function needs to
search with privacy. It cannot use general search method. 2. Database is also encapsulated in this layer.