Chapter One
Introduction
Background Of The Organisation
• Senaf International Hotel, founded in
2007 E.C in Nekemte, Ethiopia
• Initially 28 share companies, now 5 share
companies.
• Provides services like:
- bed room reservation
- food and beverage
- hall rentals
- laundry
Vision: to be the best hotel in the area and a
preferred choice for tourists.
Mission: to provide a comfortable and
satisfactory experience for clients
Existing System Study
Existing System Statement of Problem
• Manual booking system Inefficiencies of the manual system:
using Telegram, WhatsApp, • Time-consuming reservation and
cancellation.
Email, Phone calls etc.
• Difficulties in checking room
• Lack of a website for availability.
customer access • Miscalculations in customer billing.
• Time-consuming report generation.
• Data redundancy and lack of
security
• Need for automation
Proposed System
• Web-based application: A platform for
customers to find and use hotel services.
• Automated Reservation and Cancellation:
Customers can book and cancel rooms online.
• Real-time room availability: Customers can
view available rooms on a dashboard.
• Report generation: System will generate
reports for the organization.
• Online payment: Digital banking options for
payment.
• Database Security: Transition to a modern
database for better security.
Objective of the Project
General Objective: Develop a user-
friendly and powerful hotel booking
system.
Specific Objectives:
• Save guest information into a
database.
• Customize room types and prices.
• Enable guests to book rooms via the
website.
• Improve guest experience.
• Provide secure transactions.
Scope of the Project
Scope Limitation
• user management • The system focuses on
(admin, customer) bed room reservations,
• booking management not other hotel services
• admin dashboard
• reporting and analytics
Methodology
Data Gathering System Development
• Interviews with hotel staff. • Unified Modeling Language
• Observation of the existing (UML) for modeling.
manual system. • Object Constraint Language
• Document analysis of relevant (OCL) for specifying system
materials properties
Cont...
System Development
Tools
Hardware: Personal computer, Front-End: HTML5, CSS,
flash drive, hard disk. Javascript.
Software: XAMPP, Internet Back-End: MySQL with PHP.
access, MS Office, Visual
Studio Code, Draw IO (UML).
Chapter Two
System
Feature
Functional Requirements
User Requirements System Requirements
• Customer/Admin registration and • User management
login
• Booking Management
• Room booking and cancellation
• Dashboard
• Room availability display
• Online payment
• Reporting and analytics
• Profile management • Database management
• Service inquiry • Security features
• Admin functionalities (report • Error handling
generation, room updates)
Non Functional Requirements
• Usability • Documentation
• Performance • Security
• Accessibility • Backup
• Maintainability • Reusability
• Error Handling
Analysis Model
Object-Oriented Analysis (OOA): Object-Oriented Design (OOD):
this focuses on developing the uses the requirements identified
system's requirements and during OOA to develop object-
specifications using an object oriented models of the software.
model. Instead of traditional data These models serve as blueprints
or functional views, OOA looks at for implementation. The project
the system as a collection of uses the Unified Modeling
interacting objects. Language (UML) for modeling.
Data Flow Diagram
Activity Diagram
These diagrams show the
steps and flow of control
within the system. They
illustrate the order in
which activities occur and
whether they happen
sequentially or
concurrently.
Chapter
Three
System
Design
Introduction
• System design is a crucial stage in development, providing the
backbone for handling various scenarios.
• It represents the business logic of the software.
• It is essential for transitioning from requirements to implementation.
• The design phase handles the exceptional scenarios.
Deployement Diagram
• A deployment diagram shows the
architecture of the system,
detailing the distribution of
software artifacts to deployment
targets.
• Artifacts are concrete elements
in the physical world.
• The diagram visualizes the
physical deployment of the
system.
Component Diagram
• Component diagrams model the
physical aspects of object-
oriented systems.
• They are used to visualize,
specify, and document
component-based systems.
• They can be used for
constructing executable systems
through forward and reverse
engineering.
Architectural Design
• Architectural design defines the
system's structure, components,
and relationships.
• It ensures that the system meets
functional and non-functional Class Diagram
requirements. Class diagrams represent the structure and relationships of classes within a
system.
They show class names, attributes, and methods, as well as relationships.
User Interface Design
• UI design focuses on maximizing
efficiency and responsiveness for
good user experience.
• It facilitates completing tasks and
increases usability.
• The design promotes good user
experience and functionality.
Data Structure and Design
• An Entity Relationship Diagram
(ERD) graphically illustrates an
information system’s entities and
their relationships.
• It provides a conceptual model of
data.
