Latest Update: Congratulation! We got your resubmitted abstracts.We will get back to you soon with the selected projects.

Ingenieur

A Project Implementation Competition

Roll your sleeves up and put on your thinking caps. It is time to innovate, it is time to ENGINEER. Write code, brainstorm contraptions and engineer solutions to innovate and improve functionality in your own day to day lives. Implement software and hardware brilliance to make the lives of students, faculty and academicians simpler. If you love challenges and have the mettle to be an engineer – then join the fun. This is your chance to be the cool nerds of the campus who will be remembered for generations to come.
GO ENGINEER!

Do you have an Idea that will make a difference? Then logon to your laptop or computers and pen down your thoughts in a Word document. Submit your abstracts by 10th March 2015 to be a part of the team that will engineer the coolest solutions on campus.

Abstract Submission

Mark the date. Submit your abstracts by March 10th 2015. Download the abstract template and fill in all the relevant details. Click here to download.



Project Sponsorship

While the manual labor will be put in by the team members, the students/staff will assist in testing of the product/services. The hardware/software projects have to be submitted to college and the expenses incurred on hardware or in procuring licensed software will be reimbursed by college but only upon successful implementation of the project



Project Timelines

Please refer to the Project Timelines Section to get further details.



Winners

Three to Five abstracts will be selected and all of them will be deemed winners. The prizes will be distributed to these teams upon successful implementation of project.



Project Implementation

The project will be marked as completed only when the product/service is implemented within college, the users trained on it and the relevant documentation is approved by mentors/jury



Mentors and Jury

Alumni will act as mentors and some others will act as jury. Mentors will regularly interact with teams and guide them. Besides mentors, other alumni will also volunteer to give advice relevant to their specialties.

Project Timelines

The following timelines can be used as a point of reference to understand how Ingenieur will progress through the year 2015

Submission Deadline

Project Abstracts should be submitted by March 10th 2015

Jury Demo

A demo should be arranged for the jury in the month of June 2015

Final Submission

The implementation of project, testing, training and submission must be completed before December 2015

Competition Format

‘Ingenieur’ is a project competition unlike others in which every project that is selected to compete will automatically be declared a winner upon its implementation. ‘Implementation’ being the keyword here. The students can only work on projects that will solve a problem at SGGS or innovate a process at SGGS or add value to an existing process. Students will be asked to participate in teams of two to five members each. Each team will be given a time span of fifteen days in which they will be required to submit an abstract of the project that they wish to undertake. The jury will evaluate the abstracts and select five teams. These teams will NOT compete against each other rather every team that successfully implements the project undertaken will be automatically declared a winner. The project will be implemented at SGGS and will be used by the intended users which may be staff or students. As such students should architect projects in such a way that it should allow extensibility and easy maintenance in future.

Guidelines

The competition will ONLY be open to those projects which can be implemented in SGGS I E & T, Nanded. The project statement should aim to resolve a current problem or add value to an existing process.

The competition will be open to students pursuing sixth semester at SGGS I E & T, Nanded.

The teams will get a time span of 6 months to a year to complete the project.

The project competition will run from Feb 2015 to Dec 2015.

Upon successful completion, the college will consider the project for grading as the final year first semester project. Depending on the complexity of the project, the college can also consider this as a major project and grade it for both semesters. A written approval will be required from college prior to the commencement of the competition.

Implementation of the project will be considered as successful completion and not just mere completion. The team that implements the project will also be required to train users on how to use the product and they will also be responsible for mentoring another team of students who will assist in maintaining the project after these students have graduated.

The students should ideally follow a product development lifecycle. The product should be well documented so that end users and future students maintaining the product/service can easily reference these documents for help.

List of documents

Document

Recipients

Responsibilities

Update frequency

Requirements Document

Jury/Mentor

Team

n/a

Design Document

Mentor

Team

Weekly or till design is finalized

Technical Guide

Mentor/Students who will maintain it in future

Team

Monthly

User Guide

End Users/Jury/Mentor

Team

With every new major version

Project Status Report

Mentor

Team Lead

As required by mentor

Team Structure

Ideally the teams should comprise of at least three members each. The maximum number of members can be seven however depending on the complexity of the project/product that the teams plan to develop they may choose to have more than seven team members. The names of the team members should be clearly indicated when the abstracts are submitted. Changes to the team can be made within the first three months of the commencement of the competition. After that the students need to work with the existing team members to complete the project.

Team goals

Each team must elect a team lead who will be the main point of contact for communication with the Jury and the mentor. While the mentor will interact with all team members it is ideal that all communication is routed through a single individual or a single email ID so that the mentor doesn’t have to repeat things.

It is the responsibility of every team member to ensure that the entire team is updated whenever a change is proposed or implemented in the product/project. Any directions or instructions from the mentor or the jury must be clearly articulated to every team member.

Each team member should report their project task status to their lead and it is the responsibility of the lead to compile this in a project status report and forward it to the mentor.

The team should try to follow a modular development approach so that each individual is responsible for a small module of the project. The design of the product needs to accommodate this modularity. However this is not a necessity. It will simply allow for easier management of resources and allow users to focus on their tasks and also help in preventing arguments/contradictions on the approach to be taken for developing the same piece of a product.

The team as a whole must strive to deliver the project within the timelines proposed and they must acknowledge that the college is the client for their product and they should try to meet all deliverables on time and satisfactorily.

The team must make efforts to maintain smooth and regular communication within the team and also with the jury and mentors.

Student Volunteers

You can reach out to the following student volunteers for further information about the competition