Stolen Cars Repository

Software Requirements Specification

Version 1.0

Group Id: S22027D4DC

Supervisor Name: Komal Saleem

 Revision History
Date Version Description Author
(dd/mm/yyyy)
05-07-2022 1.0 Stolen Cars Repository is an online BC180402553
database system used to store
stolen car records in a database.
And it will also be useful for getting
information about any stolen car.
 Table of Contents

1. Scope (of the project)

2. Functional Requirements Non Functional requirements

3. Use Case Diagram

4. Usage Scenarios

5. Adopted Methodology

6. Work Plan (Use MS Project to create Schedule/Work Plan)

 SRS Document

1. Scope of Project:

Many cars are stolen these days. Some of them are in the police records, but most are not
in the records. And it has become very important to keep these records. Because many
cars are stolen in one day. The system will allow both the car owner and the police to
take advantage of online searches for stolen cars. In addition, if a person wants to buy a
car, he will be able to get information about the car from the database. Before buying a
car he will know if the car is stolen or not. And this database can be made available all
over the country.

2. Functional and non Functional Requirements:

2.1 Functional Requirements:

User panel:
• The login availability as user.
• New users sign up for the public will be created based on CNIC
no.
• Sign in page for downloading the facility of software and personal
help.
• Only registered users will be able to enter the record of his/her
stolen car.
• Cars could be searched by all types of users on the basis of the
Registration No, model, Chassis No, Engine No
Admin panel:
• Login availability as admin created based on CNIC no.
• Admin will maintain database for all public user and police.
• The administrator will maintain a database of all stolen cars..
• New entries in the list of stolen cars must be announced.
• Preparation of reports on stolen cars on daily and monthly basis.
• Graphical representation of data from the last 1 year.
• Recover stolen car information from all users.
• Cars could be searched by all types of users on the basis of the
Registration No, model, Chassis No, Engine No
Police panel:

• Login availability as police will created based on CNIC no..

• Police will be able to record the stolen vehicle.
• Updating any records on car recovery by police only.
• Cars could be searched by all types of users on the basis of the
Registration No, model, Chassis No, Engine No
2.2 Non-Functional Requirements:
• Operating System:
The software will run on all operating systems such as Windows
XP, Windows 7 and others.
• Usability:
The software will be easy to use so that e-learners can use it
without any hassle.
 Mmaintainability:
The software will be designed to make it easier to classify
errors and restore mechanisms.
 Flexibility:
The software will be flexible so that it can easily accept all
changes at low cost, time and experience.
 Security:
 The software will be safe. No one can use this application
without a registered username and password.
 Reliability:
 The system will support 7 X 24 operations.
 Performance:
Permission will be completed within 90% of one minute.
The average authorization time will not exceed 30 seconds.
 Access:
 The software will be accessible on the Internet.

3. Use Case Diagram(s):

4. Usage Scenarios:

Use Case Title Registration/Signup

Use Case Id 01
Actors User, Admin, Police
Description User, admin and Police can create New account to login to application
Pre Conditions The web application must be running, create a new account page must be available.
Exceptions None
Post Condition Action performed successfully
Author BC180402553

Modification 1.0
History
Modification Date 30-06-2022

Use Case Title Login

Use Case Id 02
Actors Admin, User, Police
Description Admin, User and Police shall need to login to use the application
Pre Conditions Application should in running condition. Login page should available
Exceptions None
Post Condition Action performed successfully
Author BC180402553
Modification 1.0
History
Modification Date 30-06-2022

Use Case Title Enter Record

Use Case Id 03
Actors User, Police
Description After registration users and Police can enter record
Pre Conditions User will registered and enter data
Exceptions None
Post Condition Action performed successfully
Author BC180402553
Modification 1.0
History
Modification Date 30-06-2022

Use Case Title Update/Delete Record

Use Case Id 04
Actors Admin, Police
Description Data will be updated by police and admin
Pre Conditions Admin and police can update recorded data after processing.
Exceptions None
Post Condition Action performed successfully
Author BC180402553
Modification 1.0
History
Modification Date 30-06-2022

Use Case Title Search Car

Use Case Id 05
Actors Admin, Police, User
Description Cars could be searched by all types of users on the basis of the Registration No, model,
 Chassis No, Engine No.
Pre Conditions Recorded car will search by all type of user.
Exceptions None
Post Condition Action performed successfully
Author BC180402553
Modification 1.0
History
Modification Date 30-06-2022

Use Case Title Report Status

Use Case Id 06
Actors Admin, User, Police
Description All types of user will check the report status.
Pre Conditions All types of users will check the reports by using car identity like as Registration No, model,
Chassis No, Engine No.
Exceptions None
Post Condition Action performed successfully
Author BC180402553
Modification 1.0
History
Modification Date 30-06-2022

Use Case Title Maintenance

Use Case Id 07
Actors Admin
Description Admin will maintain proper record of all types of user available in database
Pre Conditions Application should in running condition. Manage remedies page should available
Exceptions None
Post Condition Action performed successfully
Author BC180402553
Modification 1.0
History
Modification Date 30-06-2022

Use Case Title New entry Announcement

Use Case Id 08
Actors Admin
Description New entry announced from the admin.
Pre Conditions Application should in running condition.
Exceptions None
Post Condition Action performed successfully
Author BC180402553
Modification 1.0
History
Modification Date 30-06-2022

Use Case Title Generate Report Daily/monthly

Use Case Id 9
Actors Admin
Description Admin will be generating monthly and daily report of stolen cars.
Pre Conditions Application should in running condition.
Exceptions None

Post Condition Action performed successfully

Author BC180402553
Modification 1.0
History
Modification Date 30-06-2022

Use Case Title Create Graphic Report past 1 year

Use Case Id 10
Actors Admin
Description Admin will be generating past 1 year report graphical report of stolen cars.
Pre Conditions Application should in running condition.
Exceptions None

Post Condition Action performed successfully

Author BC180402553
Modification 1.0
History
Modification Date 30-06-2022

5. Adopted Methodology

"Methodology is a framework used to structure, plan and control the process

of developing an information system."
The Vu process model is a combination of waterfall and spiral model.
5.1 Waterfall model:
The waterfall model is a fast-paced model that will be introduced. This
model is also known as linear sequential or classic life cycle model.
This model is shown in the following diagram.

System
Requirements

System and
software Design

Implementation and
unit testing

Integration and system

It has of five steps:
i. System Requirements:
At this stage, system services, interruptions, and targets are established by
consolidating with system users. It is described in detail and serves as the details
of the system.

ii. System and Software Design:

In this stage, we will conceptualize overall system [Link] design phase
involves fundamental system abstraction and their relationships.
Implementation and Unit testing:
In this stage, the software design realized as a set of programs or a
program units .In unit testing we will verify that each unit must meet its
specifications.
iii. Integration and system testing:
At this stage, the individual program units or programs of the system are
integrated and tested with the complete system to ensure that the software
requirement is met. After testing, the software system was ready for the
customer.
iv. Operating and Maintenance:
At this stage, this software is the longest stage of the life cycle.
Maintenance means,
Correcting some errors that were not discovered in the early stages of
development.
5.2 VU Process Model:
This is a combination of waterfall model and spiral model. It is also called the hybrid
approach to system development. It has five phases that are gathering and analyzing
needs, planning, analysis and design, development and implementation. Services and
barriers to the need phase goals are established after interaction with the user. It also
maximizes system quality and minimizes any risks and errors.
5.3 Reason for choosing vu process Model:

1. The main idea of choosing is to get the benefits of these two models.
2. It is sequential model with backward repetition.
3. This is a sequential model with backward repetition.
4. We want to get the linear nature of the waterfall and the repetitive and risk
reduction nature of the spiral model.
5. In the Vu process model, we will work step by step to complete the given
project.

6. Work Plan (Use MS Project to create Schedule/Work Plan)