Project Updates (Important)

IEEE Transaction Paper

All final year students who have registered their project must have received a confirmation e-mail now. In case the team members have been repeated, only the first registration is considered valid. All attempts to change the registration (team members or add additional members) will incur a penalty. This will be of 5 credits. Those who have given non-working e-mail ids or incorrect email ids must send the corrected version through the tentative project lead or a team member who has successfully received the project team confirmation e-mail.

You need not send e-mail for future registrations. Use this Registration Page to register your project if you have not done so already. Please do not send e-mail for registration hereafter, but directly use this form. Those who have completed this process can read further.



For the next milestone, you may get in touch with me by e-mail to check your abstract and idea. You can also ask me about the feasibility. Further, you can also get in touch with anyone who is willing to assist you in your project (without bothering whether they will finally be your 'Technology Project Guide' or 'Academic Project Guide.') They will assist you in connecting your idea with a paper that has been published under IEEE Transactions.

"IEEE Transactions" are published annually on topics like 'Communication', 'Medical Instrumentation and Imaging' for ideas that have been deemed suitable for implementation. Please note that All IEEE Papers are not eligible for usage in a project as some are pure theoretical treatises which may not be feasible for implementation. The image at the start of this blog illustrates an IEEE transaction on Mobile Computing. It is best to select a transaction publications from 2011, or in case your idea is not found, use publications from 2010 verifying that there are no completely proven implementations already available.

At PITS, our 'Digital' Library has IEEE XPlore  membership that permits us to access transaction papers. You can avail this facility exclusively on terminals at our Institution. It is best that you find the title and possibly a brief abstract or keyword set on the paper before you ask for access to the full work.

For Milestone 2 it is important that you follow these instructions for the best results.

Milestone 2    (Credits:20)

1. Collect a list of Topics of your interest. These must be result oriented. You can consult Mr.Sunil for selecting a topic. You can minimize this to one (1) after a discussion within your project team.
2. Find an IEEE Transaction Paper which gives the theoretical background for your idea. If you have multiple ideas, you can collect a list.
3. Conduct a short preliminary study, listing out all necessary references, pre-requisite knowledge, resources and skills.
4. Create a Project Abstract in not more than 300 words which describes the following Items: - 'The Problem being Solved', 'The Area of Technology used', 'Requisite Skills', 'The Result type: (a)Research Thesis (b) Hardware Design, Prototype (c) Software Design, Prototype (d)Data Correlation Thesis'
5. The Project Abstract Submission form will be made available to you through your registered e-mail. You need to fill the same.

To help you select a project well, here is a simple example, which hopefully everyone can relate to.

Title
"Mobile Agent based P2P Network Load Balancer"

Abstract
"A Mobile software agent that dynamically balances heterogeneous P2P networks implemented in CORBA that implements the work of Hui Li and Fei Shao as a portable CORBA plugin usable in multiple frameworks, 'An improved load balancing algorithm for P2P system based on mobile agent,' (AIMSEC), 2011 2nd International Conference on , vol., no., pp.2791-2794, 8-10 Aug. 2011

This example illustrates a project whose deliverable is a CORBA based software-plugin that can be used for P2P load balancing. As Mozilla (Firefox and Aurora) are written using a strong CORBA interface, that could easily prove as the demonstration platform. Hence it complies to "The Result type (c) Software Design, Prototype."