Graphical User Interface project --------- 100 pts.

One of the major requirements for this course is the design and development of a working GUI. You can either select a GUI from the list below or propose another for my approval. You may use Visual Basic or C# (other languages require my approval.) You may develop a Windows Application, Web Application, or a Windows Phone App (other environments require my approval.)

Conference Registration System	Inventory System	Point of Sale System
Appointments System	Alumni guestbook that puts information into a database and displays it	Home Purchase Contract with a Mortgage Loan Application System
Outfitters Whitewater Rafting Application System	Economic Cost of Living Comparison System	Gourmet Food Truck Mobile Ordering System
Online evaluation tool to help students evaluate whether they are ready for CS I	Membership Application System	Airline Reservation System
Flashcards	Genealogy database System	Help Desk Log System
Wampus game	Xchange game	Games

This must be your work. Any material that you use from other sources must be properly cited.

This assignment will be accomplished by small teams of three students.

Assignment	Due Date	Points
A. Project Proposal Due	March 31, 2014	10
B. Project Analysis and Design (Prototype) Due (5 min presentation)	April 14, 2014	20
C. Final Project Implementation Due (20 minute presentation)	April 28, 2014	70

Grading Rubric:

95-100: Everything is done exceptionally well, plus special complex feature(s)

90-94: Everything in B done very well plus excellent self appraisal (external document) that completely explores known bugs, unexpected and counter-intuitive behavior

85-89 (Very Good): program must work without errors.

• user interface should be intuitive to use and able to cope with null data, non-numeric data, CTRL-D
• should be able to handle missing or garbled file / data

Deliverables must include

1. Cover sheet with names
2. Requirements document
3. Hard copy of documented source code (your vb files)
4. User documentation – how to build and use (use case document)
5. Maintenance documentation
• Description of program structure
• Description of algorithms used
• Description of class hierarchy (e.g. UML diagram)
6. Electronic submission of source code for program

80-84(Good): Runs without errors, but -

• Missing one minor piece of the documentation, or
• A few minor deficiencies in programming style (poor variable names, inadequate internal documentation)

75-79: Usually runs without errors or has two problems listed above

70-74 (Satisfactory): Usually runs without errors AND has a problem listed above

60-69: Runs with “normal” input but lots of missing pieces

50-59: Turned in everything, but program doesn’t run.

0-49: turned in something, but little or no effort was put into what was turned in