Design DocumentVersion 1.1

March 27, 2011

FACULTY TRAVEL FORMS

Vijayeandra Parthepan

Submitted in partial fulfillmentOf the requirements of

Advanced database systems

Module-Database Design:

1.0. Database Schema Design

1.1. Introduction

The database schema design provides complete the description of the database that is used in the project. It consist of entities, attributes and relations of the tables data that need to be create in the database

1.2. Scope

The Western Kentucky University travel forms web page is designed to run on the departmental server and to allow three different categories of user’s,

● Faculties can search, view, edit and add their travel request data in the database.● Approver can just search, view and approve the data from the database.● Administrators can maintain the database.

1.3. Database Schema Design

LDAP stands for Lightweight Directory Access Protocol. LDAP is used for authentication of the faculties as well as dean and head of the department. In my database design, i classify the users based on role. Initially, when the user logs in to the system first time with his network

identification values through LDAP, we add him in to our db_user table and classify him accordingly.

When the user is a faculty, he is given the db_faculty table and he can add any type of trips and can also request amount for his trips. If the requested trip is a single trip, then update the db_single_trip and if it is a blanket trip, then update the db_blanket_trip. The estimated cost is updated in the db_estimate_cost table and the remaining details of the individual cost values are stored in db_cost table and other links to it.

When the user is a dean or the department head, then update the db_approver table, when a trip_id from the db_faculty is approved by the particular user. Furthermore depending on whether he is a dean, head of the department or provost update the respective tables and also add their approved amount. If the approved amount of dean and head of department is the same, then update the db_approver table.

Figure 1 Database design schema

1.4. Software Tools

Hardware: Web ServerOperation System Window 98 or above

Database Tool: Mysql-essential version 5.1.39Reference: http :// dev . mysql . com / downloads / mysql /5.1. html Code Standard SQL scriptDesign Tool: UMLet version 10Reference: http :// www . umlet . com /

Module-Form design:

2.0. Travel web form Design

2.1. Introduction

The web page form design provides complete the description of the different forms that is used in the project and their connections. It consist of user types, forms and relations between them.

2.2. Scope

The Western Kentucky University travel forms web page is designed to run on the departmental server and to allow three different categories of user’s,

● Faculties can access the search, view, edit and add page of their respective travel request data forms from the database.

● Approver can access the search, view and approve the data from the database page.● Administrators can access the admin page to maintain the database and it consists of all

the required functions.

2.3. Travel Web Form Design

We use JavaScript for the external form design. LDAP is used for authentication of the faculties as well as dean and head of the department. In my form design, i classify the users based on role. Initially, when the user logs in to the system through LDAP, he gets directed based on the type of the user.

When the user is a faculty, he can add any type of trips and can also request amount for his trips. If the requested trip is a single trip, then show the single trip web page and if it is a blanket trip, then update the blanket trip web page. The estimated cost is updated through the estimate cost page.

When the user is a dean or the department head, then show the approver menu depending on whether he is a dean, head of the department or provost and he can add their approved amount by respective users with reference to the other users.

2.3.1 Dataflow diagram for login

Brief DescriptionThe Web Server is waiting the user to login with their username and password.

Initial step-by-step descriptionFor this use case to be initiated, the user must be connected to the Internet and connected to

the Web Server.1. The client sends the username and password to the Web Server.2. The server check for username and password form the LDAP university database.3. The database returns user information back to the server.4. The server set the authorization for the client.5. The server redirect to the another page.

● If authorization is success, it redirect to menu page.● Else it redirect to the Login page with the error message.

2.3.2 Dataflow diagram for menu

Brief Description:

The Menu page shows the menu for the user to select.

Initial step-by-step description:For this use case to be initiated the user must be connected to the Internet and must be logged

in on the Menu Page.1. The client selects the link on the menu.

2.3.3 Dataflow diagram for faculty

Brief Description:The Web page displays the empty travel request form to be filled by the user.

Initial step-by-step description:For this use case to be initiated the user must be connected to the Internet and be logged in.1. The client pass the entered travel request data to the server.2. The server checks for correctness of information and validate the data.3. The server stores the faculty travel request file’s address to the database through

hibernates.4. The hibernates maps the details of the record with the web page through object relational

mapping.5. The server displays the travel request complete or error page.

2.3.4 Dataflow diagram for view

Brief Description:The Web page displays the travel requests to be approved.

Initial step-by-step description:For this use case to be initiated the user must be connected to the Internet and be logged in as

a head of the department or dean.1. The client pass the user selected faculty travel request to the server.2. The server searches the faculty travel request file’s address to the database through

hibernates.3. The hibernates maps the details of the record with the web page.4. The server opens the travel request form to be viewed by the approver.5. The server displays the travel request form data on the client screen.

2.3.5 Dataflow diagram for Approver

Brief Description:The Web page displays the list of travel form requests, that are sent by faculties..

Initial step-by-step description:For this use case to be initiated the user must be connected to the Internet and be logged in as

a head of the department or dean.1. The client pass the entered travel request data approval to the server.2. The server checks for correctness of information and validate the data.3. The server stores the faculty travel request file’s address to the database through

hibernates. Now, the travel request form gets approved or disapproved.4. The hibernates maps the details of the record with the web page through object relational

mapping. This will check whether the data entered by the user is validated.5. The server displays the travel request approval complete or error page

2.4. Software Tools

Hardware: Web ServerOperation System Window 98 or aboveCode Standard SQL scriptDesign Tool: UMLet version 10Reference: http :// www . umlet . com /

Design Tool : Dreamweaver MX 2004 version 7.0.1 Reference : WKU Labs