automated software testing
1. List three characteristics of a good software metric.
The characteristics of a good software metric are:
Simple and computable: It should be easy to learn how to derive the metric.
Empirically and intuitively persuasive: The metric should reach the standards under any considerations to satisfy the engineers. consistent and objective: The metric results should always be distinct consistent in its use of units and dimensions : The mathematical computational of the metric should use measures that do not lead to odd combinations of units.
Programming language independent: metrics should be based on requirements, design, and structure of the program itself.
An effective mechanism for high quality feedback: The metric should provide you the information that can lead to a higher quality end product.
2. Component-level design metrics focus on what three internal characteristics of software components?
Component-level design metrics for conventional software components focus on internal characteristics of a software component and include measures of the "three CS"-Module cohesion, coupling, and complexity.
Cohesion metrics: :It defines the collection of metrics that provide an indication of the cohesiveness Coupling metrics: It provides an indication of the "connectedness" of a module to other modules
Complexity metrics: A variety of software metrics can be computed to determine the complexity of program control flow.
3. Technical testing metrics fall into two major categories. What are they?
Testing metrics fall into two broad categories. They are: metrics that attempt to predict the likely number of tests required at various testing levels. metrics that focus on test coverage for a given component.
4. Describe the five activities associated with the software measurement process.
The five activities associated with the software measurement process are:
Formulation
The identification of software measures and metrics
The characteristics of a good software metric are:
Simple and computable: It should be easy to learn how to derive the metric.
Empirically and intuitively persuasive: The metric should reach the standards under any considerations to satisfy the engineers. consistent and objective: The metric results should always be distinct consistent in its use of units and dimensions : The mathematical computational of the metric should use measures that do not lead to odd combinations of units.
Programming language independent: metrics should be based on requirements, design, and structure of the program itself.
An effective mechanism for high quality feedback: The metric should provide you the information that can lead to a higher quality end product.
2. Component-level design metrics focus on what three internal characteristics of software components?
Component-level design metrics for conventional software components focus on internal characteristics of a software component and include measures of the "three CS"-Module cohesion, coupling, and complexity.
Cohesion metrics: :It defines the collection of metrics that provide an indication of the cohesiveness Coupling metrics: It provides an indication of the "connectedness" of a module to other modules
Complexity metrics: A variety of software metrics can be computed to determine the complexity of program control flow.
3. Technical testing metrics fall into two major categories. What are they?
Testing metrics fall into two broad categories. They are: metrics that attempt to predict the likely number of tests required at various testing levels. metrics that focus on test coverage for a given component.
4. Describe the five activities associated with the software measurement process.
The five activities associated with the software measurement process are:
Formulation
The identification of software measures and metrics