Requirements Specification

Requirements Specification
WIRELESS ROBOT
12 September 2011 Ankur Goyal ECE/08/105 Ankur Rana ECE/08/106 Deepak Dabas ECE/08/110 Priyank Malhotra ECE/08/135

MENTOR`s NAME Mrs Ankita Joshi

(Approved by AICTE, Ministry of HRD, Govt of India & DTE, Govt of Haryana and Affiliated to M. D. University, Rohtak)

Page i

Requirements Specification

Table of Contents
Table of Contents .......................................................................................................................... ii Revision History ............................................................................... Error! Bookmark not defined. 1. Introduction ..............................................................................................................................1
1.1 1.4 2.1 2.2 2.3 4.1 4.2 4.3 4.4 5.1 5.2 5.3 5.4 Purpose ........................................................................................................................................ 1 Project Scope ............................................................................................................................... 3 Perspective ................................................................................................................................... 3 Features........................................................................................................................................ 3 Characteristics ............................................................................Error! Bookmark not defined. User Interfaces ............................................................................................................................. 4 Hardware Interfaces....................................................................Error! Bookmark not defined. Software Interfaces .....................................................................Error! Bookmark not defined. Communications Interfaces ........................................................Error! Bookmark not defined. Performance Requirements.......................................................................................................... 4 Safety Requirements .................................................................................................................... 4 Security Requirements................................................................................................................. 4 Software Quality Attributes ......................................................................................................... 4

2. Overall Description .................................................................... Error! Bookmark not defined.

4. External Interface Requirements ...........................................................................................4

5. Other Nonfunctional Requirements .......................................................................................4

Appendix A: Glossary....................................................................................................................5 Appendix B: Analysis Models .......................................................................................................5 Appendix C: Issues List .................................................................................................................5

Page ii

Software Requirements Specification

1. Introduction
Intelligent spy robot project has been designed for the spying purpose .it is radio controlled and can be operated at a radial distance of 100 metres. Many time our army personnel need to venture into the enemy area just to track their activities. Which is often a very risky job, it may cost precious life. Such dangerous job could be done using small spy robot. All the developed and advance nations are in the process of making combat robot design, a robot that can fight against enemy. This robot is just a step towards similar activity. This robot is radio operated, self-powered, and has all the controls like a normal car. This is not possible until a wireless camera is installed. Wireless camera will send real time video and audio signals which could be seen on a remote monitor and action can be taken accordingly. Being small in size, it will not be tracked by enemy on his radar. It can silently enter into enemy canopy or tent and send us all the information through its tiny camera eyes. It can also be used for suicide attack, if required. The robot is controlled by a wireless remote using radio frequency. It is small in size and its compact design is one of the basic advantages. It has all the control like normal car, self powered through rechargeable battery ,stops instantly when stop applied , moving in both the direction turning left and right. Wireless camera is installed sends continuous audio and video signals that can be monitored on any display screen remotely controlled by looking at remote television through radio remote control.

1.1 Purpose
This requirement specification document is to tell about the requirements during the development of the wireless robot car. The document is intended to give the detailed description of all the hardware and software requirements of the project. The various hardware components required are ATMEGA 16: Atmega 16 is the 8 bit microcontroller which is used as the main controlling unit for the robot car. It is developed by ATMEL CORPORATION. The ATmega16 microcontroller used in this lab is a 40-pin wide DIP (Dual In Line) package chip. This chip was selected because it is robust, and the DIP package interfaces with prototyping Introduction to the ATmega16 Atmel 2 San Jos State University Dept. of Mechanical and Aerospace Engineering rev. 3.4 06SEP2010 supplies like solderless bread boards and solder-type perf-boards. This same microcontroller is available in a surface mount package, about the size of a dime. Surface mount devices are more useful for circuit boards built for mass production. Figure 1 below shows the pin-out diagram of the ATmega16. This diagram is very useful, because it tells you where power and ground should be connected, which pins tie to which functional hardware, etc.

Page 1 of 6

Software Requirements Specification

L293d: The L293D are quadruple high-current half-H drivers. The L293D is designed to provide bidirectional drive currents of up to 600-mA at voltages from 4.5 V to 36 V. Both devices are designed to drive inductive loads such as relays, solenoids, dc and bipolar stepping motors, as well as other high-current/high-voltage loads in positive-supply applications. All inputs are TTL compatible. Each output is a complete totem-pole drive circuit, with a Darlington transistor sink and a pseudo-Darlington source. Drivers are enabled in pairs, with drivers 1 and 2 enabled by 1,2EN and drivers 3 and 4 enabled by 3,4EN. The L293d is used in our project to drive the motors which will be working as tures for the robot car.

HT12E Encoder for RF modules: The HT 12E Encoder ICs are series of CMOS LSIs for Remote Control system applications. They are capable of Encoding 12 bit of information which consists of N address bits and 12-N data bits. Each address/data input is externally trinary programmable if bonded out. HT12D Encoder For RF modules: The HT 12D ICs are series of CMOS LSIs for remote control system applications. This ICs are paired with each other. For proper operation a pair of encoder/decoder with the same number of address and data format should be selected. The Decoder receive the serial address and data from its corresponding decoder, transmitted by a carrier using an RF transmission medium and gives output to the output pins after processing the data.

Page 2 of 6

Software Requirements Specification

Crystal oscillator: crystal oscillator of 16 MHZ for providing the clock and timing to the complete circuit. Push Switches: Push switches are required for the construction of the remote control. Some other small components (like resistances capacitors and diodes) are also required.

1.2 Project Scope

This robot is radio operated, self-powered, and has all the controls like a normal car. This is not possible until a wireless camera is installed. Wireless camera will send real time video and audio signals which could be seen on a remote monitor and action can be taken accordingly. Being small in size, it will not be tracked by enemy on his radar. It can silently enter into enemy canopy or tent and send us all the information through its tiny camera eyes. It can also be used for suicide attack, if required. The robot is controlled by a wireless remote using radio frequency. It is small in size and its compact design is one of the basic advantages. It has all the control like normal car, self powered through rechargeable battery ,stops instantly when stop applied , moving in both the direction turning left and right. Wireless camera is installed sends continuous audio and video signals that can be monitored on any display screen remotely controlled by looking at remote television through radio remote control.

2. Overall Description
2.1 Perspective
This project is a advancement of the basic robot car which is capable of moving and performing similar tasks like turning, avoiding obstacles etc. Instead it can also be grouped in the family of robot car having some special features. Our project is also equipped with a a very useful feature that it can be controlled by a wireless remote, which is very useful feature. Using this feature the device can be sent to distant and unfavourable places to human being.

2.2 Features
The device is not only capable of moving but it is equipped with feature that it can be controlled from a distant place using a wireless remote. The project after further modification can be used for a number of applications.

Page 3 of 6

Software Requirements Specification

3. External Interface Requirements

3.1 User Interfaces
AVR Studio: AVR studio is used as an interface to the hardware and the developer. All the programming is done on the AVR Studio which is later burnt on the chip. PCB Express: PCB Express is a software used as a user interface. The PCB express Software is used to design the Printed Circuit Board which contains all the circuit components embedded on it.

4. Other Nonfunctional Requirements

4.1 Performance Requirements
<If there are performance requirements for the product under various circumstances, state them here and explain their rationale, to help the developers understand the intent and make suitable design choices. Specify the timing relationships for real time systems. Make such requirements as specific as possible. You may need to state performance requirements for individual functional requirements or features.>

4.2 Safety Requirements

<Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the products design or use. Define any safety certifications that must be satisfied.>

4.3 Security Requirements

<Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied.>

4.4 Quality Attributes

<Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning.>

Page 4 of 6

Software Requirements Specification

Appendix A: Glossary
<Define all the terms necessary to properly interpret the RS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each RS.>

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams.>

Appendix C: Issues List

< This is a dynamic list of the open requirements issues that remain to be resolved, including TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>

Page 5 of 6