Documentation - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - SYSTEM PLANNING-DEPLOYMENT-BEST PRACTICES GUIDE 10.3 30-03-2010 System Planning Manual

When building your lab, you do not need to build the entire lab with physical hardware. You are not
testing the breaking point here. You are testing functionality and whether or not there are any major
issues found with the overall design. You should use actual production hardware to test functionality
at the device level, but the server infrastructure could be virtualized to save hardware costs. The idea
is to reflect the design so you can prove that it is solid.

4.4 Documentation

Documentation is the most important aspect of the design phase. It is critical that you document all
decisions that are made during the design phase and keep these items up-to-date. After the document
has been finalized, it is important to keep it up-to-date to reflect all changes to both the ZENworks
Configuration Management infrastructure that is in place, as well as the infrastructure and services
that ZENworks Configuration Management relies on.
In addition to reflecting the infrastructure, the design document can prove to be a useful and
powerful knowledge transfer document. As individuals within the organization move in and out of
the IT Services division, they can use this document to better understand what was put in place, and
how the system is connected and interconnected. It is a tool to provide insight into what was decided
during the project and beyond.
We recommend that you store the design document in a documentation repository if you have one,
and you should provide access to the document as required. However, you should limit who has
write access to the document so that it is not updated by unauthorized personnel.
80 System Planning, Deployment, and Best Practices Guide