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:
Assessing the SCM Process



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.

Assessing the SCM Process

    Software configuration management (SCM) (SEPA 5/e, Chapter 9) is intended to help control software engineering work products and the changes that are often made to them. The checklist that follows is NOT intended as a complete SCM audit, but the more questions that elicit a negative response, the lower the likelihood that an SCM audit would be successfully passed (see also the questions noted in SEPA 5/e, Section 9.6).

  • Have you developed an SCM plan for the project?
  • Are the procedures defined in the SCM plan followed by the software project team?
  • Have you developed an identification scheme for all work products? Is the identification scheme used?
  • Has a repository or library been established for configuration items (objects)?
  • Have baselines been established?
  • Has a change control authority been defined?
  • Does a written change control procedure exist? Is it followed by all project teams?
  • Are "check in" and "check out" procedures used for all SCIs.
  • Is every change request accompanied by documentation?
  • Are change reports and/or engineering change orders generated for all change requests that are approved?
  • Does a version control process exist? Is it followed by all project teams?
  • Can an existing SCI be retrieved in less than 5 minutes? Can the version of the SCX be identified immediately? Is it possible to identify all related SCIs in less than 5 minutes?
  • Is a change log maintained?
  • Are changes reported to those with a need to know?
  • Are formal reviews conducted prior to the release of a changed SCI?


    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