Part 4 Sample 1

8/3/2019 Part 4 Sample 1

1/40

ANALYSIS AND DESIGN

OF

(PROJECT)

Systems Design Specification


2/40

Table of ContentsANALYSIS AND DESIGN............................................................................................1

OF............................................................................................................................1

(PROJECT)................................................................................................................1

Table of Contents ....................................................................................................... 2

Table of Figures: ......................................................................................................... 4

Executive Summary: ................................................................................................... 5

Introduction: ............................................................................................................... 5

Overview: ............................................................................................................... 5

Purpose: .................................................................................................................. 5

Scope: ..................................................................................................................... 5

Detailed Process Description: ..................................................................................... 6

Context Level Process Description: ......................................................................... 6

Process Description (Context level): ..................................................................... 6

Level 1 Process Description: .................................................................................... 7

Process Description (Process 1.0): ....................................................................... 7

2.1.1.Process Description (Process 2.0): .............................................................. 8




Process Description (Process 6.0): ..................................................................... 10

3.Input/output Specifications: ................................................................................... 10

Process 1: Login authorization ............................................................................... 10

Process 2: Hotel information: ................................................................................ 11

Process 3: Customer information: ......................................................................... 12

Process 4: Make reservation: ................................................................................. 13

Process 5: Payment: .............................................................................................. 14

Process 6: Generate report: ................................................................................... 154.Database Schema: ................................................................................................. 16

Data Structures & Algorithms ................................................................................ 16

Normalization: ....................................................................................................... 19

3.2.Relationship: .................................................................................................... 20

3.3.Data Items: ...................................................................................................... 21


3/40

5.System Navigation: ............................................................................................... 24

Navigation Map: .................................................................................................... 24

5.2.Site Map: ......................................................................................................... 25

Customer site: ................................................................................................... 25

6.Screen Designs: ..................................................................................................... 26

Screen Calls: .......................................................................................................... 26

Screen Design Specifications: ............................................................................... 27

Main Screen: ...................................................................................................... 27

Creation Screen ................................................................................................. 27

Login Screen ...................................................................................................... 27

Modification Screen: ........................................................................................... 27

Reports Screen: .................................................................................................. 28

Sample Screen Designs: ........................................................................................ 28

Home Page ............................................................................................................ 29

My Account: ........................................................................................................... 30

Create Login: ......................................................................................................... 31

Room Availability:.................................................................................................. 32

Create Reservation: ............................................................................................... 33

7.2.1.Confirmation Receipt: ................................................................................... 33

Confirmation: ......................................................................................................... 34Report Designs: ........................................................................................................ 35

Management Reports: ........................................................................................... 35

Staff Reports: ........................................................................................................ 35

Management Report Design: ................................................................................ 37

Staff Report Design: .............................................................................................. 37

Structure Specifications: ........................................................................................... 38

Subsystem Decomposition: .................................................................................. 38

PHP Backend: ..................................................................................................... 38

Database Wrapper: ........................................................................................... 38

Room Management Subsystem: ........................................................................ 38

Management Subsystem: .................................................................................. 38

Hardware/Software Mapping ............................................................................... 39

7.Conclusion: ............................................................................................................ 40


4/40

References: .............................................................................................................. 40

Table of Figures:Figure 1Relationship.................................................................................................20

Figure 2 Navigation Map...........................................................................................24

Figure 3 Screen Calls................................................................................................26

Figure 4Hardware / Software Mapping.....................................................................39


5/40

Executive Summary:The following document contains brief overview of the project with the purpose and scope of

the project. The main process taken from the context diagram is broken-down into sub processes

and each process is described in detail with the help of process description chart which also

contains simple English statements to know deeply about processes and dataflow. Input and

output Specifications is made to specify the dataflow. With the navigation map one can know the

flow of screen. The graphical user interface will allow the users to see all the data on screen and

modify the data in real time. A screen call is added to the document to give a clear picture of the

screen designs. Finally, several mock ups of user interfaces have been included to try to give the

reader an idea of what the final system may look like.

Introduction:

Overview:

The ASAP system is designed for customers to have a simple way to make online

reservations. Users will be able to see available rooms, make reservations, see the menu, and

see the latest promotions or specials. Managers will be able to see an overview of what

reservations have been booked, allow or deny rooms from being reserved. Staff will be able

to also see what reservations have been booked and make reservation entries for people who

call into the restaurant.

Purpose:

The primary focus of this system is reservation and room management, the foundation of

the hotel business. Customers of hotel will be given a way of creating reservations through

our system. There won't be any customer employee interaction until the customer checks into

their room. Involved in this process are the customers and employees.

Scope:

The hotel application to be designed will meet the following overall objectives:

Handle Guest Reservation Services and room allocation

Have a Billing Subsystem to handle all transactions


6/40


7/40

Then Customer gets an access to his account.

Else Enter correct password.

Ifcustomer makes a reservation.

Then gets a confirmation.

Else would you like to make a reservation

If Customer makes a payment.

Then he gets a Receipt.

Else enter your details.

Ifnew Customer creates a login.

Then gets an access.

Else create a login.

Ifstaff enters a correct user ID and password.

Than Access to customer information.

Else enter correct ID or password.

IfStaff requests for Report.

Than generate report.

Level 1 Process Description:

Process Description (Process 1.0):

Date: 17/09/08 Analyst: Sameera Madhani

Process: Process 1.0

Login Authorization

System: ASAP (Online Hotel

Reservation System)

Inputs: Customer Creates a Login

Staff Logs in.

Outputs: Customer gets access to reservation.

Staff gets Access.

Ifcustomer ID and Password is equal to customer details

Than customer gets access

Else Login Denied or New customer registration

IfStaff enters correct Username and Password

Than Staff gets login

Else Login Denied or Invalid Username or Password


8/40

2.1.1.Process Description (Process 2.0):



Hotel Information


Reservation System)

Inputs: Customer makes an enquiry about Hotel.Occupancy Report data is sent from generate report process.

Outputs: Customer gets Hotel information.

Hotel Information data is sent to make reservation process

IfCustomer makes enquiry about Hotel.

Than customer receives room information according to enquiry made by customer with the

help of Occupancy report and room availabilityand customer receives ID and Password

Else Sorry No Vacancy.




Customer Information


Reservation System)

Inputs: Staff request to view Customer Information Data.

2. New customer information is received from Reservation process.

Outputs: 1. Staff gets Customer Information.

2. Updated Customer Information data is sent to Customer record file.

Ifstaff requests customer informationThan staff can view customer information.

Else no process.

Ifreservation is confirmed.

Than Customer record file is updated.

Else data not sent to record file.


9/40




Make reservation


Reservation System)

Inputs: Customer makes reservation.

2. Room record database file sends in room information to the reservation

process.

Outputs:

1. Customer gets confirmation.

2. Updated room information is sent to room record file.

Ifroom availability is greater than room required.

Than customer gets confirmation.

Else Cancellation or Choose another room.

Ifroom reservation is confirmed.

Than updated information is sent to room record file.

Else not sent.




Payment process.


Reservation System)Inputs: 1. Customer initiates payment.

2. Payment Details

Outputs: Customer gets receipt.

Ifinitiated payment is equal to payment details

Than Accept payment.

Else reject payment.


10/40




Generate Report

System ASAP (Online Hotel

Reservation System)

Inputs: 1. Staff request to view room report.

2. Data from Customer record file is sent to generate report.

3. Data from room record file is sent to generate report

Outputs: 1. This process gives report to staff.

2. Updated report file sent to Customer record file

3. Sends in occupancy report to hotel information process.

Ifstaff request for report

Then send report to staff

Else send report to customer record file.

3. Input/output Specifications:

The following input and output specifications were developed to illustrate the input and

output of the system in an increasing level of detail.

Process 1: Login authorizationInput Description

Username

(Text Field)

Password

(password Field)

MIH Users Use this to enter their username and password

to access to the Online ordering System

Sign In

(Button - Submit)

Send the data above to server to check the login is available

or not

Help

(Button) This will Open a help file for users

Cancel

(Button)Cancel Login Process

Output Description


11/40

Help FileThis will include all the help users need to use this system

in alphabetical order

Error Message

(alert box)

If any error in connecting the database ,Wrong Login

details or the input of the page is empty, then this message

will display

Main WindowWhen login is successful This Window will open

Process 2: Hotel information:

Input Description

Hotel Name

(text box)

In this box the name of hotel will be store

Phone number(text box)

In this text box contact number of the hotel will give.

Star rating

(List box)

This list box will allow the star rating of the hotel.

Address

(Text box)

This text box will store the address of the hotel

City

(text box)In this text box the city of the hotel will be store

State

(text box)This will store in which state the hotel is located

Postcode

(text box)In this text box include the post code

Update

(button-update)This button will update all the information to system


12/40

Output Description

Updated customer window This will include the found customer details



Error Message/PageIf any error of the input or in the back-end process. The

error message or page shows what error

Process 3: Customer information:

Input Description

Customer First name

(Text Boxes)In this text box Customer first name will be stored.

Customer Surname

(Text box)In this text box Customer surname will be stored.

Street

(text box)In this text box Customer street address will be stored.

City

(Text box)In this text box Customer city will be stored.

State

(Text box)In this text box state where Customer living will be stored.

Post code

(Text box)In this text box include the post code

Phone number

(Text box)This will include customer contact number details

E-mail address

(Text box)This will include customer email id details

card Type

(selection box)

This will direct the customer to choose type of card.

Credit Card number

(Text box)This will include the customer card number

Expiry date

(Date Selection box)This will direct the customer to select the date

Submit

(Button)This will direct the customer to submit all details


13/40

Output Description

Updated customer details window This will include the show all the customer details to user

Help File

This will include all the help users need to use this system




Process 4: Make reservation:

Input Description

City

(text box)This will include customer city details

State

(text box)This will include customer state details

State

(text box)This will include customer state details.

Country

(text box)This will store the name of the country

Checked-in-date

(date/time selection box)

In this selection box selected check in date and time will be

store

Checked-out-date

(date/time selection box)

In this selection box selected check out date and time will

be store

Number of room

(number selection box)In this selection box selected number of beds will be store

Max room price

(price selection box)In this selection box selected price of the room will be store

Bed type

(list selection box)In this list selection box bed type list will be store

Smoking room

(list selection box)

In this selection box yes and no for smoking will be store

Cancellation reservation

(button)

This button will simply cancel the reservation made by the

customer with sending information to the system.

Output Description

Reservation confirmed window This will included the reservation details with reservation


14/40

confirmation details.

Cancellation reservation windowThis will included the reservation details with reservation

cancellation details.

Help File

This will include all the help users need to use this system




Process 5: Payment:

Input Descriptions

Total amount

(Price selection box)

This box will store total amount for reservation

Payment method

(List box of card)

This box will allow customer to select the method

of payment

Card number

(text box)

In this box credit card number of the customer will be

store

Name on Card

(text box)

The name on the card which is used to make reservation

will be store

Expiry date

(date /time box)In this box expiry date of the credit card will be store

Cancel(button)

Cancel payment Process

Pay confirm

(button)Confirm payment Process

Output Description

Payment confirmed and

successful window

This will include payment confirmation and payment

successful details will display

Payment cancelled window This will include cancellation of payment process and it

will display payment has been cancelled display






15/40

Process 6: Generate report:

Input Description

Display Occupancy Report

(Button)

This button will send request to system and will display

occupancy report of the hotel

Print report(Button)

This button will send request to the system and print therequested report

Updated report

(Button)

This will send information to the system to store the and

update data

Finance report

(Button)

This button will send request to the system for financial

report


16/40

Output Description

Occupancy Report window The occupancy report window be display on the request

after the button is pressed

Print successful windowThe print successful window will open if the report is

printed

Print error report window The print error window will open if the report is not printed

or any other problem

Updated report window The updated report window will be open if the report is

successfully update

Finance report window The finance report window will display if the system

received and find

4. Database Schema:

Data Structures & Algorithms

Our decision to implement the hotel reservation system using standard PC technology

and a commercial database product has narrowed our choices of implementation algorithms

and data structures. We have chosen to implement this system with the PC database program

MS Access that uses a relational data model. Basically what this means is that related data is

grouped together in what can be logically viewed as a columnar table of records. Each record

within a particular table is composed of a number of fields that hold the relevant information.

Each record can be uniquely described by one or more fields in the record. These fields

are referred to as the records primary key. Information is retrieved from the table by

specifying the records primary key. The entire system is made up of a number of tables, each

of which can be thought of as describing one logical entity. For example a table that has field

entries corresponding to the customers name, address and so on represents a customer.

Specifying the customers name, which is the primary key for the customer table, retrieves

information about each customer.

With this basic information in mind we have specified the required tables, their primary

keys and related field information below. Each table is laid out as a heading, followed by a


17/40

list of the fields that make up the table. The tables' primary keys are indicated with Blue

field names.


18/40

5.2.


19/40

Normalization:

Customer:

CustomerIDFirst

name

Last

nameAddress City State Country

Zip

codePhone/mobile Email CCNumber CCExp

Staff:

StaffID JobTitle Firstname

Lastname

Address City State Country Zipcode

Phone/mobile Email

Reservation:

Reservation

IDCustomer ID StaffID

CheckIn

Date

CheckOut

DateRoomNo TotalPrice

Reserved

DateCancellation

Room:

RoomNo RoomType

Room type:

RoomType RoomDesc RoomRent MaxGuestNo


20/40

3.2. Relationship:

Figure 1Relationship


21/40

3.3. Data Items:

1. Check in date

Month is numeric and between 1 and 12

Day is numeric and between 1 and 30 (or) 31

2. Check out date


Day is numeric and between 1 and 30 (or) 31

3. Type of reservation

Must be selected

Drop down menu

4. Home phone

Numeric, format depends on country

5. Work phone

Numeric, format depends on country

6. Email

Must contain an @

Must contain a . (Dot)

Must contain: com, net, org, biz, edu, or gov

7. Credit Card type

Must be selected

Drop down menu

8. Credit Card Number

Must be Numeric

Must be at least 16 digits long

9. Exp. Date


Year is numeric, four digits

10. State

Must be active or cancelled


22/40

Non-editable field

11. First name

Alpha-numeric

16 characters maximum

12. Last name

Alpha-numeric

16 characters maximum

13. User Name

Must be at least 6 characters

14. Password

Must be at least 6 characters


23/40


24/40

5. System Navigation:

Navigation Map:

Figure 2 Navigation Map


25/40

5.2. Site Map:

Customer site:

Web forms Purpose

Available Room The web page displays available room(s)

Cancel ReservationThe web page for look up and canceling a

reservation

Confirm Create AccountThe web page for confirmation of creating

a new account for the customer

Confirm Cancel ReservationThe web page for confirmation of

canceling the reservation

Confirm Update AccountThe web page for confirmation of updating

the customer account properties

Create New Account The web page for creating a new customeraccount

Customer Menu1 The user control for Customer menu

Default The default web page

Update AccountThe web page for updating the customer

properties

Find Room The web page for searching room(s)

Room ResultThe web page for displaying result of the

room searching

Reservation The web page for placing a reservation

Room PreferencesThe web page allows customers to select

their room preferences

Log In The web page for login to secure web sites

Log Out The web page for confirmation for logout


26/40

6. Screen Designs:

Screen Calls:

User Web server Screen

Call write screen

Return Screen Code

Call Handler

Return Pointer to next screen

Show Page

Send Form

Figure 3 Screen Calls


27/40

Screen Design Specifications:

The graphical user interface will allow the users to see all the data on screen and modify

the data in real time.

Main Screen:

The main screen will have buttons for creating a reservation, modifying a reservation,

and generating reports. The buttons will fill in the content pane located below the buttons

with the corresponding screen.

Creation Screen

There will be a creation screen which will have text boxes for the input of the check

in date, check out date, credit card number, first name, last name, home phone number,

work phone number, e-mail, and credit card expiration date. There will be drop down

boxes for the type of reservation and credit card type. The state of the reservation will be

a text field which is non-editable.

Login Screen

The login screen consists of two text fields and a button. The text fields are for the

user name and password input. The password characters will be of maximum 10

characters. The user can also register on this screen.

Modification Screen:

The modification screen will be identical to the creation screen except, the fields will

dynamically fill in based on the customers last name and date of check in. The data then

can be modified and saved using the update reservation button. The cancel reservation

button will change the state of the reservation and store the result in the reservation data

file.


28/40

Reports Screen:

The reports screen will have 3-5 buttons corresponding to the reports and employee

or manager can generate. When the button is pushed, the report will be sent to a printer

and displayed on screen.

Sample Screen Designs:

The customer has to enter the URLwww.moveinnhotel.com.au to take him to the system.
http://www.moveinnhotel.com.au/http://www.moveinnhotel.com.au/http://www.moveinnhotel.com.au/


29/40

Home Page

Title: Home

PageSection: Move Inn hotel reservation system

Date:

20-10-08Version

Interface Elements:

None

Graphics:

4 Category

images

Company Logo

Text:

Home Page

Search engine

4 Category list

Introduction ofsite

Audio:

None

Notes: This page displays Home Page of the site

Description: The page brief introduction of company 4 category search engine company logo

Source material: None

Interactions: Links to Home Page & Sub pages

To Do list: Connect pages with their categories search engine placement and various offers.

Navigation: All other pages of thee site


30/40

My Account:

Title: My A/C

PageSection: Move Inn hotel reservation system Customer A/C

Date:

20-10-08Version

Interface Elements:None

Graphics:

Company Logo

Links to all pag

Customer Login

Text:

Customer A/C

Search engine

4 Category list

Audio:None

Notes: This page displays Customer A/C

Description: The page brief introduction of company 4 category search engine company logo




Navigation: All other pages of the site


31/40

Create Login:

Title: create

loginSection: Move Inn hotel reservation system Create Customer Login

Date:

20-10-08Version

Interface Elements: No

Graphics:

Company Logo

Links to all pag

Create Login

Text:

Create Login A

Search engine

4 Category list

Audio:

None

Notes: This page displays Create Login

Description: The page brief introduction of company 4 category, search engine and company logo






32/40

Room Availability:

Title: View

room types

Section: Move Inn hotel reservation system Room type and

availability

Date:

20-10-08Version


Graphics:

Company Logo

Links to all pag

Display Room

Information.

Customer canselect room type.

Text:

Room availabili

Room details

Search engine

4 Category list

Audio:

None

Notes: This page displays types of room available

Description:The page brief introduction of company 4 category search engine company logo, allows

Customer to select room type for booking .






33/40

Create Reservation:

7.2.1. Confirmation Receipt:

Title: Make

reservationSection: Move Inn hotel Make Reservation

Date:

20-10-08Version


Graphics:

Company Logo

Links to all pag

Customer make

reservation.Text:

Room availabili

Room details.

Check In andcheckout date.

NO: of rooms

required.

Type of room

required

Search engine

4 Category list

Audio:

None

Notes: This page lets the user make reservation.

Description:The page brief introduction of company 4 category search engine company logo, allows

Customer to select room type, NO: of rooms, takes various information from user for bookin






34/40

Confirmation:

Title: Get

confirmationSection: Move Inn hotel Reservation details and confirmation

Date:

20-10-08Version


Graphics:

Company Logo

Links to all pag

System confirm

the reservation.Text:

Customer name

Room details.

Check In and

checkout date.

NO: of rooms

reserved.

Type of roomreserved.

Search engine

Audio:

None


Description:The page brief introduction of company 4 category search engine company logo, system get

confirmation from the customer for reservation made.





Title:confirmation

Section: Move Inn hotel Issue confirmation Date:20-10-08

Version


Graphics:

Company Logo

Links to all pag

System confirm

the reservation andissues receipt

Text:

Search engine

4 Category list.

Confirmation

Receipt.

Audio:None


Description: The page brief introduction of company 4 category search engine company logo, system get

confirmation from the customer and issues a receipt






35/40

Report Designs:

The Day-End run may be tailored to meet hotels requirements. It always includes:

Guest Ledger

Daily / Period Sales Analysis

Daily Terms / Occupancy

Daily Revenue Report

Postings Audit

Deposits Report

It could also optionally include:

Sales Ledger

Daily Business

Guest History

Tomorrow's Arrivals / Departures, etc.

Guest Lists

Managers Daily Report

Management Reports:

These reports include an expected occupancy, expected room income, incentive report.

Staff Reports:

These reports include a daily arrival and a daily occupancy report. Accommodation bills-

This is the bill that will be handed to the customer at check out. This bill includes: date

printed, guest name, room number, arrival date, departure date, number of nights, total

charge.


36/40


37/40

Management Report Design:

Staff Report Design:

Title: Staff

ReportSection: Move Inn hotel Staff Report

Date:

20-10-08Version


Graphics:

Company Logo

Links to all pag

Text:

Search engine

4 Category list.

Staff Login

Start date.

End Date.

Sales Commissi

report.

Audio:

None


Description:The page brief introduction of company 4 category search engine company logo, system

produces sales report to the Staff. Reports can be on a daily basis or weekly basis.






38/40

Structure Specifications:

Subsystem Decomposition:9.1.1. HTML Frontend:

The html frontend will be responsible for user interactions. The interface will be

intuitive for users so that minimal documentation will be required.

PHP Backend:

The PHP backend will be responsible for turning user commands from the interface

into database queries. PHP will also be used for error and consistency checking.

Database Wrapper:

The database wrapper will have direct interaction with the database functions. It will

allow adding, deleting, and editing data entries.

Room Management Subsystem:

The room management subsystem is responsible for adding available room to the

database. The subsystem will keep track of the maximum amount of people and the

availability of the table.

Management Subsystem:

The management subsystem will be responsible for all administrative tasks for the

Hotel. They will have full permissions to modify and delete items from the reservation,

rooms and other subsystems.


39/40

Hardware/Software Mapping

Both PHP and SQL are very versatile. Each service can run on one server or for better performance separate servers.

We plan on implementing a separate server approach so that the system is more responsive to the users. The web

server will run on a dedicated server while the database will be run on a separate more powerful server. The two

servers will be connected internally by fibre so the delay between servers becomes unrecognizable. If needed the server

configuration can be changed at any time with minimal downtime to the user

User

ComputerDatabase Server

Hotel

ComputerWeb server

PHP

Database

Wrapper

Database

Figure 4Hardware / Software Mapping


40/40

7. Conclusion:

The project has achieved the main objective of completing the system design specification.

The complete systems design was carried out which determined the prototype of the designs and

gave an insight on how to adapt and integrate ideas which produced the final prototype

application. Although the study highlighted MS Access as an adequate application platform, as

the research study progressed it became apparent that the combination of web based applications

have enhanced both upgrade-ability and the integration of a greater choice of software packages.

References:

Schmuller, J, SAMS Teach Yourself UML in 24 Hours, Sams Publishing, Indianapolis Indiana

1999.

Schach, Stephen R., Object-Oriented and Classical Software Engineering, 5th Ed., McGraw

Hill, 2002.

HyperDictionary (2003), [Online]. [Accessed 24th May 2005]. Available from World Wide

Web: http://www.hyperdictionary.com/

Powell, T. and Schnieder, F. The Complete Reference: JavaScript Second Edition, McGraw

Hill/Osborne, Emeryville California 2004. Bench-Capon, T., (2002) Third Year Honours Project Guidelines 2000-2001,

http://www.csc.liv.ac.uk/~tbc/projects/body.htm

Diaz, B. M., (2002) Student Projects - Diz's Resource Page,

http://www2.csc.liv.ac.uk/~diz/Projects/

Icon project, the, (2002) The Icon programming language,

http://www.cs.arizona.edu/icon/index.htm

Documents

Part 4 Sample 1