Information Technology Reference
In-Depth Information
business, while many other companies have corporate websites offering
goods, services, and customer contact capabilities. Without adequate
planning, valuable data and key services can be impaired if inadequately
protected. An enterprise architect must identify which elements of the
information architecture act as currency within the organization's opera-
tional envelope, in order to plan and negotiate for sufficient resources to
identify, acquire, manage, and use information and needed information
technologies. The value of IT programs must be made clearly evident to
stakeholders and users alike, particularly when an architectural change
creates disruption or change to the users' day-to-day experience. The archi-
tect should look for the “low-hanging fruit” that easily generate return on
the initial investment, while looking down the road for longer-term bene-
fits that might require greater planning, effort, and expense to achieve.
Avoid Drawing Fire
A popular cartoon by Bill Mauldin printed during World War II showed
an illustration of an officer, standing proudly and boldly in the face of
oncoming fire from the enemy while two GIs huddled in the foxhole at
his feet. One of the GIs says to the officer, “Would you mind not drawing
their fire while inspiring us, Sir?” This humorous aside should be kept
in mind whenever a decision is made to include controversial or newly
emergent technologies into enterprise planning. A network enterprise is
not the place to test beta versions of new software, nor to implement
wholesale change to meet the latest fad in computing practices, software,
or information delivery.
An excellent example of drawing fire while trying to do the right thing
comes from the attempt to establish the OpenDocument Format (ODF)
as a mandatory requirement within the Commonwealth of Massachu-
setts' information technology strategies. In addition to user groups voic-
ing opposition to the change from the more familiar Microsoft Office
user suite, the state found itself addressing a wide range of concerns. The
strongest objections came from organizations representing persons with
disabling conditions who might be barred from working with the state or
accessing its offered services because of the relative scarcity of accessibil-
ity-related development applied within the open software environment,
specifically the OpenOffice suite of products that was being considered
