Scribd
Upload
51 views3 pages

2.1 (Discuss 3 Existing Systems, Each System Must Have at Least 1 Erd)

This chapter discusses requirements collection and analysis for a hotel booking system. It analyzes three existing systems by reviewing their entity relationship diagrams. Each existing system is summarized, noting their primary keys and relationships. A table then compares the key criteria of the existing systems to each other and outlines how the new system aims to improve upon them, such as having a single foreign key for bookings rather than splitting check-in and check-out dates across multiple keys.

Uploaded by

nurshazihah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
51 views3 pages

2.1 (Discuss 3 Existing Systems, Each System Must Have at Least 1 Erd)

This chapter discusses requirements collection and analysis for a hotel booking system. It analyzes three existing systems by reviewing their entity relationship diagrams. Each existing system is summarized, noting their primary keys and relationships. A table then compares the key criteria of the existing systems to each other and outlines how the new system aims to improve upon them, such as having a single foreign key for bookings rather than splitting check-in and check-out dates across multiple keys.

Uploaded by

nurshazihah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Chapter 2: Requirements Collection and Analysis

2.1 Analyze Existing Systems (discuss 3 existing systems, each system must have at least 1
ERD)

 This diagram has rate, room type, room, booking, extra and guest.
 For primary key are room_type,booking_id, extra_id, and consists 2 id for room and
guest.
 First need to make a booking for guest which is key in first name, last name and
address. Nest, for booking room guest can choose the room type.
 This diagram has rate, hotel, room, book and guest.
 For primary key are roomNumber, hotelNumber, and have two guestNumber.
 First need to make a booking for guest which is key in guestName and guestAddress.
Nest, for booking room guest can choose the room type.
 The Primary key was identified for each entity and the foreign key was included
where there is a relationship.
 For entities that have a many to many relationship, junction tables were created.

2.2 Comparison amongst systems including New System (in a table)


Criteria Current System Current System B Current Your System
A System C
Details Have a four FK Only one FK but There no Have one FK
Booking divided into two: any ERD - CheckinDate
1. ArrivalDate about and
and details CheckoutDate
departureDat booking
e
Room Have one FK FK – hotelNumber Have eight Have one FK
and it just focus only entity - Roomtype,
on RoomLevel
max_occupancy and
RoomPrice
Services There no any There no any ERD There no Have one FK
ERD about about services any ERD - ServicesName
services about and
services ServicesPrice
(must provide detail and clear comparison)

You might also like