ABSTRACT
Managing the development of software-intensive projects is a knowledge-intensive process, and much of that knowledge comes from taking measurements. Timely Corrective Actions must be taken because that will result in realizing maximum benefits from the software measurement program. There are two basic types of software measurements that are collected: direct and derived. Management indicators should be tailored to the system being developed. Additional indicators and supporting base measurements can be added to address critical or unique needs of each program. One of the most comprehensive approaches to defining an MIS was published by the practical software measurement group. The software engineering process group at the program or subsystem level must perform analysis of the software management indicators in accordance with their scope of control. Management decisions based upon the analysis of Software Management Indicators should use thresholds to highlight or flag non-nominal conditions.
