Description

 

Tasks

Complete the tasks below accurately and in order.
Refer to the relevant hybrid activities resources if needed.

 

1. Create a new folder for the Git repository of assignment 3, in the location below, replace Your_Name with your full name (as shown in ACSIS) separated by underscores ( _ )

 

C:\CST8116_Assignment_03_Your_Name

 

2. Create a new Java project named: Assignment 3

 

3. Create a new Git repository for the project, inside the folder listed above.

 

4. Verify that Git is configured to ignore the bin folder when adding files to the staging area.

 

5. Commit #1: Commit the project to the repository, with a description:

   New Project Assignment03 by YourFullName

 

• Use your actual full name in the description
• Add a signed-off message, it should have your full name and college email.
• Note that at this point the project should not have any Java files.

 

6. Add a Java class named Assignment03YourFullName

 

• Add a main method into the class, have it print the text “Program by YourFullName“
• Use your actual full name in the class name and the printed text
• Verify that the project compiles and runs correctly
• Your Java file should be between 5 to 8 lines long, do not add comments yet.

 

 

7. Commit #2: Commit the Java file to the repository, with a description:

   Added source code file Assignment03YourFullName with method main

 

• Use your actual full name in the description
• Add a signed-off message as before
• Note that this commit should only include one Java file.

 

8. Into your main method, before the line that prints your name, insert the exact code below:

• Note that at this point the program will run and terminate with an exception.

Do not fix this exception just yet.

 

9. Add programmer comments to the Java file

 

10. Commit #3: Commit the Java file to the repository, with an appropriate description of what changes you are committing.
    • Add a signed-off message as before

 

11. Run the program, and notice that it terminates due to an exception.

 

12. Use the methods you have learned in this course to locate and correct the mistake(s) in the code.

 

13. Screenshot #1: Take a clear screenshot of the complete program’s output, name it: png

 

14. Commit #4: Commit the Java file to the repository, with an appropriate description of what changes you are committing.
    • The first description line must indicate what problem you have corrected
    • Add a signed-off message as before
15. Screenshot #2: Take a clear screenshot of the Git history of your project, name it: png

 

• The screenshot will include all the history columns: your commit: id, message, author, authored date, committer and committed date
• The screenshot will show the 4 commits you have done in the project. If you don’t see all 4 commits, you may not be showing the history for the project, but for a specific folder/file.

 

1. Zip File of the Repository: Create a zip archive of the folder on C: drive you created under

 

C:\CST8116_Assignment_03_Your_Name

Submission Requirements

Use the rubric below to verify the files you are required to submit:

 

• png
• png
• A zip file of your repository

 

Once verified, submit all 3 files and look for a confirmation email on your submission.

Grading (10 points)

Screenshots	Missing / Poor (0)	Below Expectations (1)	Meets Expectations (2)
output.png	Missing or poorly done	The program is not crashing but the output shows it wasn’t fixed correctly: roll numbers may not make sense and/or 10 dice are not rolled.	Shows program executing successfully, student’s full name as part of output.
history.png	Missing or poorly done	Shows some but not all of the requested commits, or commit text not correct.	Shows all four requested commits.

Repository	Missing / Poor (0)	Below Expectations (3)	Meets Expectations (6)
Git Repository	Missing from submission or only a project folder and not a full Git Repository.	Does not have requested folder name for repository, git log command may show inconsistencies when compared to screen shot. The bin folder content was committed and not ignored. The source file is not documented.	Has requested folder name for repository, git log command closely matches the history seen in the screen shot.