e-Yantra Ideas Competition <Category:Title of the idea>

Student Name College College Address Email Branch Year (First Fourth) Category (among the five project categories) Date

Abstract
Not more than 200 words. Please make sure that the entire text of the abstract fits on this page alone. A small hand sketched (scan it and put it here) figure would be better along with the abstract. Make sure both the text and the figure fits on this page itself. The abstract should not include any clichs or any common knowledge such as The mobile devices are getting common these days. Describe the problem in common language, then describe the field where it is applicable, the technical problem underneath and source of inspiration. The sketch you put here should give us an idea as to how the idea in your opinion will look as a product. Important: Remember that we will be manually going through hundreds of proposals such as yours and the Abstract is the first impression. The reviewer might skip your proposal entirely if your abstract does not give the right impression so be careful in what you right here and keep it consistent with rest of the document.

The Problem Statement

The Problem Area
Tell us which area this idea belongs to. [This is just one word e.g. Agriculture]. Please keep this in mind and submit the document in the correct category when you upload on the e-Yantra Ideas submission page.

Motivation
What motivated you to think of a solution to his problem? It might be the case that it is a common problem in your home, locality, hometown and so on. We want you to look around for an interesting problem which when solved we expect the community or society at large to be benefited greatly. It also tells us about how observant you are and whether the problem is worth solving in first place.

Beneficiaries
Who do you think will benefit by your solution. If you can be quantitative we will appreciate that. This means please try where possible to avoid words such as the machine is big or small or moves fast or slow you should give suggestive numbers in place of these words. Make sure you give us some source for your stats OR tell us how you deduced the number. References must be added only in the reference section.

Challenges
Real world problems must map to technical challenges. For example a room-cleaning robot might have a challenge such as covering entire area of the house or cleaning whilst avoiding obstacles. Please detail these challenges in bulleted form only and each bulleted item should be not more than one sentence. Let there be some logical flow between these sentences.

Graphics
If you want to add any photos, sketches of your problem please feel free to add it here.

The Solution
Hardware Required
Write as bulleted points the hardware that is required for the implementation of the project. Hardware includes not only the computer but also the mechanical accessories required. These should be separately detailed.

Software Required
Write as bulleted points the software required for implementation of the project. All the software should be open source or free to use for academic and/or non-commercial use.

Approach
Describe your solution in bulleted form. Do not use vague words such as user friendly, efficient, long, fast and so on. Give details such as We construct a box of 3x4x1 feet. We attach an arm as described in figure 1 to the robot and so on. It is of paramount importance that you add figures to support your solution design. This is likely to be the longest section of your document.

Algorithms and Flowcharts

Describe your algorithms in a formal way. You may use a programming language or pseudo code or use other formal ways of describing your logic such as state charts, FSMs or UML diagrams.

Test Cases
It is not enough to merely describe a solution but you should tell us the circumstances under which this equipment must be tested. Imagine that the actual product has been built using your idea and these test cases will be used to validate that work. Hence the test cases should not be vague like The robot should move fast instead it should be the robot must not take more than 5 seconds to reach from point A to point B as shown in the figure 2. You may aid figures here. For example if you are making a Rangoli making robot you should present at least 3 diagrams which you will robot draw as a diagram.

Potential Risks and Problems

Please enumerate the potential risks you envisage in implementation of this solution. The risks mean the reason for which this project might fail. For example if your project involves a camera a potential risk may be Ambient light in the atmosphere where our robot is expected to work may not have lightning condition suitable for image processing. Please refer to the documentation of various open sourced e-Yantra projects for more examples.

References