Software designers, developers, and architects are constantly confronted with the same confounding problem: how to design software that is both flexible and resilient amid change. To accomplish this tall task, practitioners must utilize the best available technologies to the fullest.
Java Design relies on a combination of best practices and best-of-breed technologies to create a clear and concise guide to building high-quality, lasting software designs. In particular, the author provides unique insight into using the Unified Modeling Language (UML) to develop Java applications.
The first half of the book focuses on the software process and how UML, Java technology, and object-oriented programming can be used effectively. The advantages of each technology are enumerated, highlighting common principles. Also included are in-depth discussions of design patterns, the Unified Process, and Extreme Programming.
The second half of the book describes how these complementary technologies can be used together as a system of checks and balances to ensure successful creation of high-quality software. You'll also find details on modeling strategies, a phased approach to adopting each of the technologies outlined, and the design of subsystems.
Key topics include:
Armed with a fresh perception of current design tools, this book will give you a deeper understanding of how to design cleaner Java applications using UML. Learn how you can expand your developer's toolkit using existing technologies in new ways--and create better software.
Kirk Knoernschild is a hands-on software consultant who is passionate about using leading best practices to build better software. In addition to his work on large development projects, Kirk shares his experiences through courseware development and teaching, writing, and speaking at seminars and conferences on UML, Java J2EE technology, object-oriented programming, software architecture, the Rational Unified Process, and Extreme Programming. Kirk can be reached at kirk@kirkk.com, or by visiting his Web site at www.kirkk.com.
Product Details
Would you like to update product info or give feedback on images?
|
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
5 of 6 people found the following review helpful:
5.0 out of 5 stars
For programmers who has mastered the basics of Java,
By Midwest Book Review (Oregon, WI USA) - See all my reviews
This review is from: Java Design: Objects, UML, and Process (Paperback)
Java Design: Objects, UML, And Process by software is consultant and Java expert Kirk Knoernschild a comprehensive computer programmer's reference for the creation of high quality, useful, reusable, and long-lasting software designs. Individual chapters cover the basics of UML, modeling strategies, analyzing problems, designing subsystems and much more. Java Design: Objects, UML, And Process is a superbly organized and presented reference for programmers who has mastered the basics of Java and are ready to broaden their applied skills and expertise in the robust, highly practical, and increasingly popular computer language of Java.
2 of 2 people found the following review helpful:
5.0 out of 5 stars
AGILE application of Objects, UML, and Process,
By
Amazon Verified Purchase(What's this?)
This review is from: Java Design: Objects, UML, and Process (Paperback)
I came across this book after reading The Elements of UML Style's Bibliography by Scott W. Ambler who is a founder and thought leader on the Agile Modeling methodology. I thought it might explain a different way to do OOAD using UML compared to books written by Craig Larman. Not really.But the surprise to me was how agile it made the use of OO, UML, and process. The title should be: Agile Java Design Objects, UML, and Process. This only the book that I have read that made me feel confident about using RUP and how it's use should not slow down the process. While I have read other UML modeling books, none of them made it clear to not get hung up on every detail in each iteration. The book is shorter some of other UML OO books and this adds to its agility. It directs you to get through the process more quickly and to not lose sight of the end goal. Here's a nugget: "However, even more important is satisfying use requirements in the allotted time frame. Don't spend a lot of time trying to find the best solution the first time. Instead, find something that works and continue to refine and improve that system throughout the development effort." Also, the book has numerous best practices and best-of-breed technologies on object-oriented analysis and design that I have not read in any other books. For example, while it emphasizes that architecture plays a key role, it says it is advantageous to use UML to obtain feedback from peers and mentors, and to develop throwaway prototypes as Frederick Brooks recommended in the Mythical Man-Month to contribute to a more resilient, robust, and flexible final product. The bottom-line surprise was that this book helped me guage the appropriate level of detail for an software architecture document and tells why reverse-engineering source is inappropriate for this. As Kirk writes, "We should be cautious when producing detailed, low-level diagrams because they risk becoming outdated as our internal code structure changes. Instead, higher-level, architecturally signficant diagrams should be created that communicate our architecture and solve complex architectural challenges. In general, our golden rule should be to produce any artifact only if it contributes positively to the development of better software."
4 of 5 people found the following review helpful:
3.0 out of 5 stars
If you CAN read it's a good book...,
By
This review is from: Java Design: Objects, UML, and Process (Paperback)
Whilst not perfect (an it is a bit wordy), this is a good overview of a difficult topic which is too often overlooked by other books. It isn't as trendy as XP (which this book mentions in passing) or future-perfect at AOP but the use of UML with a robust process for developing applications such as that espoused by this book will keep you out of a whole lot of trouble. Where this book goes wrong, in my opinion, is the overcomplication in the terminology used. The processes described are fairly simple in themselves - it's just the way they're explained which isn't. In short, a good technical editor would've helped this book immensely. If you're interested in a simpler (but less process oriented solution), try Enterprise Java with UML by CT Arrington which is, so far the best book on this subject.
Share your thoughts with other customers: Create your own review
|
|
|
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|