L5DC Project Documentation Contents KKKK

Research & Development of
Reserving System for

Empire Prestige Hotel
Using Web-Application
Name : KYAWT KAY KHAING KYAW

NCC NO : 00186527
Report Date :
1|Page
Table of Contents
2|Page
Abstract
The project is to make the Hotel Empire Prestige’s Booking system from paper work
system to computerized system by developing website. There will be 7 Parts to
develop the computerized system for the hotel. Firstly, the developers will need to
prepare project proposal to study the current system, history of the company,
estimated costs for the project and most importantly to create a project plan in order to
develop the system more accurately without having any errors in both website and
development system. In Part 1, there will be introduction about the project by
reviewing the background of the current business of the hotel and detailed explanation
about the proposed system. In Part 2, there will be a research and comparison
between 2 or 3 rival companies’ websites or application system flows and designs.
After Part 2 the feasibility study will undergo to decide the best methodology and
developing language for the project by explaining and comparing 2 or 3 usable
methodologies. Also, the programing languages that will use in the website will be
decide in this part by comparing them side by side. Those methodology and
programing languages research and decision will be doing under Part 3. The Part 4
will be the initial process of developing the website by deciding the target users,
Requirements for the program and risk managing. Part 5 is the actual developing
process of the website. It includes creating timeboxes, creating diagrams needed,
functional requirements, coding and testing. Part 6 is about the deployment of the
system. The conclusions and evaluation of the whole project will be done under part 7.
3|Page
Acknowledgement
4|Page
Project Proposal
5|Page
1. Project Proposal
1.1 Overview (200 to 400) words

The development of online technology these days makes a lot convenient for its users
which is why online reservation for hotel is easy and friendly to make. Nearly all of the hotel’s
important aspect is using reserving or booking system so, to stand at the top of among all
other competitors, latest technology of reserving system must be used on this system to get
positive comments and advantages than the competitors by also following the up-to-date
trends. To achieve the goals of this Hotel, the above technique must be effective. Being the
system is hotel reserving system so, reserving of the hotel’s rooms is the significant process
so the room reserving system of this hotel need to be dynamic and to maximize hotel
earnings, the process should be efficiently completed.
All of the dynamic, adaptable functions required to operate a hotel are included in the
hotel reservation system, along with operational connectivity between reservations, guest
history, reception, sales ledger, accounting, and modules’ reporting. It is the perfect solution
for efficiently managing resources with little effort or time spent in order to increase income. A
hotel reservation system is designed to help with the administration of bookings as well as the
evaluation of marketing and financial performance utilizing data from reports. This Empire
Prestige Hotel has an online reserving system for its customers to make a reserving of their
favorite hotel rooms.
1.2 Current Business History

Empire Prestige Hotel is established in 2001 and it got about 22 years of experience in
hotel industry. As the era is information technology era, the hotel management team decided
to have a website and since CEO of the company want to change the booking system
including data management system from paper work system to digital system, the
management team planned out to do hire the web developing team to develop the website.
Empire Prestige Hotel is located in River district, 1.1km from Asian Civilizations Museum
850 meters from Boat Quay and close to the Historical Bridge. Nearby Shopping Plaza able to
be reached by a few walks. Enjoyable outdoor area with swimming pool and fitness center
and steam baths.
All of the Hotel rooms are fitted with air conditioning and wi-fi as well as ironing and
laundry services and famous and modern brand of electronics are used for every room like
6|Page
kettle and fridges for mini-bar. Spa & Wellness center is also added for customers’ health with
additional fees and also Babysitting services for families.
Breakfast is served as a buffet for every single day and guests can enjoy other menu at
hotel’s Vivala Restaurant. The evening Roof top bar is made in Black & White Theme and a
lounge. Hotel is existed in busy area and famous Market Café are 525meters away and bus
stop is 200 meters away.
1.3 Current Business Process

Customer POV
1. Customer have to phone call to the hotel to book for a room.

2. Have to tell customer information such as name, phone, date of visit to the staff on
phone.
3. Initial Payment to the hotel by transferring money to the bank account.
Make a Phone call to book for room – customer have to call to the company reception
and ask for room types and prices.
Giving Customer Information – Customer must give to the receptionist about their
personal information needed to book room.
Initial Payment system – Customer have to transfer money to the hotel to confirm the
reservation.
Staff/Admin POV
1. Accept Phone call from customer and explain about what they ask.
2. Record Customer information on book.
3. Receive initial Payment from customer.
4. Record and Prepare Room.
Accept Phone call and explain – Receptionist of the hotel have to answer the customer’s
phone call and explain about the room type, facilities and requirements.
Record customer information – Receptionist have to record customer’s information

needed to book for room and also have to check the availability of the room.
Receive initial Payment – Receptionist have to give bank account number of the hotel to
receive initial payment from the customer to confirm a reservation.
7|Page
Record and Prepare Room – After interacting with the customer, the receptionist have to
check, record the given room and prepare the room.
8|Page
1.4 Current Business Issues (Manual System Issues)
1.4.1 Information Error
During manual pauperized system booking process, there can be lack of information or
misunderstanding between Staffs and customers when communication on phone call.
Information Error like duplicated information or lack of information can leads to bigger problem
between hotel and customers.
1.4.2 Misunderstanding
Misunderstanding between Receptionists and Customers is the most common issues on
phone call manual booking system such as customer misunderstand the information about
Single Room and Deluxe Room can leads to financial issues.
1.4.3 Lengthy Booking Duration
Once the whole booking process is made on phone call, the duration of explaining room
information and recording information process will take longer time.
1.4.4 Cost More Money
For Customer POV, since they have to call to the hotel and the duration is taking longer,
they will cost more money on telephone services. And as for Hotel POV, the management
team have to hire more Staffs in Reception department to cover the time to service both on
phone and walk-in customers.
1.4.5 Discount Point System
The hotel can’t make point system discount campaign since the hotel can’t track the
purchase of the customer.
9|Page
1.5 Proposed System Scope
The Booking System plays one of the most important roles in hotel industry. Nowadays,
there are many websites or applications that compares hotels and resorts about their
websites, services and costs to make more convenience for the first coming visitors so the
Empire Prestige hotel’s website should have good usability with simple looks which can also
explain the room types and information within one click with pictures.
1.5.1 Registration Process

Before the customers books for the room, they should have to create an account in
order to let the hotel management team to track customer information on booking
process and as for the customers, they only have to give their personal information
once in registration process which can reduce the time waste on filling forms. But they
can still look around the website and check the hotel situation without creating
account.
1.5.2 Availability and Record Room Process
The website booking process will be connected with the database of the hotel which
will record the amount of room left for certain type of room and due to the availability,
the activeness of the type of room in the website will change. Also once the booking is
placed, the whole booking process will be saved in data base including customer
account.
1.5.3 Digital Slip Process
Once the booking process is completed, a digital slip that includes all information
about reservation will be delivered which is printable.
1.5.4 Information Process
The website will include many information like Phone, Picture, E-mail and address of
the hotel in the design or will be with certain page.
10 | P a g e
1.6 Aims and Objectives
1.5.1 Aims
The Main Aim of the project is to make change the current paper work manual booking
system to computerized online booking system including data storing and also due to IT era 5-
star hotel like Empire Prestige a fancy website to attract visitor is a must. Also, the current
manual system costs the hotel a lot more than using computerized system.
1.5.2 Objectives
Analysis (Total: 20days)
- Analysis of the current system (3 days)

- Research and analyze the proposed system and requirements (10 days)
- Researching and calculating Methodologies, Programing Languages, hardware and
software (12 days)
Analysis Deliverable – After Analysis process, there will be project proposal report including
the research about current and proposed system and there will also be a report of comparing
similar business systems and feasibility studies.
Design (Total: 25 days)
- Researching and deciding the business’s functional and non-functional requirements

(15days)
- Creating Timebox plan (5 days)
- Arranging and managing Risks and project plans (5 days)
Design Deliverable – low level design, time box plan and required diagrams will be produced
after Design Objective.
Implementation (75 days)
- Developing Website (40 days)

- Usability testing (10 days)
- Functional testing (10 days)
- Solving Errors and retest (15 days)
11 | P a g e
Implementation Deliverable – Website Coding and Testing process will be produced in
Implementation process.
Evaluation (20 days)
- Evaluation of the proposed system with similar system (5 days)

- Evaluation of the whole project (15 days)
Evaluation Deliverable – Reports of evaluating the whole project.
1.7 Estimate Cost and Duration

1.7.1 Hardware Cost
No Item Description Unit Price Quantity Sub-Total
1 Desktop Computer To develop and host $ 2460 2 $4920

with license (Core i7 website
(10th generation))
2 Printer To print out digital slip $350 1 $350
Total Hardware Cost $5270
1.7.2 Software Cost
1 Window 10 OS Window 10 Operating $109 2 $218
12 | P a g e
system to run PC
2 Antivirus Window Defender to $5.5 2 $11

protect pc from virus
3 Browser Chrome, Firefox (Free) $0 0 $0
4 Office Software Office 365 to make $100 2 $200

reports
Total Software Cost $429
1.7.3 Development Cost
1 Web Development Cost Language: $6000 - $6000

PHP
Database:
MYSQL
2 Hosting Cost Host Gator $90 per - $90
month
3 Domain Name Registration “.com” $30 - $30
Total Development Cost $6120
13 | P a g e
1.7.4 Summary Cost
Category Cost
Software $429
Hardware $5270
Development $6120
Total $11819
14 | P a g e
1.8 Project Plan (Gantt chart)
Fig (1) Project Proposal
???
15 | P a g e
Chapter-1
Introduction
16 | P a g e
1. Chapter – 1 Introduction
1.1 Background of the Current System

The hotel Empire Prestige is established since 2001 so all of the hotel staffs and
management team have over 20 years old experiences. Although the hotel is worked
for 20 years, the buildings of the hotel is renovated in 2022 so it is like brand-new
hotel. The booking and data storing process of the hotel is currently on manual mode
of recording on spreadsheet. The current process can have issues like wasting more
time, more money and more energy. So, the management team decided to have a
computerized booking system for the company.
17 | P a g e
1.2 SWOT Analysis (Current System)
Strengths
The Payment system is more secure since they use cash down and bank transfer method
directly to the account. Also, the questions that customer ask can get immediate response
since it is directly phone call system.
Weaknesses
The information sharing system can have errors and the security of the customer’s personal
information can get leaked due to the booking recording system is directly write down to the
spread sheet. Also paper work spread sheets takes a lot of space to store data and
information.
Opportunities
The
Threats
- XXXXXXXXXXXXXXXXXXXXXXXXXXX
- XXXXXXXXXXXXXXXXXXXXXXXXXX
- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
- XXXXXXXXXXXXXXXXXXXXXXXXXXXX
18 | P a g e
1.3 Proposed System Scope
In hotel industry, there are 2 types of customers approaching to the hotel, the first one
is walk-in process which is very simple to accept or reject due to availability of room.
The second one is pre book for a room by contacting to the hotel for about 1 or 2 days
and in some situation a month ahead. Since management team decided to have a
website and computerized booking system, the proposed project will be creating a
simple and attractive website including booking system. In proposed system, there will
be Registration Process, Room Record Process, Digital slip and information sharing
about hotel process.
1.4 Aims & Objectives of the Project

Aims
The Main Aim of the project is to make change the current paper work manual booking
system to computerized online booking system including data storing and also due to IT era 5-
star hotel like Empire Prestige a fancy website to attract visitor is a must. Also, the current
manual system costs the hotel a lot more than using computerized system.
Objectives
Analysis (Total: 20days)
- Analysis of the current system (3 days)

- Research and analyze the proposed system and requirements (10 days)
- Researching and calculating Methodologies, Programing Languages, hardware and
software (12 days)
Analysis Deliverable – After Analysis process, there will be project proposal report including
the research about current and proposed system and there will also be a report of comparing
similar business systems and feasibility studies.
Design (Total: 25 days)
- Researching and deciding the business’s functional and non-functional requirements

(15days)
- Creating Timebox plan (5 days)
- Arranging and managing Risks and project plans (5 days)
Design Deliverable – low level design, time box plan and required diagrams will be produced
after Design Objective.
19 | P a g e
Implementation (75 days)
- Developing Website (40 days)

- Usability testing (10 days)
- Functional testing (10 days)
- Solving Errors and retest (15 days)
Implementation Deliverable – Website Coding and Testing process will be produced in

Implementation process.
Evaluation (20 days)
- Evaluation of the proposed system with similar system (5 days)

- Evaluation of the whole project (15 days)
Evaluation Deliverable – Reports of evaluating the whole project.
20 | P a g e
1.5 Short overview of the remaining chapters
Summary of remaining chapters are in chapter 2 there will be comparison between two
similar industries’ websites. In chapter 3, there will be feasibility study of
methodologies, programing languages and Databases. The chapter 4 is the deciding
part of functional and non-functional using MOSCOW prioritization, timebox strategy
and risks management. In chapter 5 there will be exploration engineering process
which the main developing process is produced. The coding, testing and solving error
process will be done under this chapter. Chapter 6 is the data migration process and
also deliver deployment diagram of the project. Chapter 7 is the final conclusion and
evaluation part of the whole project.
21 | P a g e
Chapter-2
Similar Product Comparison
(Investigation)
22 | P a g e
2. Chapter-2 Similar Product Comparison
2.1 Similar Product Introduction

Intro & explain & Screenshot
Unlimited Channel Website
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXX
Fig (1) UC home page design
23 | P a g e
M9 E-Store Website
XXXXXXXXXXXXXXXXXXXXXXXX
Fig (2) M9 home page design
24 | P a g e
2.2 Functional Comparison
(1) Customer Registration
Shop.com
Fig (1) Customer Signup Form from Shop.com (__)
XXXXXXXXXXXXXXXXXXXXXXXXX
25 | P a g e
City Mall
Fig (2) Customer Signup Form from City Mall
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
26 | P a g e
2.3 Non-Functional Comparison
10 Usability Heuristics
1. Visibility of System Status

Explain??????????????????
Shop.com
Fig (1)??? Explain………………
CityMall
Fig (2)??? Explain………………
27 | P a g e
1. Functional Comparison Evaluation
No Function Shop.com City Mall
1 Customer Registration 12345 12345
Functional Comparison Summary
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.
28 | P a g e
2. Non-Functional Comparison Evaluation
No Function Shop.com City Mall
1 Visibility of System Status 12345 12345
10
Non-Functional Comparison Summary
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.
29 | P a g e
Chapter-3
Feasibility Study
30 | P a g e
3. Chapter-3 Feasibility Study
3.1 Technical Feasibility

A technical feasibility study is an excellent tool for problem solving and long-term planning.
It can be used as a flow chart showing how goods and services are developed and moved to
the company to really reach the market. Technical feasibility is to access the system technical
difficulty and usually requires analyzing whether an expert system can be used with the
implementation of state-of-the-art techniques and tools. For expert systems, Analyzing the
shell in which the system will be produced is an important part of technical feasibility. The
shell used to create an expert system can greatly affect its quality. It is critical to the success
of the system. A system shell of a desirable professional should be flexible enough to involve
skilled reasoning even though it can vary depending on task and domain requirements. It
should also be easy to connect with current computer system. Additionally, User-friendly
design shell makes user use the system frequently.
3.1.1 Methodologies
A. Definition
DSDM (Agile)
DSDM is an agile project management framework used for software development and
business projects. It emphasizes collaboration, iterative development, and the delivery of
working software in short timeframes which is commonly known as iterations. This framework
is based on eight principles, including active user involvement, frequent delivery of working
software, and prioritization of requirements based on business value. It also provides a set of
roles and responsibilities for team members, including the project manager, business sponsor,
and technical coordinator. DSDM is a vendor-agnostic approach that focuses on making
individuals more collaborative to effectively achieve business goals. It is also available for any
project in any industrial and technical environment
SSADM
SSADM is a linear, phased methodology that emphasizes a structured approach to systems
analysis and design. It is suitable for large, complex projects where a comprehensive
understanding of the system requirements is critical. The development flow of SSADM
gradually changes, starting from early stages such as analysis and research going step by
step until final testing and customer evaluation. By doing this, project management becomes
more manageable and the techniques comes to be more efficient for developing a system with
specific requirements
B. Strength and Weakness of each Methodology

Strength of DSDM
31 | P a g e
 XXX
 XXX
 XXX
Weakness of DSDM
 XXX
 XXX
 XXX
Strength of SSADM
 XXX
 XXX
 XXX
Weakness of SSADM
 XXX
 XXX
 XXX
C. Comparison of Methodology
Criteria DSDM SSADM
Timeline
Size
D. Recommendation for Methodology

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
32 | P a g e
33 | P a g e
3.1.2 Programming Languages
A. Definition
PHP
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (__).
ASP.NET VS C# VS Python VS JSP (Java)

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (__).
B. Strength and Weakness of each Programming Languages

Strength of PHP
 XXX
 XXX
 XXX
Weakness of PHP
 XXX
 XXX
 XXX
Strength of ASP.NET
 XXX
 XXX
 XXX
Weakness of ASP.NET
 XXX
 XXX
 XXX
34 | P a g e
C. Comparison of Programming Languages
Criteria PHP ASP.NET
D. Recommendation for Programming Language

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
35 | P a g e
3.1.3 Databases
A. Definition
MYSQL
Microsoft SQL Server VS Access VS PostgreSQL VS Oracle
B. Strength and Weakness of each Databases
C. Comparison of Databases
Criteria
D. Recommendation for Programming Language
36 | P a g e
3.2 DSDM Feasibility (DSDM eight principles)
Principle 1 – Focus on the business need
The developer team have to discuss with management team of the hotel and decide functions
by using MoSCoW prioritization to meet the main objective of the hotel needs.
Principle 2 – Deliver on time
The developer team should create time box plan and project plan Gantt Chart in order to
deliver the project on time to the customers.
Principle 3 – Collaborate
The developer team and hotel management team should collaborate in order to develop the
project less error and more efficient.
Principle 4 – Never Compromise Quality
The developer team should decide the quality of the website in the start of the project by
sitting meeting with the management team of the hotel to set a default quality by deciding the
required functions with MoSCoW prioritization method and planning time box strategy.
Principle 5 – Build Incrementally from firm foundations
The project developing team should work together step by step from the start by researching
and analyzing the project scope to carry out the project with full efficiency.
Principle 6 – Develop iteratively
The Developer team have to take the users’ and testers’ feed back about the website and
improve the project iteratively in order to have satisfactory output of the project.\
Principle 7 – Communicate continuously and clearly
The members of project development team should have good communication with one
another in order to deliver the project more efficiently with less error and fault. The members
should sit meeting at least once a week to discuss the problems and difficulties they are facing
with their parts.
Principle 8 – Demonstrate Control
In this stage, the team leader of both development team management team should monitor
the members to carry out their task correctly in time by using the work flow of time-box
approach.
37 | P a g e
3.3 Possible LESPI (Legal, Ethical, Social and Professional) Issues
Legal Issues
(a) XXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXX
(b) XXXXXXX
(c) XXXXXXX
38 | P a g e
Ethical Issues
(d) XXXXXXX
(e) XXXXXXX
(f) XXXXXXX
39 | P a g e
Social Issues
(g) XXXXXXX
(h) XXXXXXX
(i) XXXXXXX
40 | P a g e
Professional Issues (BCS Code of Conduct)
(j) XXXXXXX
(k) XXXXXXX
(l) XXXXXXX
41 | P a g e
Chapter-4
Foundations
42 | P a g e
4.1 Target User
In business, choosing target user is very important to advertise or attract customer to buy the
company’s product. It is the process to attract the certain type of customer who will surely buy
the company’s product. For the website of Empire Prestige hotel, The Main Target user will be
including both customers and admin of the hotel.
Type of User Age Computer skill / IT Language skill

Literacy (Especially English
skill)
Customer 18-70 Basic Lower Intermediate
Managers/ Admin 20-50 Advanced Upper Intermediate
Receptionist/ Admin 20-35 Basic Lower Intermediate
Customer Support/ Admin 20-35 Advance Upper Intermediate
43 | P a g e
4.2 Functional Requirement
TIMEBOX 1
1.1 Manage Accounts (High level)
 Register New Staff Account(Middle Level)

o Register Staff ID (Low level)
o Register Staff Name (Low level)
o Register Staff Email (Low Level)
o Register Staff Password (Low Level)
o Register Staff Address (Low level)
o Register Staff Phone Number (Low Level)
 Update Staff Account Info (Middle Level)
o Update Staff Name (Low level)
o Update Staff Email (Low Level)
o Update Staff Password (Low Level)
o Update Staff Address (Low level)
o Update Staff Phone Number (Low Level)
 Delete Staff Account (Middle Level)
 Delete Customer Account (Middle Level)
 Login (Middle Level)
o Check Staff Account Credentials (Low level)
2. Manage Rooms Availability (High level)
 Create New Hotel Room (Middle Level)

o Register Room ID (Low level)
o Register Room Category (Low Level)
o Register Availability (Low Level)
o Input Description (Low Level)
o Upload Image (Low Level)
o Register Price (Low Level)
 Update Room (Middle Level)
o Register Room Category (Low Level)
o Register Availability (Low Level)
o Input Description (Low Level)
o Upload Image (Low Level)
o Register Price (Low Level)
 Delete Hotel Room (Middle Level)
 View Room (Middle Level)
3. Manage Room Category (High level)
 Create Room Category (Middle Level)

o Register Room Category ID (Low level)
o Register Category Name (Low level)
 Update Category (Middle Level)
44 | P a g e
o Check Room Category Name and Update (Low level)
 Delete RoomCategory (Middle Level)
 Display RoomCategory (Middle Level)
4. Manage Booking Process (High Level)
 View Bookings (Middle Level)

 Cancel Booking (Middle Level)
o Check Booking Availability and Cancel (Low level)
TIMEBOX 2
1. Manage Customer Account (High level)

 Register Customer Account (Middle Level)
o Register Customer ID (Low level)
o Register User Name (Low level)
o Register Email (Low level)
o Register Password (Low Level)
o Register Phone (Low Level)
o Register Address (Low Level)
 Update Customer (Middle Level)
o Update User Name (Low level)
o Update Email (Low level)
o Update Password (Low Level)
o Update Phone (Low Level)
o Update Address (Low Level)
 Delete Customer Account (Middle Level)
 Customer Login (Middle Level)
o Check Customer Account Credentials (Low level)
1.2 Process Booking (High level)
 Record Booking (Middle Level)
 Record Booking ID (Low level)

 Record Date (Low level)
 Record Total Occupancy (Low level)
 Record Check in Time (Low Level)
 Record Check out Time (Low Level)
 Record Payment Type (Low Level)
 Record Card Number (Low Level)
 Record Security Number (Low Level)
 Record Month (Low Level)
 Record Year (Low Level)
Update Booking (Middle Level)
45 | P a g e
 Update Date (Low level)
 Update Total Occupancy (Low level)
 Update Check in Time (Low Level)
 Update Check out Time (Low Level)
 Update Payment Type (Low Level)
 Update Card Number (Low Level)
 Update Security Number (Low Level)
 Cancel Booking (Middle Level)
 View Booking (Middle Level)
46 | P a g e
4.3 MOSCOW Prioritization
Must
Must Justification
Manage Account The function like Manage Account, Room Availability,

Room Category and Booking Process must be include in
Manage Room Availability
the program to meet the company’s requirement of
Manage Room Category computerized booking process. Since those functions are
the main function of the project, they are justified in Must
Manage Booking Process
Prioritization.
Should
Should Justification
Update Booking The function like Update Booking, Cancel Booking and
View Booking are not highly necessary in the program to
Cancel Booking
include because of the admin staff can do adjustment of the
View Booking booking on the must prioritized functions. So, the following
functions will be justified in Should Prioritization.
47 | P a g e
4.4 Non-Functional Requirements (4)
1. Usability – Usability means the product is very simple and easy for the
customers to use. Having a good usability is one of the key requirements to
develop an application or website because of the user’s education level can
be varies according to their experiences.
2. Security – The security is very important for the programs that work with
the user’s personal data and information. Since the website is working via
internet, the developers should have security features like encrypting
passwords in the program.
3. Performance- The performance of the website like response time of

process should be flexible to reduce time wasting.
4. Interface – The project like booking systems have 2 parts of interfaces like
Customer POV and Admin POV. The interface of the program can be varies
according to the users’ role. For example, customer book for a room and
admin check availability and records the room.
48 | P a g e
4.5 Time box Plan
Time box 1: User Account Registration and Modification
Time box Name User Account Registration and Modification

Start Date 16 January 2023
End Date 7 February 2023
Task Duration Start Date End Date
Functional Requirement 1 day January 16, 2023 January 16, 2023
Use Case Diagram 1 day January 17, 2023 January 17, 2023
Class Diagram 1 days January 19, 2023 January 19, 2023
Sequence Diagram 1 days January 20, 2023 January 20, 2023
High Level & Low-Level 1 days January 18, 2023 January 18, 2023
Prototype
Coding 9 days January 23, 2023 February 2, 2023
Functional Testing 1 days February 3, 2023 February 3, 2023
Usability Testing 1 days February 6, 2023 February 6, 2023
Time Box Summary 1 day February 7, 2023 February 7, 2023
Key Deliverables (Output)
Design
 Use Case Diagram for Purchase Process
 Functional requirement of Booking process
 Sequence Diagram of Booking process
 High level and low-level prototype of Booking process
Coding
 Admin register, login, delete, update and search page
 Room register, update, delete and search page
Testing
 Unit Test Document
49 | P a g e
Time box 2: Booking Process
Time box Name Booking Process

Start Date 16 January 2023
End Date 2 March 2023
Task Duration Start Date End Date
Functional Requirement 1 day February 8, 2023 February 8, 2023
Use Case Diagram 1 day February 9, 2023 February 9, 2023
Class Diagram 1 days February 13, 2023 February 13, 2023
Sequence Diagram 1 days February 14, 2023 February 14, 2023
High Level & Low-Level 1 days February 10, 2023 February 10, 2023
Prototype
Coding 9 days February 15, 2023 February 27, 2023
Functional Testing 1 days February 28, 2023 February 28, 2023
Usability Testing 1 days March 1,2023 March 1,2023
Time Box Summary 1 day March 2,2023 March 2,2023
Key Deliverables (Output)
Design
 Use Case Diagram
 Functional requirement
 Sequence Diagram
 High level and low-level prototype
Coding
 Customer register, login, delete, update and search page
 Booking register, update, delete and display page
Testing
 Unit Test Document
50 | P a g e
4.6 Risk Management
Risk
When developing a project, risk is a must for the development team to face. The risk or issues
of the projects can be varying according to the type of projects.
Risk Management
Before working on project, the development team should discuss about the possible risks they
can face during the development and prepare to solve the problems occurs to lessen the
damage to the project.
4.6.1 Identification of Possible Risks (10-12)
Technical Risk
 Virus Detect
Nowadays of IT era, Virus and malware are common technical risk which can harm both
program and hardware of the project. This can cause leaking of the important secret data,
lost important data and authentication brokage which can lead the company and
development team to face with Legal problems.
 Device Lost/ Destroyed
Devices Lost or Destroyed can be happen in some case of emergency situation or the
user fault of carelessness. This can lead the project to delay and cost more money to repair
or to sub with new device.
 Error Detect and Project Late
Error Detection is the most common risk on developing a new program. This can lead to
project delaying and in some cases that can lack in important functions to include in the
program.
 Security Risk
There are many types of security risks that can occur on developing a project such as
leakage of data, broken authentication and stolen devices. This can cause the project to
delay, cost more and also can lead to face legal issues.
 Outsourcing Risk
 FR NFR Requirements Risk

Req Changes
51 | P a g e
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXX
4.6.2 Risk Matrix (High-Medium-Low)
Risk Probability Impact Proactive Reactive Risk

Action Action Owner
Not enough Medium Medium Learn about Discuss with

experience business supervisor
process and about project
discussion
with the user
Virus
Detect
4.6.3 Critical Success Factors for current project
Top management support
52 | P a g e
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.
53 | P a g e
The Whole System Use Case & Class
54 | P a g e
Chapter-5
Exploration & Engineering
55 | P a g e
5.1 Time-box 1: Manage Purchase Time-box Development
Project Plan for Time Box 1
5.1.1 Functional Requirements List
Manage Purchase Process Timebox (1)
1.1 Manage Staff (HL)

 Register Staff (ML)
Email already exist check (LL)
Password Length check (LL)
 Update Staff
 Delete Staff
 Search Staff
 Staff Login
1.2 Manage Supplier
 Register Supplier
 Update Supplier
 Delete Supplier
 Search Supplier
1.3 Manage Brand
 Register Brand
 Update Brand
 Delete Brand
 Search Brand
1.4 Manage Category
 Register Category
 Update Category
 Delete Category
 Search Category
1.5 Manage Product
 Register Product
 Update Product
 Delete Product
56 | P a g e
 Search Product
1.6 Manage Purchase
 Record Purchase
 Confirm Purchase
 Search & Report Purchase
5.1.2 Use Case Diagram
Use Case Description
Use Case Name Record Customer
Actor Receptionist
Flow of Event Fill the customer details in the customer form. Register button is
clicked.
57 | P a g e
For remaining, see Appendix.
5.1.3 Screen Design
1) Customer Register Form
Fig (1) Low Level Prototype for Customer Registration
Fig (2) High Level Prototype for Customer Registration
58 | P a g e
5.1.4 Iteration for Screen Design
Iteration 1
Users tell that table form and room form design are needed to change. So, table style
combo box is added in table entry form and room size combo box and Facility text box is also
added in room form.
(Iteration 1) Screen Design for Customer Register Form
Before
After
59 | P a g e
5.1.5 Class Diagram
Initial Class Diagram
60 | P a g e
Detailed Class Diagram
Detail Class Definitions
Class Name Customer
Attributes Customer ID, Customer Name, Phone No, Address, Email, Member Type
Operation Register (),Cancel (), AutoID(), Checkdata()
Description << The Customer class is used to do register for customers who booked.>>
For remaining, see Appendix.
61 | P a g e
5.1.6 Sequence Diagram for Booking Process
Sequence Diagram Description
XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
62 | P a g e
5.1.7 Functional Testing
Test Plan
Module 1: Customer Entry
Test Script Description Date Tester
1.1 Test customer Name text 17- August- 2021 Shain Thu
box can be null or not
1.2 Test Customer Phone no text 7- August- 2018 Kyal Sin Linn
box
1.3 Test Customer Address text 7- August- 2018 Kyal Sin Linn
box
1.4 Test the ‘@’ in the E mail 7- August- 2018 Kyal Sin Linn
1.5 Test Customer Email text 7- August- 2018 Kyal Sin Linn
box
1.6 Test Register Button 7- August- 2018 Kyal Sin Linn
Module 2: Supplier Entry
Test Script Description Date Tester
1.1 Test customer Name text 7- August- 2018 Kyal Sin Linn
box
1.2 Test Customer Phone no text 7- August- 2018 Kyal Sin Linn
box
1.3 Test Customer Address text 7- August- 2018 Kyal Sin Linn
box
1.4 Test the ‘@’ in the E mail 7- August- 2018 Kyal Sin Linn
1.5 Test Customer Email text 7- August- 2018 Kyal Sin Linn
box
1.6 Test Register Button 7- August- 2018 Kyal Sin Linn
63 | P a g e
Test Script (1)
Unit Test 1 Test Case: Register by data entry Designed by: Mg Mg

customers
Data Source: Customer Objective: To test the Register of data Tester: Mg Mg
Table entry customers
Test Case Description Test Procedure Expected Actual
Result Results
1.1 Test 'Register' button is clicked. Customer Show See
customer Name is blanked. ‘Please fill Fig.1.1 &
Name text
out this 1.2
box
field’
message.
Before Testing
Fig.1.1
After Testing
Fig.1.2
64 | P a g e
65 | P a g e
Result Results
Customer Name is blanked. ‘Please fill Fig.1.2
Phone no
out this
text box
field’
message.
Before Testing
Fig.1.1
After Testing
Fig.1.2
For remaining test cases, please see Appendix.
66 | P a g e
5.1.8 Usability Testing
Visibility of System Status
Can see text box

with different color
Explain
XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Match between System and Real World
Aesthetic and Minimalist Design
Consistency and standard
Error Prevention
User Control and Freedom
67 | P a g e
5.1.9 Iteration for Usability Testing
Iteration 2
Users tell that table form and room form design are needed to change. So, table style
combo box is added in table entry form and room size combo box and Facility text box is also
added in room form.
(Iteration 2) Iteration For Visibility of System Status
Click to the
help link
68 | P a g e
5.1.8 Time box Summary
Work Done
Problems (Issues)
Solutions
Remaining Time-boxes
69 | P a g e
CHAPTER – 6
Deployment
70 | P a g e
6.1 Deployment
6.1.1 Deployment Diagram
Explanation for diagram
Users get access to the website by using the web browser via Internet cloud then the data
about booking, user accounts and roles will be stored in MySQL server. User uses PC which
is connected to the printer to print out digital slip and connected to the router to get online.
<<MYSQL>>
71 | P a g e
6.2 Data Migration
6.2.1 Data to Migrate
Explain
Time Box Master Data Transaction Data
Time Box 1: User Account Admin, Customer, Room Display, Registration

Registration and
Modification
Time Box 2: Booking Booking Booking
6.2.2 Plan
TimeBox Data To Migrate Duration Start End Date Responsible

Date person
Time Box 1: - Admin 4 days 3 March 7 March

User Account - Customer 2023 2023
- Room Receptionist,
Registration
and Manager
Modification
Time Box 2: - Booking 2days 8 March 10 March Admin Staffs,

Booking 2023 2023 Manager
Process
72 | P a g e
6.3 Training
6.3.1 Training plan
No Content Trainee Start End Venue Time

Date Date
1 Time Box 1 Receptionist, 11 11 Hotel 9 am –

Manager March March Empire 12 pm
- Admin
- Customer 2023 2023 Prestige
- Room Ball Room
2 Time Box 2 Admin Staffs, 11 11 Hotel 2 pm – 5

- Booking
Manager March March Empire pm
2023 2023 Prestige
Ball Room
6.3.2 User Manual
Firstly, set the booking date
And set the booking time
After choosing the booking

type click to the Find
button
And Choose the booking
type
73 | P a g e
CHA
PTE
R–
7
CON
CLU
SIO
N 74 | P a g e
&
7.1 Evaluation against Aim & Objectives

Aim
The main aim of the Project is to have a simple and attractive website that include
booking system. The program should be errorless, usable and secure since the working
system uses customers’ personal data and information.
Objective 1
The development team firstly analyze the current system of the hotel. Then research
and analyze the similar businesses’ website designs and functions to get idea for the
proposed project. The development team also adjust the current system’s strengths and
weakness by analyzing with SWOT analysis strategy. They also research and compare the
methodologies, programing languages and database management system to choose the most
suitable one to the project.
Objective 2
The development team firstly decide the target users and client’s first prioritized functions to
develop by researching functional and non-functional requirements of the project, planning
Timebox plan to fulfill the project within time plan, Managing the possible risks to increase the
project’s success rate.
Objective 3
The development team planned to create class diagram, Detailed class diagram and Use
case diagrams before developing the program to firm the foundation of the project to lessen
the failure percentages.
Objective 4
The development team planned to test out the website with tester to avoid bias on testing
progress. After testing, the developer team should take feedback and comments from the
tester to improve the program by modifying the functions or designs that the testers
mentioned.
75 | P a g e
Objective 5
After completing all program developing process, the development team should give training
to the staffs of the company who are going to use the program. Creating user manual about
the website and hand out to the users.
76 | P a g e
7.3 Evaluation against Justification Made
Methodology
 Selected Methodology
 Problems Encountered
 Lessons Learnt
Language
 Selected Languages
 Lessons Learnt
Database
 Selected Database
 Lessons Learnt
77 | P a g e
7.4 Evaluation against Time Box Plan
Time Box 1: Room and Table Booking Time Box
When making the time box plan, the end date for time box 1 is ‘August 9, 2018’. And
time box 1 was finished with all the needed iteration within this date. Therefore, end date was
matched with time box plan.
78 | P a g e
7.5 Personal Evaluation
79 | P a g e
7.6 Strength & Weakness of ABC POS
Strength
Weakness
80 | P a g e
7.7 Future Amendment
 Program
 Design
 Report
81 | P a g e
APP
END
IX
82 | P a g e
Section A: Use Case Descriptions
Timebox 1: Room and Table Booking Timebox
Section B: Detailed Class Definitions

Timebox 1: Room and Table Booking Timebox
Section C: Coding
Form Function Purpose
Ingredient Entry, Table Save () To save the data from the forms into the
Entry, Room Entry, Food database. When SAVE button is clicked
Entry, the input data are loaded into variables
and then using sql statements, inserting
is made.
Shopping Cart Functions AddProduct() XXXXXXXXXXXXXXXXXXXXXXXXX
Shopping Cart Functions RemoveProduct() XXXXXXXXXXXXXXXXXXXXXXXXX
83 | P a g e
Section D: Test Scripts
Result Results
Customer Name is blanked. ‘Please fill Fig.1.2
Phone no
out this
text box
field’
message.
Before Testing
Fig.1.1
After Testing
Fig.1.2
84 | P a g e
Section F: Interview Scripts
When interview with manager
85 | P a g e
References
86 | P a g e
References List
87 | P a g e

L5DC Project Documentation Contents KKKK

Uploaded by

Copyright:

Available Formats

L5DC Project Documentation Contents KKKK

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

L5DC Project Documentation Contents KKKK

Uploaded by

Copyright:

Available Formats

Research & Development of

Reserving System for

Name : KYAWT KAY KHAING KYAW

1.1 Overview (200 to 400) words

1.2 Current Business History

1.3 Current Business Process

1. Customer have to phone call to the hotel to book for a room.

Record customer information – Receptionist have to record customer’s information

1.5.1 Registration Process

Analysis (Total: 20days)

- Analysis of the current system (3 days)

Design (Total: 25 days)

- Researching and deciding the business’s functional and non-functional requirements

Implementation (75 days)

- Developing Website (40 days)

Evaluation (20 days)

- Evaluation of the proposed system with similar system (5 days)

Evaluation Deliverable – Reports of evaluating the whole project.

1.7 Estimate Cost and Duration

No Item Description Unit Price Quantity Sub-Total

1 Desktop Computer To develop and host $ 2460 2 $4920

2 Printer To print out digital slip $350 1 $350

Total Hardware Cost $5270

1.7.2 Software Cost

No Item Description Unit Price Quantity Sub-Total

1 Window 10 OS Window 10 Operating $109 2 $218

2 Antivirus Window Defender to $5.5 2 $11

3 Browser Chrome, Firefox (Free) $0 0 $0

4 Office Software Office 365 to make $100 2 $200

Total Software Cost $429

1.7.3 Development Cost

No Item Description Unit Price Quantity Sub-Total

1 Web Development Cost Language: $6000 - $6000

Fig (1) Project Proposal

1.1 Background of the Current System

1.4 Aims & Objectives of the Project

Analysis (Total: 20days)

- Analysis of the current system (3 days)

Design (Total: 25 days)

- Researching and deciding the business’s functional and non-functional requirements

- Developing Website (40 days)

Implementation Deliverable – Website Coding and Testing process will be produced in

Evaluation (20 days)

- Evaluation of the proposed system with similar system (5 days)

Evaluation Deliverable – Reports of evaluating the whole project.

2.1 Similar Product Introduction

Unlimited Channel Website

Fig (1) UC home page design

Fig (2) M9 home page design

Fig (1) Customer Signup Form from Shop.com (__)

Fig (2) Customer Signup Form from City Mall

1. Visibility of System Status

Fig (1)??? Explain………………

Fig (2)??? Explain………………

No Function Shop.com City Mall

1 Customer Registration 12345 12345

Functional Comparison Summary

No Function Shop.com City Mall

1 Visibility of System Status 12345 12345