Final Design and Implementation

Slides:



Advertisements
Similar presentations
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v Determining Customer Requirements Cisco Unity Design ProcessPresales.
Advertisements

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-1 Providing Cutover Support and Optimization Final Design and Implementation.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-1 Understanding Cisco Unity Configurations and Messaging Models Cisco Unity Design Process—Presales.
1 © 2004, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.1 Module 6 Switch Configuration.
MCSE Guide to Microsoft Exchange Server 2003 Administration Chapter 14 Upgrading to Exchange Server 2003.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Configure a Wireless Router LAN Switching and Wireless – Chapter 7.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-1 Migrating from Voice Mail to Unified Messaging Migrating Voice Mail to Unified Messaging.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-1 Understanding the Role of Telephony Components in Cisco Unity Design Cisco Unity Design Process—Presales.
Cognos Finance: Growing with your business Allen Sherbrook Concessio.
3.1 © 2004 Pearson Education, Inc. Exam Managing and Maintaining a Microsoft® Windows® Server 2003 Environment Lesson 3: Introducing Active Directory.
Cisco – Semester III Documentation. What is it most important component of a good network?  Documentation.
15.1 © 2004 Pearson Education, Inc. Exam Planning, Implementing, and Maintaining a Microsoft® Windows® Server 2003 Active Directory Infrastructure.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 10: Server Administration.
MCTS Guide to Microsoft Windows Server 2008 Network Infrastructure Configuration Chapter 8 Introduction to Printers in a Windows Server 2008 Network.
3.1 © 2004 Pearson Education, Inc. Exam Managing and Maintaining a Microsoft® Windows® Server 2003 Environment Lesson 3: Introducing Active Directory.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-1 Using Active Directory and Exchange 2000 or 2003 in Cisco Unity Design Cisco Unity Design.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-1 Developing an Implementation Plan Final Design and Implementation.
Duties of a system administrator. A system administrator's responsibilities typically include:
© 2007 Cisco Systems, Inc. All rights reserved.ICND1 v1.0—4-1 LAN Connections Using a Cisco Router as a DHCP Server.
Configuration Management Supplement 67 Robert Horn, Agfa Healthcare.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-1 Designing VPIM Solutions Migrating Voice Mail to Unified Messaging and Interoperability.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Backup, Restore, and Server Replacement Josh Rose UCBU Software Engineer.
SOE and Application Delivery Gwenael Moreau, Abbotsleigh.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-1 Designing with the Directory and Mailstore in Domino Cisco Unity Design Process—Presales.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—2-1 Understanding Bandwidth Provisioning Issues The Design Process—Planning.
© Drexel University Software Engineering Research Group (SERG) 1 Based on the paper by Philippe Kruchten from Rational Software.
WP3 Semivirtual Campus Progress Report Petr Grygarek VSB-CZ.
1 © 2005 Cisco Systems, Inc. All rights reserved. Cisco Unity Connection 1.x Documentation What you need to know.
Current Job Components Information Technology Department Network Systems Administration Telecommunications Database Design and Administration.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.0 Module 6 Switch Configuration.
ITEC 3220M Using and Designing Database Systems
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Configure a Wireless Router Basic Wireless Concepts & Configuration Chapter.
Physical Design of a network People who develop & support networks.
Secure Messaging Workshop The Open Group Messaging Forum February 6, 2003.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Filtering Traffic Using Access Control Lists Introducing Routing and Switching.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—2-1 Understanding Capacity-Planning Considerations The Design Process—Planning.
Module 5: Implementing Printing. Overview Introduction to Printing in the Windows Server 2003 Family Installing and Sharing Printers Managing Access to.
Lecture Introduction to Software Development SW Engg. Development Process Instructor :Muhammad Janas khan Thursday, September.
© 2006 Cisco Systems, Inc. All rights reserved CUDN v1.1—1 Cisco Unity Design and Networking.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—1-1 Planning Routing Services Creating an Implementation Plan and Documenting the Implementation.
Jini Architecture Introduction System Overview An Example.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
1 © 2004, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.1 Module 6 Switch Configuration.
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public Course v6 Chapter # 1 Chapter 2: Troubleshooting Processes for Complex Enterprise.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Filtering Traffic Using Access Control Lists Introducing Routing and Switching.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-1 Developing a High-Level Design Final Design and Implementation.
MICROSOFT TESTS /291/293 Fairfax County Adult Education Courses 1477/1478/1479.
1 © 2005 Cisco Systems, Inc. All rights reserved. Cisco Unity 4.1 Documentation What you need to know.
11 DESIGNING AN ADMINISTRATIVE SECURITY STRUCTURE Chapter 7.
Copyright 2007, Information Builders. Slide 1 iWay Web Services and WebFOCUS Consumption Michael Florkowski Information Builders.
© 2002, Cisco Systems, Inc. All rights reserved..
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—1-1 Planning Routing Services Lab 1-1 Debrief.
7.1 © 2004 Pearson Education, Inc. Exam Designing a Microsoft ® Windows ® Server 2003 Active Directory and Network Infrastructure Lesson 7: Planning.
1 Welcome to Designing a Microsoft Windows 2000 Network Infrastructure.
© 2002, Cisco Systems, Inc. All rights reserved..
Chapter 17 Windows NT/2000 Domains Cisco Learning Institute Network+ Fundamentals and Certification Copyright ©2005 by Pearson Education, Inc. Upper Saddle.
Job offer IT System & Software Specialist We are currently looking for an IT database administrator in order to respond to one key-account customer demand.
1 © 2007 Cisco Systems, Inc. All rights reserved.Cisco Public Network Architecture Characteristics  Explain four characteristics that are addressed by.
© 2003, Cisco Systems, Inc. All rights reserved. 2-1 Campus Network Design.
© ITT Educational Services, Inc. All rights reserved. IS3120 Network Communications Infrastructure Unit 10 Network Management—FCAPS.
Network Life Cycle Created by Michael Law
© 2002, Cisco Systems, Inc. All rights reserved.
Unit 27: Network Operating Systems
Hybrid Search Phased Approach.
Systems Analysis and Design in a Changing World, 6th Edition
Planning a Network Upgrade
1 Stadium Company Network. The Stadium Company Project Is a sports facility management company that manages a stadium. Stadium Company needs to upgrade.
The Design Process—Planning
Module 1: Overview of Systems Management Server 2003
Presentation transcript:

Final Design and Implementation Developing a Low-Level Design

Low-Level Design Definition Draws input from the high-level design Analyzes specific configuration tasks Provides direction to project participants Creates one document for small installations Creates multiple documents for large installations Used as basis for implementation plan Becomes the sign-off document

Low-Level Design—Cisco Unity System Description Document these Cisco Unity system components: All Cisco Unity system configurations in detail Cisco Unity physical hardware configurations Cisco Unity switch integration detail Cisco Unity networking and subscriber addressing scheme Physical network connectivity

Low-Level Design–Cisco Unity Network and Messaging Infrastructure Detail Document these Cisco Unity integration components: Cisco Unity domain usage (depending on which messaging servers are used) Cisco Unity directory usage, including schema extension or Lotus DUCs installation Name resolution hosts Service accounts and access in detail End-user access to Cisco Unity and to the infrastructure Any special security considerations discovered during the planning phase

Low-Level Design–Administration and Management Document the administration plan. Who will maintain accounts, users, and servers? Plan for and document the system management standards. Document the subscriber naming convention. Document the support plan, contact personnel, and escalation procedure for each phase of the project.

Summary Low-level design adds all detail necessary to give a clear direction to all project participants. Document Cisco Unity hardware, software, and network configurations in a Cisco Unity system description. Document each Cisco Unity integration with the infrastructure. Document the administration, system management, and support plans for both implementation and operation.