Information Technology Reference
In-Depth Information
of more full-fledged changes that are difficult to reverse and invariably
address substantial functionality.
Take a look at a word processor. If one were to change a font for a
particular document, one would not call it configuration because it applies
only to that document and does not apply across the installation. However,
if one were to select a default font during installation of one's word
processor, one would call it configuration. In either situation, one would
not
call it customization.
A user may get features that he or she wants through customization
or configuration. Generally, configuration is cheaper than customization
because it does not involve the use of tools or expensive development
resources. For example, MyYahoo provides personalization through con-
figuration, not customization. The user is limited to the options that Yahoo
permits for a MyYahoo page. Some products, however, might go with the
smallest set, offering some configuration but no customization. The issue
of configuration versus customization looms larger in shared or managed
application environments. There, the costs of supporting multiple custom-
ized instances of the product can be very expensive compared to sup-
porting a table-driven, user-specific, multiple-configuration environment.
Would you call these customization or configuration?
Changing the reclining angle of your seat's back
Replacing the fabric of the chair
Hanging a new painting on the wall
Repainting the wall
Adding a new field to a screen
Moving a field around on the screen
Replacing the speakers in your car with better ones
Setting tuner pre-selects on your radio
Setting up account codes in a GL (general ledger)
package
Customization and Ground-Up Creation
Customization differs from ground-up creation in many ways. During
customization, one is working off somebody else's body of creative work.
