Fundamentals Of Object-Oriented Design In Uml

Fundamentals Of Object-Oriented Design In Uml

Fundamentals of Object-Oriented Design in UML shows aspiring and experienced programmers alike how to apply design concepts, the UML, and the best practices in OO development to improve both their code and their success rates with object-based projects.From the Inside Flap"You say you want some evolution. Well, you know, I'm just doing what I can." -- Charles Darwin, On the Origin of Species People who reviewed this book in its draft form had several questions for me, questions that perhaps you share. Let me address some of them. I'm a programmer. Why should I care about design? Everyone who writes code also designs code -- either well or badly, either consciously or unconsciously. My goal in writing this book is to encourage people working in OO -- and their number increases annually - to create good object-oriented designs consciously and prior to coding. To this end, I introduce notation, principles and terminology that you and your colleagues can use to evaluate your designs and to discuss them meaningfully with one another. I'm not yet an OO programmer. Will this book teach me an OO programming language? No. Although I occasionally swoop down close to code, this isn't a book on object-oriented programming. But if I'm learning an object-oriented language, will this book help? Yes, it will. If you don't currently know an object-oriented programming language, you can begin your object-oriented knowledge with Chapter 1. Knowing the key concepts of object orientation will speed your learning an object-oriented language and, I hope, boost your morale as you move into unfamiliar territory. The later chapters of the book, on sound design, will also help you in getting your early programs to work successfully. On the other hand, if you're already an experienced object-oriented programmer, you can use Parts II and III of the book to enhance the design skills that are vital to your being a rounded, professional software designer or programmer. Why aren't the code examples in this book in C++? I've written the code in this book in a language of my own devising, which is a blend of four popular languages: C++, Eiffel, Java and Smalltalk. I did this because there are two kinds of programmers: those who are fluent in C++ and those who aren't. If you're a C++ aficionado, then you'll find the code a breeze to translate into C++. If you're not familiar with C++, then you might have found the language's arcane syntax getting in the way of the examples. I'd like you to feel welcome in this book whatever your programming language might be. However, there is a fragment of Java in this book. I used Java because it's more accessible to a non-Java programmer than C++ is to a non-C++ programmer. Why isn't this book devoted to the design of windows, icons and menus? There are two reasons: First, I don't believe that object orientation is useful only for the design of graphical user interfaces. Second, there are many books on the market devoted solely to the topic of object-oriented window design. I want this book to cover topics that are not well covered by the other object-oriented books on the market. However, in Chapter 7 I offer some notation for window-navigation design. Is this book about a methodology? No. As you know, a development methodology contains much more than design. For example, there's requirements analysis, library management and so on. Also, a true methodology needs to explain how the various development activities fit together. A lot of stuff! So, instead of turning out a book as diffuse as many other books on object orientation, I decided to focus on a single topic: object-oriented design. You've said a lot about what this book isn't about. What is it about? It's about the fundamental ideas, notation, terminology, criteria and principles of object-oriented software design. Object-oriented software is software that comprises objects and the classes to which they belong.