SoftwareDesign

Don’t miss this year’s newest competition! You, alone or with
up to 5 of your compatriots, are challenged to submit a
software project that you have created within the past year.
Show New Hampshire what you have done! Have fun! Meet
other students with like interests from other schools! Show a
bunch of adult judges what great work you do!

Special Incentive: The Department of Computer Science at the
University of New Hampshire will pay the entry fees for the
first fifty students who register for the Software Engineering
Design Project Contest.

What do you have to do? (The Requirements!)

A. Select a competition category:
Individual or Team (2-6 members)

B. Demonstrate your project--you’ll have no more than 5
minutes!

C. Compile the following required items into a
folder/binder for review by the judges:
1. Your project’s summary (problem description).
2. Your design documents used for your project--
      these can include, but not limited to:
         a.        Flowcharts
         b.        Pseudocode
         c.        Screen captures
         d.        Data Flow Diagrams
         e.        UML diagrams
         f.        Any other documents
3. Source code of your project
4. A working demonstration of your project.

D. You will have a table for you and your team to show off
your project. You will then present your project to the
judging panel using an overhead projector (provided)

What do you have to bring? (Hardware!)
In order to demonstrate a working demo of your project, you
will need a laptop computer. An overhead projector will be
provided for you. If you do not have a laptop available, do not
let that stop you from entering! Arrangements can be made on
a limited basis.

10% Problem Definition
How difficult to dissolve, culturally or technically, are the boundaries being challenged by
this application?

60% Design
Equal consideration will be given to:
1. Innovation—applications that approach a new problem, or look at an old problem in
a new way.
2. Impactfulness—applications that either impact a large number of people very
broadly, or impact a smaller number of people very deeply.
3. Effectiveness—to what degree the application actually solves the problem in
question.

15% Development
The judges will be looking for elegant system architectures that break the problem down
into logical chunks and modules.

15% Presentation
The judges will be looking for oral presentations that provide background and context to the
project, explain why the problem is an interesting one, highlight how the system works, and
include an insightful demonstration. Teams will also be evaluated on their ability to take
questions from the judging panel.