Now that you have defined your E-R model and project description in the project you started and worked on inWeeks 1 and 2, start converting your logical E-R model to a physical model.
In this week, complete the following tasks:
In a Microsoft Excel spreadsheet, define columns with the following headings:
Primary Key
Null (NorY)
Running Head: DATABASE PLANNING
1
DATABASE PLANNING
Chernae Dalton
7/22/19
DATABASE PLANNING
2
Hotel Booking System
A Hotel Booking System is an automated guest reservation system. For easier checkout and
management of finances and accounts, the application will be integrated with the existing
website and ERP. The proposed system should display available rooms for specific dates with
their various entities such as size, number of people, prices, and services. The customers will
book the rooms online, make any payments, and receive automatic notifications. The hotel
management will manage the bookings from the system’s backend. Various entities and
attributes will be defined in designing the database. The data schema was then created, and
applicable rules, constraints, roles, and security set up.
Systems Development Life Cycle (SDLC) is a systematic, repetitive process that defines the
process of designing, developing, testing, and deploying an information system. It is standard
practice in the fields of systems engineering, information systems, and software engineering. The
concept is composed of the following six stages: analysis, design, development and testing,
implementation, documentation, and evaluation (Everatt & McLeod, 2007). All of the steps
highlighted were considered in the development of the Hotel Reservation System to achieve a
high-quality system that exceeds customer expectations.
For successful implementation, the value propositions of the desired Hotel Reservation System
were analyzed. The analysis sets to outline the merits of the proposed system, cost-benefit
analysis, and give a plan of implementation. From the study, the proposed system will get rid of
the challenges that the current system cannot handle (Blanchard & Fabrycky, 2006). There will
also be significant savings on costs.
DATABASE PLANNING
3
An analysis of the existing system to establish its pros and cons indicated a lack of essential
features such as automated online check-in and checkout, online payments, and automatic emails
confirmations. However, on the positive, the system had a robust accounting module enabling
the organization to make accurate financial projections, analyze their accounts, and generate
reports.
Due to its robust accounting and finance module, the existing system will be integrated with the
proposed software to function together as a single system for maximum value to the business. To
achieve integration, an Enterprise Service Bus (ESB) will be used. The two systems will
communicate without any physical connections between them. Usage of ESB is cost-effective
and flexible since it can link different interfaces into one subsystem directly.
Documentation is vital for computer software. It defines the software functionality as well as
usage procedure. For sufficient documentation, the following documents will be delivered along
with the software: requirements document, system design document, technical document
(showing the code, algorithms, interfaces, and APIs), end-user manuals, and system information
(Post & Anderson, 2006).
A product vision will be developed to manage future changes. The concept will outline the highlevel business goals. The product vision is a broad picture of the future. It will highlight the
significant value propositions and features the product will have. The view will guide in the
development while aligning stakeholders and customers to ensure the long-term success of the
product. The product vision will define the target customer, the problems the product will solve,
and comparison of the product to other existing products.
DATABASE PLANNING
In the design of the proposed system, to save time and reduce development and maintenance
costs, the design, interfaces, integrations, and data from the existing system will be reused. The
reuse will deliver a standardized system in comparison with the current system
4
DATABASE PLANNING
5
References
Everatt, G.D.; McLeod Jr., R. (2007). The Software Development Life Cycle. John Wiley &
Sons.
Blanchard, B. S., & Fabrycky, W. J.(2006) Systems engineering and analysis (4th ed.) New
Jersey: Prentice-Hall.
Post, G., & Anderson, D. (2006). Management information systems: Solving business problems
with information technology. (4th ed.). New York: McGraw-Hill Irwin.
BOOKING SYSTEM OF AN HOTEL
PAYMENT
PAYMENT ID
TRANSACTION AMOUNT
PAYMENT STATUS
CURRENCY
TRANSACTION DATE
BOOKING SYSTEMOF AN HOTEL
ROOM
ROOM NUMBER
ROOM PHONE NUMBER
ROOM TYPE
ROOM RENOVATION DATE
BED TYPE
BOOKING SYSTEM OF AN HOTEL
RESERVATION
RESERVATION ID
CHECK-IN DATE
CHECK-OUT DATE
RESERVATION STATUS
RESERVATION DATE
BOOKING SYSTEM OF AN HOTEL
PERSON
FIRST NAME
SURNAME
TELEPHONE NUMBER
E-MAIL ADDRESS
REGISTRATION DATE
BOOKING SYSTEM OF AN HOTEL
CREDIT CARD
CARD NAME
CARD TYPE
CARD NUMBER
EXPIRY DATE
CARD VERIFICATION CODE
BOOKING SYSTEM OF A HOTEL
RATE
RATE ID
RATE
STARTING DATE
ENDING DATE
DISCOUNT
ENTITIES AND ATTRIBUTES IN A HOTEL BOOKING SYSTEM
PAYMENT: Payment ID, Transaction Amount, Payment Status, Currency,
Transaction Date
ROOM: Room Number, Room ID Number, Room Phone Number, Room Type,
Room Renovation Date, Bed Type
PERSON: Full Names (First and Surname), Telephone number, E-mail Address,
Registration Date, Password
RESERVATION: Reservation ID, Check-in Date, Check-out Date, QR Code,
Reservation Status, Reservation Date,
CREDIT CARD: Card Name, Card Type, Card Number, Expiry Date, Card
Verification Code