Vihaan’17… A Hackathon By DTU
Vihaan is an annual event organized by IEEE DTU Women in Engineering (WIE) Affinity Group, a university wide professional organization dedicated to encourage women to take up and continue their careers in STEM Fields.
IEEE WIE believes in encouraging talent that is not bounded by gender inequalities and with Vihaan, IEEE DTU aims at carrying this thought forward. The event is a 24 hour Hackathon which provides a platform to budding programmers to come up with a solution to an existing problem using technology. Students can participate in a team size of upto 4 members with at least 1 female participant in the team.
Date: 27-28 October, 2017.
- The team can consist of 4 members at max, with at least one female participant.
- Teams should be made up exclusively of students (or recent graduates within one year of having graduated) who are not organizers, volunteers, judges, sponsors, or in any other privileged position at the event.
- All team members should be present at the event. Leaving the venue for some time to hack elsewhere is fine.
- Teams can of course gain advice and support from organizers, volunteers, sponsors, and others.
- All work on a project should be done at the hackathon.
- Teams can use an idea they had before the event.
- Teams can use libraries, frameworks, or open-source code in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed.
- Adding new features to existing projects is allowed. Judges will only consider new functionality introduced or new features added during the hackathon in determining the winners.
- Teams must stop hacking once the time is up. However, teams are allowed to debug and make small fixes to their programs after time is up. e.g. If during demoing your hack you find a bug that breaks your application and the fix is only a few lines of code, it’s okay to fix that. Making large changes or adding new features is not allowed.
- Projects that violate the Code of Conduct are not allowed.
- Teams can be disqualified from the competition at the organizers’ discretion. Reasons might include but are not limited to breaking the Competition Rules, breaking the Code of Conduct, or other unsporting behaviour.
Teams will be judged on these four criteria. Judges will weigh the criteria equally. During judging, participants should try to describe what they did for each criterion in their project.
TECHNOLOGY: How technically impressive was the hack? Was the technical problem the team tackled difficult? Did it use a particularly clever technique or did it use many different components? Did the technology involved make you go “Wow”?
DESIGN: Did the team put thought into the user experience? How well designed is the interface? For a website, this might be about how beautiful the CSS or graphics are. For a hardware project, it might be more about how good the human-computer interaction is (e.g. is it easy to use or does it use a cool interface?).
COMPLETION: Did the team stretch themselves? Did they try to learn something new? What kind of projects have they worked on before? If a team which always does virtual reality projects decides to switch up and try doing a mobile app instead, that exploration should be rewarded.
LEARNING: Does the hack work? Did the team achieve everything they wanted?
For More Details, Click Here.