|
Decide on the focus
Decide on the focus of the update (e.g. process models, location models, etc) ... this step is to define the list of
required participants.
|
Gather Required Information
The information required for the update, including existing IT architecture, is gathered together. For
example, for updating a Technology level architecture, the following information will be of use:
-
The Technical Perspective documentation;
-
Project and business plans and objectives;
-
Existing network logical and physical design;
-
Existing databases and database design;
-
Existing server environment (configuration, software versions, planned upgrades);
-
Existing standards (network, naming, protocols, and so on).
These documents should be collated and made available to those participating in the update.
|
Inform Attendees
Each attendee is given sufficient notice about the update activity, and what is expected of them in terms of
both preparatory work and their involvement in the update process. As general guidance, you should consider the
following stakeholders when inviting attendees to participate in the meetings:
-
Direct users of the 'system', and also testing and documentation staff;
-
Domain or subject-matter experts for the system;
-
Peers: other IT architects or IT experts with experience in the domain or technology.
Include only those participants who will contribute to achieving the objectives of the update. In general, it is
usually more productive to hold several focused sessions with a smaller number of participants, than to hold one
involving many stakeholders.
|
|
