SRS Stolen Cars Repository

It becomes very important to maintain the record of stolen cars now a days, as in Pakistan, many cars are stolen on a daily basis. Law enforcement agencies, and people whose car has stolen will take benefit from it by checking cars online. Moreover, before buying a car, it would be a great idea to check it in a database. We will manage the record of stolen cars in any city.

Scope of Project Stolen Cars Repository:

Project scope is the part of project planning that involves determining and documenting a list of specific project  goals, deliverables, tasks, costs and deadlines. Defining the project scope involves adopting a clear vision and an agreement on the outcomes of the project. This allows each milestone of the project to stay on target

Functional and Non Functional Requirements of Stolen Cars Repository:

Functional Requirements :

A functional requirement shows that what the system must do what services the system present to users. It describes a software system or its component. A function is nothing but inputs to the software system, its behavior, and outputs

Functional Requirements of Stolen Cars Repository:

User panel:
1. The login availability.
2. Login for the public will be created based on CNIC no.
3. User will be able to enter the record of his/her stolen car.
Admin panel:
1. Login availability.
2. Admin will maintain database for all user’s.
3. Admin will maintain database for all stolen cars.
4. An announcement should be made upon a new entry in the list of stolen cars.
5. Generation of reports regarding stolen cars on a daily and monthly basis.
6. Graphical representation of data for the past 1 year.
7. The retrieval of stolen car information by all users.
Police panel:
1. Login availability.
2. Police will be able to enter the record of a stolen car.
3. Updating any record upon recovery of a car by police only.

NON-FUNCTIONAL REQUIREMENTS Stolen Cars Repository:

• Application is user friendly.
• Application Perform fast manipulation and calculations.
• Application is adaptable.
• Application will be able to work on all types of operating systems.
• Application will be capable to handle multi user activities simultaneously.
• There will be back up system to face any problem in system
• All the options should be learning friendly I.e. member could easily understand what that option will do if he clicked on it.
• Response Time is very awesome.

Some others are:

• Accessibility
• Maintainability
•  Fault Tolerance.
• Security
• Robustnes

Use Case Diagram of Diagnosis of Stolen Cars Repository

a use case diagram can summarize the details of your system’s users   and their interactions with the system. Scenarios in which your system or application interacts with organizations, people, or external systems. Goals that your system or application helps those entities achieve

Usage Scenarios Diagnosis of Stolen Cars Repository:

A brief user story explaining who is using the system and what they are trying to accomplish. A Scenario is made up of a number of simple, discrete steps that are designated as being performed by either the System or a  User.

ADOPTED METHODOLOGY for Stolen Cars Repository:

The adopted methodology for this project is vu process model. Vu process model is a combination of water-fall model and spiral model. This combination has many advantages. This model has high risk analysis so avoidance of risk would be achieved. This model is easy to understand and use. Now first we will discuss the Water-fall model.

Work Plan of Diagnosis of Stolen Cars Repository:

Work plan

for complete srs contact us

watsapp: 03469806607