Software Requirements Specification

(SRS)
CAR SECURITY SYSTEM(CSS)

Authors:
Hamza Qureshi : 19-Arid-1203
Humna zaheer : 19-Arid-1191
Matiya-tur-Rasool : 19-Arid-1197

Introduction:
This Software Requirements Specification (SRS) document is to produce a comprehensive
description of all software requirements for a CAR SECURITY SYSTEM. The SRS is split
into subsections in which each presents a different topic to be discussed. Section 1 contains an
overview of the whole system, what purpose the project will have, and what will be targeted
specifically for the SRS. Section 2 depicts how the system will behave, what dependencies
the system will have, and will also explain the criteria that show that all goals have been met.
Section 3 gives the specific requirements for how our system is expected to behave and how
that behavior meets all the project goals. Section 4 contains the modeling of our system so
that when it is implemented, it will show how all of our classes will behave, and show how
the functionality will perform in the viewpoint of the users. Section 5, the prototype, explains
how our system will behave in given scenarios by showing the actions the system will take.
Section 6, the references, are all the resources that were mentioned throughout the SRS
document. Section 7 has a point of contact for this project.
 Stakeholders:
 Suppliers
 Customers
 Communities
 Investors
 Owners
 Media
 Environmental partners
 Public
 Business
 Users
 government

DESCRIPTION:
Project Description:
Our project category is web application based on information system in which we making an
application about car security. In which when your car lock is opened by someone or users the
owner get a notification on his/her mobile phone. If your car is in use by someone else the
location of your car show on your mobile. This application help the user or owner to save
his/her car by misused and reduce the cases of car stolen by thefts . This application has much
more features. With an advancement of smart technologies, the future of vehicle security
systems are changing into smart systems for various benefits. With this continuous
advancement, internet has become an integral part of one life where Things is the latest and
emerging internet technology that has changed the way one looks at things. Things is
developing everyday from small scale machines to large scale machines that can share data
and accomplish tasks while individuals are occupied with other activities. The main aim of
the project is to design a smart car security system, that is to turn a car systems to a smart car
security systems for accessing and controlling car using a mobile. To be specific, we aim to
design a light-weight, low cost, extensible, flexible wireless smart car security which
employs the integration of Radio Frequency Identification (RFID), Global Positioning System
(GPS), Global System for Mobile communication (GSM), wireless communication, cloud
networking, and fuzzy algorithm that is used for decision tree. This smart system is created to
provide car information such as position, time, alarm informed to the owner of the vehicle by
either using Short Message Service (SMS) or using mobile application. The combination of
the above technologies can be used as a smart car security key to control a car (lock or unlock
one car with the help of SMS) from remote locations. The complete system is designed
considering all types of cars by providing a simple, to provide car extreme security and it will
be a means for preventing, detecting and counter-measuring robbery of vehicles.

Problem statement:
As you have a brand new expensive car or you have a smaller, modest car that is a few years
old, you want to keep it safe. Your car is the way that you get to and from work, pick up the
kids, go grocery shopping, take trips, and go out on the town. Your car is not merely a
convenience. It is a necessity. Therefore, it is only natural that you want to do everything you
can to keep it safe. You make sure it is maintained and cleaned and that it is running well. As
you aren’t always there to make sure your vehicle is safe. It is unfortunate, but vandalism, car
burglaries, and car thefts happen more often than many realize. This means that car security is
highly important. As you likely rely so much on your car, it is important that you take steps to
improve your car’s security. Think for a moment just how much more of a hassle it would be
to do all of the things that you now take for granted. If someone were to steal your car, you
would not be able to go anywhere without calling for a ride. It would slow down your life and
quickly become frustrating. Even though you might have insurance and be covered, it will
still be a massive hassle. Even if someone were to break into your car and not steal it, you still
have to go through the process of getting the car repaired. Overall, it’s a hassle that no one
should have to deal with. By having the right tools to secure your car, that will be possible.
While most of the cars on the road today feature basic car alarms and car anti-theft devices
from the manufacturer, they are rarely enough. It is important to consider getting a car tracker
that can supplement your overall car security. When you have added protections, it will help
to keep your car safer. It can provide you with more peace of mind, as you will not have to
worry so much about what might happen to your car. You know you have the technology to
keep it safer and to track it down in the event someone does steal it.

Problem solution:
To solve this problem There are several basic types of car security systems available in this
project . You might find that you do not need to have just one of these systems. Instead, you
may want to consider some of the benefits that can come from having these types of systems
working together. A car alarm and a car tracker tend to work well together, for example.Car
alarms are still a very popular option and they tend to be available in most vehicles that have
been made in recent years. They may be passive alarms, which will be armed as soon as the
ignition turns off and the last door has been closed. There are also active systems, which
require that you press a button on your transmitter to arm and disarm the alarm. These are
simple to use alarms, and they can provide a loud siren whenever someone tries to break into
the car. However, many people today simply ignore car alarms when they hear them. They
can help to dissuade some thieves and vandals, but they are not a perfect solution. Car
trackers are another excellent option. There are a couple of types GPS trackers and trackers.
These can be highly beneficial because they are able to provide actual tracking of your car.
This lets you and the police know where the car is located, which will make tracking down
the criminals and recovering the vehicle easier. In some cases, these can be disabled easily. It
is therefore important to choose a quality tracker that will be able to alert you if someone
attempts to disable the device. The third type of option on the market is an immobilizing car
anti-theft device. After a thief has broken into the vehicle, they will need to be able to start the
car to take off. If they do not have a key to the car, they will have to hotwire it. An
immobilizing device will prevent the car from starting in case this happens. These are often
tied into tracking systems, but they are not a part of all tracking systems. These can work
well, but there may be a risk of the system being immobilized when it shouldn’t be.As you
can see, there are a number of problems associated with the various types of car security
systems. For the best protection, it is important that you take the time to look at all of the
options that are available and find those that will work best for your car.
1.1 Purpose:
This SRS document is to render comprehensive requirements of the CAR SECURITY
SYSTEM. It provides the primary requirements for the team of developers to complete their
tasks and will state how the goals will be met. This is to ensure clear verifiability with our
client. The intended audience for this document is for those that are familiar with automotive
software systems.

*Advantages/benefits of the solution:

One of the top options you will certainly want to consider is the Car Lock Car Security
System. This is a tracker that can provide a wealth of features and benefits that will help to
make it easier to keep your car safe. This security system will provide the owner with a range
of notifications regarding their vehicle. The system will know when someone has started the
car engine without you in the car and provide an alert. The system can also provide alerts for
unusual vibrations, such as when someone is trying to break into the car. It will send an alert
if the device has been disconnected and if the car is being moved. It can also provide real-
time tracking. The system keeps you fully updated about everything that’s happening with the
car, so you can alert the authorities if it is stolen.Your car will be much safer when you add
car tracking and a car alarm. By improving your car security, you can reduce the risks to your
vehicle. By concluding these all 1:The system is simple to design and easy to use
2. The system is reliable and consumes less power.
3. Installation of the system is very easy.
4. We get the exact co-ordinates of location. So there is no chance of errors.
5. Improved Security: From this system we can try to save our car by anywhere we are in this
global world. As this system gives us the information about the our car front doors
(open/close), anyone on the font sit, any type of vibration on the car, anyone try to start the
car and anyone take car by pushing or revolving. If anything is happened we can get the
information about all parameters including detected parameter. So this system is more
advanced and useful than the simple car security system which available in today market.
6. Better Customer Service: Here wet better service plus also benefited with cost wise because
its cost is very less compared to car cost.

1.2 Scope:
The scope of the project will only be the car security system. The goal of a car alarm is to
prevent the theft of your personal belongings within the vehicle and to prevent the theft of
the vehicle itself. That said, not all car alarms are the same. Some are triggered by different
actions and have different features.The application domain will be an embedded system for
automotive systems.CSS will brake the car at a corresponding speed depending on the
predicted time of the collision and alert the driver when the system is taking action. The
system will not maneuver out of the way of collision if the collision is imminent and is only
designed for security. If inclement weather affects the system performance, the driver will be
alerted.Camera can be interfaced to the current system. It will capture the image of
driver. In case of car theft, image of thief will be sent to the owner. By implementing
these car security system projects by using GPS , a car can be protected from thefts. In
future, this security system will be improved to function as an integrated-data-security
system for car communication systems. It would ensure that all the data exchanged
within the car and outside the vehicle is protected.
1.3 Definitions, acronyms, and abbreviations
Abbreviations:
● Pedestrian Collision Avoidance System (PCAS) - a system which can automatically
detect a potential forward collision and activate the vehicle braking system to decelerate
the vehicle with the purpose of avoiding or mitigating a collision
● Light Detection and Ranging (LiDAR) - a camera using image recognition to detect an
imminent crash.

1.4 Organization
The rest of the Software Requirements Specification is split into six parts. Section two gives
an overall description of the requirements. The functions of the system are described and any
constraints or assumptions about the system and its environment are given. Changes to be
made for future versions of the system are also included. It also includes a description of who
would use CSS. The following section, section three, lists out the requirements of the system.
These include system requirements and security requirements. Section four shows the
modeling requirements of the system. Several models are shown, including a use case
diagram, class diagram, state diagrams, and sequence diagrams which together demonstrate
how the system is designed to work and what scenarios it can be in. The next section details
the prototype of the system. A description of the prototype and how to use it are given as well
as an example scenario of the prototype. The final two sections give references used and a
point of contact for further information about the project.

2 Overall Description
This section will be focusing on describing the main functionalities and dependencies of
the Car Security system. Six divisions will be included:
● Product Perspective - The context of the CSS
● Product Function - Major functions that the software will perform
● User Characteristics - Background information about users of the system
● Constraints - Restrictions on the CSS to not be violated
● Assumptions and Dependencies - Assumptions made about the system or environment
● Apportioning of Requirements - Requirements to be addressed in future versions of the
CSS.

2.1 Product Perspective

CSS is an automobile safety system designed to prevent or reduce the severity of the collision
between car and pedestrian. The system uses all-weather radar or LIDAR and camera to
 detect an imminent crash with pedestrians. An object analyzing system is also included to
analyze data collected by the above sensors. Its main objection is to analyze if the detected
obstacle and trigger a wired brake if needed. The CSS can be a small part of Collision
Mitigation in the Advanced Driver Assistance System. In this CS system, only pedestrians
moving from the right side will be detected. The car brake will be triggered softly so that an
appropriate g-value will be applied to the car.

2.2 Product Functions

1. Camera scan environment: Camera is on when the car is started. It continually looks for
pedestrians in the surrounding environment and sends this information to the risk analysis
system.
2. LIDAR scan environment: LIDAR sensors are on when the car is started. They track the
motion of objects near the vehicle and track their path.
3. Risk Analysis: The risk analysis system will take both visual information and abstract
information from cameras and LIDARs. The system will use this information to determine
whether a pedestrian is at risk of entering the vehicle’s collision zone or not.
4. Wired brake: When the risk analysis system recognizes a pedestrian at risk of being hit by
the vehicle, a signal needs to be sent to the wired brakes of the car.
5. Driver override: Drivers have the ability to override the brake triggered by the CS system
by stepping on the gas pedal in the case of a miss-detection.
6. Alert driver: When the CS system takes action to prevent a collision, an alert will be sent
to the driver to warn them of the preventative measures being taken.
7. System auto on/off: The CS system will be turned off if the car is shut down or fully
stopped. It will only be on while the car is on.

Prevent pedestrian
collisions

Detect pedestrian
path

Accelerate vehicle
Brake vehicle when when pedestrian
pedestrian may will not enter
enter colliision collision zone

Driver can override Driver can override

Alert the driver
brakes by pressing acceleration by
when braking
gas pedal pressing brakes

2.3 User Characteristics

The user of the CSS is any driver operating a vehicle with CSS. The driver must be:
 A legally authorized driver.
 Able to pay attention while driving.
 Able to override the system when a missing trigger happens on the brake.
 Get your key fob and locate the lock button.
  The lock button might read "Lock" in small print or it may include a picture of a lock in
its locked position.
 Press the lock button once. Press it quickly and use pressure. Do not hold it down.
 Listen for a beeping sound. Some vehicles activate the alarm after one press of the
button. If it does not beep, you'll hear all of the doors lock. Press the lock button again
to activate the alarm.

2.4 Constraints
Safety-critical:
● The driver must have the ability to override the brake triggered by the system when a
miss detection happened.
● The system will not work if any camera or LIDAR is not operational.
Other constraints:
● The system will only focus on detecting pedestrians coming from the right-front side of
the car.
● Only one pedestrian will be detected by the CS system at a time.
● The system must be always on while the car is moving.
● The driver must be notified when a pedestrian is detected.
 When theif open the door a message comes to user.
 When anybody comes and check the doors the cars beeps .

2.5 Assumptions and Dependencies

The CS system would require there to be some type of camera and LIDAR sensors on the
vehicle that would be able to detect the surrounding objects/pedestrians around the carThe
system would also need to have access to the vehicle’s wire system. One assumption that can
be made would be that the pedestrian would be heading in a path that is perpendicular to the
vehicle’s path, either static or constant speed, that would be starting from the right-hand side
of the vehicle. There are a few things we can assume about the vehicle; the vehicle has a
width of 2 meters and that the vehicle would initially be at a steady-state velocity of 50 kph
(30 mph or 13.9 m/s). User interactions would be from the driver overriding the system by
performing some action, like pressing down on the brake pedal.

2.6 Apportioning of Requirements

Something that commonly occurs in vehicles, either manual or autonomous, is the jerking
motion due to stopping when detecting a pedestrian or some type of object in the vehicle’s
field of view. This is something that can be improved upon in future versions by simply
changing the mode of acceleration when the sensor detects a pedestrian or other object. One
way this can be accomplished is by having a setting that would have a name similar to
“comfort mode” where it will decrease the acceleration limits from 0.25g/0.7g
(acceleration/deceleration) to 0.18g/0.3g. Another requirement to be addressed in the future is
the detection of objects outside of pedestrians. This version of the CSS only stops for
pedestrians but future versions should stop for any obstacles in the path of the vehicle that
could prove dangerous if collided with. This would further improve the safety of the
passengers of the vehicle and people in other vehicles if the CS could detect any obstacle. It
would also make the system more desirable to have and could see more people getting
vehicles with this functionality.

3: Specific Requirements:
1. The system needs to be able to detect pedestrians that are in danger of colliding with the
vehicle.
2. The speed and position of the pedestrian need to be calculated from a sensor.
3. Pedestrian needs to be detected as early as 14 meters away to ensure the vehicle stops in
time.
4. In order to minimize vehicle downtime, the vehicle must slow down at a rate of at most 0.7
g without causing damage to the passenger.
5. The system must detect when the pedestrian is out of range of the vehicle so that the
vehicle can continue the motion.
6. Long-distance and high-frequency sensors always on for detection
7. Vehicle Brake by Wire System stops the car after detection.
8. Driver override ability in case the car stops when it shouldn’t need to.
9. Zero vehicle/pedestrian collisions for every test case.
10. Compatible with the current hardware of the vehicle.
11. The motion of the pedestrian can be static or in motion, can also change in velocity with
infinite acceleration.
12. When the pedestrian is moving, they are only moving at a right angle to vehicle path a
Size of the pedestrian will be a circle with a diameter of 0.5 m
13. When a pedestrian is avoided the vehicle velocity will automatically return to a steady-
state velocity of 50 kilometers per hour.
14. Works in any weather conditions, like rain, snow, fog, etc. and light intensity (sunny or
night).
15. Sensors should be able to view 360 degrees of its surroundings for potential back or side
collisions.
16. you’ll receive alerts when your system is triggered. You can view these alerts on any
Compustar LCD 2-way remote, such as the PRO T12 or the PRIME 901. This way, you’ll
know exactly when an alarm is triggered so you can quickly check on your vehicle.

Cybersecurity-Specific Requirements:
1. LIDAR sensors can be tricked by anybody by using a low power laser to fake an object is
near the car when in reality there is no car, causing the vehicle to stop. The system needs a
 way to pick apart when signals like these are being used and to avoid using the brakes in these
situations.
2. Since the brakes can be activated by a controller, external hackers can send incorrect
signals to the brakes from other car communication systems, if they exist, so the CSS needs to
be able to detect incorrect messages and prevent them from being sent.

4: Modeling Requirements:
Figure below shows the use case diagram for the system. The LIDAR sensor and the camera
will predict the path the pedestrian is taking and detect nearby pedestrians respectively.
Information from these use cases is used to evaluate the risk that the vehicle has of colliding
with the detected pedestrian. Evaluate risk also includes checking sensor conditions, which
ensures that the sensor information was accurate based on any environmental conditions, such
as weather or time of day, and also makes sure the sensors are still operational. If the risk is
high enough, a warning alert will be issued to the driver, indicating that the CSS is taking
emergency measures.
Information from the risk evaluation is then used to verify if the path is clear for the vehicle.
If it is not and the risk is too high, the CSS will activate the brakes on the car, preventing the
vehicle from hitting the pedestrian. If the path is clear and the car is free to regain motion, the
CS system will proceed to accelerate the car back to steady-state velocity. If the CSS makes
an incorrect decision, the driver will have the ability to override the CSS. The driver can step
on the brake pedal to slow the vehicle if the CSS fails to detect a pedestrian. They can also
accelerate the vehicle using the throttle if the CSS activates the brakes when no pedestrians
are present.
Use case Diagram

Car security system

Warn Test
ing sensor
alert condition
s
Predict
<<extend>>
pedestria
DRIVER n path
<<include>>

Override <<includes>>
PCAS Evaluate
risk

Accelerate LIDAR
car <<include>>

THROLLELE
<<include>> <<include>>
CONTROL <<include>> Pedestria
n
detection
Verify
Change
path is
speed
<<include>> Slow vehicle clear
down

BRAKES CAMERA

Use case predict pedestrian path

Actors LIDAR
Description Calculates the direction a pedestrian is
travelling and in what direction in order for
the system to take appropriate
 action,potentially stopping the car.
Type primary
Includes None
Extends None
Cross refs 1,2,5,6,15
Use cases If use case evaluate risk detects a
pedestrian ,predicts their path.

Use case Pedestrian detection

Actors camera
description The camera will detect if an approaching
object is a pedestrian or not.if the camera
detects a pedestrian, the CSS will slow the
car down.
type primary
Includes None
Extends None
Cross refs 1,3,6,15
Use cases Send information to use-case evaluate risk if
a pedestrian is detected.

Use cases Evaluate risk

Actors None
Description Camera and LIDAR combined will detect
pedestrians and where they are relative to the
car,giving an overall report as to the action
the CSS shall take.
Type Primary
Includes Test sensor conditions,predicts pedestrian
path, detect pedestrian
Extends None
Cross refs 1,5,6
Use cases Always activate use-case test sensor
conditions.send risk assessment to use-case
verify path is clean.
Use cases Test sensor conditions

Actors None
Description The system makes sure that the sensor are in
working order no matter what outside
condition and if a problem arises, alerts the
driver while shutting off the braking system.
Type Primary
Includes None
Extends None
Cross refs 6,14
Use cases None

Use cases Verify path is clear

Actors None
Description Uses information from sensors to determine
whether the pedestrian is out of the way and
the car is free to move.if a pedestrian is seen
by the sensors,the brakes are triggered and a
warning alert is sent to the driver.when the
path is clear , the car returns to steady-state
velocity.
Type Primary
extends None
Includes Evaluate risk
Cross refs 5,7,13
Use cases Send use-case warning alert to the driver if
the path is not clear.if the path is not
clear,activate either accelerate car or slow
vehicle down use-cases.

Use cases Warning alert

Actors Driver
Description The system alerts the driver if a pedestrian is
detected and the car takes action or if the
sensors are faulty.
Type secondary
Includes None
Extends Evaluate risk
Cross refs 8
Use cases If there is a risk,get information from use-
case evaluate risk and let the driver know
about the risk.

Use cases Accelerate car

Actors Driver
Description If the driver overrides the brakes or if the
system detects that the pedestrian is out of
the way of a collision,the car will accelerates.
Type primary
Includes None
Extends None
Cross refs 5,13
Use cases Change speed

Use cases Override CSS

Actors driver
Description After a delay,if the brake system does no
deactivate when it should,the driver can press
on the pedal and accelerate the car.the driver
can also slow down the car if CSS fails to
detect a pedestrian.
Types Secondary
Includes Change speed
Extends None
Cross refs 8
Use cases If the driver activates brake or gas
pedal,activate the use-case change speed.
Use cases Change speed

Actors Throttle control,brakes

Description If the car needs to slow down in case a
pedestrian is in the path of the vehicle or the
car needs to speed up to return to steady-state
velocity,CSS can change the velocity of the
vehicle.
Type Primary
Includes Accelerates car,slow vehicle down
Extends None
Cross refs 4,5,7,10,13
Use cases None

The class diagram for the CSS is shown in figure, which describes the key elements of the
system and their relationships with other elements. The overall CS system contains the
LIDAR sensor and the Camera, which individually gather object data. The Camera is able to
detect whether an object is a person or not by using machine learning to pick apart human
features and make a decision based on the collected information. The LIDAR sensor can pick
up the direction, position, and speed of an object. This information combined is sent to Risk
Analyzer, which is software that determines if the pedestrian is at risk or not. If the pedestrian
is found to be at risk of collision with the vehicle, Risk Analyzer will trigger the braking
system and start slowing the car down.
The Driver will receive an alert from Risk Analyzer that warns the CSS is taking measures to
prevent a collision. Risk Analyzer acts directly with the Brake to bring the car to a halt. The
Driver can override the decision if the Brakes are falsely activated by pressing on the gas
pedal, triggering Throttle Control. Throttle Control decides the amount the vehicle should
 accelerate based on the amount the driver presses on the gas pedal. If the Driver performs this
action, the CSS decision can be overridden by the Throttle Control..

Throttle control Overrides

CSSystem
Controlspeed(intensity :float():void
Overrides Status: bool
PCASOverride():void

Camera
Activates Detectpedestrian(object):b LIDAR
ool
Gatherinformation(object)
:vector<>

Object
Detects
Position:vector
Get information
Speed:float from
Driver
Alert
Direction:float
Pressgas():float
Alert Status:
bool Pedestrian: bool Send information to
Pressbrakepedal():float

Activates
Controls Send
information

Risk analyzer
Brake

Status :bool
Acceleratescar(riskfactor:int):void

CSSoverride():void Activatebrakes(riskfactor: int):void

Triggers
Slowcar(intensity:float):void Calculaterisj(speed:float,direction:float,position
:vector<>):int

Testsensor():void

Class diagram for CSSystem

Elements Name Description

Alert Alarms driver if a pedestrian is close to

collision or sensors are falling.
Attributes
Status: tool If true,the alert system is in
the on state.if false,the alert
system is off.
Relationships Alarms the driver if needed,takes input from
object analyzer.
UML extensions

Element name Description

Brake Activates a wire system inside inside of the

vehicle that reduces the velocity of the
vehicle.
Attributes
Status :tool If true, the brakes are
activated and the car is
slowing/stopped.if false ,the
brakes are deactivated.
Operations
CSS override():void Overrides any decision made
by the CSS and activates
brakes.
Slow car(intensity Slows the car down
:float):void proportionately to how much
the driver or CSS designs.
Relationships If the object analyzer detects that the car
needs to stop,it will apply the brakes.the
driver can activate the brakes to slow down
the car if needed.
UML Extensions

Element name Description

Camera Camera sensor that detects pedestrians that

may be of risk with colliding with the
vehicle.
Operations
Detect pedestrians If true, a detected object is a
(objects):tool pedestrian.if false the object
is not a pedestrian.
Relationships The camera is one of the sensors that make
up the CSS.the camera searches for
pedestrians near the vehicle path.if it finds
one,it is reported to risk analyzer.
UML Extensions

Element name Description

Driver Operator of the vehicle.can make override

 decisions if CSS acts unaccordingly.
Operations
Press gas():float Driver presses the gas pedal a
certain amount to accelerate
the car.
Press brake pedal():float Driver presses the brakes to
slow the car down.
Relationships Receives cues from the alerts system to know
if the CSS is taking emergency measures.can
accelerate the car by using throttle control
and can use brakes to slow down the car.
UML Extensions

Element name Description

LIDAR LIDAR sensor that detects objects and

calculate where they are in relation to the car
and their velocity.
Operations
Gather Gets the speed,direction,and
information(pedestrian):vector<> position of an object
Relationships LIDAR is part of the CSS.Information from
the object is used by the LIDAR to figure out
how far said object is from the vehicle as well
as the direction they are facing and their
speed.
UML Extensions

Element name Description

Object An object near the vehicle that has CSS.

Attributes
Is pedestrian():tool Dictates if the object is a
pedestrian or not.
Position:vector< > A value containing
coordinates of where the
object is relative to the car.
Speed: float The speed value of the
object.
Direction: float The angle relative to the car
that the object is moving.
Relationships Camera and LIDAR both retrieve
information from the object,which is sent to
the risk analyzer if the object is a pedestrian.
UML Extensions

Description

The system that determines whether a

pedestrian is in danger of colliding with the
vehicle or not and how to respond.
Attributes
Status:tool If true,the system is on.if
false,the status is off.
Relationships Contains the sensors,LIDAR and camera,that
determine information about pedestrians in
the path of the vehicle. Throttle control and
brake can override the CSS if the driver
deems necessary.
UML Extensions

Elements name Description

Risk analyzer Software that takes information from the

LIDAR and camera sensors and calculates
the risk of a pedestrian colliding with the
car.from there,it can activate the brakes or the
speed the car up,and can test if the sensors
are working properly.
Operations
Accelerate car(risk factor Based on the risk of the car
:int):void hitting the pedestrian,the car
can be accelerated.
Activate brakes(risk factor: Based on the risk of the car
int):void hitting a pedestrian,the
brakes can be activated.
Calculate risk (speed:float Returns a risk factor,value
direction:float,position:vector indicating the risk that a car
< >):int will hit a pedestrian,based on
the speed,direction,and
position of the pedestrian.
Test sensor():void Tests the sensors to indicate
if they are working
properly.activates the alert if
they are not.
Relationships Takes in information from the camera and
LIDAR outputs to alert,brake,and throttle
control to determine whether they need to be
activated or not.
UML Extensions

Element name Description

Throttle control The throttle used to accelerate the car.

Operations
Control speed (intensity: Accelerates the car as
float): void determined by the CSS or
driver.
CSS override():void Overrides any decision made
by the CSS and activates the
throttle.
Relationships Overrides the braking system if the car needs
to accelerate.
UML Extensions

There are three main scenarios that the CSS can encounter. The first scenario is shown by the
sequence diagram in figure , where a person is moving and will enter the vehicle’s collision
path. The Camera will detect pedestrians and the LIDAR sensor will predict pedestrian path.
Risk Analyzer then takes information from these two sensors and evaluates the risk of a
collision. The risk is calculated and CSS makes the decision to trigger the brakes to slow the
car down. After the car brakes are activated, the LIDAR sensor will continue to predict the
pedestrian path. The Risk Analyzer will evaluate the risk and once there is no more risk, the
Throttle Control will be activated and the car will accelerate back to steady-state velocity.
The next sequence diagram in figure shows a scenario where a person is stopped, then begins
moving towards the vehicle. The Camera and LIDAR sensor detects a pedestrian and predicts
their path respectively. This information is then sent to the Risk Analyzer, which evaluates
the risk of the vehicle hitting the pedestrian. No risk is detected, so the Throttle Control
continues to keep the car speed steady by accelerating it. The LIDAR continues to predict the
pedestrian path and that data is sent to Risk Analyzer. Since the person has begun to move,
the Risk Analyzer recognizes the risk and notifies the Brake to slow the car down.
The third scenario in figure depicts a scenario where the CSS detects a static pedestrian
outside of the collision path. The camera detects the pedestrian and the LIDAR predicts their
path. The Risk Analyzer uses this information to calculate the risk and determines no risk is
present, so the Throttle Control continues to operate. Since the person does not move after
this point, no further events occur in the system for this scenario.
Figure shows the state diagram for the CSS. When the car turns on, CSS becomes active. The
state it starts in is Scan Environment, where the LIDAR and cameras are looking for any
pedestrians that may be at risk of collision. In this state, the driver can override the CSS by
pressing on the brake pedal, sending it to the state Car Stopped, where the PCAS is not
scanning for pedestrians. The driver can give control back to CSS by stepping on the gas
pedal. The environment will continually be scanned until the LIDAR begins to gather
information about an object near the collision path. This will cause CSS to enter the
Evaluating Object state, where it is deciding if an object is a person or not using object
recognition software. If the object is not a pedestrian, it will go back to scanning. If it is, the
brakes will be activated, and the alert system will turn on.
When a pedestrian is detected near the collision path, the state the system is in is Wired
Brakes On. Here,CSS will activate the brakes, slowing the car eventually to a halt, and will
gather information about the pedestrian until it can determine the person is no longer in
danger of being hit. While the brakes are on, the risk will be calculated until there is no risk,
in which the car will accelerate and the alert system will shut off, bringing the system back to
the scanning state. This can also occur if the driver presses the gas pedal. During any state, if
the car is turned off, the CSS system turns off.

Press gas()
CS System status==false press brake pedal()
Car stopped
Scan
Press brake pedal()
enviroment

Detect pedestrian()=0
Gatherinformation() calculate=0

Evaluating
object
Press gas()/=0

Detect pedestrian==1

Wired brakes
on
Calculate risk()>0

CS System state diagram

The state diagrams for Brake and Alert are shown in figures respectively. Brake begins with
“status” equal to True, indicating the brakes are activated. If Driver presses the gas pedal or
the Risk Analyzer sends the signal to Throttle Control to accelerate, the status of Brake
becomes False. This means the vehicle is currently in motion and the brakes are off. Once
Driver presses on the brake pedal or Risk Analyzer activate the brakes, the status of Brake
returns to True.
Alert begins in the off state since there is no warning to issue to the Driver. When Risk
Analyzer detects a situation where a pedestrian is at risk, it will activate the brakes. This
sends a signal to Alert and changes the status to True, causing an alert to be sent to the Driver.
Once Risk Analyzer concludes that the situation has been mitigated, it sends a signal to
accelerate the car. This also ends the alert to the driver, and the status of Alert is switched
back to False.

Activate car(risk factor : int)o pressgas

Status : ture Status:false

Acceleration brakes(risk factor: int)

Brake state diagram

Activate brakes(risk factor : int)

Status : false Status:true

Acceleration car(risk factor: int)

Alert state diagram
In figure the state diagram for the Risk Analyzer is shown. When the CSS is activated, Risk
Analyzer is in the Inactive state, where it is performing no function. Once the LIDAR detects
an object approaching the collision path and the camera recognizes the object as a person,
Risk Analyzer enters the Determine Risk state, where it gathers the information from the
LIDAR and camera and evaluates whether action needs to be taken by the CSS or not. If the
risk calculated is greater than zero, the brakes are activated and the Risk Analyzer stays in the
Determine Risk state.
There are two ways for the Risk Analyzer to exit the Determine Risk state and return to the
Inactive state. One such way is when the risk is calculated to be zero, meaning the person has
successfully avoided the path of the vehicle. During this transition, the car is accelerated,
returning it to its steady-state velocity of fifty kilometers per hour. Another way to enter the
inactive state is when either the driver presses the gas or brake pedal, overriding the decisions
made by the Risk Analyzer. These transitions give no output.
 Calculate risk>0/

Detect pedestrian==1and gather Information() active brakes

Determine
Calculate risk>0/acceleratecar()
inactive
risk

Press gas() or press break pedal()

Risk analyzer state diagram

5: Prototype:
The prototype demonstrates various scenarios that CSS will encounter and how the system
operates under those conditions. The user can select from different options that detail
different attributes of a pedestrian near a car that has CSS and the prototype will demonstrate
how the CSS operates using pictures and descriptions. It will show what the input from the
sensors is and what decisions the CSS makes based on the risk of a person being hit by the
vehicle with the onboard system.

5.1 How to Run Prototype:

In order to start the prototype, you must choose between one of the three scenarios; static,
moving then static, or static then moving. Once you choose one of the three scenarios you are
shown a picture or pictures which have a description of what is happening in the picture. You
then are given the option to choose between how you want the scenario to continue. In the
case of static, you are given the three options of how far to the right of the vehicle you want
the pedestrian to be; in front of the car, 2 meters away from the car, and 4 meters away from
the car. Once you choose one of those options you then click the submit button and the
prototype shows you the complete scenario. If you want to choose a different scenario, click
the submit button next to the drop-down menu.

5.2 Sample Scenario:

The system begins with the car driving down a straight road. A person is walking towards the
collision path of the vehicle.The person is detected by the sensors to be at risk of getting hit
by the vehicle. A warning is issued to the driver, indicating that preventative actions will be
taken by the CSS. The CSS triggers the wire brakes, stopping the vehicle before any collision
can occur. The car will accelerate again once the pedestrian is outside of the collision zone

6:Reference:
7:Point of Contact:
For further information regarding this document and project, please contact Arid uni
students(BSSE-3 HAMZA QURESHI,HUMNA ZAHEER,MATIYA). All materials in this
document have been sanitized for proprietary data. The students and the instructor gratefully
acknowledge the participation of our industrial collaborators