Software Development Cross Solution - Index of - Free

#5. Refactoring
Refactoring is the process of modifying the structure of your code,
without modifying its behavior. Refactoring is done to increase the
cleanness, flexibility, and extensibility of your code, and usually is
related to a specific improvement in your design.
Most refactorings are fairly simple, and focus on one specific design
aspect of your code. For example:
public double getDisabilityAmount() {
// Check for eligibility
if (seniority < 2)
return 0;
if (monthsDisabled > 12)
return 0;
if (isPartTime)
return 0;
// Calculate disability amount and return it
}
While there’s nothing particularly wrong with this code, it’s not as
maintainable as it could be. The getDisabilityAmount()
method is really doing two things: checking the eligibility for disability,
and then calculating the amount.
By now, you should know that violates the Single Responsibility
Principle. We really should separate the code that handles eligibility
requirements from the code that does disability calculations. So we can
refactor this code to look more like this:
public double getDisabilityAmount() {
// Check for eligibility
if (isEligibleForDisability()) {
// Calculate disability amount and return it
} else {
return 0;
}
}
Now, if the eligibility requirements for disability change, only the
isEligibleForDisability() methods needs to change—and
the method responsible for calculating the disability amount doesn’t.
Think of refactoring as a checkup for your code. It should be an
ongoing process, as code that is left alone tends to become harder and
harder to reuse. Go back to old code, and refactor it to take advantage
of new design techniques you’ve learned. The programmers who have
to maintain and reuse your code will thank you for it.
Download at WoweBook.Com
We’ve taken two responsibilities,
and placed them in two separate
methods, adhering to the SRP.
leftovers
Refactoring
changes the
internal structure
of your code
WITHOUT
affecting your
code’s behavior.
you are here 4 441