Psm guide 4.0b part9

PSM, Version 4.0b - Part 9

PSM
PART NINE
Supplemental Information
This part of Practical Software and Systems Measurement: A Foundation for Objective Project Management provides supplemental information to promote a better understanding of the concepts and terms used within the Guide. It also provides additional background information about Practical Software and Systems Measurement. Theinformation in this part of the Guide includes: • • • • • Glossary - This section provides definitions of terms used throughout the Guide. List of Acronyms - Acronyms used throughout the Guide are defined in this section. Bibliography - References related to PSM and software measurement are provided in this section. PSM Project Information - The project attribution policy and contact information areincluded in this section. Comment Form - Comments and suggestions concerning the PSM Guide may be submitted using this form.

9-1

[This page intentionally left blank.]

9-2

PSM, Version 4.0b - Part 9

TABLE OF CONTENTS
Glossary Acronyms ........................................................................................................5......................................................................................................12

Bibliography ......................................................................................................14 PSM Project Information....................................................................................18 Evaluation and Comment Form ........................................................................209-3

[This page intentionally left blank.]

9-4

PSM, Version 4.0b - Part 9

Glossary
actual data acquirer See measured value. The individual or organization responsible for funding or purchasing the software product or system. The acquirer can be defined as the customer for the software development or operations and maintenance effort. See customer. Effective measurement analysis andreporting requires that the data be aggregated to higher levels of the product and organizational structure. The aggregation structure defines the different ways the measurement data can be grouped and organized for reporting on the project. The aggregation structure describes how the measurement data relates to existing product and process structures. This organization allows the measurementresults to be combined, and later decomposed, meaningfully. Software produced for a specific user need, as opposed to general system software. Examples include software for navigation, fire control, payroll, or general ledger. In the PSM process, this term refers to one of the four basic measurement activities which comprise the software measurement process. The application activity involvescollecting, analyzing, and reporting the measurement data. See tailor measures, implement process, evaluate measurement. Characteristics or properties assigned to each software measurement data item. Attributes provide categories for sorting and selecting data. The attributes of the measurement data must be collected with the data. An example of an attribute is problem reports priority levels, ordevelopment organization. Contains the essential elements of effective processes for one or more disciplines. These elements are organized into hierarchical stages or levels. Commercial items that require little or no unique government modifications or maintenance over the life cycle of the product to meet the needs of the procuring agency. A class of concern that is basic or common to almost all programs.PSM defines seven common software issues. See issue. Any separately-identifiable software or system element or unit. A component may be defined at any size or functional level within a product. A component may be defined as any of the structural elements that are commonly defined for products including units, design modules, or configuration items. A component may refer to any entity in the...