Managing the software process
Why should you use a personal software process?
ACM SIGSOFT Software Engineering Notes
Measuring and Evaluating Maintenance Process Using Reliability, Risk, and Test Metrics
IEEE Transactions on Software Engineering
Controlling Overfitting in Classification-Tree Models ofSoftware Quality
Empirical Software Engineering
Using A Defined and Measured Personal Software Process
IEEE Software
Software Metrics Model For Integrating Quality Control And Prediction
ISSRE '97 Proceedings of the Eighth International Symposium on Software Reliability Engineering
Classification Tree Models of Software Quality Over Multiple Releases
ISSRE '99 Proceedings of the 10th International Symposium on Software Reliability Engineering
| Hi-index | 0.00 |
Using data collected throughout a major project, the authors apply common statistical methods to quantitatively assess and evaluate improvements in a large contractor's software-maintenance process. Results show where improvements are needed; examining the change in statistical results lets you quantitatively evaluate the effectiveness of the improvements. We selected a process-assessment methodology developed by J.E. Henry (1993) that follows Total Quality Management principles and is based on Watts Humphrey's Process Maturity Framework. It lets you use a process modeling technique based on control-flow diagrams to define an organization's maintenance process. After collecting process and product data throughout the maintenance process, you analyze it using parametric and nonparametric statistical techniques. The statistical-analysis results and the process model help you assess and guide improvements in the organization's maintenance process. The method uses common statistical tests to quantify relationships among maintenance activities and process and product characteristics. The relationships, in turn, tell you more about the maintenance process and how requirements changes affect the product.