Data Management - The CIO's Guide to Oracle Products and Solutions - page 201

Guideline 2: The planning and management of the enterprise-wide
technical architecture must be unified and have a planned evolution
that is governed across the enterprise .

1. A unified approach will require a change in cultural attributes.

2. Normal evolution will require prioritization and reprioritization

across all IT initiatives.

3. Dependencies must be maintained.

4. The architecture must be continually reexamined and refreshed.

5. Short-term results vs. long-term impact must be constantly
considered.

6. Establishing enterprise architecture takes time and involves a lot of

change.

7. Make sure that the chosen architecture has a broad range of
capabilities to handle vast needs and best-of-breed solutions in
the marketplace (Internet and PDAs and kiosk).

8. Planning for retirement must be considered for obsolete and
nonstandard products.

9. Retraining of staff moving from obsolete technologies will be
required.

10. In-house software engineers, data architects, DBAs, and ware-
house experts will need to be developed and trained.

Guideline 3: Architecture support and review structures shall be used
to ensure that the integrity of the architecture is maintained as sys-
tems and infrastructure are acquired, developed, and enhanced.

1. A structured project-level review process and authority will be
needed to ensure that information systems comply with the IT
architecture and related standards.

2. Processes incorporating the guidelines of this (technical) archi-
tecture must be developed for all application procurement, devel-
opment, design, and management activities.

3. This compliance process must allow for the introduction of new
technology and standards.

4. Conceptual architecture and technical domain guidelines should
be used as evaluation criteria for purchasing as well as developing
sotware.

5. Negotiation at the enterprise level will be needed to handle an
increase in compliant systems.