What do you think?
Rate this book
OBJECT-ORIENTED DESIGN
Near Fine Hardcover BRAND NEW Copy w/wrinkling to pg 135 from poor shelving (?). 2nd volume in a series of guides to objected-oriented design (OOD), companion to the book Object-Oriented Analysis (OOA) written primarily for practicing software engineers who work with real-world systems daily. 10 1, Improving Design; 2, Developing the Multilayer, Multicomponent Model; 3, Designing the Problem Domain Component; 4, Designing the Human Interaction Component; 5, Designing the Task Management Component; 6, Designing the Data Management Component; 7, Applying OOD the OOPLs (or Less Than an OOPL); 8, Applying OOD Criteria; 9, Selecting CASE for OOD; and, 10, Getting Started with OOD, followed by OOA/OOD Notation Summary, OOA Strategy Summary, & OOD Strategy Summary. Fine copy despite wrinkled page 135.
197 pages, Hardcover
Published January 1, 1991
2 people are currently reading
66 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 2 of 2 reviews
April 3, 2016
Good and nice book and pure beginner's introduction to Object-Oriented Programming.
Read
October 28, 2018This is an interesting book, despite its age. Entire chapters feel like "Clean Code" or "Code Complete", while other parts feel like extended adverts for the authors' CASE tools.
Most of this is based around character-based interfaces, with a nod to the impending GUI "revolution". Naturally, nothing of the web in there, but interestingly the character-based parts feel more relevant to the web than the GUI.
Sadly, it does rather suffer from a pro-CASE bias, with the authors assuming that at some point in the future there will be a CASE tool that does all the work and nobody will need to write a line of code again. We've been hearing that since 1981 and "The Last One", and no doubt someone will reinvent that square wheel again in a few years.
It's more of an interesting historical read than anything. Some parts, such as those on human interaction and code organisation, haven't aged and are still very relevant. Some is of historical interest, to see how their predictions have and haven't panned out. And some is of questionable value - should the analysis phase really dictate the organisation of the classes in the code?
It's an interesting insight into the design thinking nearly 30 years ago now.
Most of this is based around character-based interfaces, with a nod to the impending GUI "revolution". Naturally, nothing of the web in there, but interestingly the character-based parts feel more relevant to the web than the GUI.
Sadly, it does rather suffer from a pro-CASE bias, with the authors assuming that at some point in the future there will be a CASE tool that does all the work and nobody will need to write a line of code again. We've been hearing that since 1981 and "The Last One", and no doubt someone will reinvent that square wheel again in a few years.
It's more of an interesting historical read than anything. Some parts, such as those on human interaction and code organisation, haven't aged and are still very relevant. Some is of historical interest, to see how their predictions have and haven't panned out. And some is of questionable value - should the analysis phase really dictate the organisation of the classes in the code?
It's an interesting insight into the design thinking nearly 30 years ago now.
Displaying 1 - 2 of 2 reviews