Introduction
eGURU
eCONTENT
eOUTREACH
Brochure
Contact Details
FAQs
Student Guidelines
The objectives of an eGURU project are to ensure that the Student Group

  • Understands and internalises the quality processes

  • Understands the underlying technical area through guided reading

  • Receives guidance in resolving technical implementation problems

  • Actually does the work (does not copy from earlier projects)

The Student Group Process in the eGURU Programme

  • Registration: A Student Group first registers giving details of individual members. Each individual student can register as a member of only one group. The students will give the details of their academic institute and their roll numbers, which will be used to check for uniqueness. Academic institutes will be chosen only from the pull down menu for AICTE accredited institutes (the other option is for other institutes). The students will also specify the duration and effort required for their project (expected to be 1 person year for the full team.) The group will be given a group mailbox, which will in effect send mails to individual students. The Student Group will communicate with the Mentor only through the portal and the assigned mailbox. The identity of the Mentor and the Student Group will be strictly confidential.

  • Endorsement: eGURU will seek endorsement of the Student Group from their academic institute. A local coordinator from the institute is expected to endorse the students’ identities and their suggested project duration and effort.

  • Proposing a project: A Student Group can optionally propose their own project idea. The project description should have sufficient details to enable the Student/Mentor community to understand the description and choose the project. The effort should be around 1 person year. The Student Group is treated as 'owner' of the project idea and is expected to answer queries in understanding the description.

  • Selection of Project: A Student Group can choose from a list of available projects (apart from their own project idea). The projects will be displayed along with information on whether any Mentor has opted to mentor them. Once a Student Group and Mentor have (independently) chosen a project, the project will be assigned to both of them.

  • Acceptance of Mentoring: Once a project is assigned, the Mentor will be asked to accept the responsibility. Once a Mentor accepts the responsibility, the Student Group and the Mentor can proceed with the execution.

  • Start Date of Project: The eGURU is a round the year and nationwide initiative. Academic institutes have their own schedules and estimated effort for final year projects. The schedules could be vastly different. The start date of the project is the date on which the Student Group has to submit the Final Project Proposal to their institute. The Student Group should not to be disappointed if a Mentor is not assigned to them. One option would be to visit the site frequently and try to select a project idea which already has Mentors interested in it, rather than waiting for a Mentor to select one's project idea. The Student Group can choose to execute a project even without a Mentor if time runs out. The eGURU team can guide the Student Group on quality principles if a Mentor is not assigned to the group.

Completing an eGURU Project
An eGURU project is likely to have an effort of around 1 person year (2000 hours).
Expectations from a Student Group in different phases.

  • Problem definition phase: Scoping and writing system requirement specifications. Reading supplementary material on business area and/or technology.
    Deliverable: System Requirement Specifications
    Note: It is expected that the team will be divided into separate design and test teams or alternately the project is split into independent pieces for which design and test can be assigned to different individuals.

  • Design Phase: Capturing the solution in the form of a design document. Understanding various sections of the document.
    Peer review of the design document.
    Deliverable: Design Document

  • Construction Phase: Writing software as per specification.
    Peer review of code.

  • Unit/Integration Testing: Understanding importance of testing.
    Preparation of a test plan.
    Peer review of test plan (completeness).
    Documentation of test results.
    Deliverable: Test Plan and Test Result

  • Code Submission: No effort. Filling up of a feedback report. (Optional)

eGURU Support

The eGURU team will publish guidelines, standards and explanatory articles on all the phases. The Mentor may review applicability and give formal permissions to drop certain sections.
Login Panel
Username
Password
 
Forgot Password ? click here
 User Guidelines 
Register Now
 Student Groups
Mentors
Academic Institutions
Statistics
Hit count since April 2006 610641