Jeff Martens' IS247 & Java Page
The text is Lewis, DePasquale, and Chase Java Foundations,
second edition. We do not directly use the CD or anything on the
CD, so a used copy of the text missing the CD is fine.
For More Practice:
IS 247 is a three credit course, so students are expected to spend
6-9 hours per week on IS 247 outside of class. This means reading
the text, reviewing the notes, doing the assignments, and,
especially, programming. To do well most students will have to
spend more time programming than is afforded by graded
assignments.
- The lecture notes have many examples that can be run,
modified, etc.
- The lecture notes often suggest extra programming
exercises.
- The text has examples, questions, and suggested programming
problems.
-
An excellent source for extra practice is David
Eck's Introduction
to Programming Using Java, 6th edition. At the end of
each chapter Eck has placed a chapter quiz, with answers, and
related programming exercises, with sample solutions.
-
thenewboston.com
has many Java tutorials in video format which are fairly
good. Note, though, that these videos do not follow typical
Java coding conventions, e.g., capitalization of class
names. Also, the videos do not cover data structures-related
issues.
Local Stuff:
- Code examples from the lecture notes
are here, organized by chapter.
- Advice
on answering a common type of test question.
- A brief introduction to space and time complexity
is here.
- Some tests and quizzes from Spring
2008. Also, the first test from IS
247-2 spring 2011. These may or may not resemble those given
in any other semester, including this semester.
- Foreach, Arrays, and
Enums: Discussion
and Working Code
- The
Iterator and Iterable
interfaces. What's
the difference? How are they related?
- Using
Scanner
to process
input.
- WhereAmI.java is a quick
little ditty to display the current working directory. It
illustrates use of a static method from
the
System class, provides a static method that
can be called from elsewhere to get a process's current
working directory, or can be run from a GUI IDE to determine
the current working directory in that environment. This is the
intended primary use: when writing Java programs that perform
file I/O, knowing the current working directory often
simplifies matters. Often, the IDE hides this from the
student, making this tool useful.
-
Sometimes it is useful to know how long it takes to run a
piece of code. I have a brief discussion of this and a simple
tool here.
External Links:
