Hotel Management System

System Design Document

Revised Version: SDD 2.0

Prepared by

Team #26
Ruken GÜNEŞ

Bahar TEKE

Özlem HAYRAT

Ömer ÖZTÜRK

2012
HOTEL MANAGEMENT SYSTEM

Preface

This document is Software Design Document for our project named as Hotel Management
System. In this document, system modul will be documented clearly.

Atılım University 2/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

TABLE OF CONTENT

PREFACE.......................................................................................................................................2
INTRODUCTION............................................................................................................................3
1.1. Purpose...................................................................................................................................4
1.2. Scope......................................................................................................................................4
1.3. Definitions, Acronyms & Abbreviations...............................................................................4
1.4. REFERANCES.................................................................................................................5
3. SYSTEM COMPONENTS.............................................................................................................7
3.1. Decomposition Description.................................................................................................7
3.1.1. Module Decomposition................................................................................................7
3.1.2. Data Decomposition..................................................................................................21
3.2. Dependency Description...................................................................................................21
3.2.1. Intermodule Description............................................................................................21
3.2.2. Data dependencies....................................................................................................23
A user can book several rooms. A room can be reserved by one user.........................................24
3.3. 3.3 Interface Description...................................................................................................25
3.3.1. Module Interfaces......................................................................................................25
3.3.2. User Interfaces (GUI)...............................................................................................26
4. DETAILED DESIGN................................................................................................................31
4.1. Module Detailed Design....................................................................................................31
4.1.1. Login Module.............................................................................................................31
4.1.2. Register Module.........................................................................................................31
4.1.3. Messaging Module....................................................................................................31
4.2. RTM...................................................................................................................................32
4.3. Data Detailed Design.........................................................................................................33
4.4. Appendix 1 – ER Diagram..................................................................................................36
4.5. Appendix 2 - Class Diagram...............................................................................................36
4.6. Appendix 3 – Interface Codes...........................................................................................37
4.6.1. Main Page Interface Codes (index.html)....................................................................38
4.6.2. Sign Up Interface Codes.............................................................................................39
4.6.3. Sign In Interface Codes..............................................................................................43
4.6.4. Administrator Interface Codes...................................................................................45
4.6.5. Messaging Interface Codes........................................................................................47
4.6.6. Reservation Interface Codes......................................................................................50
4.6.7. Booking Interface.......................................................................................................57
4.6.8. User(Authorized) Interface Codes..............................................................................60

Atılım University 3/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

1. Introduction

1.1. Purpose

The purpose of Software Design Description is to identify what need to coded that is
specified in SRS. In this document, brief information of Hotel Management System will be
given.

1.2. Scope

In this document, the detailed description of Hotel Management System will be given.
Our hotel management system project will have a web interface.

In the web interface, there are 3 types of user and which are;

-Administration

-Staff

-Authorized user

Each user type will have a different authorization to access to the system.

1.1. Definitions, Acronyms & Abbreviations

Atılım University 4/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

DB Database
FP Function Points
GUI Graphic User Interface
HTML Hypertext Markup Language
HW Hardware
IDE Integrated Development Environment
IE Internet Explorer
IEEE Institute of Electrical and Electronics Engineers
I/O Input / Output
IP Initial Plan
KU Knowledge Unit
LOC Line Of Code
MS Microsoft
PS Problem Statement
RAM: Random Access Memory
SDD Software Design Description
SPS Student Portal System
SPMP Software Project Management Plan
SQL Structured Query Language
SRS Software Requirements Specification
SW Software

1.3. REFERANCES

 IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans
 Pressman, Roger S., Software Engineering, 4th edition, McGraw-Hill, 1997
 Fairley, R. E., Work breakdown Structure, Software Engineering Project Management,
IEEE CS Press, 1997

Atılım University 5/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

2. System Overview

Hotel management system is a web based project, which helps to hotel employees
interacting to clients and each other. To do this, hotel management system has messaging,
sending e-mail module

Atılım University 6/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

3. System Components

1.2. Decomposition Description

1.2.1. Module Decomposition

The way followed while making module decomposition is to divide the system into
modules so that the operations are done under each module will be higly related with each
other, but they are not so much related with other operations in other modules. Taking this
into consideration, hotel management system project’s main services are as follows;

3.1.1.1 User Authetication Module

Identification: User Authentication Module

Type: Application

Purpose: This Module provide user to register and authenticate user.

Function: User enables to register to system and log in. Also this module provide
changing password and help user if they forgot their password.

Subordinates:

- Sing in

- Log in

- Changed Password

 Forgotten Password

3.1.1.1.1. Sign in
Identification: Sign in
Type: Process

Atılım University 7/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

Purpose: Provides user to get their authorization level which is recorded in corresponding
cell of the user table.

Function: A user enters their required information (e-mail, password) to the web form. If
those information match with a row of the user table, user gets their authorization level.

Subordinates:

- None

3.1.1.1.2. Sign Up

Identification: Sign up

Type: Process

Purpose: Provides a registration process to user, if user information is not

recorded to the user table.

Funtion: A visitor fills the registration form and click on the Complete Registration
button. If every information given is correct, user's information is recorded to user table
and user get the “customer”status by default. For other employee is defined by the
administrator in their panel manually.

3.1.1.1.4. Change Password

Identification: Change Password

Type: Process

Purpose: To make user able to change their passwords.

Funtion: User enters their old password and new password. New password replaces with
the old password if it is correct.

Atılım University 8/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

Subordinates:

 None

3.1.1.1.5. Forgotten Password

Identification: Forgotten Password

Type: Process

Purpose: By this module, user can get their fogotten password.

Funtion: User sends a request to the system that denotes they have forgotten their
password. System sends them an e-mail including their password.

Subordinates:

 None

3.1.1.2 Messaging Module

Atılım University 9/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

Identification: Messaging Module

Type: Application

Purpose: This module is used for messaging between users except customer.

Function: Employees can send or receive message each other.

Subordinates:
Send Message
Messaging Module (Other Users)
- Send Message
- Delete Message

3.1.1.2.2 Send Message

Identification: Send Message
Type: Process
Purpose: For faster communication, provides hotel employee to send and
receive text messages.
Funtion: User fills the required areas in the form and clicks on the “Send”button.
According to the information in the messages table, every user has their sent and received
messages.
Subordinates:
 None

3.1.1.2.3 Delete Message

Identification: Delete Message

Type: Process

Purpose: Provides hotel employee to delete their messages visually.

Funtion: User clicks on the “Delete” button. Message status changes to“deleted” and user
can not see that message anymore. At the end, the message does not deleted from table.
Because of foreign key constraints, the corresponding message's status changes.

Atılım University 10/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

Subordinates:
 None

3.1.1.3 Searching Module

Identification: Searching Module

Type: Application

Purpose: It allows user to searching infomration, data in the system.

Function:

Subordinates:

Searching Module(Administrator)
- Search Room
- Search Employee
- Search Customer

Atılım University 11/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

3.1.1.3.1 Search Room (Administrator)

Identification: Search Room
Type: Process
Purpose: Provides a sophisticated room searching to administrators.
Funtion: Administrator enters the capacity and price intervals to the module.
All suitable rooms are listed.
Subordinates:
 None
3.1.1.3.2 Search Employee
Identification: Search Employee
Type: Process
Purpose: Provides administrator to search employee by type, name, etc.
Funtion: Administrator specifies how the search will be done, all suitable employee
information are listed.
Subordinates:
 None
3.1.1.3.3 Search Customer
Identification: Search Customer
Type: Process
Purpose: Provides administrator to search customer by name and SSN.
Funtion: Administrator specifies how the search data, all suitable customer information
are listed.
Subordinates:
 None

Atılım University 12/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

3.1.1.5 Online Reservation Module

Identification: Online Reservation Module

Type: Application

Purpose: This module allows to customer

Function:

Subordinates:

- Reserve Room

- Modify Reservation

-Cancel Reservation

3.1.1.5.1 Reserve Room

Identification: Reserve Room
Type: Process
Purpose: Provides customer to reserve a room.
Funtion: Customer picks a room. Specifies entering and leaving dates and how the room
price will be paid. Clicks on reserve button.
Subordinates:
 None

Atılım University 13/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

3.1.1.5.2 Modify Reservation

Identification: Modify Reservation
Type: Process
Purpose: Provides customer to change their reservation information.
Funtion: Customer clicks on modify reservation button. They can change any information
about the room and cancel the reservation.
Subordinates:
 Cancel Reservation

3.1.1.5.2.1 Cancel Reservation

Identification: Cancel Reservation
Type: Process
Purpose: Provides customer to cancel the reservation. Any related data in the reservation
table will be erased.
Funtion: Customer clicks on cancel reservation button. Reservation is canceled.
Subordinates:
 None

3.1.1.6 Manage Room Module

Identification: Manage Room Module

Type: Application

Purpose: Adminstator enable to manage room.

Atılım University 14/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

Function: This module provides add, delete or change room information like room is
vacated or occupied.

- Add Room

- Delete Room

 Modify Room Information(Vacated/Occupied)

3.1.1.6.1 Add Room

Identification: Add Room
Type: Process
Purpose: Provides administrator to add a new room.
Funtion: Administrator clicks on “Add new Room” button, fills the form according to
room specifications, clicks on save button.
Subordinates:
 None

3.1.1.6.2 Delete Room

Identification: Delete Room
Type: Process
Purpose: Provides administrator to delete a room.
Funtion: Administrator clicks on “Delete Room” button, clicks on save button. Because
room information does not erased from the database, this process is reversible.
Subordinates:
 None

3.1.1.6.1 Modify Room Information

Identification: Modify Room Information
Type: Process
Purpose: Provides administrator to modify a room's information.
Funtion: Administrator clicks on “Modify Room Information” button, all the information
can be changed.
Subordinates:
 None

Atılım University 15/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

3.1.1.8 Employee Management Module

Identification: Employee Management Module

Type: Application

Purpose: Employee management module provides recording all user information except
from customer.

Function: Adding, deleting and modifying employee information.

Subordinates:

- Delete Employee

- Modify Employee Information

 List Employees

3.1.1.8.2 Delete Employee

Identification: Delete Employee
Type: Process
Purpose: Provides administrator to delete an employee.
Funtion: When an employee is fired or quit, administrator clicks on “Delete employee”
button and employee is deleted from user table.
Subordinates:
 None

Atılım University 16/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

3.1.1.8.3 Modify Employee Information

Identification: Modify Employee Information
Type: Process
Purpose: Provides administrator to modify an employee's information.
Funtion: When it is required, administrator clicks on “Modify” button and makes
the necessary changes.
Subordinates:
 None

3.1.1.8.4 List Employees

Identification: List Employees
Type: Process
Purpose: Provides administrator to list all the employees according to
given interval.
Funtion: Administrator clicks on “List” button and specifies the listing property. All the
suitable employee information are listed.
Subordinates:
 None

Atılım University 17/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

3.1.1.9 Contact to Supplier Module

Identification: Contact to Supplier Module

Type : Application

Purpose: Administrator can control Supplier relation in side of order.

Function: This module provides contact to supplier, sending email and order.

Subordinates:

- Search Supplier

 Send E-Mail

3.1.1.9.1 Search Supplier

Identification: Search Supplier
Type: Process
Purpose: Provides administrator to search suppliers.
Funtion: Administrator clicks on “Search” button and specifies the wanted supplier
properties. All the suitable suppliers are listed.
Subordinates:
 None

3.1.1.9.2 Send E-Mail

Identification: Send E-Mail
Type: Process
Purpose: Provides administrator to send an e-mail to supplier.
Funtion: Administrator clicks on e-mail link in the supplier information, clicks on “Send”
button.
Subordinates:
 None

Atılım University 18/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

3.1.1.10. Announcements Module

Identification: Announcement Module

Type: Application

Purpose: This module provides giving information about events.

Function: Administator enable to add, delete or change announcement.

Subordinates:

- Add Announcement

- Delete Announcement

 Modify Announcement

3.1.1.10.1 Add Announcement

Identification: Add Announcement
Type: Process
Purpose: Provides administrator to add a new announcement.
Funtion: Administrator clicks on “Add new Announcement” button,enters the
announcement information and clicks on “Done” button.
Subordinates:
 None

3.1.1.10.2 Delete Announcement

Identification: Delete Announcement
Type: Process
Purpose: Provides administrator to delete an announcement.
Funtion: Administrator clicks on “Delete” button, and deletes the announcement.

Atılım University 19/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

Subordinates:
 None

3.1.1.10.2 Modify Announcement

Identification: Modify Announcement
Type: Process
Purpose: Provides administrator to modify an announcement.
Funtion: Administrator clicks on “Modify” button, makes the necessary changes, clicks
on “Done” button.
Subordinates:
 None

3.1.1.11. Restaurant Management Module

Identification: Restaurant Management Module

Type: Application

Purpose: This module provides information about food.

Function: Staff enables to add food information.

Subordinates: Add information food

3.1.1.11.1 Add Food Information

Identification: Add Food Information
Type: Process
Purpose: Provides the charged staff to add food menu information.
Funtion: Staff clicks on “Add” button, fills the fields and clicks on “Done” button.
Subordinates:

Atılım University 20/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

 None

1.2.2. Data Decomposition

ER and Class Diagrams for Hotel Management System is given in appendix section.

1.3. Dependency Description

1.3.1. Intermodule Description

The services and modules of Hotel Management System are given detailed in section 3.1.1.
In this part, the dependency between modules under services will be explained. Also, at the
beginning of that section, dependencies between services are depicted. This part of SDD
examines the dependency between modules under those services. These dependencies are
categorized as following:

If module can be used by only authenticated user, this relation is shown with letters “AU”
stands for “Authenticated Users”.

If module gets some data from other module, this relation is shown with letters “GD”
stands for “Get Data”.

Atılım University 21/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM
Dependency
Matrix

Mana Employe Contac Restaurant

User Mess Sear ge e Anno to management
Authent Reserv age ch room Manage u nce Supplier module
ication ation Mod Mod Modu ment Modu Module
Module Module ule ule le Module le

User
Authentication
GD GD
Module GD GD GD GD

Reservation
Module GD

Message Module GD

Search Module GD

Manage room
Module
Employee
management
Module GD GD

Announcement
module GD GD

Contact
toSupplier Modu
Restaurant
management
Module

Intermodule Description

Atılım University 22/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

1.3.2. Data dependencies

In this part of SDD, relations between entities will be mentioned.

userregistrationInfo – userGeneralInfo

userRegistrationInf
o 1 1 userGeneralInfo

1:1 relation. A user can have one general information. A general information can
belong to one user.

userregistrationInfo – messages

userRegistrationInf
o 2 M Messages

2:M relation. A user may have many messages. A particular message belongs to two
users which are sender and receiver.

userregistrationInfo – announcement

userRegistrationInfo 1 N Announcement

1:N relation. One user(administor) can give several announcements. An

announcement may belong to one user(administrator).

userregistrationInfo - room

Atılım University 23/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

userRegistrationI
nfo 1 N Room

A user can book several rooms. A room can be reserved by one user.

Atılım University 24/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

1.4. 3.3 Interface Description

1.4.1. Module Interfaces

In this part of SDD, communication between modules is explained in detail.

ViewInformation
viewReservedRoom
Database Module < - > <-> Profile Module
viewMessages
viewMails

viewSentMessage
viewReceivedMessage
Database Module < - > viewDeletedMessage <-> Message Module
viewMesSender
viewMesReceiver

login
Database Module < - > registration <-> Authentication Module
passwordTransections

setHeader
setImage
Database Module < - > <-> Announcement Module
setContent
announcementHistory

1.4.2. User Interfaces (GUI)

Atılım University 25/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

In this part of SDD, user interfaces are explained in detail. The screenshots are taken from
Google Chrome and only HTML and CSS are used in designing user interfaces. There may
be some incompatibility issues with other browsers such as Internet Explorer because of
CSS. However

they will be tested and handled during the application development process.

1.4.2.1. Main Page Interface

This interface will be variated according to different user types. For unauthorized users,
there will be a common interface which contains advertisements, announcements, and sign
in, sign up menus.

When user signed in, according to their type, users will be shown different main pages and
those are;

Authorized user: This type of users’ menu will have standard options (HOME, CONTACT,
ABOUT US, and LOG OUT) and RESERVATION option. Also their

Profile information can be seen.

Atılım University 26/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

Administrator: This interface will have ROOMS, MESSAGES, SUPPLIER,

CUSTOMERS and LOG OUT menu. Also an Announcement wizard will be seen

Accounter: This interface will have ROOMS, MESSAGES, ACCOUNTING,

CUSTOMERS and LOG OUT menus. Latest activities will be shown in this menu. Those
activities will be recorded to database in activity history section.

Atılım University 27/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

Staff: This interface will have ROOMS, MESSAGES and LOG OUT menus. Staff also can
operate offline reservations.

3.3.2.2 Registration Interface

All types of users will have to sign up using this interface. They will have to give
their names, e-mail addresses, passwords and authentication level to complete
their registration. Also a security image will be shown and user will be forced to
enter the text in this image for security issues.

Atılım University 28/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

3.3.2.3 Login Interface

To login, all users will have to use this interface. It will ask the e-mail and password
to users.

3.3.2.5 Messaging Interface

Administrators, staff and accounters can use this interface to send and receive
messages. Also deleting and organizing messages features will be included.

3.3.2.6 Reservation Interface

In this interface, authorized users(customers) can choose and book a room

according to their needs. To make this progress easier, there will be a reducing

Atılım University 29/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

wizard who accepts lowest price and higher price to eliminate the unsuitable
rooms. A screenshot is given in appendix section

There will be profile pages for each user which show the information for each user
such as registration date, name, SSN.

Atılım University 30/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

2. Detailed Design

2.1. Module Detailed Design

2.1.1. Login Module

Method Name: Login

Description: allows users to enter the system
Share Type: public
Return Type: Boolean
Parameters: username, password, imageVerification

2.1.2. Register Module

Method Name: registration

Description: registers a new user to the system
Share Type: public
Return Type: boolean
Parameters: firstName, lastName, password, email, birthDate, gender, country, city, distinct.

2.1.3. Messaging Module

Method Name: messageing

Description: allow to send and receive between users
Share Type: public
Return Type: void
Parameters: online friends list, ignore user list
4.1.4 Adding Announcement

Method Name: adding announcement

Description: allows users to add announcements
Share Type: public
Return Type: Boolean

Atılım University 31/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

Parameters: login information, payment Status

3.1. RTM

Requirement Design
Requirement # Requirement Description ref. reference Module name
CR1
User Authentication Module
- Log-in
1 User Authentication 2.2.1.1 3.1.1.1. - Sign-up
- change Password
- Forgotten Password

Room Management Module

2 Manage Room 2.2.3.1 3.1.1.6. -Add Room
-Delete Room
-Modify Room
Information(Vacated/Occupied)
Manage Employee Module
3 Employee management 2.2.3.5 1.1.8. - Delete Employee
- Modify Employee Info -
List Employee

4 Messaging 2.2.3.3 3.1.1.2. Messaging Module

-Send Message
- Delete Message
CR2

Searching
5 Searching 2.2.3.6 3.1.1.3. Module(Administrator)
- Search Room
- Search Customer
- Search Employee

6 Online Reservation 2.2.2.1 3.1.1.5. Online Reservation Module

- Reserve Room
Announcement Module
7 Announcement 2.2.4.2 3.1.1.10 - Add Announcement
- Delete Announcement
- Modify Announcement

8 Contact to Supplier 2.2.5.1 3.1.1.9.

Contact Supplier Modul
- Add Supplier

Atılım University 32/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

CR3

6 Online Reservation 2.2.2.1 3.1.1.5. Online Reservation Module

-Modify Rezervation
Searching
5 Searching 2.2.3.6 3.1.1.3. Module(Administrator)
- Search Customer
Food Food
9 Food Information Information Information
Module Module Module Food Information Module

2.2. Data Detailed Design

Table Name: userRegistrationInfo
This table holds user’s registration information.

Column Name Data Type Description Example

userId (PK) INT primary key, auto increment, not null 1

firstName VARCHAR(15) holds first name of user Murat

lastName VARCHAR(15) holds last name of user Çatal

Password VARCHAR(15) holds password of user $123_321$

Email VARCHAR(45) holds email of user [email protected]

templateId INT holds the template id of user. This column

is PK for template table. 23333

Table 1: User Registration Info

Table Name: userGeneralInfo

This table holds the user’s general information.

Column Name Data Type Description Example

userId (PK) INT primary key, auto increment, not null 1

Atılım University 33/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

birthDate VARCHAR(15) holds birthDate of user 22.05.1986

Gender VARCHAR(5) holds gender of user Male

Country VARCHAR(45) holds the name of country where user lives Turkey

City VARCHAR(45) holds the name of city where user lives Ankara

District VARCHAR(45) holds the name of district where user lives Bahçelievler

Table 2: User General Info

Table Name: messages

This table holds the messages.

Column Name Data Type Description Example

messageId(PK) INT primary key, auto increment, not null 1

sendDate VARCHAR(15) shows the send date of the message 22.05.2010

byWhom VARCHAR(15) shows the sender of the message Murat

toWhom VARCHAR(15) shows receiver of the message Satiye

readDate VARCHAR(15) shows the read date of the message 23.05.2010

Title VARCHAR(45) shows the title of the message SDD

messageType VARCHAR(45) shows the type of the message (inbox,

outbox etc) Outbox

userId(FK) INT shows that this message belongs to which

user 1

Table 3: Message

This table holds information about announcements.

Column Name Data Type Description Example

announcementId(PK) INT primary key,auto increment, not null 1

Description VARCHAR(15) holds the description of the announcement 50% price cut

Active INT holds the announcement is active or not 1

Atılım University 34/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

Picture VARCHAR(15) holds the name of picture of the announcement picture.jpeg

publishPlace VARCHAR(15) holds the web site publish place of the

announcement left down

userId INT holds the id of the user which gives

announcement 4

Table 4: Announcement
Table Name: rooms

This table holds information about rooms.

Column Name Data Type Description Example

roomId(PK) INT primary key,auto increment, not null 1

Capacity INT holds the description of the capacity 4

Status INT -1:N/A, 0:Reserved, 1:Available 1

Picture VARCHAR(15) holds the name of picture of the announcement picture.jpeg

publishPlace VARCHAR(15) holds the web site publish place of the

announcement left down

userId INT holds the id of the user which gives

announcement 4

2.3. Appendix 1 – ER Diagram

Atılım University 35/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

2.4. Appendix 2 - Class Diagram

Atılım University 36/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

2.5. Appendix 3 – Interface Codes

2.5.1. Main Page Interface Codes (index.html)

<html>

Atılım University 37/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<head>

<title>HTML Frames Example - Content</title>

<style type="text/css">

body {

font-family:verdana,arial,sans-serif;

font-size:10pt;

margin:30px;

background-color:#CCCCCC;

a{

text-decoration:none;

color:#000000;

font-weight:bold;

</style>

</head>

<body><p align="center">

<a href="">HOME|</a>

<a href="">CONTACT|</a>

<a href="">ABOUT US|</a>

<a href="">SIGN IN|</a>

<a href="">SIGN UP</a>

</p>

<p align="center"><img src="../template/marriot1.jpg" align="center"></p>

<p align="center">&nbsp;</p>

Atılım University 38/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<p align="center">&nbsp;</p>

<p align="center">&nbsp;</p>

</body>

</html>

2.5.2. Sign Up Interface Codes

<html>

<head>

<title>HTML Frames Example - Content</title>

<style type="text/css">

body {

font-family:verdana,arial,sans-serif;

font-size:10pt;

margin:30px;

background-color:#CCCCCC;

a{

text-decoration:none;

color:#000000;

font-weight:bold;

</style>

</head>

<body><p align="center">

<a href="">HOME|</a>

<a href="">CONTACT|</a>

Atılım University 39/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<a href="">ABOUT US|</a>

<a href="">SIGN IN|</a>

<a href="">SIGN UP</a>

</p>

<p align="center">&nbsp;</p>

<table align="center">

<tr>

<td width="201">

Name:</td>

<td width="149">

<input type="text" />

</td>

</tr><br>

<tr>

<td>

Surname:

</td>

<td>

<input type="text" />

</td>

</tr>

<tr>

<td>

E-Mail:

Atılım University 40/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

</td>

<td>

<input type="text" />

</td>

</tr><br>

<tr>

<td>

Password:

</td>

<td>

<input type="password" />

</td>

</tr>

<tr>

<td>

Authentication Level:

</td>

<td>

<select>

<option value="admin">Administrator</option>

<option value="accounter">Accounter</option>

<option value="staf">Staf</option>

<option value="user">Client</option>

</select>

Atılım University 41/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

</td>

</tr><br>

<tr>

<td>

<img src="vcm_s_kf_repr_201x122.jpg" width="173" height="99"></td>

<td>

<input type="text">

</td>

</tr>

<tr>

<td>

<input type="submit" align="right" value="Submit">

</td>

</tr>

</table>

<p align="center">&nbsp;</p>

<p align="center">&nbsp;</p>

<p align="center">&nbsp;</p>

</body>

</html>

2.5.3. Sign In Interface Codes

<html>

Atılım University 42/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<head>

<title>HTML Frames Example - Content</title>

<style type="text/css">

body {

font-family:verdana,arial,sans-serif;

font-size:10pt;

margin:30px;

background-color:#CCCCCC;

a{

text-decoration:none;

color:#000000;

font-weight:bold;

</style>

</head>

<body><p align="center">

<a href="">HOME|</a>

<a href="">CONTACT|</a>

<a href="">ABOUT US|</a>

<a href="">SIGN IN|</a>

<a href="">SIGN UP</a>

</p>

<p align="center">&nbsp;</p>

<table align="center">

Atılım University 43/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<tr>

<td>

E-Mail:

</td>

<td>

<input type="text" />

</td>

</tr><br>

<tr>

<td>

Password:

</td>

<td>

<input type="password" />

</td>

</tr>

</table>

<p align="center">&nbsp;</p>

<p align="center">&nbsp;</p>

<p align="center">&nbsp;</p>

</body>

</html>

2.5.4.Administrator Interface Codes

Atılım University 44/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<html>

<head>

<title>HTML Frames Example - Content</title>

<style type="text/css">

body {

font-family:verdana,arial,sans-serif;

font-size:10pt;

margin:30px;

background-color:#CCCCCC;

a{

text-decoration:none;

color:#000000;

font-weight:bold;

</style>

</head>

<body><p align="center">

<a href="">ROOMS|</a>

<a href="">MESSAGES|</a>

<a href="">SUPPLIER|</a>

<a href="">CUSTOMERS|</a>

<a href="">LOG OUT</a>

<p>You are logged in as administor</p>

<h3>ADVERTISEMENT CREATOR</h3>

Atılım University 45/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<table width="292" height="142">

<tr>

<td height="55">

Header:</td>

<td>

<input type="text">

</td>

</tr>

<tr>

<td height="67">

<input type="button" value="choose an image">

</td>

<td bgcolor="#FFF">

<p style="color:#000000">Image Section</p>

</tr>

</table>

<input type="button" value="Reservations">

</p>

<p align="center">&nbsp;</p>

<p align="center">&nbsp;</p>

<p align="center">&nbsp;</p>

</body>

</html>

2.5.5.Messaging Interface Codes

Atılım University 46/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<html>

<head>

<title>HTML Frames Example - Content</title>

<style type="text/css">

body {

font-family:verdana,arial,sans-serif;

font-size:10pt;

margin:30px;

background-color:#CCCCCC;

a{

text-decoration:none;

color:#000000;

font-weight:bold;

</style>

</head>

<body align="center" >

<a href="">ROOMS|</a>

<a href="">MESSAGES|</a>

<a href="">ACCOUNTING|</a>

<a href="">CUSTOMERS|</a>

<a href="">LOG OUT</a>

<p>You are logged in as accounter</p>

<a href="">Inbox|</a>

Atılım University 47/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<a href="">Sent|</a>

<a href"">Trash</a>

<table>

<tr>

<td>

From:

</td>

<td>

Mustafa Demirci (Administrator)

</td>

</tr>

<tr>

<td>

To:

</td>

<td>

<input type="text" />

</td>

</tr>

<tr>

<td>

Subject:

</td>

<td>

<input type="text" />

Atılım University 48/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

</td>

</tr>

<tr>

<td>

Text:

</td>

<td>

<textarea></textarea>

</td>

</tr>

<tr>

<td>

File:

</td>

<td>

<input type="button" value="Attach File">

</td>

</tr>

</table>

</body>

</html>

2.5.6. Reservation Interface Codes

<html>

Atılım University 49/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<head>

<title>HTML Frames Example - Content</title>

<style type="text/css">

body {

font-family:verdana,arial,sans-serif;

font-size:10pt;

margin:30px;

background-color:#CCCCCC;

a{

text-decoration:none;

color:#000000;

font-weight:bold;

</style>

</head>

<body><p align="center">

<a href="">HOME|</a>

<a href="">CONTACT|</a>

<a href="">ABOUT US|</a>

<a href="">RESERVATION|</a>

<a href="">LOG OUT</a>

</p><br>

<br>

<br>

Atılım University 50/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

Room Capacity

<select>

<option>1</option>

<option>2</option>

<option>3</option>

<option>4</option>

</select><br>

<br>

<br>

<table>

<tr>

<td>

ROOM FINDER

</td>

</tr>

<tr>

<td>

Low Price:

</td>

<td>

<input type="text">$

</td>

<td>

Atılım University 51/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

</td>

<td>

High Price:

</td>

<td>

<input type="text">$

</td>

</tr>

</table>

<br>

<br>

<br>

<table width="336" height="312" align="left" valign="top" border="1">

<tr>

<td width="344" height="36" align="center">

Room 1</td>

</tr>

<tr>

<td height="149">

<img src="hotel-room-2.jpg" width="328" height="276"></td>

</tr>

<tr>

<td height="117" align="center">

Room Price: 300$<br>

Atılım University 52/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

Status: Available<br>

<input type="submit" value="Book">

</td>

</tr>

</table>

<table width="336" height="312" align="left" valign="top" border="1">

<tr>

<td width="344" height="36" align="center">

Room 2</td>

</tr>

<tr>

<td height="149">

<img src="hotel-room-2.jpg" width="328" height="276"></td>

</tr>

<tr>

<td height="117" align="center">

Room Price: 400$<br>

Status: Available<br>

<input type="submit" value="Book">

</td>

</tr>

</table>

<table width="336" height="312" align="left" valign="top" border="1">

Atılım University 53/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<tr>

<td width="344" height="36" align="center">

Room 3</td>

</tr>

<tr>

<td height="149">

<img src="hotel-room-2.jpg" width="328" height="276"></td>

</tr>

<tr>

<td height="117" align="center">

Room Price: -<br>

Status: Reserved<br>

</td>

</tr>

</table>

<table width="336" height="312" align="left" valign="top" border="1">

<tr>

<td width="344" height="36" align="center">

Room 4</td>

</tr>

<tr>

<td height="149">

<img src="hotel-room-2.jpg" width="328" height="276"></td>

Atılım University 54/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

</tr>

<tr>

<td height="117" align="center">

Room Price: 300$<br>

Status: Available<br>

<input type="submit" value="Book">

</td>

</tr>

</table>

<table width="336" height="312" align="left" valign="top" border="1">

<tr>

<td width="344" height="36" align="center">

Room 5</td>

</tr>

<tr>

<td height="149">

<img src="hotel-room-2.jpg" width="328" height="276"></td>

</tr>

<tr>

<td height="117" align="center">

Room Price: -<br>

Status: N/A<br>

</td>

Atılım University 55/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

</tr>

</table>

<table width="336" height="312" align="left" valign="top" border="1">

<tr>

<td width="344" height="36" align="center">

Room 6</td>

</tr>

<tr>

<td height="149">

<img src="hotel-room-2.jpg" width="328" height="276"></td>

</tr>

<tr>

<td height="117" align="center">

Room Price: 300$<br>

Status: Available<br>

<input type="submit" value="Book">

</td>

</tr>

</table>

</body>

</html>

2.5.7. Booking Interface

Atılım University 56/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<html>

<head>

<title>HTML Frames Example - Content</title>

<style type="text/css">

body {

font-family:verdana,arial,sans-serif;

font-size:10pt;

margin:30px;

background-color:#CCCCCC;

a{

text-decoration:none;

color:#000000;

font-weight:bold;

</style>

</head>

<body><p align="center">

<a href="">HOME|</a>

<a href="">CONTACT|</a>

<a href="">ABOUT US|</a>

<a href="">RESERVATION|</a>

<a href="">LOG OUT</a>

</p>

<table width="336" height="312" align="left" valign="top" border="1">

Atılım University 57/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<tr>

<td width="344" height="36" align="center">

Room 1</td>

</tr>

<tr>

<td height="149">

<img src="hotel-room-2.jpg" width="328" height="276"></td>

</tr>

<tr>

<td height="117" align="center">

Room Price: 300$<br>

Status: Available<br>

<input type="submit" value="Book">

</td>

</tr>

</table>

<table align="center">

<tr>

<td>

Payment Type:

</td>

<td>

<select>

<option>Credit Card</option>

Atılım University 58/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<option>Transfer</option>

<option>Cash</option>

</select>

</td>

</tr>

<tr>

<td>

Check-In:

</td>

<td>

<Input type="text">

</td>

</tr>

<tr>

<td>

Check-out:

</td>

<td>

<input type="text">

</td>

</tr>

<tr>

<td>

Atılım University 59/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

</body>

</html>

2.5.8.User(Authorized) Interface Codes

<html>

<head>

<title>HTML Frames Example - Content</title>

<style type="text/css">

body {

font-family:verdana,arial,sans-serif;

font-size:10pt;

margin:30px;

background-color:#CCCCCC;

a{

text-decoration:none;

color:#000000;

font-weight:bold;

</style>

</head>

<body><p align="center">

<a href="">HOME|</a>

<a href="">CONTACT|</a>

<a href="">ABOUT US|</a>

Atılım University 60/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

<a href="">RESERVATION|</a>

<a href="">LOG OUT</a>

<p align="center">You are logged in as authorized user</p>

<h3>User Information</h3>

<table>

<tr>

<td>

Name:

</td>

<td>

Ruken

</td>

</tr>

<tr>

<td>

Surname:

</td>

<td>

Gunes

</td>

</tr>

<tr>

<td>

SSN:

Atılım University 61/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26
HOTEL MANAGEMENT SYSTEM

</td>

<td>

123

</td>

</tr>

</table>

</body>

</html>

Atılım University 62/62 System Design Document

COMPE 492 Version: 2.0
TEAM #26