chapter 1 object-oriented design (.. contd )

Liang, Introduction to Java Programming, Sixth Edition, (c) 2007 Pearson Education, Inc. All rights reserved. 0-13-222158-6 1

Chapter 1 Object-Oriented Design(..contd)


Objectives

To design systems by identifying the classes and discovering the relationships among these classes (§12.4).

To implement the Rational class and process rational numbers using this class (§12.5).

To design classes that follow the class-design guidelines (§12.6).

To model dynamic behavior using sequence diagrams and statechart diagrams (§12.7 Optional)

To know the concept of framework-based programming using Java API (§12.8).


Class Design

1. Identify classes for the system.

2. Describe attributes and methods in each

class.

3. Establish relationships among classes.

4. Create classes.


Class Design Guidelines/Issues Cohesion and Consistency: Designing a

Single Class. Encapsulation: Using Modifiers public,

protected, private and static Using Inheritance or Aggregation Using Interfaces or Abstract Classes


Designing a Class A class should describe a single entity or a set of

similar operations. A single entity with too many responsibilities can

be broken into several classes to separate responsibilities.

The String class, StringBuffer class, and StringTokenizer class all deal with strings, for example, but have different responsibilities.


Designing a Class, cont. Classes are usually designed for use by many

different customers. To make a class useful in a wide range of

applications, the class should provide a variety of ways for customization through properties and methods.


Designing a Class, cont. Classes are designed for reuse. Users can incorporate classes in many different

combinations, orders, and environments. Therefore, you should design a class that imposes

no restrictions on what or when the user can do with it, design the properties to ensure that the user can set properties in any order, with any combination of values, and design methods to function independently of their order of occurrence.


Designing a Class, cont. Provide a public no-arg constructor and override the equals

method and the toString method defined in the Object class whenever possible.

Follow standard Java programming style and naming conventions.

Choose informative names for classes, data fields, and methods.

Always place the data declaration before the constructor, and place constructors before methods.

Always provide a constructor and initialize variables to avoid programming errors.


Using Visibility Modifiers Each class can present two contracts – one for the users of the class

and one for the extenders of the class. Make the fields private and accessor methods public if they are

intended for the users of the class. Make the fields or method protected if they are intended for

extenders of the class. The contract for the extenders encompasses the contract for the

users. The extended class may increase the visibility of an instance

method from protected to public, or change its implementation, but you should never change the implementation in a way that violates that contract.


Using Visibility Modifiers, cont. A class should use the private modifier to hide its data from direct

access by clients.

You can use get methods and set methods to provide users with access to the private data, but only to private data you want the user to see or to modify.

A class should also hide methods not intended for client use.

The gcd method in the Rational class in Example 12.2, “The Rational Class,” is private, for example, because it is only for internal use within the class.


Using the static Modifier

A property that is shared by all the instances of the class should be declared as a static property.


Using Inheritance or AggregationThe difference between inheritance (is-an-extension-of) and aggregation (has-a)

For example, an apple is fruit; thus, you would use inheritance to model the relationship between the classes Apple and Fruit.

A person has a name; thus, you would use aggregation to model the relationship between the classes Person and Name.


Using Inheritance or Aggregation, cont.

Sometimes, the choice between inheritance and aggregation is not obvious.

For example, you have used inheritance to model the relationship between the classes Circle and Cylinder.

One could argue that a cylinder consists of circles; thus, you might use aggregation to define the Cylinder class as follows:


Using Inheritance or Composition, cont.

public class Cylinder { private Circle circle; /** Constructors */ /** Methods */}


Using Inheritance or Aggregation, cont.

Both designs are fine. Which one is preferred? If polymorphism is desirable, you need to use the inheritance design. If you don’t care about polymorphism, the aggregation design gives more flexibility because the classes are less dependent using aggregation than using inheritance.


Using Interfaces or Abstract Classes

Both interfaces and abstract classes can be used to generalize common features. How do you decide whether to use an interface or a class?

Liang, Introduction to Java Programming, Sixth Edition, (c) 2007 Pearson Education, Inc. All rights reserved. 0-13-222158-6

A strong is-an-extension-of relationship

In general, a strong is-an-extension-of relationship that clearly describes a parent-child relationship should be modeled using classes.

For example, since an orange is a fruit, their relationship should be modeled using class inheritance.

17


A weak is-an-extension-of relationship

A weak is-an-extension-of relationship, also known as an is-kind-of relationship, indicates that an object possesses a certain property.

A weak is-an-extension-of relationship can be modeled using interfaces.

Liang, Introduction to Java Programming, Sixth Edition, (c) 2007 Pearson Education, Inc. All rights reserved. 0-13-222158-6

ComparableFor example, all strings are comparable, so the String class implements the Comparable interface. A circle or a rectangle is a geometric object, for example, so Circle can be designed as a subclass of GeometricObject. Circles are different and comparable based on their radius, for example, so Circle can implement the Comparable interface.

19


Using Interfaces or Abstract Classes, cont.

Interfaces are more flexible than abstract classes, because a subclass can extend only one superclass, but implement any number of interfaces.

However, interfaces cannot contain concrete methods.

You can combine the virtues of interfaces and abstract classes by creating an interface with a companion abstract class that implements the interface.

So you can use the interface or its companion class whichever is more convenient.


Sequence diagramsSequence diagrams describe interactions among objects by depicting the time ordering of method invocations.

anObject: TheClass Class role

Method Invocation

Activation

anotherObject: TheOtherClass

Method InvocationanotherMethod()

aMethod()


Sequence diagrams, cont.

name: Name : BorrowLoan address: Address loan: Loan borrower: Borrower

setFirstName

setMi

setLastName

setStreet

setCity

setState

setZip

setAnnualInterestRate

setNumOfYears

setLoanAmount

setName

setAddress

setLoan


Statechart diagramsStatechart diagrams describe flow of control of the object.

IndicateInitial State

Transition

State1

State2


Statechart diagrams, cont.

Class Loaded

JVM loads the class for the object

Use the new operator to create the object

Object Created

Invoke the finalize method on the object

Object Destroyed


Supplement P: Designing Generic Matrix Classes

Objective: This example gives a generic class for matrix arithmetic. This class implements matrix addition and multiplication common for all types of matrices.

GenericMatrix


Example 12.3, cont.

GenericMatrix -matrix: Object[][] #GenericMatrix(matrix: Object[][]) +getMatrix(): Object[][] +setMatrix(matrix: Object[][]): void +addMatrix(secondMatrix: Object[][]): Object[][] +multiplyMatrix(secondMatrix: Object[][]): Object[][] +printResult(m1: GenericMatrix, m2: GenericMatrix, m3: GenericMatrix, op: char): void #createGenericMatrix():GenericMatrix #add(o1: Object, o2: Object): Object #multiply(o1: Object, o2: Object): Object #zero():Object

IntegerMatrix

RationalMatrix


Example 12.3, cont.

Objective: This example gives two programs that utilize the GenericMatrix class for integer matrix arithmetic and rational matrix arithmetic.

TestIntegerMatrix Run

TestRationalMatrix RunRationalMatrix

IntegerMatrix


The Java APIThe Java API (Application Program Interface, Application Programming Interface, or Application Programmer interface) consists of numerous classes and interfaces grouped into more than a dozen of packages.

You have used classes and interfaces in the java.lang, javax.swing, and java.util packages.


Framework-Based ProgrammingTo create comprehensive projects, use more classes and interfaces in the Java API. The classes and interfaces in the Java API establish a framework for programmers to develop applications using Java. For example, the classes and interfaces in the Java GUI API establish a framework for developing GUI programs. Use these classes and interfaces and follow their conventions and rules to create applications.


Framework-Based Programming, cont.

Once you understand the concept of Java and object-orient programming, the most important lesson from now on is learning how to use the API to develop useful programs. The most effective way to achieve it is to imitate good examples.

chapter 1 object-oriented design (.. contd )

Documents

single class

rational class

stringtokenizer class

stringbuffer class

class useful

object class

classa class

string class