M3 Document
M3 Document
Management Studies
School of Management,
IT and Governance
Information Systems and
Technology
(Westville Campus)
Page | 1
Table of Contents
Group details 3
Logical Models 6
Context-Level Diagram 6
Context-Level Narrative 6
Sitemap Diagram 11
Page | 2
Group No Group/ System Name
Page | 3
Aspect of Improvement to What was done to enhance Level of Success(High,
Front-End System(FES) this aspect of FES Moderate, Low)
1. Restricting age limit We set a maximum date of High
31/12/2004 on the calendar
control tool that allows users
to choose their date of birth.
Update booking:
The system was updated to
ensure that only available
rooms for the chosen booking
dates are displayed and picked
for a booking.
Page | 4
The available rooms are
displayed and selected using
and data grid.
Page | 5
Logical Models
Context Level Diagram
In this diagram, each user logs onto the system, and a confirmation is sent from the system
to the user.. The details of the customer are requested and then captured in the system once
received. The booking details from the customer are captured in the system. These booking details
for a customer are summarized, and an invoice detailing the room booked and payment due is issued.
Payment is made, and a receipt is issued to the customer to finalise the booking. When a customer
checks out, they rate the hotel according to their satisfaction and this is captured in the system.
The administrator checks in a customer upon their arrival to confirm a book is occupied. Once a
customer leaves, the administrator checks them out and the room details are updated from occupied
to available. The administrator adds any new rooms, or any new room details created. The
administrator also updates room details, the availability status, and other details such as any changes
to room pricing.
Page | 6
The manager requests a report on the performance of hotel such as the number of bookings received
and customer ratings of the hotel. In the case of a booking cancellation, a customer sends a
cancellation request. The manager is the only entity with the authority to cancel bookings, so this
request is forwarded to the manager. The manager finalises the cancellation process and the
confirmation of the booking cancellation is forwarded to the system. The customer receives a
notification confirming the booking cancellati
Page | 7
Page | 8
Level-0 Data Flow Diagram
When a customer requests a booking, the system will check current bookings to confirm room
availability. Upon confirming availability, the customer provides their personal details, these details
are stored and can be updated when necessary. Requirements the customer may have for the room
are also stored in the system, this process also includes determining how many beds per booking is
needed and if breakfast needs to be provided. The system finds a suitable room/s and stores the
other relevant information. An invoice is then sent to the customer with the amount due for the
room. When payment is finalised, the customer is issued to a receipt to finalise the booking. Staff
facilitate the check-in and check-out processes.
In the case of a booking being cancelled the manager is the only party who may process this. The
customer will send the hotel a cancellation request and the manager will process it. The cancellation
finalisation is then forwarded to the customer and updated on the system. Reports gather
information from rooms, customers, bookings to provide intuitive business insight
Page | 9
User stories:
-As a Customer/Admin I want to be able to check room availability so that I can view the rooms
available for my preferred dates.
-As a Customer/Admin I want to be able to add/delete/update user details so that the detail on the
system is always correct
-As a customer I want to be able to make a booking online instead of directly contacting personnel as
the hotel so that it is more convenient to make a booking
-As a customer I would like for the website to have a gallery so I can see what the hotel and its rooms
look like before I decide to make a booking
-As a customer I would like a help subsystem to guide me through the website to clear any ambiguity
-As a manager I would like intelligence reports, so I have insight into making better business
decisions
-As a customer I would like all the hotels contact information to be available to me in the event I
would have to contact the hotel.
-As a customer/admin I would like some form of password control to make sure only I can access my
personal profile
-As a customer I would like information about the surrounding area so I am aware of
activities/points of interests close by to the hotel if I decide to stay there.
Page | 10
Site map
Page | 11
Page description diagram (PDD)
View reservation
details
Sign up - Admin account Allows for an admin to create an Add admin details
account
Sign up - Customer Allows for customer create an New customer account
account.
Facilities Information of facilities available customer
at hotel
Local area Information of surrounding area customer
of hotel, including attractions,
notable sites.
Contact This displays all the relevant customer
contact details of Asoka Hotel
Page | 12
Website usability strategy
Website usability pertains to how a web application appears to users and how they interact
with it, as well as whether the experience is satisfactory. While it comes to web
development, there are numerous aspects to consider when designing a web app, including
screen size, quality, and accessibility. To deliver a pleasant experience to the end user, a
web app should ideally be created with as many of these principles in mind as possible, the
website design shows:
• User-Centric Security: Our commitment to safeguarding customer and admin data begins
with a user-centric approach.
Page | 13
• Access Control: To access the full range of services, including booking, users are required to
sign up or log in.
• Menu Browsing: While users can freely browse the menu without logging in, certain actions
like initiating the booking process are only accessible after completing the sign-up process
APPENDIX A
Page | 14
Page | 15
APPENDIX B
Page | 16
Page | 17