Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out
Your Federal Quarterly Tax Payments are due April 15th Get Help Now >>

COVER PAGE - Download as DOC

VIEWS: 76 PAGES: 46

									COVER PAGE
Project Team Information

Name                       Matriculation No   Email Contact

Goh Zhi Xiong Danny

Ko Hui Jun                 075018A06

Lai Huimin Lysia

Liu Jianxing

Ng Wee Yen Jonathan

Siew Zhihui                075263C06




                                                              Page 2
Table of Contents
1     Task & Role Allocation ......................................................................................... 5

2     Refined System Specifications ............................................................................ 6

3     Use Case Diagrams............................................................................................. 7

4     Activity Diagrams ............................................................................................... 11

    4.1       Registration Activity Diagram ............................................................................... 11

    4.2       Process Login Activity Diagram ........................................................................... 12

    4.3       Manage Profiles Activity Diagram ........................................................................ 13

    4.4       Make Bookings Activity Diagram.......................................................................... 14

    4.5       Book Facilities & Services Activity Diagram ......................................................... 15

    4.6       Manage Bookings Activity Diagram ..................................................................... 16

    4.7       Manage Policies Activity Diagram ........................................................................ 17

    4.8       Manage Rates Activity Diagram ........................................................................... 18

5     Analytical Model – Class Diagram ..................................................................... 19

6     Design Model – Sequence Diagrams ................................................................ 20

    6.1       Customer Registration Sequence Diagram .......................................................... 20

    6.2       Customer Login Sequence Diagram .................................................................... 21

    6.3       Customer Edit Profile Sequence Diagram............................................................ 22

    6.4       Quick Booking Sequence Diagram ...................................................................... 23

      6.4.1      Quick Booking (Alternate Flow 1) .................................................................................... 23

    6.5       Custom Booking Sequence Diagram ................................................................... 24

    6.6       View Bookings Sequence Diagram ...................................................................... 25

    6.7       Cancel Booking Sequence Diagram .................................................................... 26

      6.7.1      Cancel Booking (Alternate Flow 1) .................................................................................. 27

      6.7.2      Cancel Booking (Alternate Flow 2) .................................................................................. 27

    6.8       Book Facilities & Services Sequence Diagram .................................................... 28

      6.8.1      Book Facilities & Services (Alternate Flow 1) ................................................................. 29

      6.8.2      Book Facilities & Services (Alternate Flow 1.1) .............................................................. 30
                                                                                                                        Page 3
      6.8.3      Book Facilities & Services (Alternate Flow 2) ................................................................. 31

      6.8.4      Book Facilities & Services (Alternate Flow 2.1) .............................................................. 32

    6.9       Cancel Facilities & Services Sequence Diagram ................................................. 33

      6.9.1      Cancel Facilities & Services (Alternate Flow 1) .............................................................. 33

    6.10      Room Rates Sequence Diagram ......................................................................... 34

    6.11      Policy Sequence Diagram.................................................................................... 35

    6.12      Generate Report Sequence Diagram................................................................... 36

    6.13      Admin Login Sequence Diagram ......................................................................... 37

7     Testing ............................................................................................................... 38

    7.1       Black Box Testing ................................................................................................ 38

8     Discussion ......................................................................................................... 44

    8.1       Derivation and Refinement of Analytical and Design Models ............................... 44

      8.1.1      Deriving the class diagram .............................................................................................. 44

      8.1.2      Deriving the sequence diagram....................................................................................... 44

    8.2       User Interface Design .......................................................................................... 44

    8.3       Project Difficulties Encountered and Solutions applied ........................................ 45




                                                                                                                                   Page 4
1 Task & Role Allocation
*Module Development includes form design, module design, backend coding as well as testing.

Goh Zhi Xiong Danny

Role: Team Leader/ Programmer

Tasks: Develop Module for Quick Bookings, View Bookings, Cancel Bookings, Make Bookings and
overall System integration.

Ko Hui Jun

Role: Web Designer/ Database Administrator

Tasks: Develop Overall Web Design with matching colour schema and theme. Create and maintain
database.

Lai Huimin Lysia

Role: Programmer

Tasks: Develop Module for Login, Register Account, Upgrade Account and Edit Profile

Liu Jianxing

Role: Programmer/ Assistant Database Administrator

Tasks: Develop Module for Custom Bookings.

Ng Wee Yen Jonathan

Role: Programmer

Tasks: Develop Module for Add/Edit/Delete Rates and Add/Edit/Delete Policies.

Siew Zhihui

Role: Programmer

Tasks: Develop Module for Book a Service, Book a Facility, Cancel Booking of Service or Facility and
View Bookings of Service or Facility




                                                                                               Page 5
2 Refined System Specifications
The web based hotel room booking system allows customers of The Grand Quarts Hotel to
book hotel rooms.

To use the online system, customers have to be registered with the system. Unregistered
customers can only view the rates of hotel rooms, facilities and services, whereas registered
customers can also view and book rooms, facilities and services. During registration,
customers are to input their personal information and they can choose to be a corporate
customer by inputting a valid corporate ID. Customers can view and edit their profiles and
change their passwords. Public customers can also upgrade their account to corporate
under profile management.

For room reservations, customers can choose to make a quick reservation if they have no
preference on which specific room they would like to stay. To do so, they are only required to
input the check-in/check-out date, number of rooms and the room type preference. The
system will display the rooms that meet the criteria. Besides a quick reservation, customers
with more specific preferences can choose to select specific room(s). After inputting the
check-in/check-out dates, room type and region, customers are able to view the availability
of each specific room during the booking process. Additionally, customers can view their
own room bookings and can cancel their room bookings up to 3 days in advance.

Upon confirmation of a room reservation, customers have the choice to proceed to payment
or choose to request for hotel services and book facilities. Services provided by the hotel
include transportation to hotel and dining reservation. Hotel facilities include tennis courts
and Function Rooms. A customer has to make a room reservation before he/she can
request for a service. Facilities can be booked as long as it is available and if the customer
has registered with the hotel. During the facilities and services booking process, customers
can choose to cancel their current booking session and proceed to payment for the room
reservation (if any).

Administrators are allowed to add, edit and view basic rates and policies. Policies and
promotions will affect the basic rate for rooms for a specific period. However, rates for
facilities and services will not be affected by policies and promotions. Furthermore,
administrators are allowed to view sales reports, booking reports and statistic reports.
Reports can be generated using data records from all bookings.

An external credit card system is required to validate credit card information to facilitate
payment.




                                                                                            Page 6
3 Use Case Diagrams




                      Page 7
Identified Actors

Actors                          Role

Customer                        Uses the HRBS to make room reservations, book facilities,
                                and request for hotel services and register an account or
                                update their account information.

Administrator                   View, add and edit rates and policies. View reports

Credit Card System              External entity to validate credit card information

Database System                 Existing system to maintain reservations, room information,
                                rates, policies and customer/hotel employees‟ information.



Use Case Description

Register Account

Actors               Customer

Description          Customers need to register with the system before they can log on and
                     use the functions of the system. During registration, they are to input
                     their personal information. In addition, customer can choose to be a
                     corporate customer by inputting a valid corporate ID.

Assumption           N/A



Edit Profile

Actors               Customer

Description          Customers can view and edit their profiles. They can also change their
                     passwords.

Assumption           User has logged in



Make Bookings

Actors               Customer

Description          Customers are allowed to make room reservations and/or facilities and
                     services. Room reservations can either be a quick or an advance
                     customised bookings. Booking of facilities and services can be
                     followed immediately after room bookings. If customer did not reserve
                     any rooms, only facilities can be booked.

                                                                                      Page 8
Assumption          User has logged in.



Cancel Bookings

Actors              Customer

Description         Customers can cancel their bookings up to 3 days in advance.
                    However, if the customer cancels their booking after the 3 days period,
                    they will be still be charged for the booking while the rooms booked will
                    be freed.

Assumption          User has logged in.



Add/Edit Policies

Actors              Administrator

Description         Administrators are allowed to add and edit policies, promotions and
                    corporate policies that will affect the room rates for different periods.
                    Promotions and corporate policies can affect the basic rates of all
                    rooms during the specified period.

Assumption          User has logged in.



Add/Edit Rates

Actors              Administrator

Description         Administrators are allowed to add and edit basic rates for different
                    room types, facilities and services.

Assumption          User has logged in.



View Policies

Actors              Administrator

Description         Administrators are allowed to view period, promotions and corporate
                    policies.

Assumption          User has logged in.




                                                                                         Page 9
View Rates

Actors             Administrator

Description        Administrators are allowed to view the rates for different room types,
                   facilities and services.

Assumption         User has logged in.



View Reports

Actors             Administrator

Description        Administrators are allowed to view sales reports, booking reports and
                   statistic reports.

Assumption         User has logged in.



Validate Payment

Actors             Credit Card System

Description        The system is an external entity that validates credit card information
                   to facilitate payment

Assumption         Returns payment success/failure status.



Update Records

Actors             Database System

Description        The system is an existing system that stores and updates records of all
                   reservations, rates, policies, and customer/hotel employees‟
                   information.

Assumption         Database System is an existing system.




                                                                                    Page 10
4 Activity Diagrams
4.1 Registration Activity Diagram




                                    Page 11
4.2 Process Login Activity Diagram




                                     Page 12
4.3 Manage Profiles Activity Diagram




                                       Page 13
4.4 Make Bookings Activity Diagram




                                     Page 14
4.5 Book Facilities & Services Activity Diagram




                                                  Page 15
4.6 Manage Bookings Activity Diagram




                                       Page 16
4.7 Manage Policies Activity Diagram




                                       Page 17
4.8 Manage Rates Activity Diagram




                                    Page 18
5 Analytical Model – Class Diagram




                                     Page 19
6 Design Model – Sequence Diagrams
6.1 Customer Registration Sequence Diagram




                                             Page 20
6.2 Customer Login Sequence Diagram




                                      Page 21
6.3 Customer Edit Profile Sequence Diagram




                                             Page 22
6.4 Quick Booking Sequence Diagram




6.4.1 Quick Booking (Alternate Flow 1)
This is an alternate flow where no rooms are found hence a message is shown to the customer that
no rooms were found.




                                                                                         Page 23
6.5 Custom Booking Sequence Diagram




                                      Page 24
6.6 View Bookings Sequence Diagram




                                     Page 25
6.7 Cancel Booking Sequence Diagram




                                      Page 26
6.7.1 Cancel Booking (Alternate Flow 1)
This is an alternate flow of a booking cancellation that simply informs the customer that he is making
a cancellation that has passed the 3 days period.




6.7.2 Cancel Booking (Alternate Flow 2)
This is an alternate flow of a booking cancellation when the customer confirms and acknowledges
that the cancellation has passed the 3 days period. The booking will be cancelled once the customer
confirms.




                                                                                             Page 27
6.8 Book Facilities & Services Sequence Diagram




                                                  Page 28
6.8.1 Book Facilities & Services (Alternate Flow 1)




                                                      Page 29
6.8.2 Book Facilities & Services (Alternate Flow 1.1)




                                                        Page 30
6.8.3 Book Facilities & Services (Alternate Flow 2)




                                                      Page 31
6.8.4 Book Facilities & Services (Alternate Flow 2.1)




                                                        Page 32
6.9 Cancel Facilities & Services Sequence Diagram




6.9.1 Cancel Facilities & Services (Alternate Flow 1)




                                                        Page 33
6.10 Room Rates Sequence Diagram




                                   Page 34
6.11 Policy Sequence Diagram




                               Page 35
6.12 Generate Report Sequence Diagram




                                        Page 36
6.13 Admin Login Sequence Diagram




                                    Page 37
7 Testing
7.1 Black Box Testing
Test Function               Inputs                  Expected Output       Actual Output
Case
No.

1.   Valid Login            User ID:                Login successful
                            S8493729Y
                            Password: stic          Index page
                            Customer Type:          displayed
                            Corporate

     Invalid Login –        User ID:                Error message:
     Invalid Customer       S8493729Y               “Please ensure that
     Type                   Password: stic          User ID, Password
                            Customer Type:          and Customer Type
                            Public                  are correct”

     Invalid Login –        User ID: abcd           Error message:
     Invalid User ID        Password: abcd          “Please ensure that
     and/or password        Customer Type:          User ID, Password
                            Public /Corporate       and Customer Type
                                                    are correct”

     Invalid Login –        User ID: null           Pop up error
     Blank fields           Password: null          message: “Please
                            Customer Type:          enter User ID”
                            Public/Corporate        “Please enter
                                                    Password

2.   Valid Registration     All fields filled in.   Registration
                            If customer type is     successful
                            Public, Corporate
                            code field is blank,    Login Page
                            else if customer        displayed
                            type is Corporate,
                            valid Corporate
                            Code entered
                            (SAFRA2008)

     Invalid Registration   All fields filled in.   Error Message:
     – Invalid Customer     Customer Type:          “Invalid Customer
     Type                   Public                  Type”
                            Corporate Code:
                            SAFRA2008


                                                                                    Page 38
                            All fields filled in.   Error Message:
                            Customer Type:          “Invalid Customer
                            Corporate               Type”
                            Corporate Code: -
                            blank-

     Invalid Registration   All/Some                Pop up error
     – Compulsory           compulsory fields       message: “Please
     fields not filled in   (marked with *) not     ensure all fields
                            filled in               indicated with * are
                                                    filled”

3.   Valid Edit Profile –   Relevant fields         Profile edited
     No changing of         edited                  successfully
     password               Password fields
                            blank                   Index page
                                                    displayed

     Valid Edit Profile –   Relevant fields         Profile edited
     Change of              edited                  successfully
     password               Old Password:
                            correct old             Index page
                            password                displayed
                            New Password:
                            abcd
                            Confirm Password:
                            abcd

     Invalid Edit Profile   All/Some                Pop up error
     – No changing of       compulsory fields       message: “Please
     password               (marked with *) not     ensure all fields
                            filled in               indicated with * are
                                                    filled”

     Invalid Edit Profile   All compulsory          Error Message:
     – Change of            fields (marked with     “Please ensure old
     Password               *) filled in            password is correct”
     (incorrect old         Old Password:
     password)              1234 (incorrect)
                            New Password:
                            ****
                            Confirm Password:
                            ****

     Invalid Edit Profile   All compulsory          Pop up error
     – Change of            fields (marked with     message: “Please
     Password (New          *) filled in            ensure Confirm
     password and           Old password:           Password is the
     Confirm password       correct old             same as New
                                                                           Page 39
     does not match)        password             Password”
                            New Password:
                            1234
                            Confirm Password:
                            abcde

4.   Valid Quick            Select start date:   Display
     Booking                25 March 2008        Confirmation page.
                            Select end Date:
                            29 March 2008
                            No. of rooms: 1
                            Type: Presidential
                            Suite
     Valid Quick            No. of rooms: 3      Display
     Booking- at least      Type: null           Confirmation page.
     one field is not       Type: Presidential
                            Suite
     empty (when no. of
                            Type: null
     rooms is >1)

     Valid Quick            Promo code:          Display
     Booking- with          LABOURDAY            Confirmation
     promo code                                  page.(Price
                                                 amended 5%
                                                 rebate)

     Invalid Quick          Select start date:   Display Error
     Booking-End date       29 March 2008        Message
     is before start date   Select end Date:
                            25 March 2008


     Invalid Quick          Select start date:   Display Error
     Booking- Empty         null March 2008      Message
     field for dates        Select end Date:
                            null March 2008

     Invalid Quick          Type: null           Display Error
     Booking- Empty                              Message
     field room type
     (when no. of rooms
     is 1)

     Invalid Quick          No. of rooms: 3      Display Error
     Booking- Empty         Type: null           Message
     field room type        Type: null
                            Type: null
     (when no. of rooms
     is >1)

     Invalid Quick      Select start date:       Display Error
     Booking- rooms not 25 March 2008            Message(booking
                                                                      Page 40
     available              Select end Date:     not process)
                            29 March 2008
                            No. of rooms: 1
                            Type: Presidential
                            Suite
5.   Valid Quick            Select start date:   Display
     Booking                25 March 2008        Confirmation page.
                            Select end Date:
                            29 March 2008
                            No. of rooms: 1
                            Type: Presidential
                            Suite
     Valid Quick            No. of rooms: 3      Display
     Booking- at least      Type: null           Confirmation page.
     one field is not       Type: Presidential
                            Suite
     empty (when no. of
                            Type: null
     rooms is >1)

     Valid Quick            Promo code:          Display
     Booking- with          LABOURDAY            Confirmation
     promo code                                  page.(Price
                                                 amended 5%
                                                 rebate)

     Invalid Quick          Select start date:   Display Error
     Booking-End date       29 March 2008        Message
     is before start date   Select end Date:
                            25 March 2008


     Invalid Quick          Select start date:   Display Error
     Booking- Empty         null March 2008      Message
     field for dates        Select end Date:
                            null March 2008

     Invalid Quick          Type: null           Display Error
     Booking- Empty                              Message
     field room type
     (when no. of rooms
     is 1)

     Invalid Quick          No. of rooms: 3      Display Error
     Booking- Empty         Type: null           Message
     field room type        Type: null
                            Type: null
     (when no. of rooms
     is >1)

     Invalid Quick      Select start date:       Display Error
     Booking- rooms not 25 March 2008            Message(booking
     available          Select end Date:         not process)
                        29 March 2008
                                                                      Page 41
                             No. of rooms: 1
                             Type: Presidential
                             Suite
6.   Valid book              Transportation to   Display
     Services                hotel               Confirmation page
                             Flight No:SQ006
                             Arrival Date:
                             March 29 2008
                             Arrival time: 10.30
                             AM
                             Air Line: SQ
                             No. of Passengers:
                             6


     Invalid book            Transportation to     Display Error
     Services- empty         hotel                 Message
     fields                  Flight No: null
                             Arrival Date: null

                             Arrival time: null
                             Air Line: null
                             No. of Passengers:
                             null



7.   Valid book facilities   Tennis court          Display
                             No of courts: 1       Confirmation page
                             Date: 29 March
                             2008
                             Time: 1.30PM

                             Other Request*: A
                             few bottles of soft
                             drinks to be place
                             on the table beside
                             the court.

     Invalid book            Tennis court          Display Error
     facilities- Empty       No of courts: null    Message
     Fields                  Date: null
                             Time: null

8.   Valid Confirmation      Card holder Name:     Display Receipt
     Page                    John Doe              Page
                             Credit card Type:
                             American Express
                             Platinum

                                                                       Page 42
                     Credit card no:
                     9876 2589 5112
                     3321

Invalid              Card holder Name:      Display Error
Confirmation Page-   null                   Message
Empty Fields         Credit card Type:
                     null
                     Credit card no: null




                                                            Page 43
8 Discussion
8.1 Derivation and Refinement of Analytical and Design Models

8.1.1 Deriving the class diagram
We conducted interviews with the client for requirements of the system. Based on the
preliminary specifications, we identified the entities and their relationship that are within the
system. The HRBS is the main class of our system. As it is a web-based system, it is
composed of web user interfaces that contain all the necessary web-forms. In addition, a
database manager class is provided to handle all connections and queries to the existing
hotel database.

All web-forms encapsulate Java Servlets that handle all redirection and requests between
web pages throughout the application. Processes and flow of data between objects are
handled by their respective managers. This design is necessary to ensure that the logic flow
is isolated into one class so that when amendments are made; there will be minimum
modification of codes.

8.1.2 Deriving the sequence diagram
From the use case diagram, different modules of the system are identified.

For each module, the logical flow is thought out as detailed as possible using the activity
diagrams. The focus is on the objects‟ interaction in the system. The relations between these
objects and the processes defined in the use case diagram are clearly identified. The
sequence diagrams are refined as the process of coding out the module progresses.

In addition, alternate flows of sequence diagrams can help identify exceptional cases. This
helps the programmer „step through‟ the codes to facilitate the debugging process.

8.2 User Interface Design
Firstly, we have to identify our website viewers that we are targeting. For our hotel website,
the target audiences are the hotel potential customers. Hence in this website we should give
the viewers a welcoming and cozy feeling that can attract them to book rooms in our hotel.
Also, it should create an environment in which the user can accomplish tasks with a
minimum of anxiety, confusion, fatigue and boredom.

Research on various hotel websites was done to get a feeling of how the theme should look
like. After the research, the conclusion was that the design should be classy and easy to
view. The color themes used should not too colourful. The overall colour theme should not
have too many colors in one website. Other than that the font used should be readable. The
size should be big enough for general viewers to read. Besides, the content of the website
should be located at a very clear place. The layout of the page should be clear to viewer
such as where the content displaying is and where to navigate the website. Furthermore the
menu in the website should avoid having more than two submenus. Usually there is a global
menu at a place where viewers can easily navigate. Besides these, the website can have
some multimedia to interact with the viewers. Lastly, the most important factor of the user
interface has to make sure that the website layout is consistent.
                                                                                           Page 44
With all the information, a design template was designed for the overall website. 2 menus
were designed; one for global access and the other one is for customers who login to the
system. Both menus are implemented with Flash to have interaction with the customers and
to beautify the website. This allows the viewers to know which of the menu they are pointing.
Other thing that is implemented in Flash is the banner of the website. The banner shows the
outer view of the hotel we are helping to develop the website for. Furthermore, the colour
palette was decided to be purple and brown. This creates a royal feeling which suits the
hotel theme. Consistency was kept for the website by creating CSS which specify the color,
font and layout.

The global menu is at the top together with the banner. This is to let viewer differentiate that
with the side menu.

<printscreen>

The side menu is place at the left side after login is done.

<printscreen>

The content of the website is displayed at the right side.

<printscreen>

8.3 Project Difficulties Encountered and Solutions applied


JSP

The team had little to no prior experience in coding in JSP. The concept of using servlets
and JSP pages was foreign hence to speed up the learning process; we examined several
existing JSP applications. In addition, as we isolated the logic and the presentation layers by
adopting a Form-to-Manager approach, we reduced the confusion and complexity of the
project development. And by using the include JSP tags, the programmers need not worry
about most of the presentation format and need only focus on the logic flow of their modules
or at the very least need only design their forms.




The Hotel Business Flow

The entire team was not familiar with the Hotel Chain Industry and hence did not know
clearly what would be required in the system. Hence, the team did multiple case studies on
existing systems available on the web as well as conduct interviews with real hotel staff
management as well as customers.




                                                                                        Page 45
Integration

We decided on a modular development approach such that members would not crisscross
on each other‟s work. Commonly used functions would be developed by a single team
member while the entire team would discuss what this function would need to perform
leaving that single member to develop the specifics. For example, a function in the Date
Utility tool is required to accept in 2 dates and produce out the difference in days. The
function‟s job was discussed by the team. The assigned programmer would then develop
such a function out. Members would not be allowed to modify another member‟s codes.
Should there be a change in requirements this would be raised during a meeting.

With regards to design, the web designers created colour schema and common style sheet
that all members can use. This ensured that the website maintained a similar look and feel.

The system would be constantly integrated and updated weekly. Then the files would be
uploaded to Assembla where its version no. would be noted down. A date would be
appended to the files to show when it was modified. An alphabet would be included if more
than one modification was done on the same date.




                                                                                     Page 46

								
To top