Lectures Top-Down Network Design - Chapter 14: Documenting Your Network Design

Nội dung text: Lectures Top-Down Network Design - Chapter 14: Documenting Your Network Design

1. Top-Down Network Design, Ch. 14: Documenting Your Network Design Top-DNtkDiDown Network Design Chapter Fourteen Documenting Your Network Design Copyright 2010 Cisco Press & Priscilla Oppenheimer Documenting Your Design • If you are given a request for proposal (RFP), respond to the request in the exact format that the RFP specifies • If no RFP, you should still write a design document – Describe your customer’s requirements and how yygour design meets those re quirements – Document the budget for the project – Explain plans for implementing the design Copyright 2004 Cisco Press & Priscilla Oppenheimer Page 1
2. Top-Down Network Design, Ch. 14: Documenting Your Network Design Typical RFP Response Topics • A network topology for the new design • Information on the protocols, technologies, and products that form the design • An implementation plan • A training plan • Support and service information • Prices and payment options • Qualifications of the responding vendor or supplier • Recommendations from other customers • Legal contractual terms and conditions Contents of a Network Design Document • Executive summary • PjProjec t goa l • Project scope • Design requirements • Current state of the network • New logical and physical design • RltftkdittiResults of network design testing • Implementation plan • Project budget Copyright 2004 Cisco Press & Priscilla Oppenheimer Page 2
3. Top-Down Network Design, Ch. 14: Documenting Your Network Design Design Requirements • Business goals explain the role the network d es ign w ill p lay in he lp ing an organization succeed • Technical goals include scalability, performance, security, manageability, usability, adaptability, and affordability Logical and Physical Design • Logical design – Topology – Models for addressing and naming – Switching and routing protocols – Security strategies – Network managggement strategies • Physical design – Actual technologies and devices Copyright 2004 Cisco Press & Priscilla Oppenheimer Page 3
4. Top-Down Network Design, Ch. 14: Documenting Your Network Design Implementation Plan • Recommendations for deploying the network design • Project schedule – Including any dates and times for service provider installations • Any plans for outsourcing • Training • Risks • A fallback plan if the implementation should fail • A plan for evolving the design as new requirements arise Possible Appendixes • Detailed topology maps • Device configurations • Addressing and naming details • Network design testing results • Contact information • Pricing and payment options • More information about the comppyany that is presenting the design – Annual reports, product catalogs, press releases • Legal contractual terms and conditions Copyright 2004 Cisco Press & Priscilla Oppenheimer Page 4
5. Top-Down Network Design, Ch. 14: Documenting Your Network Design Summary • When a customer provides an RFP, make sure to follow the prescribed format • When not bound by an RFP, develop a design document that describes requirements, the existing network, the logical and physical design, an implementation plan, and the budget • BtildtiBe sure to include an executive summary • In some cases, you should also include appendixes with detailed information Review Questions • Why is it important to document your netkdi?twork design? • Why is it important to submit an RFP proposal in the exact format prescribed? • What are the major topics in a design document? • What are some possible appendixes for a design document? Copyright 2004 Cisco Press & Priscilla Oppenheimer Page 5