Mainstream Objects: An Analysis and Design Approach for Business (Yourdon Press Computing Series) [Hardcover]

Edward Yourdon (Author), Katharine Whitehead (Author), Jim Thomann (Author), Karin Oppel (Contributor)

Book Description

Series: Yourdon Press Computing Series | Publication Date: March 1995

This text presents Software AG's approach to object technology, offering a practical approach to object- oriented development. It is concerned with analysis and design, not programming. Its approach can be adopted for use throughout an organization, as an organization's chosen methodology. The authors synthesize the existing techniques, including Rumbaugh and Coad/Yourdon on one hand, Jacobson on another, and techniques proposed by Wirfs-Brock.

Editorial Reviews

From the Publisher

This book presents Software AG's approach to object technology. Aimed at practitioners, including system developers and managers in mainstream commercial environments. Mainstream Objects offers a practical approach to OO development. Mainstream Objects is concerned with analysis and design, not programming. Its highly-scalable approach can be adopted for use throughout an organization.

Product Details

• Hardcover: 300 pages
• Publisher: Prentice Hall; 1st edition (March 1995)
• Language: English
• ISBN-10: 0132091569
• ISBN-13: 978-0132091565
• Product Dimensions: 9.4 x 7.1 x 1.1 inches
• Shipping Weight: 1.6 pounds
• Average Customer Review: 4.3 out of 5 stars  See all reviews (7 customer reviews)
• Amazon Best Sellers Rank: #5,634,362 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

1 of 1 people found the following review helpful:

5.0 out of 5 stars Get it, June 12, 1998

By A Customer

This review is from: Mainstream Objects: An Analysis and Design Approach for Business (Yourdon Press Computing Series) (Hardcover)

This is the actual book from which I learned some analysis and design. I read it once before the first project I managed and I was really bored. I managed the project and the result was not much that I'm proud of. I read it again and found that all the concepts in there were exactly what kept me from doing a good design. The next project went great - much because of this book.

1 of 1 people found the following review helpful:

5.0 out of 5 stars Great book, January 6, 1998

By A Customer

This review is from: Mainstream Objects: An Analysis and Design Approach for Business (Yourdon Press Computing Series) (Hardcover)

This is a terrific intro to object oriented system analysis, design and construction. It provides a great overview of when to use various techniques and how to apply to them to a systems project. I highly recommend it if you are new to the topic or even if you need a refresher to OO concepts. It works well as a project manager's guide as well as for very technical folks. Couple this with McConnell's "Rapid Development" and you have some fine software development books.

3.0 out of 5 stars WIthout UML notation, very outdated and confusing., February 27, 2006

By 

Charles Ashbacher (Marion, Iowa United States) - See all my reviews
(TOP 500 REVIEWER)    (VINE VOICE)    (HALL OF FAME REVIEWER)   

This review is from: Mainstream Objects: An Analysis and Design Approach for Business (Yourdon Press Computing Series) (Hardcover)

In rereading this book after many years, I am still impressed with the quality of the material. It starts with an overview of the object-oriented paradigm and how valuable an approach it is to software development. The second section is an overview of modeling techniques, how object structures are modeled, sequential actions described, how objects interact, and the lifecycle of an object and how systems are modeled. Part three deals with the object-oriented development process, from initiative to the testing of the final product. The last section deals with learning how to think in an object-oriented manner.
While the material is good and the notation used to represent the concepts will be familiar, it all came before UML and therefore is outdated. Even small differences in notation can render diagrams difficult or impossible to understand, and that is the case here. Without the advantages of modern UML notation, this book could confuse you more than it could help you. However, if UML notation were used, it would be a very useful and valuable book.