Maintenance Prediction

Goal of Maintenance Prediction

1 pts

volume_mute

What is maintenance prediction primarily concerned with?

Determining which programming language a system should have been written in originally

Predicting the exact date a system will be retired down to the calendar day

Assessing the changes that may be required in a system and identifying parts most likely to be expensive to change

Forecasting stock market trends related to the software industry

note_alt Add notes

flag Flag

Correct Answer

Explanation

Three Types of Maintenance Predictions

1 pts

Match each maintenance prediction category to the question it primarily answers.

To complete the line match

Click on an item in the first group
Click on the match in the second group

To delete a match, double click on a line

Prediction

Predicting maintainability

Predicting maintenance costs

Predicting system changes

Question Answered

What parts of the system will be the most expensive to maintain?

What will be the lifetime maintenance costs of this system?

How many change requests can be expected, and what parts of the system are most likely to be affected?

note_alt Add notes

flag Flag

Correct Answer

Explanation

Factors Affecting Number of Change Requests

1 pts

volume_mute

Which of the following are factors that help evaluate the relationship between a system and its environment, used to predict the number of change requests? Select all that apply.

The number of times the system has been backed up

The number of inherently volatile system requirements, especially those reflecting organizational policy

The exact font used in the system's user interface

The number and complexity of system interfaces

The business processes in which the system is used

note_alt Add notes

flag Flag

Correct Answer

Explanation

Volatile Requirements and Organizational Policy

1 pts

volume_mute

Why are requirements that reflect organizational policies and procedures likely to be more volatile than requirements based on stable domain characteristics?

Domain-based requirements are illegal to modify once approved

Volatile requirements are always related to user interface color schemes only

Organizational policy requirements are always written in a less precise language

Organizational policies and procedures change more frequently than fundamental domain facts, leading to more change requests over time

note_alt Add notes

flag Flag

Correct Answer

Explanation

Complexity and Maintainability Relationship

1 pts

volume_mute

What did early research on the relationship between program complexity and maintainability find?

The more complex a system or component, the more expensive it is to maintain

Simpler systems are always more expensive to maintain than complex ones

Complexity only affects maintenance cost in embedded systems, never in business systems

Complexity has no measurable relationship to maintenance cost at all

note_alt Add notes

flag Flag

Correct Answer

Explanation

Process Metrics for Assessing Maintainability

1 pts

volume_mute

Which of the following are process metrics described as useful for assessing maintainability after a system has been put into service? Select all that apply.

Average time required for impact analysis

The number of cups of coffee consumed by the maintenance team

Number of requests for corrective maintenance

Average time taken to implement a change request

Number of outstanding change requests

The total number of physical servers in the data center

note_alt Add notes

flag Flag

Correct Answer

Explanation

Rising Corrective Maintenance Requests

1 pts

volume_mute

What might an increase in the number of bug and failure reports over time indicate about a system?

It indicates that the hardware running the system needs more electricity

It has no relationship to maintainability and is purely a coincidence

It may indicate that more errors are being introduced into the program than are being repaired, suggesting declining maintainability

It always indicates the system has too many active users

note_alt Add notes

flag Flag

Correct Answer

Explanation

Impact Analysis Time vs. Implementation Time

1 pts

volume_mute

True or False: The average time required for impact analysis and the average time taken to implement a change request measure exactly the same thing and are interchangeable metrics.

True

False

note_alt Add notes

flag Flag

Correct Answer

Explanation

COCOMO 2 Maintenance Effort Basis

1 pts

volume_mute

According to the COCOMO 2 cost estimation model, what two factors form the basis of an estimate for software maintenance effort?

The market value of the company and the average national software salary

The total original development budget and the number of years since release

The number of programmers originally hired and the size of the original office

The effort to understand the existing code and the effort to develop the new code

note_alt Add notes

flag Flag

Goal of Maintenance Prediction

Correct Answer

Explanation

Three Types of Maintenance Predictions

Prediction

Question Answered

Correct Answer

Explanation

Factors Affecting Number of Change Requests

Correct Answer

Explanation

Volatile Requirements and Organizational Policy

Correct Answer

Explanation

Complexity and Maintainability Relationship

Correct Answer

Explanation

Process Metrics for Assessing Maintainability

Correct Answer

Explanation

Rising Corrective Maintenance Requests

Correct Answer

Explanation

Impact Analysis Time vs. Implementation Time

Correct Answer

Explanation

COCOMO 2 Maintenance Effort Basis

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: