Jack McGarry, of the Navy Undersea Warfare Center (NUWC), is leading an effort to define the soon to be developed Measurement Guidebook for the new revision to DoD-STD-2167A, Defense Software Systems Development standard. The revision to 2167A, with the short name of Software Development and Documentation, or 498, has been under development for some time under the leadership of Raghu Singh of the Space and Naval Warfare Systems Command (SPAWAR). The guidebook is titled MIL-Handbook-SWM Software Metrics Process. The primary objective of the guidebook is to provide practical software measurement implementation guidance to DoD Mission Critical Computer Resources (MCCR), Command, Control, Communications and Intelligence (C3I), and Automated Information System (AIS) program acquisition organizations in support of MIL-STD-498. The guidebook will target an audience consisting of government program managers, government technical managers, and development organizations. The focus of the effort is the project and the program organization which manages the project.
The McGarry effort is sponsored by the Joint Logistics Commander Computer Resources Management Committee, in short the JLC-CRM. The JLC-CRM also sponsors the 498 revision to 2167A. McGarry has formed a committee of DoD and industry personnel which has been meeting for several months.
The objectives of the committee's effort are to:
The Handbook is outlined in four parts:
The basic points, or guidelines of the Handbook are that data and metrics will be required by all programs and the Handbook will be targeted at inexperienced metrics users. It will include basic management and product metrics. The metrics being targeted are those that are in widespread use and easily understood and analyzed. There are also enhanced guidelines for more experienced users who have a requirement for a more sophisticated metrics program. The effort includes a plan for an advanced version of the guidebook which would be published at a future date.
There are a variety of measurement rules that are under consideration. Some of these are: analysis based on low level software attribute data, all data to be derived or collected on a periodic basis and in a consistent manner, a flexible metrics implementation based on program objectives and data availability, and a focus on single program analysis, not cross program comparison.
In the current thinking the metrics would be structured in five measurement categories to include: Milestone Performance, Schedule Performance, and Work Unit Completion in the Progress area; Effort Allocation, Staff Allocation, Cost Performance and Facility Utilization in the Resources area; Defect Profiles and Product Stability (Requirements and Engineering Change Proposals (ECPs)) in the Product Quality area; Size (pages of documentation, Software Design Units, etc.), Computer Resources, Complexity, and Reliability in the Product area; and Capability, Performance and Environment in the Process area.
The committee is considering a wide range of issues to include:
While there is some concern that MIL-STD-498 may not be published (due to the recent OSD policy announcement on increased use of commercial practices (see page 3 of this newsletter "Two New Memoranda Issued by the DoD")) the Committee believes that the guidebook will stand on its own for the implementation of a measurement program. The actual construction of the guidebook, once the committee finishes its work, will be under contract to Logicon, Inc.
This article was prepared from development materials of the Metrics HDBK working committee and does not represent the position of the committee or the Joint Logistics Commanders Computer Resources Management Coordinating Group. For information on this program contact:
