Object-Oriented Design - Java Software Solutions: Foundations of Program Design - page 372

Summary of Key Concepts

The effort put into design is both crucial and cost effective.

■

The nouns in a problem description may indicate some of the classes and
objects needed in a program.

■

A static variable is shared among all instances of a class.

■

An aggregate object is composed of other objects, forming a has-a
relationship.

■

An interface is a collection of abstract methods and therefore cannot be
instantiated.

■

The values of an enumerated type are static variables of that type.

■

We can add attributes and methods to the definition of an enumerated
type.

■

A complex service provided by an object can be decomposed to make use
of private support methods.

■

When an object is passed to a method, the actual and formal parameters
become aliases.

■

The versions of an overloaded method are distinguished by the number,
type, and order of their parameters.

■

Testing a program can never guarantee the absence of errors.

■

A good test is one that uncovers an error.

■

It is not feasible to exhaustively test a program for all possible input and
user actions.

■

The design of any GUI should adhere to basic guidelines regarding consis-
tency and usability.

■

The layout manager of a container determines how components are visu-
ally presented.

■

When changes occur, the components in a container reorganize themselves
according to the layout manager's policy.

■

The layout manager for each container can be explicitly set. ■

Borders can be applied to Swing components to group objects and focus
attention.

■

A GUI's appearance is a function of the containment hierarchy and the
layout managers of each container.

■