0% found this document useful (0 votes)
9 views25 pages

Presentation S.E Updated

The document presents a hotel reservation system developed by Group 2 from the University of Sialkot's Computer Science Department, detailing its data flow diagram (DFD) and use case diagram. It outlines key components, functional and non-functional requirements, and class-based modeling aspects of the system. The presentation concludes with a thank you note for the audience's engagement.

Uploaded by

Noor Noora
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views25 pages

Presentation S.E Updated

The document presents a hotel reservation system developed by Group 2 from the University of Sialkot's Computer Science Department, detailing its data flow diagram (DFD) and use case diagram. It outlines key components, functional and non-functional requirements, and class-based modeling aspects of the system. The presentation concludes with a thank you note for the audience's engagement.

Uploaded by

Noor Noora
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 25

University of Sialkot

Department :
Computer Science
Subject :
Software Engineering

Presentation by :
Group 2

Group Members :
Maheen Hamid (11)
Zainab Noor (34)
Sabeeqa Shabir (7)
Ameer Hammad (1)
Hotel
Reservation
System
A Data Flow Diagram
(DFD) is a graphical
representation of how
data flows within a
system, including inputs,
processes, storage, and
outputs.
Key Components of DFD

External Entities

Process

Data Flows

Data Stores
Entities: Main
Processes
Customer
Housekeeping Hotel Reservation
System (0.0)
Manager
Room Reservation
Receptionist System (1.0)
Billing System Billing Management (2.0)
Food Management Food Service
System Management (3.0)
Housekeeping
Management (4.0)
System Administration
(5.0)
Room Management
System (6.0)
List of Activities
Reservation Management:
Record reservation (1.1)
Verify availability (1.2)
Confirm reservation (1.3)
Billing Activities:
Process payment (2.1)
Generate invoice (2.2)
Food Service Activities:
Receive food order (3.1)
Process order (3.2)
Deliver food (3.3)
Housekeeping Activities:
Record room status (4.1)
Manage cleaning and requests (4.2)
Administrative Activities:
Generating reports (5.1)
Making operational decisions (5.2)
Screensho
t
Proof
Use case diagram:
A use case diagram is a type of diagram in the that
represents the functional aspects of a system. it
provides a graphical depiction of how users (or other
systems) interact with the system to achieve specific
goals. use case diagrams are commonly used during
the requirements-gathering phase of a project to
capture the high-level functionality of the system and
its interactions.
Key Components of use case
diagram

Actor: it is an any entity that


perform a role in the system.

Use case: it represent a function


Or a action within the system.

System: it is define the scope of the use case


Continue:
Association: links an actor to a use case.
Include: a use case that is always executed as part of another use
case.
<<include>>

Extend: a use case that is conditionally executed to extend the


behavior of another use case.
<<extend>>

generalization: represents inheritance between actors or use cases.


Screenshot proof
Functional Requirements
•Customer
•Create and log in to accounts
•Book, choose, and change rooms
•Pay using credit/debit cards or online methods
•Order food and view bills
•Manager:
•Manage rooms, staff, and reports
•Create discounts and offers
•Housekeeping/Staff:
•Track room cleaning and supplies
•Get tasks from the manager
•Receptionist:
•Handle check-ins/outs, bookings, and room assignments
•Process payments and create invoices
•Food:
•Manage menu, track orders, and deliver food
Non-Functional Requirements:
•Performance : Quick responses (<30 seconds), handle busy
times

•Security:
Protect data with encryption, require strong
passwords and extra security .

•Usability: Simple interface, works on all devices

•Availability: Always on (24/7), regular backups

•Compliance: Follow privacy laws .

•Reliability: No booking/payment mistakes, clear error messages


Class-based Modeling
 Class-based modeling represents the objects that the system will
manipulate.

 The operations also called methods or services that will be applied to


the objects to effect the manipulation,
 Relationship between the objects

 Include classes , objects, attributes, operations , collaboration


diagrams
Components

 Attributes:

+plus: method is connected to public


-minus: connected to private
#number: connected to protected

 Variables declared:
variableName:VariableType

 Method declared:
method():return type
Continue
Continue
 1. Inheritance Relationships :FoodItem and Drink
inherit from Food.

 2. Composition :rooms exist as part of the customer’s


reservation during the stay.

 3. Aggregation :Manager aggregates Staff (Chef,


Receptionist, Housekeeping).A Manager supervises
these staff members but doesn’t own them.
Continue

4. Associations :
 Customer and Bill: A customer generates a bill at the end of their
stay.
 Customer and Receptionist : The receptionist helps with bookings
for the customer.
 Customer and Rooms: Rooms are linked to customers via room
assignments.
5. Dependency:
 Chef depends on Food ingrediants (Food class) to prepare meals.
 Receptionist depends on Rooms to assign bookings.
ScreenShot
ThankYou
!!

Execution complete, all functions


processed successfully. Before we
exit the program, We’d like to
commit our sincere thanks for
your attention and engagement.
Your input has truly debugged
this presentation!

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy