Transcript About This Template
Slide 1
Final Design and Implementation
Developing a High-Level Design
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-1
Design Process
• Determine the final design
• High-Level Design Definition template
– Gathered from preliminary design and physical
information
• Low-Level Design Definition template
– Detailed document of all infrastructures and dependencies
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-2
High-Level Design
1. Create a design summary.
2. Document the design approach.
3. Document design goals.
4. Create a description of the total design and all affected areas.
5. Create a description of each site installation.
6. Compile reference documentation.
7. Document the design approval.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-3
High-Level Design Diagrams
Diagram of Cisco Unity solution from the three
infrastructure perspectives:
– Messaging
– Network
– Telephony
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-4
Summary
• The final design phase consists of a High-Level and LowLevel Design Definition document.
• The high-level design includes a design summary, approach,
goals, description, rationale, and approval.
• High-level design documents should show how Cisco Unity
fits into the messaging, network, and telephony
infrastructures.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-5
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-6
Slide 2
Final Design and Implementation
Developing a High-Level Design
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-1
Design Process
• Determine the final design
• High-Level Design Definition template
– Gathered from preliminary design and physical
information
• Low-Level Design Definition template
– Detailed document of all infrastructures and dependencies
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-2
High-Level Design
1. Create a design summary.
2. Document the design approach.
3. Document design goals.
4. Create a description of the total design and all affected areas.
5. Create a description of each site installation.
6. Compile reference documentation.
7. Document the design approval.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-3
High-Level Design Diagrams
Diagram of Cisco Unity solution from the three
infrastructure perspectives:
– Messaging
– Network
– Telephony
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-4
Summary
• The final design phase consists of a High-Level and LowLevel Design Definition document.
• The high-level design includes a design summary, approach,
goals, description, rationale, and approval.
• High-level design documents should show how Cisco Unity
fits into the messaging, network, and telephony
infrastructures.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-5
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-6
Slide 3
Final Design and Implementation
Developing a High-Level Design
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-1
Design Process
• Determine the final design
• High-Level Design Definition template
– Gathered from preliminary design and physical
information
• Low-Level Design Definition template
– Detailed document of all infrastructures and dependencies
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-2
High-Level Design
1. Create a design summary.
2. Document the design approach.
3. Document design goals.
4. Create a description of the total design and all affected areas.
5. Create a description of each site installation.
6. Compile reference documentation.
7. Document the design approval.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-3
High-Level Design Diagrams
Diagram of Cisco Unity solution from the three
infrastructure perspectives:
– Messaging
– Network
– Telephony
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-4
Summary
• The final design phase consists of a High-Level and LowLevel Design Definition document.
• The high-level design includes a design summary, approach,
goals, description, rationale, and approval.
• High-level design documents should show how Cisco Unity
fits into the messaging, network, and telephony
infrastructures.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-5
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-6
Slide 4
Final Design and Implementation
Developing a High-Level Design
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-1
Design Process
• Determine the final design
• High-Level Design Definition template
– Gathered from preliminary design and physical
information
• Low-Level Design Definition template
– Detailed document of all infrastructures and dependencies
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-2
High-Level Design
1. Create a design summary.
2. Document the design approach.
3. Document design goals.
4. Create a description of the total design and all affected areas.
5. Create a description of each site installation.
6. Compile reference documentation.
7. Document the design approval.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-3
High-Level Design Diagrams
Diagram of Cisco Unity solution from the three
infrastructure perspectives:
– Messaging
– Network
– Telephony
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-4
Summary
• The final design phase consists of a High-Level and LowLevel Design Definition document.
• The high-level design includes a design summary, approach,
goals, description, rationale, and approval.
• High-level design documents should show how Cisco Unity
fits into the messaging, network, and telephony
infrastructures.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-5
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-6
Slide 5
Final Design and Implementation
Developing a High-Level Design
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-1
Design Process
• Determine the final design
• High-Level Design Definition template
– Gathered from preliminary design and physical
information
• Low-Level Design Definition template
– Detailed document of all infrastructures and dependencies
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-2
High-Level Design
1. Create a design summary.
2. Document the design approach.
3. Document design goals.
4. Create a description of the total design and all affected areas.
5. Create a description of each site installation.
6. Compile reference documentation.
7. Document the design approval.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-3
High-Level Design Diagrams
Diagram of Cisco Unity solution from the three
infrastructure perspectives:
– Messaging
– Network
– Telephony
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-4
Summary
• The final design phase consists of a High-Level and LowLevel Design Definition document.
• The high-level design includes a design summary, approach,
goals, description, rationale, and approval.
• High-level design documents should show how Cisco Unity
fits into the messaging, network, and telephony
infrastructures.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-5
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-6
Slide 6
Final Design and Implementation
Developing a High-Level Design
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-1
Design Process
• Determine the final design
• High-Level Design Definition template
– Gathered from preliminary design and physical
information
• Low-Level Design Definition template
– Detailed document of all infrastructures and dependencies
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-2
High-Level Design
1. Create a design summary.
2. Document the design approach.
3. Document design goals.
4. Create a description of the total design and all affected areas.
5. Create a description of each site installation.
6. Compile reference documentation.
7. Document the design approval.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-3
High-Level Design Diagrams
Diagram of Cisco Unity solution from the three
infrastructure perspectives:
– Messaging
– Network
– Telephony
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-4
Summary
• The final design phase consists of a High-Level and LowLevel Design Definition document.
• The high-level design includes a design summary, approach,
goals, description, rationale, and approval.
• High-level design documents should show how Cisco Unity
fits into the messaging, network, and telephony
infrastructures.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-5
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-6
Final Design and Implementation
Developing a High-Level Design
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-1
Design Process
• Determine the final design
• High-Level Design Definition template
– Gathered from preliminary design and physical
information
• Low-Level Design Definition template
– Detailed document of all infrastructures and dependencies
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-2
High-Level Design
1. Create a design summary.
2. Document the design approach.
3. Document design goals.
4. Create a description of the total design and all affected areas.
5. Create a description of each site installation.
6. Compile reference documentation.
7. Document the design approval.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-3
High-Level Design Diagrams
Diagram of Cisco Unity solution from the three
infrastructure perspectives:
– Messaging
– Network
– Telephony
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-4
Summary
• The final design phase consists of a High-Level and LowLevel Design Definition document.
• The high-level design includes a design summary, approach,
goals, description, rationale, and approval.
• High-level design documents should show how Cisco Unity
fits into the messaging, network, and telephony
infrastructures.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-5
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-6
Slide 2
Final Design and Implementation
Developing a High-Level Design
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-1
Design Process
• Determine the final design
• High-Level Design Definition template
– Gathered from preliminary design and physical
information
• Low-Level Design Definition template
– Detailed document of all infrastructures and dependencies
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-2
High-Level Design
1. Create a design summary.
2. Document the design approach.
3. Document design goals.
4. Create a description of the total design and all affected areas.
5. Create a description of each site installation.
6. Compile reference documentation.
7. Document the design approval.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-3
High-Level Design Diagrams
Diagram of Cisco Unity solution from the three
infrastructure perspectives:
– Messaging
– Network
– Telephony
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-4
Summary
• The final design phase consists of a High-Level and LowLevel Design Definition document.
• The high-level design includes a design summary, approach,
goals, description, rationale, and approval.
• High-level design documents should show how Cisco Unity
fits into the messaging, network, and telephony
infrastructures.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-5
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-6
Slide 3
Final Design and Implementation
Developing a High-Level Design
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-1
Design Process
• Determine the final design
• High-Level Design Definition template
– Gathered from preliminary design and physical
information
• Low-Level Design Definition template
– Detailed document of all infrastructures and dependencies
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-2
High-Level Design
1. Create a design summary.
2. Document the design approach.
3. Document design goals.
4. Create a description of the total design and all affected areas.
5. Create a description of each site installation.
6. Compile reference documentation.
7. Document the design approval.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-3
High-Level Design Diagrams
Diagram of Cisco Unity solution from the three
infrastructure perspectives:
– Messaging
– Network
– Telephony
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-4
Summary
• The final design phase consists of a High-Level and LowLevel Design Definition document.
• The high-level design includes a design summary, approach,
goals, description, rationale, and approval.
• High-level design documents should show how Cisco Unity
fits into the messaging, network, and telephony
infrastructures.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-5
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-6
Slide 4
Final Design and Implementation
Developing a High-Level Design
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-1
Design Process
• Determine the final design
• High-Level Design Definition template
– Gathered from preliminary design and physical
information
• Low-Level Design Definition template
– Detailed document of all infrastructures and dependencies
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-2
High-Level Design
1. Create a design summary.
2. Document the design approach.
3. Document design goals.
4. Create a description of the total design and all affected areas.
5. Create a description of each site installation.
6. Compile reference documentation.
7. Document the design approval.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-3
High-Level Design Diagrams
Diagram of Cisco Unity solution from the three
infrastructure perspectives:
– Messaging
– Network
– Telephony
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-4
Summary
• The final design phase consists of a High-Level and LowLevel Design Definition document.
• The high-level design includes a design summary, approach,
goals, description, rationale, and approval.
• High-level design documents should show how Cisco Unity
fits into the messaging, network, and telephony
infrastructures.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-5
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-6
Slide 5
Final Design and Implementation
Developing a High-Level Design
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-1
Design Process
• Determine the final design
• High-Level Design Definition template
– Gathered from preliminary design and physical
information
• Low-Level Design Definition template
– Detailed document of all infrastructures and dependencies
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-2
High-Level Design
1. Create a design summary.
2. Document the design approach.
3. Document design goals.
4. Create a description of the total design and all affected areas.
5. Create a description of each site installation.
6. Compile reference documentation.
7. Document the design approval.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-3
High-Level Design Diagrams
Diagram of Cisco Unity solution from the three
infrastructure perspectives:
– Messaging
– Network
– Telephony
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-4
Summary
• The final design phase consists of a High-Level and LowLevel Design Definition document.
• The high-level design includes a design summary, approach,
goals, description, rationale, and approval.
• High-level design documents should show how Cisco Unity
fits into the messaging, network, and telephony
infrastructures.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-5
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-6
Slide 6
Final Design and Implementation
Developing a High-Level Design
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-1
Design Process
• Determine the final design
• High-Level Design Definition template
– Gathered from preliminary design and physical
information
• Low-Level Design Definition template
– Detailed document of all infrastructures and dependencies
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-2
High-Level Design
1. Create a design summary.
2. Document the design approach.
3. Document design goals.
4. Create a description of the total design and all affected areas.
5. Create a description of each site installation.
6. Compile reference documentation.
7. Document the design approval.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-3
High-Level Design Diagrams
Diagram of Cisco Unity solution from the three
infrastructure perspectives:
– Messaging
– Network
– Telephony
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-4
Summary
• The final design phase consists of a High-Level and LowLevel Design Definition document.
• The high-level design includes a design summary, approach,
goals, description, rationale, and approval.
• High-level design documents should show how Cisco Unity
fits into the messaging, network, and telephony
infrastructures.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-5
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—3-6