0% found this document useful (0 votes)
43 views20 pages

SRS - IEEE Group 4

This document provides a software requirements specification for a hotel management system for Arse Hotel in Adama, Ethiopia. It outlines the purpose, scope, features and functionality of the web-based system which aims to improve the hotel's reservation, cancellation, and management processes. The system will offer booking capabilities for customers as well as administrative features for staff to view reservations, assign rooms, and generate reports. The document is intended to guide the development team and ensure all stakeholders share a common understanding of what the system should deliver.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
43 views20 pages

SRS - IEEE Group 4

This document provides a software requirements specification for a hotel management system for Arse Hotel in Adama, Ethiopia. It outlines the purpose, scope, features and functionality of the web-based system which aims to improve the hotel's reservation, cancellation, and management processes. The system will offer booking capabilities for customers as well as administrative features for staff to view reservations, assign rooms, and generate reports. The document is intended to guide the development team and ensure all stakeholders share a common understanding of what the system should deliver.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Addis Ababa Science and Technology

University
Department of Electrical and Mechanical Engineering

Software Engineering Department


Software Requirements Specification
For Arse Hotel Management System

Group Members: ID
Duresa Feyisa ETS-0388/13
Etsubdenk Haltom ETS-0448/13
Fikre-Silassie Kelemework ETS-0504/13
Habte-Yesus Tadesse ETS-0566/13
Gemchis Elias ETS-0539/13

Submitted To: Instructor Lelise


Submission Date: June 8, 2023
ii

Contents
CONTENTS .................................................................................................................................................................II

REVISIONS ................................................................................................................................................................. II

1 INTRODUCTION ................................................................................................................................................1
1.1 DOCUMENT PURPOSE ................................................................................................................................ 1
1.2 PRODUCT SCOPE ........................................................................................................................................1
1.3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW ................................................................................... 2
1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS ....................................................................................... 3
1.5 DOCUMENT CONVENTIONS .........................................................................................................................4
1.6 REFERENCES AND ACKNOWLEDGMENTS ...................................................................................................4
2 OVERALL DESCRIPTION ...............................................................................................................................5
2.1 PRODUCT OVERVIEW ................................................................................................................................. 5
2.2 PRODUCT FUNCTIONALITY ......................................................................................................................... 5
2.3 USE CASE MODEL ........................................................................................................................................ 7
2.4 DESIGN AND IMPLEMENTATION CONSTRAINTS ..........................................................................................8
2.5 ASSUMPTIONS AND DEPENDENCIES ........................................................................................................ 10
3 SPECIFIC REQUIREMENTS .........................................................................................................................12
3.1 EXTERNAL INTERFACE REQUIREMENTS .................................................................................................. 12
3.2 FUNCTIONAL REQUIREMENTS .................................................................................................................. 14
4 OTHER NON-FUNCTIONAL REQUIREMENTS ........................................................................................15
4.1 PERFORMANCE REQUIREMENTS .............................................................................................................. 15
4.2 SAFETY AND SECURITY REQUIREMENTS .................................................................................................15
4.3 SOFTWARE QUALITY ATTRIBUTES ........................................................................................................... 15
APPENDIX A – DATA DICTIONARY .................................................................................................................... 18
Software Requirements Specification for Arse hotel management software

1. Introduction
This is a software requirement specification document for Arse Hotel’s management system which
is found in Adama, Ethiopia. It consists of specifications which can make the hotels’ reservation
system more advanced and web-based. This software plans on making the management, reservation,
cancelation of reservation and other tasks easier by providing a web-based and easily accessible
website for customers and also the hotel’s staff.

1.1 Document Purpose

The purpose of this document is to outline the requirements and specifications for the development
of the Arse Hotel Booking Software. It serves as a reference for the software development team,
stakeholders, and other parties involved in the project, ensuring a clear understanding of the
system's functionality and behaviour.

By providing a well-defined set of requirements, the document acts as a roadmap for the
development team, guiding them in the implementation of the software according to the desired
features and functionalities. This specific document is contains all the important features and
constraints of the arse hotel software system which is used while developing the whole system or
while having a client-developer meetings. It contains descriptions about the user interface, the
privileges to use for customers, the admin properties for staff and other constraints. By clearly
defining the purpose, the document sets the groundwork for effective communication and
collaboration throughout the project.

In summary, the purpose of the Arse Hotel Booking Software SRS document is to establish a shared
understanding of the software's requirements and specifications, guide the development process,
enable effective project management, and serve as a valuable reference throughout the software
development life cycle.

1.2 Product Scope

The product has a very wide scope which makes access easier to both the hotel administrations and
guests. It is online-based so guests don’t have to be present to either make a reservation or even see
if there are rooms available. It also consists of all the services the hotel provides so guests can know
before reserving and make the right choice. It is intended for anybody who wants to know about the
hotel. But, guests can also create their own accounts which are private and secured which contains
information about their reservations and their payment processes.

The software will be accessible to both guests and hotel staff, with different levels of privileges and
functionalities based on user roles. The Arse Hotel Booking Software will encompass the following
key features and functionalities:

1
Software Requirements Specification for Arse hotel management software

 User registration and authentication


 Room availability and booking management
 Reservation modification and cancellation
 Online payment integration
 Guest feedback and reviews
 Reporting and analytics for hotel management

From the hotel staff's perspective, the software will offer features for managing room availability,
tracking reservations, and generating reports for hotel management. It will provide an intuitive and
user-friendly interface for hotel staff to view and manage bookings, assign rooms, and handle guest
requests efficiently. The software will also facilitate communication between staff members and
guests, ensuring effective coordination and seamless service delivery.

1.3 Intended Audience and Document Overview


For the Arse Hotel Booking Software, the audience includes Arse Hotel management and
stakeholders who have a vested interest in the successful development and implementation of the
software. Additionally, it includes software developers, engineers, quality assurance teams,
designers, and user experience specialists who will be involved in the software development process.
People with different skill sets are likely to use this document for their own purposes, as follows:
 Software Developers and Engineers:
This group will use the document to understand the technical requirements specifications and how
they will be transformed into a system design when the final software application is written.
The development team responsible for designing, coding, and implementing the Arse Hotel
Booking Software will use the SRS document as a primary reference. It ensures that they have a
clear understanding of the desired features, functionalities, and technical specifications to
effectively build the software.
 Testing and Validation Teams:
This group will use the document during unit testing and system integration testing to understand all
system features and how the system responds to external stimuli. Separate from the QA team, may
conduct independent assessments or audits to ensure that the software meets regulatory compliance,
security standards, or any other specific requirements. They will use the SRS document to evaluate
the software's adherence to these criteria
.

 End users:
System end users will be more interested in the overall description of the system, which will help
them understand the final system, which the developers and testers will deliver and be able to
propose other requirements that the development team might miss.

2
Software Requirements Specification for Arse hotel management software

 Arse Hotel Management and Stakeholders:


This includes executives, managers, and decision-makers within the Arse Hotel who have a direct
interest in the software's functionality and impact on hotel operations. They need to understand the
requirements and specifications to align the software with the hotel's strategic goals and objectives.
 Designers and User Experience Specialists:
User interface (UI) and user experience (UX) designers play a crucial role in creating an intuitive
and visually appealing interface for the Arse Hotel Booking Software. They will refer to the SRS
document to understand the functional requirements and design an interface that meets user
expectations.
 System Administrators:
System administrators or IT personnel responsible for deploying and maintaining the Arse Hotel
Booking Software will refer to the SRS document to understand any specific hardware or software
requirements, system dependencies, and integration points.
 Quality Assurance Team:
The QA team is responsible for testing, verifying, and validating arse hotel management software to
ensure it meets the specified requirements. They will refer to the SRS document to design test cases,
evaluate the software's performance, and identify any deviations from the intended behaviour.

1.4 Definitions, Acronyms and Abbreviations


 CSS: Cascading Style Sheet
 HTML: Hyper Text Mark-up Language
 IEEE: Institute of Electrical and Electronics Engineers
 SRS :software requirement specification
 QA: quality assurance
 NY: new york
 USA: united states of America
 OTA: online travel agencies
 UML: unified modelling language
 IDE: integrated developing environment
 SMS: short message service
 DBMS: database management system
 API: application programming interface

1.5 Document Conventions


The development of these software requirements adhered to the standards set forth by the Institute
of Electrical and Electronics Engineers (IEEE) for software and systems engineering. A
comprehensive list of both functional and non-functional requirements, as well as clear and concise
language, makes up the document convention. This ensures a structured and efficient software
development process that results in a top-notch final product that meets the needs of all stakeholders.

3
Software Requirements Specification for Arse hotel management software

1.6 References and Acknowledgments

Institute of Electrical and Electronics Engineers (IEEE), Inc. (1998). IEEE Standard 1016-1998,
IEEE Recommended Practice for Software Requirements Specifications. New York, NY, USA:
IEEE, Inc.

2. Overall Description

2.1. Product Overview


As we all know it is not that common in our country to reserve a hotel room online or see an
overview of where we are going to stay. This way seems to be so tiresome since it requires
customers to be personally present in order to reserve a room. It is also hard for the management
staff to control the operations in the hotel since all the data is managed manually and there might be
errors or maybe loss of data. This product aims on solving this problem by providing web-based
system for both the customers and the staff which can make things easy. It provides a secure, user-
friendly and appealing website.
The Arse Hotel management Software is designed to provide an efficient and user-friendly platform
for guests to make reservations and manage bookings at the "Arse Hotel." The software aims to

4
Software Requirements Specification for Arse hotel management software
streamline the hotel booking process, enhance guest satisfaction, and optimize the operational
efficiency of the hotel.

2.2. Product Functionality


 Functional Requirement for Guests
The Arse Hotel Management Software will encompass several major functions to support efficient
hotel operations and enhance the guest experience. These functions include:
1. Guest Registration: Arse hotel software will facilitate the registration process for guests,
allowing them to provide their personal details, contact information, and any specific
requests or preferences.
2. Room Booking and Availability: Guests will be able to search for available rooms based
on their desired dates, room type, and other criteria. The software will provide real-time
information on room availability and enable guests to make bookings in Arse hotel.
3. Reservation Management: The software will handle the management of guest reservations,
including modifying or cancelling bookings, managing their reservation detail, and handling
any changes or updates to guest information.
4. Check-In and Check-Out: The software will streamline the check-in and check-out
processes for guests. It will generate digital key cards or provide necessary information for
physical key retrieval, update the room status, and handle billing and payment transactions.
5. Billing and Invoicing: The software will generate accurate bills and invoices for guests,
incorporating room charges, additional services, and any applicable taxes or fees. It will also
facilitate different payment methods, such as credit cards or cash.
6. Guest Services and Requests: The software will enable guests to make service requests,
such as room service, housekeeping, or maintenance, through a user-friendly interface. It
will ensure prompt handling of these requests and track their status.
7. Reporting and Analytics: The software will generate various reports and analytics to
provide insights into hotel operations, including occupancy rates, revenue analysis, and
guest satisfaction. These reports will assist in decision-making and performance evaluation.
8. Integration with External Systems: The software will integrate with external systems and
services, such as payment gateways, accounting software, or online travel agencies (OTAs),
to synchronize data and streamline processes.
These major functions will form the core capabilities of the Arse Hotel Management Software,
providing a comprehensive solution for managing hotel operations, enhancing guest experiences,
and optimizing overall efficiency.

 Functional Requirement for Hotel Staffs


In addition to the functionalities provided for guests, the Arse Hotel Management Software will
offer various features and capabilities for the hotel staff and administration. These functionalities
include:

5
Software Requirements Specification for Arse hotel management software
1. Staff Management: The software will allow the administration to manage the hotel staff,
including creating and managing staff accounts, assigning roles and permissions, and
monitoring attendance and schedules.
2. Room Assignment and Housekeeping: The software will provide tools for assigning rooms
to guests based on their preferences, availability, and room types. It will also facilitate
housekeeping activities, allowing staff to track room cleaning status and maintenance tasks.
3. Inventory Management: The software will assist in managing hotel inventory, including
tracking and monitoring the availability of amenities, supplies, and equipment. It can generate
alerts for low stock levels, automate reordering processes, and maintain inventory records.
4. Reporting and Analytics: The software will generate reports and analytics specifically
tailored for hotel staff and administration. These reports may include staff performance reports,
financial reports, occupancy rates, and revenue analysis to support decision-making and
resource planning.
5. Reservation Management: The software will provide comprehensive reservation
management features for the hotel staff. This includes the ability to view, modify, and cancel
reservations, handle room upgrades or changes, and manage guest requests or special
arrangements.
6. Billing and Invoicing: The software will enable the hotel staff to handle billing and invoicing
processes for different stakeholders, including individual guests, corporate clients, and travel
agencies. It will generate accurate bills, track payments, and provide financial reports.
7. Security and Access Control: The software will incorporate security features to ensure that
only authorized personnel can access sensitive data and perform specific functions. It may
include user authentication mechanisms, role-based access control, and audit logs to track user
activities.
8. Communication and Messaging: The software may include internal messaging or
communication features to facilitate collaboration and communication among the hotel staff.

6
Software Requirements Specification for Arse hotel management software

2.3. Use case model

Registra
tion Staff
Manageme
nt
Room Booking
and Availability

Room
Assignment
Reservation
Management

User
Check-In Inventory Staff
and Check- Management
Out

Billing and
Invoicing
Reporting
and
Analytics
Guest Services
and Requests

Security
Payment and Access
management Control

Profile User and


manageme payment
nt autontication

Delete Communicatio
account n and
Messaging

7
Software Requirements Specification for Arse hotel management software

2.4. Design and Implementation Constraints


This system is a web application, and for that reason, it is implemented using HTML, CSS, and
JavaScript technologies. It allows users to submit book, cancel, and view different services of the
hotel. However, the system's reliance on internet connectivity may pose a challenge in areas with
poor network coverage. Additionally, the system's security measures must be robust enough to
protect sensitive user information from cyber threats.
The design and implementation of the Arse Hotel Management Software are subject to various
constraints that will impact the options available to the developers. These constraints include:
1. Hardware Limitations:
 Timing Requirements: The software must operate within certain response time
limits to provide a seamless user experience. The system should be optimized to
minimize delays in processing guest requests and retrieving information from
databases.
 Memory Requirements: The software should efficiently utilize memory resources
to ensure optimal performance and avoid excessive memory consumption.
 The hardware configuration of the system could limit the developer's options to
improve performance or add specific features to the system. For example, if the
server infrastructure is not powerful enough, the developers may not be able to add
features. That requires a lot of processing power.
2. Interfaces to Other Applications:
 Integration with Payment Gateways: The software must integrate with payment
gateways to facilitate secure online payments. The implementation should adhere to
the APIs and specifications provided by the selected payment gateways.
 Integration with External Databases: The software needs to interface with existing
hotel databases and systems to synchronize data, such as room availability and guest
information. The integration should ensure data consistency and avoid conflicts or
discrepancies.
3. Technology and Tools:
 COMET Method for Software Design: The software design should follow the
COMET (Concurrent Object Modelling and Architectural Design) method. This
approach emphasizes concurrent programming and object-oriented design principles,
facilitating scalability and modularity
 UML Modelling Language: The software design should employ the Unified
Modelling Language (UML) for visualizing and documenting the system's
architecture, components, and relationships. UML diagrams, such as class diagrams
and sequence diagrams, should be used to communicate the software design.
4. Security Considerations:
 Data Protection: The software must adhere to industry-standard security practices to
protect sensitive guest data and prevent unauthorized access or data breaches.

8
Software Requirements Specification for Arse hotel management software
Encryption techniques should be applied to safeguard personal information, such as
credit card details, during transmission and storage.
 User Authentication and Authorization: The software should implement robust
mechanisms for user authentication and authorization to ensure that only authorized
individuals can access and modify sensitive information.
5. Design Conventions and Programming Standards:
 Coding Standards: The software development should adhere to established coding
standards and conventions to promote code readability, maintainability, and
consistency. These standards may cover aspects such as naming conventions, code
formatting, and documentation requirements.
 Documentation Responsibility: The customer's organization will be responsible for
maintaining the delivered software. Therefore, the developers should provide
comprehensive documentation, including user manuals, system architecture diagrams,
and code documentation, to assist with future maintenance and updates.

6. Operating system compatibility: Certain features of the system may only be compatible
with specific operating systems. If the system is already on a specific operating system, it
may limit the developers' options to meet the needs of those who are on other operating
systems.
7. Third-party software limitations: If developers have to integrate third-party software such
as payment gateways, etc., their options may be limited by the features and interface
provided by the third-party software's vendor.
Third-Party Components: It is assumed that the Arse Hotel Management Software will
utilize certain third-party components or libraries to enhance its functionality and
performance. These components may include frameworks for user interface development,
payment gateways, or database management systems. It is assumed that these third-party
components will be available and compatible with the software's design and implementation.
8. Budget constraints: Budget limitations can also be a factor that limits the developers'
options. If the budget is limited, developers may not be able to invest in expensive hardware
or premium software modules that could enhance the system's capabilities.
9. Technical skills of the team: If development teams do not have the required technical skills,
it can limit the options available to them. They may not be able to incorporate advanced
features, or there may be a need to outsource the specific skills, leading to further cost.
10. Compliance with industry-standard security practices to ensure the confidentiality,
integrity, and availability of data.
11. Scalability and performance optimization to handle a potentially high volume of
simultaneous bookings and user interactions
12. Multi-Language and Multi-Currency Support: this arse hotel software should be
designed to support multiple languages and currencies to cater to a diverse range of guests.

9
Software Requirements Specification for Arse hotel management software
This includes providing language options for the user interface, as well as supporting
currency conversion and displaying prices in various currencies.
13. Responsive Design: The user interfaces of the software should be designed using responsive
design principles. This ensures that the interfaces adapt and provide optimal viewing and
interaction experiences across different screen sizes, resolutions, and devices.
By acknowledging and working within these design and implementation constraints, the developers
can ensure that the Arse Hotel Management Software is developed in a manner that meets the
specified requirements and aligns with industry best practices.

2.5. Assumptions and Dependencies

Assumptions:
1. Third-Party Components: It is assumed that the Arse Hotel Management Software will
utilize certain third-party components or libraries to enhance its functionality and
performance. These components may include frameworks for user interface development,
payment gateways, or database management systems. It is assumed that these third-party
components will be available and compatible with the software's design and implementation.
2. Development Environment: It is assumed that the development team will have access to
the necessary development tools, such as integrated development environments (IDEs),
version control systems, and testing frameworks. It is also assumed that the team will have
the required hardware and software resources to support the development and testing
process.
3. Operating Environment: It is assumed that the software will be deployed and operated in a
standard operating environment that meets the necessary hardware, software, and network
requirements. The software's performance and functionality may be affected if the operating
environment deviates significantly from the assumed specifications.
4. Data Availability: It is assumed that the required data, such as hotel room information,
guest details, and availability status, will be available in the existing hotel databases or
accessible through appropriate interfaces. The accuracy and availability of this data can
impact the software's functionality and reliability.

Dependencies:
1. Reuse of Software Components: The project may depend on the reuse of certain software
components or modules from previous projects or existing systems. These components may

10
Software Requirements Specification for Arse hotel management software
include modules for user authentication, database connectivity, or reporting. The availability
and compatibility of these components will impact the development and integration process.
2. External Services and APIs: The project may depend on external services, such as SMS
gateways or email delivery services, to provide certain functionalities like sending
notifications or confirmations to guests. The project's successful implementation relies on
the availability and proper functioning of these external services and their APIs.
3. Regulatory Compliance: The project may have dependencies on regulatory compliance
requirements, such as data privacy laws or payment processing regulations. The software's
design and implementation must align with these requirements to ensure legal compliance
and avoid any potential legal or security issues.

3. Specific Requirements

3.1. External Interface Requirements


3.1.1 User Interfaces

3.1.1.1. User Interface for Guests (Users):

11
Software Requirements Specification for Arse hotel management software

 Touch Screen: The user interface may feature a touch screen, allowing guests to interact directly
with the interface by tapping on the screen to select options or input data. This touch screen
functionality enhances the user experience by providing a seamless and intuitive interaction
method.
 Menus and Navigation: The interface will include menus or navigation panels that allow guests to
access different features and functionalities of the Arse Hotel Management System. Guests can
navigate through these menus to perform tasks such as room reservation, check-in/check-out, view
available services and amenities, make special requests, and view their billing information.
 Forms and Input Fields: The user interface will include forms and input fields where guests can
enter their personal details, room preferences, payment information, and any special requirements.
These forms may have validation checks to ensure accurate and complete data entry.
 Visual Feedback: The interface will provide visual feedback to guests to confirm their actions,
display notifications or alerts related to their bookings, and indicate the status of their requests or
processes. This feedback mechanism helps guests understand the system's response and provides
assurance that their actions have been successfully processed.
3.1.1.2. User Interface for Hotel Staff (Administration):
 Touch Screen: Similar to the guest interface, the user interface for hotel staff may feature a touch
screen for easy interaction. Staff members can tap on the screen to select options, navigate through
menus, and input or modify data.
 Menus and Navigation: The interface will include menus or navigation panels that allow staff
members to access different features and functionalities of the Arse Hotel Management System.
Staff can navigate through these menus to perform tasks such as guest check-in/check-out,
reservation management, room assignment, housekeeping management, billing and invoicing, and
generating reports.
 Forms and Input Fields: The user interface will include forms and input fields where staff
members can enter and update guest information, manage room allocations, handle billing details,
and perform other administrative tasks. These forms may have validation checks to ensure
accurate and complete data entry.
 Visual Feedback: The interface will provide visual feedback to staff members to confirm their
actions, display notifications or alerts related to their tasks or processes, and indicate the status of
ongoing operations. This feedback mechanism helps staff members understand the system's
response and provides assurance that their actions have been successfully processed.

3.1.2. Hardware Interfaces


Server-class computers must be used to run all server-side components. All client-side components
must run on mobile devices like smartphones and tablets, as well as workstation-class and personal-
class computers. To increase accessibility and usability for all users, it is crucial to make sure the
hardware interface is compatible with a variety of devices. Arse Hotel Management System
interacts with various hardware components to support its functionality. Here is a short description
of the different hardware interfaces:

12
Software Requirements Specification for Arse hotel management software

 Servers and Network Infrastructure: The software should be hosted on dedicated servers or a
cloud-based infrastructure. It should communicate with web servers, databases, and other necessary
hardware components to handle user requests and store data.
 End-User Devices: The software should be accessible and compatible with a range of end-user
devices, including computers, smartphones, and tablets. The interfaces should be responsive and
adaptable to different screen sizes and resolutions.
 Payment Processing Devices: The software may interface with payment processing devices, such
as credit card terminals or mobile payment systems, to facilitate secure and convenient payment
transactions. This interface enables guests to make payments for their bookings and other hotel
services.
 Front Desk Computers/Terminals: The software product will interface with the front desk
computers or terminals used by hotel staff to access the Arse Hotel Management System. These
computers/terminals provide the primary interface for staff members to perform tasks such as guest
check-in/check-out, reservation management, room assignment, and billing.
 Electronic Messaging Systems: The software may interface with electronic messaging systems,
such as email servers or SMS gateways, to send notifications and alerts to guests regarding their
reservations, check-in/check-out procedures, and any updates or changes to their bookings.

3.1.3. Software Interfaces


To import and export customer data, the online hotel management system must interface with other
external systems.The Arse Hotel Booking Software integrates with various software components
and external services. The following software interface requirements should be taken into account:
 Payment Gateways: The software should integrate with payment gateways to facilitate secure
online payments. It should communicate with the payment gateway APIs to initiate and complete
payment transactions.
 Messaging Services: The software may integrate with SMS gateways or email delivery services to
send booking confirmations, notifications, and other communication to guests.
 Database Management System: The software should interact with a reliable and scalable database
management system (DBMS) to store and retrieve data related to room availability, guest
information, and reservations.
 Third-Party APIs: The software may utilize third-party APIs to retrieve additional data or services,
such as geolocation information for mapping functionalities or currency exchange rates for payment
processing.
By defining these external interface requirements, the Arse Hotel Booking Software can be
developed to effectively communicate with users, hardware components, and external services,
ensuring a seamless and efficient booking experience for guests and hotel staff.

3.2. Functional Requirements

3.2.1. Users should be able to view services:

13
Software Requirements Specification for Arse hotel management software
3.2.1.1 The system should allow users to view all available a room.
3.2.1.2 The system should allow users to view detailed information on room amenities and features,
such as bed size, view, and in-room facilities.
3.2.1.3. The system should allow users to view all available events.
3.2.1.4. Users should be able to view menus, events held in the hotel such as weddings, meetings
and such, view detailed descriptions of the rooms whether they are single or double, and also dining
options.
3.2.2. Login privileges:
Users can create their own accounts which are secure and consists of their name, email, phone
number and password. They later can use this email and password to login and view their profiles
and make reservations and payment.
3.2.3. Record keeping:
The system should keep a record of the person’s name, email, ID, check-in and check-out dates,
number of occupants, room number and other information for an effective management and service.
3.2.4. User-friendly user interfaces:
The user interfaces should be easily accessible for everyone to use. It should be able to work
thoroughly in places with little network coverage. It should also have features which enables
disabled people to use.
3.2.5. Payment methods:
The system should provide a user-friendly interface to select from a variety of payment methods
such as Debit cards, Bank transfers, PayPal and Cash.
3.2.6. Receipts generation and confirmation emails:
Once customers are done reserving the room or choosing a service to use, the system should
generate a receipt with all the filled out information and it must be able to send that confirmation to
the customer via an email.
3.2.7. Admin interface:
Admins should be able to login into their secured account see whatever is going on in the hotel
which includes the number of reserved rooms and they should also be able to add to menus, add
rooms and so on.
3.2.8. Receptionist access:
Receptionists must be able to manage requests and give answers via a secured and private account.
3.2.9. Admins control:
Admins should be able to control staffs which are all the employees.
3.2.10. Comment and Review:
Users should be able to give reviews of the services they had, their complaints and comments about
their stay and the admin should reply.
3.2.11. Reports:
The employees must generate reports of every transaction made to the administrators.
3.2.12. Cancellation:

14
Software Requirements Specification for Arse hotel management software
Users can cancel their reservations if they change their mind and admins can also cancel
reservations on behalf of customers due to different incidents.

4. Other Non-functional Requirements


4.1. Performance Requirements

4.1.1. Quick Response Time


The system should be designed to respond to requests quickly, with a specified timeframe for
response, to ensure that customers receive timely feedback on their requests.
4.1.2. Notification System
The system should have an automated notification system in place to keep guests
informed of the progress of their requests, with timely updates on any new
developments or actions taken.
4.1.3. Documentation Management

15
Software Requirements Specification for Arse hotel management software

The system should have a robust documentation management system that maintains
accurate and up-to-date records of all requests and their resolutions, with the ability to
generate detailed reports and analytics on demand.

4.2. Safety and Security Requirements


4.2.1. Confidentiality
The system should ensure the confidentiality and privacy of user information and complaints,
with appropriate security measures in place to protect sensitive data.
4.2.2. Security
The system should have robust security measures in place to protect user data from
unauthorized access or hacking, including secure data encryption, authentication, and access
control.
4.2.3. Compliance and Regulations
The complaint management system should comply with all relevant regulations related to data
privacy and security. The system should ensure that all user information and complaints are
handled in accordance with the applicable laws and regulations. The system should also
maintain appropriate security measures to protect student data and prevent unauthorized
access.

4.2. Software Quality Attributes


4.2. Accessibility
The system should be designed to be easily accessible to all users, regardless of their
location or device, by using standard web technologies and ensuring compatibility with all
major browsers and mobile devices.

4.2.2. 24/7 Availability


The system should be available at all times to users, with no restrictions on the time of day
or day of the week.
4.2.3. Mobile Compatibility
The system should be designed to be fully compatible with mobile devices, with a
responsive design that adjusts to the screen size and resolution of any mobile device.

16
Software Requirements Specification for Arse hotel management software

Appendix A – Data Dictionary

1. Guest Information (Table: Guests)


 guest_id (Primary Key): Unique identifier for each guest.
 first_name: First name of the guest.
 last_name: Last name of the guest.
 email: Email address of the guest.
 phone: Contact number of the guest.
 address: Residential address of the guest.
 nationality: Nationality of the guest.
2. Room Information (Table: Rooms)
 room_id (Primary Key): Unique identifier for each room.
 room_number: Room number or identifier.
 room_type: Type of room (e.g., single, double, suite).
 occupancy_limit: Maximum number of guests allowed in the room.

17
Software Requirements Specification for Arse hotel management software
 amenities: Amenities available in the room (e.g., Wi-Fi, TV, mini-bar).
 price_per_night: Cost per night for the room.
3. Reservation Information (Table: Reservations)
 reservation_id (Primary Key): Unique identifier for each reservation.
 guest_id (Foreign Key): Foreign key referencing the guest_id from the Guests table.
 room_id (Foreign Key): Foreign key referencing the room_id from the Rooms table.
 check_in_date: Date when the guest is expected to check in.
 check_out_date: Date when the guest is expected to check out.
 total_price: Total cost of the reservation.
 status: Status of the reservation (e.g., booked, checked-in, checked-out).
4. Payment Information (Table: Payments)
 payment_id (Primary Key): Unique identifier for each payment transaction.
 reservation_id (Foreign Key): Foreign key referencing the reservation_id from the
Reservations table.
 payment_date: Date when the payment was made.
 amount: Total amount paid.
 payment_method: Payment method used (e.g., credit card, cash, online transfer).
 Status: Status of the payment (e.g., pending, paid).
5. Hotel staff Accounts (Table: staff)
 user_id (Primary Key): Unique identifier for each staff.
 username: Username for the staff's login.
 password: Encrypted password for the staff login.
 Role: Role or access level of the hotel staff (e.g., administrator, staff).

18

You might also like