Java Design: Designing with Components with CD-ROM

Java Design: Designing with Components with CD-ROM

Multimedia Set(2ND BK&CDR)

$44.99

Temporarily Out of Stock Online

Eligible for FREE SHIPPING

Overview

Java Design: Designing with Components with CD-ROM by Peter Coad, Jon Kern, Mark Mayfield

Praise for Java Design: Building Better Apps & Applets, Second Edition:

"This is a revolutionary book in the Java programming book market since it doesn't teach you how to program ... This is a book for those who need to implement large and complex applications and want to learn how to use all the powerful mechanisms offered by the language in order to create better and well-organized applications." —Book Review, Java Universe Developer

"Just finished devouring Java Design and I loved it! I think it is one of those books that will influence my thinking for years to come. (And there have only been a few other books like it in my experience.)" —John Pinto, Director of R&D, Precision Programming, Inc.

"I read with great pleasure your new book. Being an enthusiastic Java programmer I really appreciated your excellent combination of OO design principles and Java concepts like interfaces." —Harald Nekvasil, TAB Ltd.

Get down to business with Coad and Mayfield as they systematically unfold essential strategies for designing better Java apps.

Key Features:

  • How to develop an overall design-model shape fast, effectively, efficiently.
  • How to get the most from composition and inheritance. If you are in a hurry, be sure to read Chapters 2 and 3. These chapters will move you and will forever change the way you design. Your designs will be far more flexible; you'll gain the recognition and rewards that follow.
  • How to design responsible threads. When, how, and why to design-in threads. When you must have threads, when to avoid them.
  • How to designappropriate notification mechanisms. Especially important when you want design-in loose coupling among the major subsystems in your design.

New in the Second Edition:

  • UML 1.2 notation throughout.
  • 8 new strategies for designing with interfaces (12 total).
  • Responsible threads.
  • Inner classes for adapters.
  • 5 new notification mechanisms.

Java Design also includes a CD-ROM with source code, design strategies, and Together/J Whiteboard Edition from Object International (www.togetherj.com).

Author Biography:

PETER COAD is one of the world's most experienced designers—he has designed hundreds of component and object systems, within nearly every industry imaginable. Peter's current work focuses on Java-inspired design for building better systems. pc@oi.com, www.oi.com

MARK MAYFIELD is the Senior Object-Model Architect at Net Explorer, Inc. and has co-authored two of Peter Coad's series of five books. mmayfield@netexplorer.com www.netexplorer.com

JON KERN is a Coad-certified Mentor. Also, he is President of Lightship, Inc. (software development), where Java and C++ are the norm.

Product Details

ISBN-13: 9780139111815
Publisher: Pearson Education
Publication date: 12/08/1998
Series: YOURDON Press Computing Series
Edition description: 2ND BK&CDR
Pages: 352
Product dimensions: 7.01(w) x 9.21(h) x 0.90(d)

About the Author


Peter Coad is one of the world's most experienced designers - he has designed hundreds of component and object systems, within nearly every industry imaginable. Peter's current work focuses on Java-inspired design for building better systems. pc@oi.com, www.oi.com.

Jon Kern is a Coad-certified Mentor. Also, he is President of Lightship, Inc. (software development), where Java and C++ are the norm.

Read an Excerpt

It's been two years since the writing of the first edition of Java Design. Java is growing up nicely and is gaining widespread acceptance in many industries around the globe. All of our workshops and mentoring are with Java projects now, an exciting transition from the "just getting started" times of two short years ago.

In the first edition, we set out to write a book on design rather than programming. We did this for several reasons. One, we are designers at heart; we architect and shape large software systems for a living and truly love what we do. Two, we realize that there are hundreds (and hundreds) of Java programming books today-and that we have little to add to that genre. Three, we seek to write books that have lasting value, and so, did our best to insulate valuable design content from the evolution of Java and related technologies. The first edition has stood the test of time. While some Java programming books have gone through as many as four editions, Java Design has continued as a best-seller for two years running.

The biggest visual change is the second edition's complete transition to UML notation. We've worked with UML (currently version 1.2) for some time now on real projects. We've looked for ways to use it more effectively, still communicating some of the subtleties of earlier notations. More and more readers have asked for us to make this move. In this edition we do so.

The biggest content change is the second edition's many new sections, 68 pages of new material, delivering:

  • Eight new "design with interfaces" strategies (Chapter 3)
    • 1. Design-in: common features
    • 2.Design-in: role doubles
    • 3. Design-in: behavior across roles
    • 4. Design-in: collections and members
    • 5. Design-in: common interactions
    • 6. Design-in: intra-class roles
    • 7. Design-in: plug-in algorithms
    • 8. Design-in: feature sequences
  • How to design a "responsible thread," one that knows when it can safely terminate itself (Chapter 4)
  • How to use inner classes to encapsulate interface adapters (Chapter 5)
  • Five additional notification mechanisms (Chapter 5)
    • 1. Source-listener
    • 2. Source-support-listener (JavaBeans-style notification)
    • 3. Producer-bus-consumer (InfoBus-style notification)
    • 4. Model-view-controller (Swing-style notification)
    • 5. Source-listener across a network (Enterprise JavaBeans-style notification)
We hope you enjoy this new material as much as we have enjoyed developing it in practice. Thank you to each of you who have taken the time to write with feedback, suggestions, kind words, and gentle nudges. We value you and your input.

Yours for better design,

Peter Coad
President, Object International, Inc.
coad@oi.com
www.oi.com

Mark Mayfield
Senior Object-Model Architect, Net Explorer., Inc.
mmayfield@netexplorer.com
www.netexplorer.com

Table of Contents

Why Java Design? 1(6)
Design 2(1)
Java-Inspired Design 2(2)
A Design Book 4(1)
The Companion CD-ROM 5(1)
How to Get Updates 6(1)
Feedback, Hands-on Workshops, and Mentoring 6(1)
Chapter 1 Design by Example
7(42)
1.1 Five Major Activities
8(1)
1.2 Example, Example, Example
9(1)
1.3 Charlie's Charters
10(25)
1.3.1 Identify the Purpose and Features
10(2)
1.3.2 Select the Classes
12(3)
1.3.3 Sketch a UI
15(2)
1.3.4 Work Out Dynamics with Scenarios
17(7)
1.3.5 Build a Class Diagram
24(11)
1.4 Zoe's Zones
35(12)
1.4.1 Identify the Purpose and Features
36(1)
1.4.2 Selecting Classes
37(1)
1.4.3 Sketch a UI
38(2)
1.4.4 Work Out Dynamics with Scenarios
40(3)
1.4.5 Build a Class Diagram
43(4)
1.5 Summary
47(2)
Chapter 2 Design with Composition, Rather than Inheritance
49(32)
2.1 Composition
50(1)
2.1.1 Composition: An Example
50(1)
2.2 Inheritance
51(8)
2.2.1 Inheritance vs. Interfaces
51(1)
2.2.2 Inheritance: An Example
52(1)
2.2.3 Inheritance: Benefits
52(1)
2.2.4 Inheritance: Risks
53(3)
2.2.5 Inheritance: When to Use It
56(2)
2.2.6 Inheritance: Checkpoints
58(1)
2.3 Example: Composition (the Norm)
59(4)
2.4 Example: Both Composition and Inheritance
63(2)
2.5 Example: Inheritance (the Exception)
65(4)
2.6 Example: Inheritance in Need of Adjustment
69(3)
2.7 Example: Thread
72(3)
2.8 Example: Applet
75(2)
2.9 Example: Observable
77(2)
2.10 Summary
79(2)
Chapter 3 Design with Interfaces
81(92)
3.1 What Are Interfaces?
81(3)
3.2 Why Use Interfaces?
84(4)
3.2.1 The Problem
84(2)
3.2.2 A Partial Solution
86(1)
3.2.3 Flexibility, Extensibility, and Pluggability--That's Why
86(2)
3.3 Factor-out Interfaces
88(38)
3.3.1 Factor Out Repeaters
89(12)
3.3.2 Factor Out to a Proxy
101(10)
3.3.3 Factor Out for Analogous Apps
111(9)
3.3.4 Factor Out for Future Expansion
120(6)
3.4 A Short Interlude: Where to Add Interfaces
126(2)
3.5 Design-in Interfaces
128(32)
3.5.1 Design-in Interfaces Based on Common Features
130(3)
3.5.2 Design-in Interfaces Based on Role Doubles
133(3)
3.5.3 Design-in Interfaces Based on Behavior Across Roles
136(3)
3.5.4 Design-in Interfaces Based on Collections and Members
139(4)
3.5.5 Design-in Interfaces Based on Common Interactions
143(4)
3.5.6 Design-in Interfaces Based on Intra-Class Roles
147(2)
3.5.7 Design-in Interfaces Based on a Need for Plug-in Algorithms
149(4)
3.5.8 Design-in Interfaces Based on a Need for Plug-in Feature Sequences
153(7)
3.6 Design with Interfaces: Applying Multiple Strategies
160(4)
3.6.1 Designing-in Flexibility Is a Very Good Thing
160(1)
3.6.2 Yet There Usually Is a Design Tradeoff: Simplicity vs. Flexibility
161(3)
3.7 Naming Interfaces Revisited
164(3)
3.8 What Java Interfaces Lack
167(1)
3.9 Summary
168(5)
Chapter 4 Design with Threads
173(50)
4.1 Threads
173(11)
4.1.1 What Is a Thread?
173(1)
4.1.2 How Do Threads Get Started?
174(2)
4.1.3 Why Use Multiple Threads?
176(1)
4.1.4 If You Don't Need Multiple Threads, Don't Use Them
176(1)
4.1.5 Sync
177(1)
4.1.6 Sync: A Guarantee and a Nonguarantee
178(1)
4.1.7 Sync: Scope
179(1)
4.1.8 Shared Value (and Keeping Out of Trouble)
179(2)
4.1.9 Don't Sync Longer Than You Have To
181(1)
4.1.10 Shared Resource (and Keeping Out of Trouble)
182(2)
4.2 Multiple Clients, Multiple Threads within an Object
184(3)
4.3 Multiple Thread Objects, Multiple Threads within an Object
187(16)
4.3.1 Single Thread
188(2)
4.3.2 Responsible Thread
190(2)
4.3.3 Prioritized-Object Threads
192(4)
4.3.4 Prioritized-Method Threads
196(4)
4.3.5 Prioritized-Method Prioritized-Object Threads
200(3)
4.3.6 Overall Point
203(1)
4.4 Interface Adapters
203(17)
4.4.1 Need
204(1)
4.4.2 One Approach: Dispatcher
204(1)
4.4.3 A Better Approach: Interface Adapters
204(1)
4.4.4 What an Interface Adapter Looks Like
205(8)
4.4.5 Interface Adapters for Zoe's Zones
213(1)
4.4.6 A Zone-Monitoring Thread
213(1)
4.4.7 A Sensor-Assessing Thread and a Sensor-Monitoring Thread
213(7)
4.5 Summary
220(3)
Chapter 5 Design with Notification
223(66)
5.1 Passive Notification
224(2)
5.2 Timer-Based Notification
226(7)
5.2.1 Timer-Notification Pattern
226(4)
5.2.2 A Timer for Charlie's Charters
230(3)
5.3 Active Notification
233(52)
5.3.1 Observable-Observer
234(31)
5.3.2 Source-Listener
265(4)
5.3.3 Source-Support-Listener (JavaBeans-Style Notification)
269(6)
5.3.4 Producer-Bus-Consumer (InfoBus-Style Notification)
275(4)
5.3.5 Model-View-Controller (Swing-Style Notification)
279(3)
5.3.6 Source-Distributed Listeners (Enterprise JavaBeans-Style Notification)
282(3)
5.4 Summary
285(4)
Appendix A Design Strategies 289(8)
Appendix B Notation Summary 297(2)
Appendix C Java Visibility 299(2)
Bibliography 301(2)
Index 303

Preface

PREFACE: It's been two years since the writing of the first edition of Java Design. Java is growing up nicely and is gaining widespread acceptance in many industries around the globe. All of our workshops and mentoring are with Java projects now, an exciting transition from the "just getting started" times of two short years ago.

In the first edition, we set out to write a book on design rather than programming. We did this for several reasons. One, we are designers at heart; we architect and shape large software systems for a living and truly love what we do. Two, we realize that there are hundreds (and hundreds) of Java programming books today-and that we have little to add to that genre. Three, we seek to write books that have lasting value, and so, did our best to insulate valuable design content from the evolution of Java and related technologies. The first edition has stood the test of time. While some Java programming books have gone through as many as four editions, Java Design has continued as a best-seller for two years running.

The biggest visual change is the second edition's complete transition to UML notation. We've worked with UML (currently version 1.2) for some time now on real projects. We've looked for ways to use it more effectively, still communicating some of the subtleties of earlier notations. More and more readers have asked for us to make this move. In this edition we do so.

The biggest content change is the second edition's many new sections, 68 pages of new material, delivering:
  • Eight new "design with interfaces" strategies (Chapter 3)
    • 1. Design-in: common features 2. Design-in: role doubles
    • 3. Design-in: behavior across roles
    • 4. Design-in: collections and members
    • 5. Design-in: common interactions
    • 6. Design-in: intra-class roles
    • 7. Design-in: plug-in algorithms
    • 8. Design-in: feature sequences
  • How to design a "responsible thread," one that knows when it can safely terminate itself (Chapter 4)
  • How to use inner classes to encapsulate interface adapters (Chapter 5)
  • Five additional notification mechanisms (Chapter 5)
    • 1. Source-listener
    • 2. Source-support-listener (JavaBeans-style notification)
    • 3. Producer-bus-consumer (InfoBus-style notification)
    • 4. Model-view-controller (Swing-style notification)
    • 5. Source-listener across a network (Enterprise JavaBeans-style notification)
We hope you enjoy this new material as much as we have enjoyed developing it in practice. Thank you to each of you who have taken the time to write with feedback, suggestions, kind words, and gentle nudges. We value you and your input.

Yours for better design,

Peter Coad
President, Object International, Inc.
coad@oi.com
www.oi.com

Mark Mayfield
Senior Object-Model Architect, Net Explorer., Inc.
mmayfield@netexplorer.com
www.netexplorer.com

Customer Reviews

Most Helpful Customer Reviews

See All Customer Reviews