Process Review: A Case Study

1
Process Review A Case Study

• Paul Kvet
• 04/26/06

2
Agenda

• Process Overview
• Requirements
• Design
• Implementation
• Artifacts
• Peer Review Tool
• Case Study
• Conclusions

3

• Disclaimer
• Information modified to make presentable

4
Requirements

• Purpose
• Entry Criteria
• Inputs
• Requirements Allocated to Software
• Software Development Plans
• Process Activities
• Work Products
• Software Requirements
• Requirements Traceability
• Verification Methods

• Process Activities
• Develop and Document Software Requirements
• Document Software Verification Method
• Peer Review
• Review Software Requirements
• End User, Customer
• Control Work Products

5
Design

• Purpose
• Entry Criteria
• Inputs
• Requirements Allocated to Software
• Software Development Plans
• Process Activities
• Work Products
• Software Design
• Software Interface Design
• Preliminary Operation and Support
• Traceability

• Process Activities
• Review Software Requirements
• Develop and Document Software External Interface
  Design
• Develop and Document Software Design
• Document Traceability
• Peer Review
• Review Software Design
• End User, Customer
• Develop Operation and Support Documentation
• Control Work Products

6
Implementation

• Purpose
• Entry Criteria
• Inputs
• Software Development Plans
• Documented Software Design and Software
  Interfaces
• Traceability Documentation
• Process Activities
• Work Products
• Source Code
• Traceability
• Informal Development Test

• Process Activities
• Review Software Design
• Develop and Document Code
• Document Traceability
• Peer Review
• Verify Implementation
• Control Work Products

7
Software Process Artifacts

• Design Criteria List (DCL)
• Requirements Files (REQ)
• Design Notes (DN)
• System Interface Change (SIC)
• Informal Development Test (IDT)
• Source Code PDL

8
Peer Review Tool

• Used to conduct Peer Reviews
• Participant roles
• Interface
• Producer
• Quality
• Review Leader
• Testability
• Traceability

• Each artifact entered in and unit measure
  associated with
• Diagram
• Page
• SLOC
• Requirement
• Test Point
• All measurements used to devise metrics came from
  this tool

9
Case Study Current Project

• How well does the process work
• What metrics can be derived from available data
  to answer main question
• Other Information
• Some information gathered from sources outside
  Peer Review Tool to compliment that data

10
Time Spent on Peer Reviews
11
Implementation Oddity
12
Defects Metrics
13
Artifact Metrics
14
Developer Metrics

• Productivity
• Cannot Measure with Peer Review Tool
• Knowing 310 KSLOC and approximately 60,000 man
  hours gives about gives about 5 SLOC per Man Hour

15
Conclusions

• Problem with Process
• Probably Not
• Metrics indicate Process could work if used
  properly
• Defects written mostly non-technical / Peer
  Review needs technical reviewer
• What are the Problems
• Proper training of Developers
• Inconsistent Measurement / Define Metrics
• Inconsistent Process Usage
• Still need more Analysis

16
Questions?