Assignment 1

Home

Due Date: 4pm, Friday 11-Apr-08 (week 6)
Marks: 6%

Assignment Regulations & Example Assignment

Problem Description

Bazza's Bungy Jumping uses a different length of bungy cord depending on the weight of a customer. Bazza eyes-off a customer as they climb on to the jumping platform and classifies them as light, medium, heavy or extra-large. A light customer gets the full length bungy cord, medium gets 3m reduced from the length, heavy - 6m and extra-large - 9m. The theory is that a heavier customer will stretch the cord further. All customers should come to a halt just above the river which flows under the jumping platform. Bazza felt his system was sufficient as, if he didn't get it quite right, the customer would only get a bit of a dunking in the river. Bazza has been threatened with a serious insurance premium increase unless he uses a more structured approach to determining what length of bungy cord is appropriate for a particular customer. Bazza cannot afford the insurance premium increase. He employs you to solve the problem. The idea is to have a computer on the bungy jumping platform and a set of weighing scales. Each customer is required to get on the scales, their weight is entered into the computer, which then determines the appropriate length of bungy cord to use. A bungy cord is 30m in length but the length can be reduced mechanically on the jumping platform. The manufacturer of the bungy cord recommends a weight range for particular lengths of cord:

The scales measure a customer's weight to the nearest 0.1kg. Any customers under 35kg and over 200kg are dissuaded from jumping.

Because Bazza likes to give his customers maximum satisfaction, he introduces an "Increased Excitement" factor. If a customer chooses to go for "Increased Excitement" then 1m is added to the calculated cord length.

Assume that any input by the user is valid (no error checking of input is required). Develop a product using Visual Basic which will solve Bazza's problem.

Example Runs

Run
Weight (kg) ? 72.1
Increased Excitement  (Y=Yes, N=No) ? N
Bungy length = 24m 

Run
Weight (kg) ? 108.8
Increased Excitement (Y=Yes, N=No) ? Y
Bungy length = 19m

Run
Weight (kg) ? 200.1
Sorry but Government regulations do not allow us to let you jump  

Run
Weight (kg) ? 35.1
Increased Excitement (Y=Yes, N=No) ? Y
Bungy length = 28m

Sections Required

The assignment should be word processed with each page numbered. Suggested left margin 2.5cm, right margin a minimum of 1cm.

The following sections are required, (in this order).

1. Title Page

This should contain:

• your name
• subject name
• tutorial group
• tutor's name
• assignment number
• submission date

2. Statement of Authorship

This must contain:

• the standard text for a Statement of Authorship for the Department
• your name
• subject name
• assignment number
• your signature
• date signed

The work will not be marked without a signed statement of authorship.

3. Table of Contents

• List all the major sections in the assignment and the page numbers they occur on.

4. Defining Diagram

• As specified in class and the Defining Diagram Guide.

5. Pseudo Code

• As specified in class and the Pseudo Code Guide.

6. Data Dictionary

• As specified in class and the Data Dictionary Guide. Where possible the data dictionary should appear on the same page as the pseudo code.

7. Desk Check

• As specified in the Desk Check Guide.
• Provide Desk Checks for test run numbers 4 & 9

8. Visual Basic Code

The code should:

• match the logic specified in the Pseudo Code
• the code should be easy to read and understand. It should be
  • well formatted (e.g. correct indentation, a blank line between sections)
  • well commented. This should include comments about the program: program name, purpose, author; comments describing each variable and comments on each section of the program.
  • have meaningful variable names
• have Option Explicit

Copy the code from Access and paste it into your word processed document.

The code listing should:

• be readable
• be in a monospaced (non-proportional) font (Courier New preferred)
• use a font size of 9 or10pt
• avoid line wrapping (use a small right margin if necessary)

You must include a statement indicating whether the code listed successfully compiled (no syntax errors).

Example statement: "The code listed below compiled successfully." or "The code listed below did NOT compile."

9. Test Plan & Runs

• Using the Test Plan below, cut and paste the table into your document, test the program and fill out the actual result and correct columns of the test plan
• Provide printouts of input and output for test run numbers 4 & 9
• To capture the current Window, ensure that the window is selected (e.g. place the cursor in the desired window) and press Alt+Print Screen. This can then be pasted from the Windows Cut/Paste buffer into the desired document (such as Word).
• To provide a printout of the test runs, capture each window separately. To capture the Immediate window rather than the whole Access window, you need to undock it. To do this Right mouse click on the Immediate window and select Dockable (only if it doesn't already have a tick next to it), the Immediate window should now be a floating separate window that can be captured by itself.

Your runs must be made using the program listed in the previous section. You must include a statement indicating that the program runs are for your program as listed in the previous section.

Example statement: "The program runs below are the output of the program listed in the previous section."

Test Plan

Guide to Marks

The following is a guide to the marks assigned to each section of the assignment.

Written by Chris Cope (and Tim Whitfort).