1. Creative Project Revised 3/02

2. Creative Project Examples

3. Creative Project Examples
Fantasy Baseball Helper Program
Phone Directory
Simple HTML Editor
Slot Machine
Role Playing Character Generator
A Simple Alphabetical Code Program
A Simple Paint Program
A Simple Training Program
Simple Game (Yahtzee or simpler)
Formula Grapher for one or two formulas
A modification of a program written in original Basic or another language
A program useful for your major or a class
Simple Employee Database
A Quiz with results

4. You need a total of 12 pts. You may do several projects to add up to the total. Just make sure we know there is more than one project.

5. Use an Original Disk
There may be NO extraneous files in that directory..
TEST YOUR PROGRAM IN CLASS. Not testing on a different machine to test your work is unprofessional and unacceptable. Not testing is not an excuse. So FTP your project down to a second machine. Otherwise, we may not be able to contact you to correct any errors.

6. Requirements
Commented with your name, date & class and instructor name. (-1 to -10 pts)
Well commented. Each routine is explained. (-1 to –3 pt)
Alt and Shortcut Keys Used (-1 pt)
Good coding style, alignment, and spacing (-1 pt)
Professional Style Forms

7. Grading 12 pts needed. Each worth a point*:
Each Function
Each Non-event Subroutines
Each Modules/Forms
Global Var. (max 1pt)
Advanced Features
Animation (max 2 pts)
Toolbars (max 1 pt)
Database interaction
Other file interaction
Printing (max 1 pt)
Complex Mouse interaction
Common Dialog Box
Full Menus (max 1 pt)
Events are 0 pts, but may have additional Subroutines, Functions, etc.
*Provided they are not just “fluff”

8. We may discuss your projects in class to have the class group-problem-solve.
You may work together in a constructive manner. Please don’t actually DO any part of someone elses program.

9. Due: By the beginning of the time scheduled for the final.
-2 pt if turned in at end of time scheduled for final.

10. Designing your program

11. The Programming Process
Decide what your application is to do by creating an overall design.
Create the visual portion of your application (the screens and menus that your users will interact with).
Add Visual Basic programming language code to tie the visual elements together and to automate the program.
Test your application to locate and remove any bugs you find.
Compile your tested application and distribute the compiled application to your users.

12. Design the forms
In EVENT-DRIVEN programming every procedure is a direct or indirect result of an event.
Account for the form control driven events.
That event may range from the program loading to a button being clicked.
Not all procedures are direct results of an event. Some may be called by different event procedures or other procedures at different times.

13. First Rule of Programming: Divide and Conquer.
Break up your program into subroutines and procedures
Bite size pieces – mini programs.

14. Pseudocode Pseudocode is just what it means: false code.
Pseudocode is a somewhat verbal and somewhat coded representation of the tasks your program is engaging in.
Write comments for all of your routines before you write them explaining the task of the procedure.

15. Algorithms
Algorithm: A step-by-step problem-solving procedure, especially an established, recursive computational procedure for solving a problem in a finite number of steps.
You have to know how to do something or you can’t tell someone else how – and you can’t tell a computer how.

16. Creative Project Summary
Choose an interesting project
Plan it out before coding
Use pseudocode. Use comments