Table of Contents
- Get you ready for the week's lessons.
- Introduce you to the following concepts:
- constructing objects with new
- primitive types vs. object types (references)
- Instance fields (variables)
- Variable lifetime
Read the Scholastic Honesty Policy and Quest and Lab Integrity policies of the syllabus. Here are some clarifications for this particular lab:
- This is a solo lab that you must complete individually.
- You may discuss the code with other students for this lab.
- You must type all the code yourself and not copy from another student.
Complete these labs before class on Tuesday 2/19/19.
Project A: Code Practice
For this lab you practice coding skillz with guided exercises.
- Make sure you have completed the exercises from lesson 3 as they are submitted as part of this lab.
- Complete the Chapter 3 exercises in CodeLab. These are review exercises and you have all the information needed to complete them. If you have questions, please contact the instructor for help.
Project B: Finishing the Crab
- Scan the textbook chapter 4 to get an overview of the material.
- Complete the in-chapter exercises 4.1 through 4.26 that are listed throughout chapter 4. Exercise 4.27 is optional.
Continue with your little-crab from Lab 2. Follow the exercise steps exactly and read the textbook as you progress through the chapter to enhance your understanding. If you have a problem completing a step and need to check your work, look at the files from Ch. 2-4 of the Book scenarios.
- Exercises 4.1 through 4.9 do not directly apply to the scenario. For those exercises, create an
Actor subclass named
Exercises and add the variable declarations to the
Exercises class to ensure your variable declarations compile.
- If you declare the variables as object variables (outside a method), put the word
private in front of the variables.
- Exercise 4.5 will not compile because there is no
Control class or
Button class. Comment out this declaration.
- Exercise 4.6 needs a written text answer; see specification 6 below.
- Exercise 4.9 is a little tricky. You will need a third variable to complete the swap. Feel free to Google java swap values. Use the following print statement to verify the swap:
System.out.println("x=" + x + " y=" + y);
For those exercises steps that have a text answer, open the Scenario Information (Scenario > Scenario Information) and type the exercise number and answer at the end of the file. For example, here are my answers to the first few exercises:
Exercises with Text Answers
4.6: Variable has wrong data type
(answers needed for 4.6, 4.15, 4.16, 4.17)
Only the chapter 4 questions and answers are needed in the Scenario information.
- Add the following to the top of the Scenario Information with the "VERSION or DATE" and "AUTHORS" fields filled in:
PROJECT TITLE: Lab 3
PURPOSE OF PROJECT: Book tutorial chapter 4
VERSION or DATE: 1.0 Date Completed
AUTHORS: Your Name
- When completed, upload all the files in the scenario to Canvas as explained in the section of this document: Deliverables.
Project C: Pair Programming Worksheet
Pair programming is where two programmers work together at one computer to develop code projects. One, the driver, writes code while the other, the observer or navigator, reviews each line of code as it is typed in. The two programmers switch roles frequently . Students generally have higher confidence in their work and perform better when pair programming . These effects were tested at Cabrillo College among other places .
Programming can be beneficial, but following certain guidelines is important to maximize success . This project introduces you to the concepts and best practices of pair programming for our course programming projects.
- Watch the video Introduction to Pair Programming, a professionally developed video (10 minutes).
- Save this Pair Programming Worksheet following the menu File > Download as > Plain Text (.txt), and save the file as
- Fill out and answer the questions in
pairprogramming.txt without deleting any of the existing text.
Provide thoughtful answers for full credit.
- Submit the
pairprogramming.txt file with the rest of the assignment as described in Deliverables.
- For reference, here is a link to the The Rules of Pair Programming
References and More Information
- Pair programming: Wikipedia article
- The effects of pair-programming on performance in an introductory programming course.
- Pair Programming (Case Study 1)
- The Rules of Pair Programming
- All I Really Need to Know about Pair Programming I Learned in Kindergarten: Good suggestions on how to program in pairs.
The instructor will evaluate your lab using the following criteria. Thus you should check your lab against these criteria to maximize your XP.
Lesson Exercises (from Class)
- 2: All lesson exercises attempted and turned in
- 1: Some lesson exercises not completed and turned in or other problems found
- 0: No lesson exercises turned in or wrong folder name
Tutorial Lab (Textbook)
- 4: Demonstrates mastery of the lab exercise:
- Applies concepts from the lessons appropriately
- Follows the steps exactly
- Exercises perform correctly
- 3: Has all the major functionality expected:
- Demonstrates many techniques from the lesson
- May deviate from the specified steps in some way
- Implementation seems more complicated than necessary.
- 2: Has much of the functionality expected:
- Demonstrates some techniques from the lesson
- Deviates from the specified steps in some way
- Implementation seems excessively complicated.
- 1: Serious functional problems but shows some effort and understanding:
- Follows at least 1/2 of the of the specified steps
- Has a major error (detected by the browser) or many minor errors
- Demonstrates few techniques from the lesson
- 0: Not turned in or wrong folder name
Pair Programming Worksheet
- 4: Student completed and submitted the learning worksheet with masterful effort
- 3: Student completed and submitted the learning worksheet with substantial effort
- 2: Student completed and submitted the learning worksheet with minimal effort
- 1: Student submitted the learning worksheet
- 0: No learning worksheet submitted
Number completed correctly / number exercises * 8 and rounded up to the nearest integer.
Maximum XP: 18
CodeLab is submitted automatically, but other lab work must be submitted as described below.
- On your computer, create a folder for the lesson exercises named "lesson" (no extra characters) and place all the exercise files from Lesson 3 into this folder. Include only one "bugs" scenario, which is the culmination of all the lesson exercises completed during class.
- Create a second folder named "tutorial" (no extra characters) and place the entire "little crab" folder from chapter 4 of the textbook into this folder. Include only one scenario that contains your completed work. Do not include files from previous labs.
- Create a zip file with both folders named
lab3.zip, or one zip file for each folder with the name of the folder, and submit the zip file(s) to the Lab 3 slot of Canvas.
Please do not add any extra characters to the above folder names. Also, do not put any spaces or special characters like #, : or $ in zip file or folder names. Your crafted code must work as submitted. Remember to test and double check your files before and after submitting them. If you make a mistake, you can resubmit up to the deadline but must resubmit all your quest files.
Last Updated: February 11 2019 @15:24:47