- Hardcover: 359 pages
- Publisher: Prentice Hall (2002)
- Language: English
- ISBN-10: 0130609285
- ISBN-13: 978-0130609281
- Product Dimensions: 7.3 x 1.2 x 9.5 inches
- Shipping Weight: 2 pounds
- Average Customer Review: 5.0 out of 5 stars See all reviews (3 customer reviews)
- Amazon Best Sellers Rank: #6,327,282 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your email address or mobile phone number.
Object-Oriented Defect Management of Software Hardcover – 2002
O'Reilly Media's Brand Store
Check out these featured titles from O'Reilly Media.
Top Customer Reviews
The context of defect management in this book is defect density (defining the development life cycle phase in which the defect was injected) and inspection techniques to promote early discovery. Neither of these are new, but are difficult to employ in OO development. That is where this book becomes valuable, because it recognizes that systems developed using OO techniques are viewed and modeled differently. Instead of the relatively flat dimensions of entity-relationship and data flow, OO uses encapsulation, and structural, transformational, and causal-sequential. The changes in modeling and views require changes in process and attitude. The techniques that are given reflect the necessary changes in defect density management and inspection techniques that are required.
Aside from the unique subject matter (there are few books devoted to defect management in any development environment), this book is invaluable to developers, requirements analysts, SQA and test professionals because it covers each of these domains in great detail. Chapters 3 and 4 are focused on requirements defects and contain excellent advice for both preventing defects at this critical phase, as well as how to detect and manage ones that are introduced. Chapters 5 and 6 address the same issues in the design phase, and 7 covers the build phase. The chapters that cover the test phase are particularly good because they provide techniques that are specific to OO testing. Many books attempt to force-fit traditional testing techniques into OO environments and it plain doesn't work.Read more ›
It is difficult to make sure that every SE step outputs quality artifacts for input into the subsequent phase. When defects are not caught after each stage of the SE process, their effects can become intractable therefore costing a lot of money as time increases. Houman addresses these concerns by presenting techniques that will prevent, identify and correct requirements, design, implementation, testing and maintenance defects that will lead to developing a quality software product. For instance, Houman describes using formal descriptive and prescriptive inspection techniques for identifying anomalies of output design artifacts such as a trap state in a UML state-chart diagram.
The book is extremely organized with intuitive examples and contains a wealth of tools that any software development organization will greatly benefit from. At the epitome of this tool set is a comprehensive software inspection process that can be utilized for conducting formal reviews. I would highly recommend this book for any software engineer and software development organization.
A truly magnificent piece of work that has "level 5" written all over it. Thank you Houman!
Defect detection and management is a topic that you don't hear too much about or consider during a software development process. Once the code has been written, and then you start figuring out what went wrong, what was done incorrectly, and what needs to be redone. Younessi in his book outlines extensions to popular development processes, and puts defects in center stage (where it should be) and almost "forces" the developers, architects, tech leads, etc to think about the quality of the software that they are creating. This extension is added to every stage of the process, from inception all the way thru testing. Assuring for example that your tests are effective and you are not injecting more defects into the application while you are testing.Read more ›