PersyCup2016/SRS

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

Read first:

• http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
• http://en.wikipedia.org/wiki/Software_requirements_specification
• IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998

Document History

	Version	Date	Authors	Description	Validator	Validation Date
	0.1.0	January 18, 2016	Bin SUN,Jordan Ellapin,Taqiyéddine ZEGAOUI	Creation of the document	TBC	TBC

1. Introduction

1.1 Purpose of the requirements document

This Software Requirements Specification (SRS) identifies the requirements for the project ”PersyCup2016”. This document will describe the details of our project.

1.2 Scope of the product

This project intend to allow our robot win the PersyCup2016 in the competition. It means we should let our robot get more balls than another.

1.3 Definitions, acronyms and abbreviations

LeJOS EV3 : it’s the newest version of the robot for the competition ,and it includes the information of control the robot : the Robot language based on Java.

1.4 References

Fiche

http://air.imag.fr/index.php/PersyCup

Home Page

http://air.imag.fr/index.php/PersyCup2016

Website de competition http://persycup.imag.

2. General description

2.1 Product perspective

The product is a strategy for a robot to finish its task in the competition. It provides the interaction of the robot program ,the robot ,and the camera of the competition.

2.2 Product functions

1 Let the robot get the position of all the balls and the other robot. 2 let the robot distinguish which is the nearest ball it can get. 3.let the robot finish its actions automatic : go to the ball catch the ball ,go to note ,drop the ball

2.3 User characteristics

The users is also the developers playing for the competition .

2.4 General constraints

The laboratory for testing our strategy is not always free, but for the competition ,we should test our robot in the laboratory. The position is not very precise ,we should consider the errors.

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

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

Function: make strategy for the robot to get the balls as much as possible in the match.

Description: it makes the robot automatic distinguish the nearest balls which can get to note. And has the automatic system for finishing a whole process for note.

Inputs: the beginning of the position of our robot and the quantity of the balls.

Outputs: the nearest balls for note, and the position of the robot in the map.

Destination: to let us get more balls than the other robot and win the PersyCup.

Pre-condition: Bluetooth:for start our program ,we should take a connnection with the robot using bluetooth. Wifi PersyCup：in order to get data throw the camera ,the computeur and the robot should connect with the wifi PersyCup

4. Product evolution

our robot now can find the nearest robot in and catch it to score ,but because of the test time is not enough ,the position of the robot and the ball is not very precise， so we will have errors after some of loops and so we should continue to debug our data for the robot and the balls . Also ,we will add a error treating mechanism for the special condition .

5. Appendices

http://blog.csdn.net/sharetop/article/details/49561301 http://www.lejos.org/rcx/api/index.html http://www.lejos.org/ev3/docs/