Register your product to gain access to bonus material or receive a coupon.
Java Design: Building Better Apps and Applets, 2nd Edition
- By Peter Coad, Mark Mayfield, Jon Kern
- Published Dec 8, 1998 by Pearson.
Book
- Sorry, this book is no longer in print.
Description
- Copyright 1999
- Edition: 2nd
- Book
- ISBN-10: 0-13-911181-6
- ISBN-13: 978-0-13-911181-5
91118-0
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 design appropriate 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).
Sample Content
Downloadable Sample Chapter
Click here for a sample chapter for this book: 0139111816.pdf
Table of Contents
Why Java Design?
Design. Java-Inspired Design. A Design Book. The Companion CD-ROM. How to Get Updates. Feedback, Hands-on Workshops, and Mentoring.
Chapter 1: Design by Example.
Five Major Activities. Example, Example, Example. Charlie's Charters. Identify the Purpose and Features. Select the Classes. Sketch a UI. Work Out Dynamics with Scenarios. Build a Class Diagram. Zoe's Zones. Identify the Purpose and Features. Selecting Classes. Sketch a UI. Work Out Dynamics with Scenarios. Build a Class Diagram. Summary.
Chapter 2: Design with Composition, Rather than Inheritance.
Composition. Composition: An Example. Inheritance. Inheritance vs. Interfaces. Inheritance: An Example. Inheritance: Benefits. Inheritance: Risks. Inheritance: When to Use It. Inheritance: Checkpoints. Example: Composition (the Norm). Example: Both Composition and Inheritance. Example: Inheritance (the Exception). Example: Inheritance in Need of Adjustment. Example: Thread. Example: Applet. Example: Observable. Summary.
Chapter 3: Design with Interfaces.
What Are Interfaces? Why Use Interfaces? The Problem. A Partial Solution. Flexibility, Extensibility, and Pluggability-That's Why. Factor-out Interfaces. Factor Out Repeaters. Factor Out to a Proxy. Factor Out for Analogous Apps. Factor Out for Future Expansion. A Short Interlude: Where to Add Interfaces. Design-in Interfaces. Design-in Interfaces Based on Common Features. Design-in Interfaces Based on Role Doubles. Design-in Interfaces Based on Behavior Across Roles. Design-in Interfaces Based on Collections and Members. Design-in Interfaces Based on Common Interactions. Design-in Interfaces Based on Intra-Class Roles. Design-in Interfaces Based on a Need for Plug-in Algorithms. Design-in Interfaces Based on a Need for Plug-in Feature Sequences. Design with Interfaces: Applying Multiple Strategies. Designing-in Flexibility Is a Very Good Thing. Yet There Usually Is a Design Tradeoff: Simplicity vs. Flexibility. Naming Interfaces Revisited. What Java Interfaces Lack. Summary.
Chapter 4: Design with Threads.
Threads. What Is a Thread? How Do Threads Get Started? Why Use Multiple Threads? If You Don't Need Multiple Threads, Don't Use Them. Sync. Sync: A Guarantee and a Nonguarantee. Sync: Scope. Shared Value (and Keeping Out of Trouble). Don't Sync Longer Than You Have To. Shared Resource (and Keeping Out of Trouble). Multiple Clients, Multiple Threads within an Object. Multiple Thread Objects, Multiple Threads within an Object. Single Thread. Prioritized-Object Threads. Prioritized-Method Threads. Prioritized-Method Prioritized-Object Threads. Overall Point. Interface Adapters. Need. One Approach: Dispatcher. A Better Approach: Interface Adapters. What an Interface Adapter Looks Like. Interface Adapters for Zoe's Zones. A Zone-Monitoring Thread. A Sensor-Assessing Thread and a Sensor-Monitoring Thread. Summary.
Chapter 5: Design with Notification.
Passive Notification. Timer-Based Notification. Timer-Notification Pattern. A Timer for Charlie's Charters. Active Notification. Observable-Observer. Source-Listener. Source-Support-Listener (JavaBeans-Style Notification). Producer-Bus-Consumer (InfoBus-Style Notification). Model-View-Controller (Swing-Style Notification). Source-Distributed Listeners (Enterprise JavaBeans-Style Notification). Summary.
Appendix A Design Strategies.
Appendix B Notation Summary.
Appendix C Java Visibility.
Bibliography.
Index.
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)
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