Anne
Dawson: CSCI110A_HW4_FA04.htm
Last
updated: Saturday 13th November 2004, 14:08 PT
This
document is subject to change without notice.
Please
report any errors or omissions in this document:
adawson@coquitlamcollege.com
Special instructions:
For this assignment you must work
alone.
See schedule for due date.
Homework
4
Specification:
#2 p454 3rd Edition
#2 p456 4th Edition
#2 p470 4th Edition Update
This Programming project is not in the Essentials Edition
Step 1
Study the program specification.
Step 2
Design an algorithm (the steps to solve the problem). The
following web page will help you design your algorithm and pseudocode:
http://www.coquitlamcollege.com/adawson/Pseudocode.htm
Step 3
Development the pseudocode from your algorithm.
The following web page will help you design your algorithm and
pseudocode:
http://www.coquitlamcollege.com/adawson/Pseudocode.htm
Step 4
Using your pseudocode as a guide, implement your program in the
VB language.
Your program should start with a comment block that contains the
following information:
' File: HW4.frm (HW4.vbp)
' Purpose:
Student Grades - Random Access File
' Programmer: [write your name here]
' Course: CSCI110A
' Date: [write the date name here]
' Algorithm:
' Pseudocode:
' Test data:
Step 5
Test your program by running supplying
your own test data. You should test your program with at least 3 sets of test
data. Show your test data and results in comments at the top of your program.
Step 6
On the due date, you should save your
homework files (HW4.vbp and HW4.frm) and any algorithm and pseudocode files to
your folder on the network in:
CSCI110A\Week13\HW4
Assignment Presentations : In week 13 class 1, a random selection of the homework assignment
programs will be presented to the CSCI110A group.
Program
points will be based on the following marking scheme:
Marking
Scheme
Student
Name:
Lab
code:
CSCI110A - Homework 4 - Fall 2004
|
Category |
Points |
Description |
|
Algorithm |
10 |
An informal description of the
steps that must be taken to solve the problem. |
|
Pseudocode |
10 |
A formal description of the steps
that must be taken to solve the problem. |
|
Comments |
10 |
The program should be commented as specified
in this document. |
|
Style |
10 |
The source code should use meaningful variable
names (identifiers) and is indented (spaced out) correctly. |
|
Design |
10 |
Appropriate data types are used. |
|
Modularity |
10 |
The program has
appropriate modularity |
|
GUI Output |
10 |
Screen prompts and outputs (user interface)
should be user-friendly. |
|
Correctness |
10 |
The program compiles with 0 errors and outputs
correct results. |
|
Completeness |
10 |
The program should be complete. |
|
Test |
10 |
Comments in the code explain how the code was
tested. |