[go: up one dir, main page]
Scribd
Upload
246 views3 pages

Software Quality Metrics

Software quality metrics are implemented to provide management information on compliance with requirements and schedules/budgets, and to enable preventive/corrective actions. Metrics must be relevant, valid, reliable, comprehensive, and mutually exclusive. They should also be easy to collect without bias. Metrics are categorized by process (development and maintenance) and product (quality, productivity/effectiveness for development and corrective maintenance). Lines of code is dependent on tools/style while function points depend on manuals, but require less experience and work while providing pre-project estimates. Defining new metrics involves determining attributes, possible metrics, data collection, and interpretation.

Uploaded by

spongechie
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
246 views3 pages

Software Quality Metrics

Software quality metrics are implemented to provide management information on compliance with requirements and schedules/budgets, and to enable preventive/corrective actions. Metrics must be relevant, valid, reliable, comprehensive, and mutually exclusive. They should also be easy to collect without bias. Metrics are categorized by process (development and maintenance) and product (quality, productivity/effectiveness for development and corrective maintenance). Lines of code is dependent on tools/style while function points depend on manuals, but require less experience and work while providing pre-project estimates. Defining new metrics involves determining attributes, possible metrics, data collection, and interpretation.

Uploaded by

spongechie
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Software Quality Metrics

1) Explain the objectives of software quality metrics. Software quality metrics are implemented: a. To support control of software development projects and software maintenance contracts. Their aim is to provide management with information regarding: i. Compliance with functional (quality) performance requirements ii. Compliance with project timetable and budget. b. To deliver the metrics accumulated and analyzed by the CAB. Use of these metrics data is aimed at enabling preventive and corrective actions throughout the organization. 2) List the requirements for successful software quality metrics. Applicability of quality metrics is determined by the degree to which the following general and operative requirements are fulfilled: General requirements a. Relevant measures an attribute of considerable importance b. Valid measures the required attribute c. Reliable produces similar results when applied in similar conditions d. Comprehensive applicable to a large variety of situations e. Mutually exclusive does notmeasure attributes alreadymeasured by other metrics. Operative requirements a. Easy and simple data collection is implemented with minimal resources b. Does not require independent data collection metrics data collection is based on currently employed data collection systems, e.g. employee attendance records, cost accounting methods c. Immune to biased interventions by interested parties (team members and others). 3) Explain how software quality metrics are categorized. A two-level system of categories is used here. The first level distinguishes between two categories: Process metrics, related to the software development process Product metrics, related to software maintenance. Each first-level category is broken down into one of three sub-categories : Software process quality metrics Software process timetable metrics Software process productivity metrics. The software productmetrics are classified into four HD and corrective maintenance subcategories: HD quality metrics HD productivity and effectiveness metrics Software corrective maintenance quality metrics Software corrective maintenance productivity and effectiveness metrics. 4) Compare the KLOC and function points measures for the size of a software system.

A significant number of the metrics presented here use one of two measures for software system size, which are compared according to the following criteria: Dependency on the development tool, programming language, or programmer style. KLOC depends heavily on the development tools characteristics and on the programmers style. Alternatively, although the function point method does not depend on either of these factors, it does depend to some extent on the function point instruction manual used. It should also be noted that most successful implementations and research supporting the results of the function point method are related to data processing systems, whereas only limited experience has been gained in other areas of software systems. Professional experience required for implementation. Relatively little experience is required for counting KLOC, while relatively great experience is needed to evaluate function points. Amount of professional work required. Relatively little for KLOC; far more work for evaluation of function points. Subjective factors. Estimation of KLOC requires little subjective judgment, whereas the opposite is true for function points because subjective evaluations are required for determining the weight and relative complexity factors for each software system component, as required by the function point method. Pre-project estimates. Pre-project estimates are unavailable for KLOC but available for function points as the latter can be based on requirement specification documents. (5) Describe the process of defining a new software quality metric. The definition of metrics involves a four-stage process: (a) Definition of attributes to be measured: software quality, development team productivity, etc.

Source: Galin, Software Quality Assurance From Theory to Implementation

You might also like