Anne Dawson: CSCI102A_LAB9_SP04.htm  Thursday 11th March 2004, 9:56 PT, AHD

 

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 may work in teams of 2, or alone.

This lab is due at the end of the lab session.

 

Lab 9 Specification

-------------------

 

Before starting this lab you should read the case study (character graphics) which starts on page 442 (3rd Ed). Read up to the Self-Test Question on page 452.

 

#6 page 472 3rd Ed

 

Note: in addition to the requirements, you should override the toString() method of the Object class in both of your new classes (RightTriangle and Rectangle).

 

Submission instructions:

-----------------------

 

At the end of the lab session you should save just your source code file/s to your folder in CSCI102A\Week10\Lab9.

 

If you are working in a team, both team members save the same file to their own folder.

 

Make sure that you include your name/s and today's date in comments at the top of the code.

 

 

Marking Scheme

--------------

 

The following marking scheme applies:

 

Course Code:             CSCI102A

Semester:                SP04

Assignment Code:         Lab 9

Lab Specification:      #6 page 472 3rd Ed

Instructor Name:         Dr Anne Dawson

 

Student 1 Name:

Student 1 Number:

Student 2 Name:

Student 2 Number:

 

 

DESIGN

 

1.  The program has appropriate modularity i.e.               

    methods are used where it makes sense to

    use them.                                            /10

 

2.  Appropriate data types are used.                     /10

 

3.  Appropriate control structures are used

    (i.e. loops and decisions).                          /10

 

4.  The User Interface (output to the screen) is

    clear and tidy.                                      /10

 

MAINTAINABILITY

 

5.  The program is commented appropriately - including

    date, filename and pre- and post-condition

    comments. Comment for javadoc, and run javadoc on

    your .java files.                                    /10

 

6.  The program has meaningful identifiers.              /10

 

7.  The program is indented (spaced out) correctly, to

    aid the understanding of the code.                   /10

 

8.  The code is easy to follow.                          /10

 

CORRECTNESS:

 

9.  The program compiles with 0 errors and 0 warnings.   /10

 

10. The program runs as intended.                        /10

 

 

                                          % Complete:

                                               Bonus:

                                               Total:   /100

                                     

                                    Date: