Software Dev Tools Documentation

INTRODUCTION
This software requirements document provides complete software development tools specification
information about A road camera image management platform or system. n the following sections we
are going to look at
1) The overall project description

- Use case model survey
- Actor survey
2) Constraints
3) Requirements
- Functional requirements
- Non functional requirements
4) Testing
I. PROJECT DESCRIPTION
Road camera image management platforms are used to store, manage, and analyze images
captured by road cameras. These platforms can be used for a variety of purposes, such as traffic
monitoring, incident response, and security.
Images are a very good way of keeping events that happened in the past for referral. They are
very reliable and now with digitality have become very durable ( can be kept in storage devices
for as long as they are needed ). Hence a road camera image management system is one of the
most reliable methods of surveillance and achieving of events through images and can be used
extensively In the fields of monitoring , incident response , security just to name a few.
The system in question comprise of intelligent cameras that take pictures after detecting specific
events that can be precised or specified by the customer depending on the task to be
performed. These images can now be when taken can later be analised by a central analystic
system to check relevancy , issue targeted reports to desired authorities (such as police
authorities in case criminality detection) and classification for storage in a database.
I.1. Use Case model
For our road image management system in question, It is very important to lay down some
specifications as to who uses the system and how they use the system as shown in the use case
diagram below
II. CONSTRAINTS
We have the following constraints for the realization of our project

- Camera is very important constrai. If it does not work no image will be
captured from the environment and thus both image processing part and the processing system
will be useless
- Strong and efficient AI algorithms will be very crucial in deciding the type , time and rate of
the pictures taken
- Huge amount of storage to store all the pictures for future reference
- Power sources to ensure that the cameras always stay on
- Strong and durable devices that can function at all wheather conditions outdoors
- Cost of the hardwares should be in a reasonable margin to be affordable.
III. REQUIREMENTS
This section contains all of the software requirements to a level of detail sufficient to enable
designers to design a system to satisfy those requirements, and testers to test
that the system satisfies those requirements. The section includes two subsections which are
Functional Requirements and Nonfunctional Requirements.
III.1. Functional requirements

Functional requirements for a road camera image management platform include:
➢ The ability to store and manage images from a variety of camera sources
➢ The ability to search and filter images based on criteria such as date, time, location, and
vehicle
type
➢ The ability to export images in a variety of formats
➢ The ability to integrate with other systems, such as traffic management systems and
incident
response systems
➢ The ability to handle a high volume of images and provide realtime or near-real-time
access to images. This is important because road camera image management platforms are
often used to monitor traffic conditions and identify incidents. If the platform cannot keep
up with the volume of images being generated by the cameras, or if it takes too long to
display images, it will not be effective in helping organizations to monitor and manage
traffic.
➢ Ease of use refers to the platform's user interface and how easy it is to learn and use. This
is
important because road camera image management platforms are used by a variety of
users,
including both technical and non-technical users. The platform should have a user-friendly
interface and intuitive controls so that all users can easily access and use the information
they
need.
➢ Absence of defects refers to the platform's freedom from errors and bugs. This is
important
because defects can impact the platform's functionality, performance, and security. If the
platform has defects, it may not be able to perform its intended functions correctly, or it
may be
vulnerable to security attacks.
All three of these requirements are important for ensuring that a road camera image
management
platform is effective and meets the needs of its users.
Functional Requirement in Depth
A more precise functional requirement for a road camera image management platform
might be:
The platform must be able to display real-time images from all cameras within 500
milliseconds.
This requirement specifies a performance requirement for the platform. It states that the
platform must
be able to display images from all cameras within a certain amount of time.Another
functional requirement for the platform might be:
The platform's user interface must be easy to navigate for users with no prior experience
with road
camera image management systems.
This requirement specifies an ease-of-use requirement for the platform. It states that the
user interface
must be easy to use for even novice users.
Finally, a functional requirement for the platform might be:
The platform must be free of defects that could impact its ability to display real-time images
from all
cameras.
This requirement specifies an absence of defects requirement for the platform. It states that
the
platform must not have any defects that would prevent it from performing its intended
function of
displaying real-time images from all cameras.
III.2. Non Functional Requirements
Non-functional requirements for a road camera image management platform include:
➢ Performance: The platform must be able to handle a high volume of images and provide
realtime or
➢ near-real-time access to images.
➢ Scalability: The platform must be scalable to support a growing number of cameras and
images
➢ Reliability: The platform must be reliable and available 24/7
➢ Understandability: The platform should be easy to understand and use for all users, including
both technical and non-technical users.
➢ Efficiency: The platform should be efficient in terms of time and resources. It should be able
to
process and display images quickly, and it should be easy to scale to support a growing number
of cameras and images.
➢ Security: The platform should be secure and protect images from unauthorized access. It
should
use encryption and other security measures to protect images from being intercepted or
tampered with. Sure. Here is an example of a non-functional requirement for maintainability for
a road camera image management platform:
➢ Maintainability: The platform's code must be well-organized and documented to facilitate
future maintenance and updates. This requirement specifies that the platform's code should be
written in a way that is easy to understand and modify. This will make it easier for developers to
maintain and update the platform in the future. Here is another example of a non-functional
requirement for maintainability: The platform must use a modular architecture to facilitate the
addition of new features and functionality. This requirement specifies that the platform should
be designed in a way that makes it easy to add new features and functionality without
disrupting the existing codebase. This will make the platform more maintainable in the long run.

Software Dev Tools Documentation

Uploaded by

Copyright:

Available Formats

Software Dev Tools Documentation

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

Software Dev Tools Documentation

Uploaded by

Copyright:

Available Formats

INTRODUCTION

1) The overall project description

I.1. Use Case model

We have the following constraints for the realization of our project

designers to design a system to satisfy those requirements, and testers to test

Functional Requirements and Nonfunctional Requirements.

III.1. Functional requirements

Non-functional requirements for a road camera image management platform include:

➢ near-real-time access to images.

➢ Reliability: The platform must be reliable and available 24/7

both technical and non-technical users.

of cameras and images.

a road camera image management platform:

➢ Maintainability: The platform's code must be well-organized and documented to facilitate

You might also like