Architecture Design Form

Project Title

Architecture Team

Name Phone Email

Define Migration Stages

Does you propose deploying a single stage (one hardware/software package at all sites), or significantly different packages at different sites?

Single stage migration.

Multiple stage migration.

Describe the hardware and / or software package(s) you propose to deploy.

(If complex, provide a network diagram. If multiple stages, provide multiple diagrams.)

Estimate how long it will take to deploy these network elements.

Stage

Duration

Start Date

End Date

1

e.g. 3 months

e.g. 4/99

e.g. 7/99

(Add more rows if you checked off "Multiple Stage migration")

Locations where you plan to deploy these network elements.

Stage

Location Name

Start Date

Reason for Upgrade

1

e.g. Amsterdam

e.g. 4/99

e.g. ROI

(Add more rows if multiple locations are impacted.)

Describe Hardware and Software Decisions

If new hardware or software is being deployed, describe those network elements in detail here. Use the checklist as a guideline. Ignore any checklist areas not relevant to your project.

Describe Required Vendor Service Changes

Yes

No

Are any new or changes to existing vendor services (carrier, management, etc.) being considered?

If yes, describe. Use the checklist as a guideline.

Define SLA's and Architecture Implications

Yes

No

Do the new network elements affect network capacity, usage, availability, performance, or any other form of service quality?

If yes, describe. Use the checklist as a guideline.

Define Monitoring and Management Architecture

Yes

No

Do the new network elements change the monitoring architecture, or require any changes to the current monitoring system, the current routing/call processing/configuration databases, or the current trouble reporting procedures?

If yes, describe. Use the checklist as a guideline.

Security Architecture

Yes

No

Do the new network elements change the security requirements, or current security procedures?

If yes, describe. Use the checklist as a guideline.

Configuration and Name Standards

Yes

No

Do the new network elements change the configuration, addressing or naming standards?

If yes, describe. Use the checklist as a guideline.

Financial Analysis

Revised Estimated Total Cost
Revised Estimated ROI (3 years)

Other

Yes

No

Are there any other important parts of the architecture that should be described and reviewed (e.g. change management, naming and configuration inventories or databases)?

If yes, describe.


 

Architecture Review Dates

Submit Form | Clear Form

This Architecture Plan will be posted by the publications group. It will be the responsibility of the project leader to update this Architecture Plan whenever any changes are made to the actual architecture that differ from the description in this Architecture Plan.


Path: http://eman/ANTS/Documentation/policy-procedures/stage_two/docs/arch_design_form.html
Owner: Pete Feighner, pfeighne@cisco.com
Last Modified: December 15, 1998
This is an sns-docs controlled document. Uncontrolled if printed.

Copyright © Cisco Systems, Inc. 1998