Refactoring - Preventative Maintenance

Refactoring as continuous structural upkeep, its tie to agile methods, common "bad smells," and how it differs from reengineering

download Export

search_insights Statistics

stylus_note White Board

Quran

calculate Calculator

dictionary Dictionary

fullscreen Full Screen

more_vert More

QUESTION OF

volume_mute Read quiz aloud

Views #: 193

Questions #: 11

Time: 10 minutes

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

Definition of Refactoring

1 pts

volume_mute

What is refactoring?

The process of permanently deleting unused code without any structural improvement

The process of making improvements to a program to slow down structural degradation through change, without adding new functionality

The process of porting a system to run on a completely different hardware platform

The process of adding entirely new features to a system to meet changing customer demands

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Refactoring as Preventative Maintenance

1 pts

volume_mute

Why can refactoring be thought of as 'preventative maintenance'?

Because it is performed exclusively by doctors hired as software consultants

Because it is only ever performed once, immediately before a system is permanently retired

Because it prevents any future changes from ever being made to the system

Because it reduces the problems of future change by addressing structural issues before they become severe

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Refactoring Is Not Limited to Object-Oriented Development

1 pts

volume_mute

True or False: Although refactoring is sometimes considered to be limited to object-oriented development, the underlying principles can in fact be applied to any development approach.

True

False

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Refactoring and Agile Methods

1 pts

volume_mute

Why is refactoring described as an inherent part of agile methods?

Refactoring was invented specifically to replace all forms of testing in agile teams

Agile teams refactor code only after the software has been officially retired

Agile methods legally require refactoring to be performed exactly once per year

Agile methods are based on continuous change, so program quality can degrade quickly without frequent refactoring to counteract this

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Regression Testing and Refactoring Safety

1 pts

volume_mute

How does an emphasis on regression testing in agile methods help reduce the risk of refactoring?

Regression testing eliminates the need to ever check whether refactored code still works

Regression testing is only relevant to hardware changes, not code refactoring

Errors introduced through refactoring should be detectable because previously successful tests would then fail

Regression testing automatically fixes any errors introduced during refactoring without human intervention

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Refactoring 'Bad Smells'

1 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Bad smell

Long methods

Switch (case) statements

Data clumping

Speculative generality

Duplicate code

Description

The same group of data items reoccurs in several places and could be replaced with an encapsulating object

Statements scattered around a program that depend on a value's type, often replaceable with polymorphism

Generality is included in a program in case it is needed in the future, but can usually simply be removed

The same or similar code appears in multiple places and could be extracted into a single reusable method

A method that is too long and should be redesigned as several shorter methods

Match each refactoring 'bad smell' to its correct description.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Polymorphism as a Refactoring Solution

1 pts

volume_mute

In object-oriented languages, what technique can often replace scattered switch (case) statements that depend on an object's type?

Removing all conditional logic from the entire program permanently

Converting all switch statements into global variables

Increasing the number of switch statements to make the logic more explicit

Polymorphism, where different subclasses provide their own implementation of a common operation

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Primitive Refactoring Transformations

1 pts

volume_mute

Which of the following are examples of primitive refactoring transformations that can be used singly or together to address bad smells? Select all that apply.

Encrypt method - converting all method names into randomized strings

Delete project - permanently removing the entire codebase

Extract method - removing duplication by creating a new shared method

Pull up method - replacing similar methods in subclasses with one method in a superclass

Consolidate conditional expression - replacing a sequence of tests with a single test

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

IDE Support for Refactoring

1 pts

volume_mute

How do interactive development environments such as modern code editors typically support the refactoring process?

They automatically rewrite the entire system architecture without any developer input

They prevent developers from ever modifying code that has already been refactored once

They include refactoring support in their editors, making it easier to find dependent parts of a program that need to change

They only support refactoring for systems written in assembly language

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

When Code Cannot Simply Be Refactored

1 pts

volume_mute

What might be necessary if you take over a program for maintenance whose structure has been significantly degraded, beyond what simple code-level refactoring can fix?

Design refactoring, which involves identifying relevant design patterns and replacing existing code with code that implements them

Disabling all version control history for the project

Immediately abandoning the project with no further action

Switching the entire team to a completely unrelated project

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Reengineering vs. Refactoring - Key Difference

1 pts

volume_mute

Statement

×Takes place after a system has been maintained for some time and maintenance costs are increasing

×Uses automated tools to process a legacy system and create a new, more maintainable version

×Is intended to avoid the structure and code degradation that increases maintenance difficulty

×Is a continuous process of improvement throughout development and evolution

Reengineering

Refactoring

Match each statement to whether it describes reengineering or refactoring.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Undergraduate Professional

Definition of Refactoring

Correct Answer

Explanation

Refactoring as Preventative Maintenance

Correct Answer

Explanation

Refactoring Is Not Limited to Object-Oriented Development

Correct Answer

Explanation

Refactoring and Agile Methods

Correct Answer

Explanation

Regression Testing and Refactoring Safety

Correct Answer

Explanation

Refactoring 'Bad Smells'

Bad smell

Description

Correct Answer

Explanation

Polymorphism as a Refactoring Solution

Correct Answer

Explanation

Primitive Refactoring Transformations

Correct Answer

Explanation

IDE Support for Refactoring

Correct Answer

Explanation

When Code Cannot Simply Be Refactored

Correct Answer

Explanation

Reengineering vs. Refactoring - Key Difference

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: