Home > Store

Object-Oriented Defect Management of Software

Register your product to gain access to bonus material or receive a coupon.

Object-Oriented Defect Management of Software


  • Sorry, this book is no longer in print.
Not for Sale


  • Copyright 2002
  • Dimensions: K
  • Pages: 384
  • Edition: 1st
  • Book
  • ISBN-10: 0-13-060928-5
  • ISBN-13: 978-0-13-060928-1

  • Preventing and eliminating defects at every stage of object-oriented development
  • New and revamped techniques for managing defects in design, architecture, classes, integration, and more
  • Includes practical tools, templates, checklists, and other productivity tools
  • Compatible with UML, RUP, OPEN, and all object-oriented languages

The complete lifecycle guide to preventing and eliminating object-oriented software defects.

This is the first systematic guide to defect identification, correction, and prevention in object-oriented software development projects. Houman Younessi covers every aspect of defect reduction, going far beyond testing to cover key aspects of the software development process, from planning through software delivery. Best of all, Younessi provides hands-on templates, checklists, and other productivity tools you can use to start improving software quality—right now.

  • Why object-orientation presents powerful challenges in defect management
  • Adapting traditional defect management techniques to object-oriented environments
  • Developing, refining, and validating "low defect" requirements documents
  • Minimizing defects through the use of cohesion, coherence, coupling, contracts, and effective architecture
  • Identifying defects in object-oriented code: Fagan, Ebenau and Strauss, Gilb and Graham, and other advanced inspection techniques
  • Testing base, derived, and abstract classes
  • Integration, integration testing, and system testing for object-oriented systems

Younessi's techniques are entirely compatible with today's leading tools, notation schemes, languages, and methodologies, including the UML modeling standard, and both the RUP (Rational Unified Process) and OPEN models. No matter how large your projects are, Object-Oriented Defect Management of Software is your start-to-finish framework for maximizing robustness, reliability, and maintainability.

Sample Content

Online Sample Chapter

Object-Oriented Defect Management of Software: the Basics

Table of Contents



1. Setting the Scene.

Software, Software Engineering, and the Software Engineering Process. A Constructive Approach to Software Engineering. The Process of Constructing Software. Object Orientation. Understanding the Object Paradigm. Defect Management. Specifying Quality. Views of Quality. Internal Quality and External Quality: Form Complements Function. Software Product Quality Attributes. External Quality Attributes. Customer-Oriented Quality Assessment. Assessing Product Quality. Defect Management as a Means of Ensuring Quality. Achieving Quality Goals. Product Focus. The Link Between Product and Process. Process Focus. Recent Developments. Conclusion.

2. Defects and Defect Management in an Object-Oriented Environment.

Why Does Object Orientation Present Challenges in Defect Management? Abstraction. Encapsulation. Genericity. Inheritance. Multiple Inheritance. Polymorphism. Systemic Issues. Managing Defects. Opportunities for Defect Management. Defect Management Levels. Conclusion.

3. Developing Low Defect Requirements.

The Requirements Process Component. Comprehension of the Essence and Context of the ProblemúSituation or Issue at Hand. Elicitation of User Requirements. Specify Quality and Acceptance Goals. Analysis of User Requirements. Reconciliation of Requirements. Documentation of User Requirements. Requirements Narration. Usecases. The Requirements Document. The Requirements Document Set. Conclusion.

4. Identifying and Removing Requirements Defects.

Examining Conformance to Standards. Model Validation. Informal Model Evaluation. Class, Responsibility, Collaborator (CRC) Approach. Formal Model Validation. Requirements Document Inspection. Conclusion.

5. Preventing Design Defects.

Software Design. Design for Functionality. Design for Reliability. Design for Usability. Design for Maintainability. Design for Process Efficiency. Basic Elements of Good Design. Cohesion: A Measure for Modularity. Coherence: Another Measure for Modularity. Coupling: Another Measure for Minimality of Interaction and for Segregation. Achieving Segregation. Achieving Abstraction. Achieving Multiple Levels of Granularity. Achieving Formality. Achieving Anticipation of Invalid States (Exception Handling). Achieving Redundancy. Achieving Genericity. Architecture. Distribution: Distributed Topology. Architectural Design Styles. Styles of Control. Solving Specific Architectural Problems. Basic Steps for Architectural Design. Design Reviews. Architectural (System) Design Documentation. Object Design. Conclusion.

6. Design Defect Identification.

Design Defects. Identifying Defects in Design. Design Simulation. Design Inspection. Inspecting Design Artifacts. Class Diagram. Sequence Diagrams. Collaboration Diagrams. State Diagrams. Activity Diagram. Transformational Description. Module or Package Diagram. Implementation or Component Diagram. Deployment Diagrams. Identifying Defects in a Design. Document. Conclusion.

7. Program Defect Identification.

Defect Indentification Techniques. Evaluation. Education and Examination of Alternatives. Defect Identification. Comparing Inspection and Testing (Failure Detection). Inspecting Object-Oriented Code. Failure Detection-Oriented Defect Removal. Testing Object-Oriented Code. Conclusion.

8. Testing Classes.

Testing Base Classes. Testing for Correct Generation of Instances. Testing for Correct Attribute Values. Testing if Routines Correctly Alter the Representation of the Corresponding Object. Assertion-Based Testing of a Class. Class Invariants and Assertions at the Class Level. Constraint-Based or Assertion Constraint Coverage-Based Testing. Modal Testing of a Class. State Invariants. Modal Testing. Transformational Testing of Methods. Partitioning or Subdomain Testing. A Comparison of the Effectiveness of Subdomain-Based and Statistically Based Approaches. Conclusion.

9. Integration, Integration Testing, and System Testing.

Components and Integration. Component Interaction. Integration Strategies. Integration Testing Techniques. Scenario Testing. Modal Testing. System Testing. Usecase-Based Testing. System Temporal Boundary Testing. Performance and Load Testing. Usability Testing. System Acceptance. Beta Testing. Identify a Purpose for Beta Testing. Select Your Site Carefully. Decide What to Do Next. Conclusion.

Appendix A. Taxonomy of Defect Management.

Appendix B. Syntax of Object Z.

Appendix C. Software Inspection Process.

1. Inspection Process Script. Script I-2X Inspection Process Scripts. Author's or Author's Proxy's Task Scripts. Moderator's Task Scripts. Reader's Task Scripts. Scribe's Task Scripts. Other Inspector's Task Scripts. Script I-1 Definitions. Script I-6 Moderator's Inspection Meeting Agenda. Script I-2S Specification Inspection Process Script. Script I-2D Design Inspection Process Script. Script I-2C Code Inspection Process Script. Script I7-S Specification Inspection Checklist. Script I7-D Design Inspection Checklist. Script I7-C Code Inspection Checklist.





If you selected this book to learn more about testing of object-oriented programs, you are about to get more than you bargained for. As the title implies, this book discusses defect management of object-oriented software systems. This latter activity goes beyond merely testing object-oriented code in many respects.

First, we will be discussing defect management, of which testing is only one type. Defects can potentially be injected into our software systems at any stage of the software process. If left unchecked and undiscovered, they would manifest themselves as errors or "bugs" when the final executable is set into operation. Testing—exercising the executable in the hopes of making it fail—can uncover many of these defects. However, there are other techniques that do not require the executable code to be available and instead rely on examining various artifacts of the process. We could call these static techniques to contrast with the former, which we might call dynamic. In this book, I discuss in detail both the static and the dynamic approaches to defect management.

Second, testing is the removal of defects at the last, or nearly last, available opportunity before the product is to be used. It can thus be argued that taking an approach based on testing of code alone, a strictly corrective approach, is

contrary to the very axiom of software engineering. We also need preventive approaches. Software engineering—in its entirety—can in fact be viewed as the process of managing defects in a software product. This claim may sound controversial at first, but in reality it is not so at all. Look at it this way: Any activity we perform as part of our software process is targeted toward either preventing defects from being included in our product or identifying and removing of those that have been already introduced. This in turn implies that defect management techniques are not uniquely applied to code, but can also be employed in relation to every activity of the software engineering process. In this book, I cover defect management techniques relevant to all stages of the software engineering process and not just techniques that deal with code. Additionally, both the corrective and preventive approaches are considered.

Third, this book is about managing defects in an object-oriented environment. This does not mean, however, that all defect management techniques that are introduced in this book are exclusive to object orientation. Conversely, however, every technique I cover is useful in an object-oriented context, although it may not have been originally developed for that domain.

Finally, given the recent ascent of the Unified Modeling Language (UML) and the Rational Unified Proces (RUP) to the level of having been accepted as standard means of modeling and conducting an object-oriented process respectively, we have made every attempt to be compatible with both when logically possible.

Given these characteristics, this book might be used in many fashions. It is targeted to professional software engineers, researchers in object technology and in defect management, and postgraduate students in software engineering. It may be used as a textbook for an advanced course (masters and Ph.D. level) in object-oriented defect management or as supporting material for advanced courses in object-oriented software engineering. It may also be used as training material in a professional industry-based course in object-oriented defect management.


Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020