Software Product Metrics

Podcast

Play an AI-generated podcast conversation about this lesson

Download our mobile app to listen on the go

Get App

Questions and Answers

Match each McCall's Quality Factor with its primary focus:

Maintainability = Ease of modifying the software after delivery Portability = Ease of transferring the software to another environment Reusability = Extent to which code can be used in other applications Interoperability = Ability of the software to interact with other systems

Match each term with its correct definition in the context of software metrics:

Measure = A quantitative indication of the extent, amount, dimension, capacity, or size of some attribute of a product or process Metric = A quantitative measure of the degree to which a system, component, or process possesses a given attribute Indicator = A metric or combination of metrics that provide insight into the software process, a software project, or the product itself Goal = A specific objective that a measurement aims to achieve

Match the following measurement principles with their description:

Objectives of Measurement = Should be established before data collection begins Technical Metric Definition = Should be defined in an unambiguous manner Metrics Derivation = Should be derived based on a theory that is valid for the domain of application Metrics Tailoring = Should be tailored to best accommodate specific products and processes

Match the following stages of the measurement process with their description:

Formulation = Derivation of software measures and metrics appropriate for the software's representation Collection = Mechanism used to accumulate data required to derive the formulated metrics Analysis = Computation of metrics and the application of mathematical tools Interpretation = Evaluation of metrics results to gain insight into the quality of the representation Signup and view all the answers

Match the elements of the Goal Definition Template with their purpose:

Analyze = Name of activity or attribute to be measured For the purpose of = Overall objective of the analysis With respect to = Aspect of the activity or attribute that is considered From the viewpoint of = People who have an interest in the measurement Signup and view all the answers

Match the attributes of effective software metrics with their descriptions:

Simple and Computable = Easy to derive and does not demand inordinate effort or time Empirically Persuasive = Satisfies the engineer's intuitive notions about the product attribute Consistent and Objective = Always yields unambiguous results Effective Feedback = Provides information that can lead to a higher quality end product Signup and view all the answers

Match the following data collection and analysis principles with their descriptions:

Data Collection Automation = Whenever possible, data collection and analysis should be automated Valid Statistical Techniques = Should be applied to establish relationships between product attributes and quality Interpretative Guidelines = Should be established for each metric to provide context Signup and view all the answers

Match the following types of Function-Based Metrics with their definitions:

External Inputs (Els) = Data entering the system from outside External Outputs (EOs) = Data leaving the system to the outside External Inquiries (EQs) = Requests from outside that trigger a response Internal Logical Files (ILFs) = Data stored within the system Signup and view all the answers

Match the Architectural Design Metrics with their corresponding formulas:

Structural Complexity = $g(fan-out)$ Data Complexity = $f(input & output \ variables, fan-out)$ System Complexity = $h(structural & data \ complexity)$ HK Metric = Function of fan-in and fan-out Signup and view all the answers

Match the OO Design Characteristics (as described by Whitmire) with their definitions:

Size = Defined in terms of views: population, volume, length, functionality Complexity = How classes of an OO design are interrelated Coupling = Physical connections between elements of the OO design Completeness = Degree to which a design component can be reused Signup and view all the answers

Match the following distinguishing characteristics of OO Metrics with their descriptions:

Localization = The way in which information is concentrated in a program Encapsulation = The packaging of data and processing Information Hiding = Hidden operational details behind a secure interface Inheritance = Manner in which responsibilities of one class are propagated to another Signup and view all the answers

Match class-oriented metrics (Proposed by Chidamber and Kemerer) with its description:

Weighted methods per class = Complexity of the class Depth of the inheritance tree = How far down the hierarchy the class is Coupling between object classes = Dependencies between classes Lack of cohesion in methods = How related the class's methods are Signup and view all the answers

Match class-oriented metrics (Proposed by Lorenz and Kidd) with its description:

Class size = Number of methods and attributes in a class Number of operations overridden by a subclass = How many methods are redefined in a subclass Number of operations added by a subclass = How many new methods are added by a subclass Specialization index = Indicates the relative degree of specialization in the class hierarchy Signup and view all the answers

Match the elements of the MOOD Metrics Suite with their descriptions:

Method Inheritance Factor = Extent to which methods are inherited across the class hierarchy Coupling Factor = Measure of the degree of interconnection between classes Polymorphism Factor = Extent to which polymorphism is used in the system Signup and view all the answers

Match the Operation-Oriented Metrics (Proposed by Lorenz and Kidd) to its description:

Average Operation Size = Average lines of code in an operation Operation Complexity = Complexity within a method Average Number of Parameters per Operation = Average number of parameters passed in methods Signup and view all the answers

Match Component-Level Design Metrics with their description.:

Cohesion metrics = Focus of data objects Coupling metrics = Function of input and output parameters Complexity metrics = Cyclomatic complexity Signup and view all the answers

Match Interface Design Metrics with their description.:

Layout appropriateness = Layout entities and cost of making transitions among entities Signup and view all the answers

Match design Quality Metrics for WebApps with their description.:

User interface = Promote usability Aesthetics = Application domain and pleasing to the user Content = Imparts the most information with the least effort WebApp Architecture = Accommodate the special goals and objectives of WebApp users Signup and view all the answers

Match Hallstead's Software Science Metrics with its description.:

Comprehensive collection of metrics = Number of operators and operands Controversial = Laws generated substantial controversy Experimental Verification = Performed for selected programming languages Signup and view all the answers

Match Software testing measurements derived from Hallstead with its description.:

Lack of cohesion in methods (LCOM) = Measures the relationships between methods in the same class Percent public and protected (PAP) = Ratio of public and protected members to the total members of the class Public access to data members (PAD) = Percentage of data members with public access Number of root classes (NOR) = Number of classes in the class hierarchy Signup and view all the answers

Match Software Maintenance Metric Definitions with their description:

MT = The number of Modules in the Current Release Fc = The number of Modules in the Current Release that have been Changed Fa = The number of Modules in the Current Release that have been Added Fd = The number of Modules from the Preceding Release that were Deleted in the Current Release Signup and view all the answers

Match principles of Goal-Oriented Software Measurement to the action

Goal = establish an explicit measurement Questions = define a set of questions that must be Metrics = identify well-formulated that help to Signup and view all the answers

Match the following stages of the measurement process with an example.:

Formulation = Identify the lines of code needing to be measured Collection = Run script to retrieve the number of lines of code Analysis = Create scatterplot that maps the lines of code to test cases Interpretation = A large amount of code may mean it will take substantial resources and time to test Signup and view all the answers

Match Function-Based Metrics with the impact on the value of FP:

External Inputs (Els) = Increase the FP as it improves testabiltiy with additional data External Outputs (EOs) = Increase the FP when the information is more complex External Inquiries (EQs) = The FP remains unchanged Internal Logical Files (ILFs) = Increase FP when there additional external systems Signup and view all the answers

Match the attributes of Halstead’s Software Science with their impact on software testing effort.

Program Vocabulary = Larger vocabulary typically implies more complex code, increasing testing effort Program Length = Longer programs mean more code to test, leading to increased testing effort Estimated Length = Discrepancies between estimated and actual length may indicate inconsistencies or issues needing further investigation during testing Difficulty = Higher difficulty implies the code is harder to understand and test, thus increasing testing effort Signup and view all the answers

Match the WebApp Metrics to their corresponding Description with their impact on usability.

Content Quality = High-quality helps in overall usability Navigation Structure = A well-designed structure significantly enhances the user experience Performance = A performant site will increase usability Accessibility = A webapp that doesn't conform to accessibility is less usable Signup and view all the answers

Flashcards

What is a measure?

A quantitative indication of the extent, amount, dimension, capacity, or size of some attribute of a product or process.

What is a metric?

A quantitative measure of the degree to which a system, component, or process possesses a given attribute.

What is an indicator?

A metric or combination of metrics that provide insight into the software process, a software project, or the product itself.

What is Formulation?

The derivation of software measures and metrics appropriate for the representation of the software that is being considered.