0% found this document useful (0 votes)
24 views11 pages

SRS ResourceManagementSystem

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)
24 views11 pages

SRS ResourceManagementSystem

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/ 11

Centurion University of Technology and Management,

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)

Under the guidance of


RAKESH RAY
1 INTRODUCTION:-
Resource management is the practice of planning, scheduling, and allocating people, money, and technology to a project or
program. In essence, it is the process of allocating resources to achieve the greatest organizational value.

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.2 SCOPE OF THE PROJECT:-


The RMS project is intended for the manage the resources available in the process of reservations for room in that process
we have to manage the rooms and other accessories available inside the room .All the resources should be manage on the
basics of availability according to the date. Our Resource Management System will have two end users: Customer and
Admin. Resource Management System will consists of booking System. Customers be able to check for room’s
availability, select the rooms, and book for the room. Admin will have access to update or modify booking details, check the
activity of customer and add the customer and also will able to view the financial report and able to update room information
such as availability and category. The main goal of this introduced automated RMS software is to simplify every day process
of manage the resource. It will be able to take care of services to customer in a quick manner. This automation will be able to
replace the drawbacks of large customer information physical files which were difficult to handle. Quick retrieval of
information, ease of use, quick recovery of errors, fault tolerance are some of the benefits that development team will be
working on to achieve end user satisfaction.

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.

2.3AVAILABILITY REQUIREMENTS:- Booking confirmation message should be generated automatically


after booking the rooms and accessories ,if any other requirement will be needed then customer can connect with our
management team.

3.0 SAFETY REQUIREMENTS :-


Database should be backed up every hour. Under failure, system should be able to come back at normal operation
under an hour.

4.0 SOFTWARE SYSTEM ATTRIBUTE :-


4.1 Correctness: This system should satisfy the normal Resource Management operations precisely to fulfill the end user
objectives
4.2 Efficiency: Enough resources to be implemented to achieve the particular task efficiently without any hassle.
4.3 Flexibility: System should be flexible enough to provide space to add new features and to handle them conveniently
4.4 Integrity: System should focus on securing the customer information and avoid data losses as much as possible
4.5 Portability: The system should run in any Microsoft windows environment.
4.6 Usability: The system should provide user manual to every level of user.
5.0 Use Case Diagram:-
ACTIVITY DIAGRAM OF ADMIN:-

Use case ID:1 Use Case Name: Admin Activities

1. Admin can login to the RMS website using


any type of web browser.
Description 2. Admin can add customer after successfully
login. (Admin will only allow the valid email id
and password, information of the customer).
3. Admin can monitor customer activities

Actor Admin

1. Admin should have a proper internet


connection.
Preconditions 2. Admin should have proper login credentials.
3. Admin should have a updated web browser.

1. Admin will be logged in.


2. Customer will be added automatically by
giving the valid credentials.
Post conditions 3. Customer will be monitored by admin .

1. Admin open the browser and open the RMS


website.
Process of Admin work 2. Admin click on the login option
3. There he/she should fill the mandatory fields.
4. After successful login admin can add customer
automatically only (Customer having valid email
id and password )
5. Admin can monitor the activities customer
and manage the update process.
ASSOCIATED USECASE DIAGRAM OF ADMIN:-

Associated with use case


diagram

Exceptions 1. The password length should be greater than 10


characters
2. Password should contain some uppercase and special
character.
3. mail id should be valid
Monitor Admin will be monitor all the activity of customer like
book the room, check room ,avaliability of rooms and
accessories according to the date.

Special Requirements 1. The admin must have a valid login id and


password to get in to the system.
LOGIN ACTIVITY OF CUSTOMER:-

OTHER ACTIVITY OF CUSTOMER:-


Use case name: Customer Signup and
Login
Use case id :1
1. Customer can Signup and login into RMS
website through any browser.
Description 2. After entering valid credentials he/she only
allowed to visit the website.
Actor Customer
Preconditions 1. Customer should have a valid email , id and
password.
2. Customer should have use a web browser.
Post conditions 1.Customer will be logged in
1. Customer open the browser and open the
particular application.
2. Customer should enter their valid credentials
to signup and login.
3. At the time of signing up customer should give
Work process of Customer the email address and password.
4. After giving the correct credentials ,then
customer must be able to see and search for
booking any rooms, accessories according to their
requirements.

Associated use case diagram

1. The customer must have a valid email id.


2. The password should be alphanumeric during
Exceptions sign up
3. The user id and password should be correct for
login.
Use case name:- Roles associated with customer
Use case id:2
1. In this use case diagram customer should be successfully
logged in to the website and search their appropriate
Description requirement.
Actor Customer
Preconditions 1. Customer must be logged into the system
Post conditions 1. After entering to the website by giving valid credentials,
customer will able to search many options as per their
requirement.
1. Customer should maintain a valid address
2. After entering into the system they are able to search rooms,
accessories and book or cancel the book according to
availability of rooms as per their requirement.
3. If any customer will face any problems at the time searching
rooms, book the rooms and other needful things. They will
Contact with our Admin.
Work process of 4. Our Admin process will 24*7 ready to help and clearing all
Customer doubts about the manage and booking the process.

Associated use case


diagram

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)

7.0 TECHNICAL SPECIFICATIONS:-


1. HARDWARE
 System type : 64bit operating system
 RAM : 8.00 GB
 Processor: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
2.42 GHz
 Mouse
 Keyboard

2. SOFTWARE
Operating system: windows 11
Programming Language: FRONTEND (React, JavaScript, HTML, CSS)
BACKEND (Springboot , MySql)

You might also like