SRS ResourceManagementSystem
SRS ResourceManagementSystem
Jatani, BBSR
SOFTWARE REQUIREMENT SPECIFICATION
Domain: Software Technology
Project: Resource Management System
Group Members
Monalisha Swain (200301120084)
Situ Kumari Gope (200301120061)
Akanksha Kumari (200301120008)
Ankita Roy (200301120005)
Aradhana Sahu (200301120037)
1.1 PURPOSE:-
This Resource Management System Software Requirement Specification (SRS) main objective is to provide a base for
the foundation of the project. It gives a comprehensive view of how the system is supposed to work and what is to be
expected by the end users. Client’s expectation and requirements are analyzed to produce specific unambiguous
functional and non-functional requirements, so they can be used by development team with clear understanding to
build a system as per end user needs. This SRS for RMS can also be used for future as basis for detailed understanding
on how project was started. It provides a blueprint to upcoming new developers and maintenance teams to assist in
maintaining and modifying this project as per required changeability.
1.3 OVERVIEW:-
The remaining sections of this documentations describes the overall descriptions which includes product perspective
and functions, characteristics of users. It also consists of Assumptions, and Constraints. Overall description is listed in
includes Specific Requirements which consists of Functional and Non-functional requirements, External Interface
Requirements, Software System Attributes, Performance Requirements, Capacity Requirements, Availability
Requirements, Safety Requirements and Requirement Traceability Matrix.
2.0 PRODUCT FEATURES:-
2.1 ADMIN LOGIN:- The admin can login to the system by giving the correct user id and password after login
the admin can monitor the customer .The admin can add the customer update accessories and room availability according to
the date, manage and update the database ,check in and check out. Overall admin can handle all the things.
2.2 CUSTOMER SIGNUP & LOGIN: To get in to the system the customer needs an existing account in the
system so that he/she can login. So, he/she need to sign up to the system. The sign up include two process if the customer
wants to get a valid id, he/she has to fill the mandatory information such as Name, valid email/phone no and password, then
after he/she need to submit the OTP. After completing the process, he/she can be a valid Customer. After signing up the
customer can login using the email id and password.
2.3 RESERVATION:- The system should enable customer to check for availability of rooms and other
accessories. The system should display all the information about rooms, electronics, furniture, food according to the
availability. The system should allow customer to confirm or cancel the booking . The system should record booking details
into database.
Actor Admin
Exceptions Nil
6.0 ER DIAGRAM:-
ENTITY DESCRIPTION:-
ADMIN
Admin name Varchar(30)
Admin email Varchar(30)
Admin password Varchar(30)
CUSTOMER
Username Varchar(30)
Email Varchar(30)
Password Varchar(30)
Mobile Int(20)
LOGIN
User name Varchar(30)
Password Varchar(20)
BOOKING
Name Varchar(30)
Phone Int(30)
Email Varchar(30)
State Varchar(20)
City Varchar(20)
Post Code Int(15)
2. SOFTWARE
Operating system: windows 11
Programming Language: FRONTEND (React, JavaScript, HTML, CSS)
BACKEND (Springboot , MySql)