CPSC 231: Assignment 1 (Worth 2%)

New Concepts to be applied for the assignment

1. Learning Java syntax
2. Learning how to compile and run a Java program

Determining your lucky number

Some people believe that there are some specific numbers that provide them more luck than other numbers.  We all have heard of people who pick the same lottery numbers every week because they believe that these numbers will provide them with a higher probability of winning.  For this assignment you are to write a program that will ask the user a series of questions and generate for the person their very own "lucky number".¹  For this assignment you are to submit a program with a single class "Driver.java" that implements the capabilities listed below.

For each question a numerical 'modifier' will be computed each of which will play a role in determining the person's lucky number.

The program will then sum the modifiers generated from each of the above questions and it will either add or subtract 100 from this sum (there's an equal chance for each) to generate the final computed value ('the lucky sum').  The lucky number that the program displays to the user will depend upon which of the following ranges that the lucky sum value falls under.

For example:

Q1: Age = 114, age modifier = 13

Q2: Gender = female, gender modifier = 300

Q3: Computer owned = none, computer modifier = 0

Sum of modifiers from each of the above questions = 13 + 300 + 0 = 313. 

Assume that when the program is run it randomly determines that it should subtract 100 from this amount so the resulting final computed value equals 213 (313 - 100) so that the program would display '7' as the lucky number.  (If the program randomly determined that it should add 100 to the sum then the final computed value would equal 413 (313 + 100) and the program would display '13' as the lucky number).  Note: Your program shouldn't display the 'lucky sum' to the user but should instead display only the lucky number (showing two numbers would be somewhat confusing).  The exception is when you are testing your program and trying to determine if your lucky sum is calculated correctly.  In this case you could set up a debugging mode that would show both values but only when explicitly requested by the user.

Grading: Working submissions

Assignments that receive a 'C'

These assignments implement all of the required functionality listed above and also follow good coding style and be fully documented as described in the style guidelines.

Marking for assignments that are missing or incorrectly implement the above features:

• Missing or incorrectly handling each of the above questions: -1 letter step for each question missed.
• Missing or incorrectly calculating the final computed value: -1 letter step.
• Missing or incorrectly determining the lucky number based on the final computed value: -1 letter step.

The minimum grade for a program that compiles (and involved a considerable time and effort to write) is a 'D' regardless of the number of features that may be missing or incorrect.

Extra features:

Implementing all the features below correctly can allow you the potential to receive a grade of 'A' (again style and documentation standards must still be met).

Feature 1, the program performs some rudimentary error checking: These assignments fulfill all of the requirements for a 'C' level submission (or higher) and performs some basic error checking.  If an invalid value is entered the program will generate an appropriate error message and a default value will be used by the program.

 It is however not expected that your program can determine if the type of data that was entered is correct  e.g., at this point it's acceptable if your program crashes if the person enters a character instead of an integer.  While some of the better commercial programs do deal with issues like this, at this point it would be far too difficult to require you to implement a solution for this problem.

Feature 2, the program is able to re-run itself: These assignments fulfill all of the requirements for 'C' level submission (or higher) and each time that a calculation has been performed the program will prompt the user if he or she wishes to run the program again or if they want to exit the program. (Worth 2 letter steps).

Grading: Non-working submissions

D submissions

• The student has invested considerable time and effort into the assignment², the program does not fulfill any of the above requirements but it does compile.

D- submissions

• The student has invested considerable time and effort into the assignment², the program does not fulfill any of the above requirements and it does not compile.

Other submission requirements

In addition to having fulfill the generic assignment requirements the requirements specific to this assignment include:

1. Good coding style and documentation:  They will play a role in determining your final grade for this assignment.  Your grade can be reduced by a letter step or more (e.g., 'A' to 'A-' for poor programming style such as employing poor naming conventions for identifiers, insufficient documentation or the use of static variables or methods).  For additional details see the marking guide for coding style.

2. Include a README file in your submission:  For this assignment your README file must indicate what grade level has been completed (e.g., 'A') and which features have been implemented (e.g., "I have implemented all the features for the 'C' version plus the ability to error check and set a default value and display an error message for the gender and type of computer which amounts to a 'B-' submission.  This will allow your marker to quickly determine what he or she must look for and speed up the marking process.  Also you should include your contact information: your name, university identification number and UNIX login name so that your marker knows whose assignment that he or she is marking.  Omitting the necessary information from this file will result in the loss of a letter 'step' (assuming that the marker can actually figure out who the assignment belongs to, if it cannot be determined who the assignment belongs to then no grade will be given for the assignment, an "F" will be assigned).

3. Assignments (source code/'dot-java' file and the README file) must be electronically submitted via submit.  In addition a paper print out of the source code and README must be handed into the assignment drop box (located on the second floor of the Math Sciences building) for the tutorial that you are registered in.  Electronically submitting the assignment allows your marker to run the code in order to quickly determine what features were implemented.  Providing a paper printout makes it easier for your marker to read and flip through your source code.  Omitting the paper version of the source code file will result in the loss of a letter 'step'.  Omitting the electronic version of your assignment will only allow you to receive a maximum grade of 'D-' because it's extremely time consuming for your marker to check every program with a hand trace.  I suggest that as you complete the various features of the assignment that you immediately submit each version so that if you forget to submit the final version you will at least have something that your marker can grade because you won't be allowed to make a submission after the deadline.

4. As a reminder, you are not allowed to work in groups for this class.   Copying the work of another student will be regarded as academic misconduct (cheating).  For additional details about what is and is not okay for this class please refer to the following link.

Sample Executable

You can run a sample Java byte code file called 'Lucky.class' which can be found in Unix in the directory: /home/233/assignments/assignment1