1. Final Design and Implementation
Developing a Low-Level Design

2. 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

3. 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

4. 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

5. 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.

6. 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.