SRS - IEEE Group 4
SRS - IEEE Group 4
University
Department of Electrical and Mechanical Engineering
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
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.
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.
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
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.
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
3
Software Requirements Specification for Arse hotel management software
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
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.
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
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
Delete Communicatio
account n and
Messaging
7
Software Requirements Specification for Arse hotel management software
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.
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
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.
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.
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.
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.
16
Software Requirements Specification for Arse hotel management software
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