Software Process Improvement - Items

Submitted by Anonymous (not verified) on


Gabriele Cosmo, 20-Mar-2001

Suggested improvements

Recommendations from the OOAD assessment
  1. Traceability of requirements
  2. Training for requirements, design and documentation of design.
  3. Providing tools for project management, in particular for workflow management and size/effort estimation of work.

Agreed actions for Software Process Improvement

  • By the next TSB meeting, each Category Coordinator should make an estimation of the time-scale required for implementing traceability of requirements design implementation tests in their category.
  • By end 2000 have all existing design sources (.mdl) and documents stored in the CVS repository "documents". Update existing design documents by early 2001. Storing detailed designs in the repository is not mandatory, it's however strongly suggested to include these as well. Documentation/specifications in postscript format are accepted too.
  • Provide updated design diagrams to be made public to Software Manager coordinator by end 2000 / early 2001.
  • Retrieve and store URD in the CVS repository "documents" by January 2000.
  • Check class Category Diagram for possible violations.
  • Store raw-data and results of assessment on AFS with restricted read access.
  • Prepare list of recommended books for self-training on OOAD/OOP for G4 developers, budget (?).
  • Put in place board of experts acting as reference for consultance on architectural design changes.
  • Manpower for QA (2 qualified persons, who could devote approximately 30% of their time).

SPI Status Report

  • Revised version (March 2001) available HERE

SPI actions for traceability

  1. Review of use-cases and requirements
    Generate detailed URD.
  2. Update existing design diagrams
    From existing MDL files: review new developments and design changes, convert to UML notation, generate new diagrams to update web documents and User's Guide.
  3. Generate map of unit tests use cases.
  4. Generate map of system tests use cases.
  5. Enforce adoption of:
  • History logging
  • CVS logs
  • regular tagging (distinguishing bug-fix tags from development tags)
  • start from design documents when new developments or interface changes are introduced
  • Create and adopt group's web page
    Use it to keep track of activities and post any useful information.
  • Meeting Date