ITEC 120 2009spring ibarland nokie jmdymacek

home—info—lects—labs—exams—hws
textbook—tutor/PIs—java.lang docs—java.util docs

lect04c
practice designing classes
revising Songs

Today we'll revisit the SongTester class we wrote as part of hw02—songs and rectangles's solution . We'll see how classes are a better way to organize information than a bunch of local variables.

Consider a class Song. Its object have what sort of behaviors?

• What would a test-class look like? (Come up w/ two tests) [solution]

---

[Sect-02 reached here, Feb.16 (Mon)]

• Group exercise: Let's write the signatures. (They follow from the test-class we just wrote!) [solution]
• [On your own:] By the way: Note that in general, the signatures can often be inferred from the test-cases, even if you have no idea what the method does. For example:
  Write the signature for the constructor and methods being called:

  Floober f; f = new Floober( "Betelgeuse", 3.7 ); double x = Math.sqrt( f.squibsquib( 7, "NCC-1701" ) ); int n = (f.gluzzzzx()).length();

  (Yes, it is intentional that you have no idea what these do/mean; you can still identify the methods, and write their signatures.) [solution]

We'll continue next time, writing the signatures and method bodies.

home—info—lects—labs—exams—hws
textbook—tutor/PIs—java.lang docs—java.util docs

©2009, Ian Barland, Radford University Last modified 2009.Feb.20 (Fri)

Please mail any suggestions (incl. typos, broken links) to iba�rlandrad�ford.edu