Proj-2013-2014-Cannonball-de-Voitures-Autonomes/SRS

Document History

	Version	Date	Authors	Description	Validator	Validation Date
	0.1.0	TBC	TBC	TBC	TBC	TBC

1. Introduction

1.1 Purpose of the requirements document

This Software Requirements Specification (SRS) identifies the requirements for the autonomous car. In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves.

1.2 Scope of the product

The project is divided into two parts.

• The first one is about developping an app able to recognize and interprate marker.
• The second is the elaboration of algorithms to make a remote controlled car autonomous.

1.4 References

The main page of the project: Proj-2013-2014-Cannonball-de-Voitures-Autonomes<br\> The Arduino playground page.<br\> A website to begin with Opencv. [1]<br\>

2. General description

2.1 Product perspective

Make the autonomous car able to run a race.

2.4 General constraints

We have to make the fastest algorithms we can because the car can reach high speed and it still needs to recognize the markers.

2.5 Assumptions and dependencies

The tablet needs to be on the car.

3.Specific requirements, covering functional, non-functional and interface requirements

• document external interfaces,
• describe system functionality and performance
• specify logical database requirements,
• design constraints,
• emergent system properties and quality characteristics.

3.1 Requirement X.Y.Z (in Structured Natural Language)

Function: Make a car automous but helped by the recognization of markers along the road.

Description:

Inputs: Vidéo

Source: Caméra tablette

Outputs: Commande controle moteurs

Destination: Controleur moteurs

Action: Déplacements

• Natural language sentences (with MUST, MAY, SHALL)
• Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
• Mathematical Notations
• Tabular notations for several (condition --> action) tuples

Non functional requirements:

Pre-condition:

Post-condition:

Side-effects: