Home

  About Us

  Products

  Process Models

  SE Resources

  Commentary

  Contact us

Breaking News!

A new blog ... visit OnCenter, Roger Pressman's running commentary on the world at large

A new edition ... the 6th edition of Software Engineering is available now

A first novel ... Roger Pressman's first novel is a technothriller -- The Aymara Bridge

A new training curriculum! RSP&A has partnered with QAI to develop a comprehensive Internet-based software engineering curriculum.

A redesigned Web site ... we've done a major redesign and added many new features

 
Adaptable Process Model
Checklists:
Conducting Integration Tests



IMPORTANT NOTICE: The complete Adaptable Process Model (APM) is provided for informational purposes and for assessment by potential users. The APM is copyrighted material and may not be downloaded, copied, or extracted for use in actual project work. The full hypertext (html) version of the APM may be licensed for use and customization within your organization. Contact R.S. Pressman & Associates, Inc. for complete licensing information.

Conducting Integration Tests

    As the software is being constructed, it's necessary to consider a number of important issues. The following checklist can be applied as integration tests are planned and during the integration process itself. For this checklist, the more questions that elicit a negative response, the higher the risk that integration testing will not adequately achieve its purpose.

    • Has the software architecture been fully defined in the design document?
    • Has the structure of global data been identified?
    • Is the component-level design complete for all modules within the system?
    • Has an integration schedule been established?
    • Have drivers and stubs been defined and developed?
    • Has an appropriate integration strategy been chosen based on the needs of the customer?
    • If a top-down strategy has been chosen, are stubs available so that top-level modules can be adequately tested?
    • Is regression testing performed as new modules are integrated?
    • Are components integrated depth first so that appropriate functionality along one control path can be demonstrated?
    • Are error recording mechanisms in place?
    • If a bottom-up strategy has been chosen, are drivers available so that bottom level module clusters can be adequately tested?
    • Has smoke testing (SEPA, 5/e, p. 492) been considered as an integration strategy?


      Return to Checklist Table of Contents


Site search! We've added links to a search engine that will enable you to search our entire site for information you need. Enter the appropriate word or phrase below.

PicoSearch




Home About us Products Product Models SE Resources Commentary Contact us

Web site and all contents R.S. Pressman & Associates, Inc. 2001 - 2006, All rights reserved.
Free website templates