Lecture 28

Announcements

Test Review

Test 2 is held during normal class meeting time. It is 50 minutes long (even if you are in 1111).

LNEC and excused absences should already know about their arrangements. If you do not, contact LNEC or your professor immediately!

Test 2 Review Sheet

Topics

• General Points
  • There will be questions involving coding; problem solving will be involved.
  • You should be able to read code and interpret what it is doing.
  • The test is 50 minutes long (both 1110 and 1111).
• Not on the test
  • Writing a full class's code. Snow delays means we will only test small classes on this exam.
  • Test 1 questions. The test concepts are cumulative, but test questions will be intended to measure mastery of new material.
  • You do not have to know what to import to get access to various classes.
• Arrays and ArrayList
  • How to define, create, store in, and read from an array (see lecture 16).
  • String's split method; reading csv files.
  • Reading and writing array code.
  • Reading (but not writing) 2D array code.
  • How to use ArrayLists; how arrays and ArrayList differ (see lecture 19).
• Methods
  • The parts of a method: public vs private, static vs non-static, return type (including void), name, parameters, body.
  • Difference between defining and invoking a method.
  • return statements.
  • How to write and read methods.
• Classes
  • Basic concepts: what classes are, how to pick fields for a class, how to use classes in code.
  • Fields (also known as attributes or state).
  • Methods (also known as behaviors).
  • Special methods: getters, setters, constructors.
  • Drawing UML Class Diagrams.
  • Turning parts of UML Class Diagrams into code.
  • Because of snow delays, writing a full, detailed class implementation will be postponed until the final; however, questions asking for any particular part of a class (header, field definitions, particular methods or constructors) are fair game.

Studying for the Test

1. Practice coding without using Eclipse.

   You'll be writing code on paper. This feels different than writing it in Eclipse. You don't want to be surprised by how different it feels. Practice writing code by hand.

   A few small syntax errors is OK. But if you are really off we will take off points. Try to write correct code

   You will never need to add import statements, but you might need to write class declaration, method declaration, etc.

   Try re-solving the homework problems on paper without looking at your code or textbook.

   You can find more sample problems in Programming Challenges in the textbook; try, for example, chapter 5's problems 4, 5, 6, 7, 8, and 15; and chapter 6's problems 1, 2, and 7.

   Also remember that speed matters. 50 minutes is not a long time.

2. Read programs.

   We'll show you code and ask you what it does. You won't be able to have Java run it. Practice thinking through code without running it. Drawing memory pictures can be very helpful, but memory sketches will not be on the test directly.

3. Review the Lecture Notes.

   Not everything in the book is equally important. Review the lecture notes to see what we emphasized. If you are confused by some point, check the podcast.

From in-class review:

Section 002 (1pm)

Exam2Rewiew.java, Neanderthal.java, and Quiz9Q4.java

Section 001 (3pm)

Exam2Review.java, Puppy.java