SRS - Online Car Rental System 1

SOFTWARE REQUIREMENTS SPECIFICATION TITLE:
ONLINE CAR RENTAL SYSTEM

INDEX
1. Introduction……………….………………………………………………3
1.1 Purpose……………………………………………………………..3
1.2 Document Conventions…………………………………………….3
1.3 Intended Audience and Reading Suggestions……………………...3
1.4 Product Scope……………………………………………………...4
1.5 References……………………………………………….…………4
2. Overall Description………………………………………………………4
2.1 Product Perspective………………………………………………..4
2.2 Product Functions………………………………………………….4
2.3 User Classes and Characteristics…………………………………..5
2.4 Operating Environment……………………………………………5
2.5 Design and Implementation Constraints…………………………..5
2.6 User Documentation………………………………………………5
2.7 Assumptions and Dependencies…………………………………..6
3. External Interface Requirements………………………………………6

3.1 User Interfaces………………………………………………….…6
3.2 Hardware Interfaces…………………………………………….…6
3.3 Software Interfaces………………………………………………. 6
3.4 Communications Interfaces……………………………………….6
4. System Features………………………………………………………6&7
4.1 System Features one by one……………………………………6&7
5. Other Nonfunctional Requirements…………………………………….7

5.1 Performance Requirements………………………………………..7
5.2Security Requirements….………………………………………….7
5.3Safety Requirements….……………………………………………7
5.4Software Quality Attributes.….……………………………………7
5.5Other Requirements………….…………………………………….7
1. Introduction
A voting system is a crucial aspect of any democratic society. It is a method used to

gather and count votes in an election or referendum. A reliable and secure voting system is
necessary to ensure the fairness and accuracy of the election process. This document presents a
Software Requirements Specification (SRS) for a voting system.
1.1 Purpose
The purpose of this SRS is to specify the requirements for an electronic voting system
that will provide a secure and reliable means of conducting elections.
1.2 Document Conventions
GUI-Graphical User Interface
DBMS-Database Management Systems
CRMS-Car Rental Management System
SQL-Structured Query Language
1.3 Intended Audience and Reading Suggestions

This document is intended for the following group of people: -
● Developers for the purpose of maintenance and new releases of the software
● Documentation writers
● Testers
1.4 Product Scope

The electronic voting system will be designed to facilitate the process of voting by
enabling eligible voters to cast their votes electronically. The system will ensure that only
authorized voters are allowed to vote, and that each voter can only vote once. The system will
provide a secure and tamper-proof means of storing and counting votes, and will generate
accurate and timely results.
1.5 References
● IEEE Software Requirement Specification format.
● www.google.co.in
2. Overall Description
2.1 Product Perspective
The electronic voting system will consist of a web-based application that will allow
eligible voters to log in using their unique identification number and cast their vote. The system
will be designed to prevent multiple voting, protect against unauthorized access, and ensure the
accuracy and integrity of the voting process.
2.2 Product Functions

The electronic voting system will provide the following functions:
● Eligible voters can log in to the system and cast their vote electronically
● The system will prevent unauthorized access and ensure that each voter can only vote
once
● The system will store and count votes in a secure and tamper-proof manner
● The system will generate accurate and timely results that can be verified by authorized
stakeholders
2.3 User Characteristics
The primary users of the electronic voting system will be eligible voters who have a
unique identification number. The system will also be used by election officials and
administrators who will manage voter lists, candidate lists, and election results.
2.4 Design and Implementation Constraints

The information of all voters must be stored in a database that is accessible by the website.
MS SQL Server will be used as SQL engine and database.
Users may access SVS from any computer that has Internet browsing capabilities and an Internet
connection.
Users must have their correct usernames and passwords to enter into their online accounts and do
actions.
2.5 Assumptions and Dependencies

● The Applicants and Administrator must have basic knowledge of computers and the
English language.
● Each user has an account created and authenticated by admin. This Website can be
accessible within the company's intranet and other users can see all details about the
franchisee. Each user has to first login. No user can share their username and password to each
other.
3. External Interface Requirements

3.1 User Interfaces
All the users will see the same page when they enter this website. This page asks the users a
username and a password.
After being authenticated by the correct username and password, users will be redirected to their
corresponding profile where they can do various activities.
The user interface will be simple and consistent, using terminology commonly understood by
intended users of the system.
3.2 Hardware Interfaces
The system will use the standard hardware and data communication resources. The System must
run over the internet, all the hardware shall require to connect internet will be hardware interface
for the system.
3.3 Software Interfaces

The system is on server so it requires the any scripting language like PHP, VBScript etc.
The system requires Database also for the store the any transaction of the system like MYSQL
etc.
At the last user need web browser for interacting with the system.
3.4 Communications Interfaces

A database connection is required to save registered user data and voter details.
4. System Features
Login
The user enters a username and password. If enter details are valid, the
user account becomes available.
Vote
When a user has successfully login, he can vote successfully.
Check Status
The user can check the status of his registration and vote. The system displaces the status
information to the user.
Notifications
The user may receive the updates of the status via message or mail.
5. Other Nonfunctional Requirements
5.1 Performance Requirements

The system response time for every instruction conducted by the user must not exceed a
minimum of 10 seconds. The system should have high performance rate
5.2 Security Requirements

The main security concern is for user’s accounts and proper login mechanisms should be
used to avoid hacking. The system must automatically log out all customers after a
period of inactivity.
The system’s back-end servers shall only be accessible to authenticated administrators. Sensitive
data will be encrypted before being sent over insecure connections like the internet.
5.3 Safety Requirements

User login information should be securely saved into the database without any changes in
information.
5.4 Software Quality Attributes

Usability: The system should have a user-friendly interface, with clear navigation, intuitive
interactions, and appropriate feedback mechanisms.
Reliability: The system should be reliable, ensuring that it operates consistently and accurately.
It should minimize the occurrence of errors
Performance: The system should be responsive and performant, providing quick response times
and efficient usage of system resources.
Security: The system should be secure, protecting sensitive user data such as personal
information, payment details, and booking records.
Scalability: The system should be able to scale effectively to accommodate increasing user loads
and growing data volumes.
Maintainability: The system should be designed and developed in a way that facilitates easy
maintenance and future enhancements.
Compatibility: The system should be compatible with different web browsers, operating
systems, and devices to ensure a wide range of users can access and use the system without any
issues.
Availability: The system should have a high level of availability, minimizing downtime and
ensuring that users can access the system when needed.
5.5 Other Requirements
Notifications and Communication:
● The system should send email or SMS notifications for booking confirmations,
reminders, and updates.
● Users should be able to communicate with car owners/administrators through
messaging or chat functionality.
Rating and Feedback:
● Users should be able to provide ratings and feedback for their rental experience.
● The system should display average ratings and reviews for car owners and their
vehicles.
Integration with Third-Party Services:
● Integration with payment gateways for secure online transactions.
● Integration with SMS/email service providers for notifications.

SRS - Online Car Rental System 1

Uploaded by

Copyright:

Available Formats

SRS - Online Car Rental System 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SRS - Online Car Rental System 1

Uploaded by

Copyright:

Available Formats

SOFTWARE REQUIREMENTS SPECIFICATION TITLE:

ONLINE CAR RENTAL SYSTEM

3. External Interface Requirements………………………………………6

5. Other Nonfunctional Requirements…………………………………….7

A voting system is a crucial aspect of any democratic society. It is a method used to

1.2 Document Conventions

GUI-Graphical User Interface

DBMS-Database Management Systems

CRMS-Car Rental Management System

SQL-Structured Query Language

1.3 Intended Audience and Reading Suggestions

1.4 Product Scope

2.2 Product Functions

2.3 User Characteristics

2.4 Design and Implementation Constraints

2.5 Assumptions and Dependencies

3. External Interface Requirements

3.2 Hardware Interfaces

3.3 Software Interfaces

3.4 Communications Interfaces

5. Other Nonfunctional Requirements

5.1 Performance Requirements

5.2 Security Requirements

5.3 Safety Requirements

5.4 Software Quality Attributes

You might also like