Configuration and Implementation steps in Low Level Design
i just want to ask why we should put the implementation steps and some of configurations portions of proposed technical design in Low Level Design document. as long as the people in the site are Technical then no need to add such information and just give them the Config. file of the device (show run) at the end of the project. and just we state that the solution will be by specific technology without how (e.g: will deploy BGP).
i see that in LLD of Cisco that they give the solution implementation steps with config. portion.
can anyone give me a rigid justification why we need to include such information in LLD.
Re: Configuration and Implementation steps in Low Level Design
Hi, Mahmoud --
Without seeing the document or documents in question, it is difficult to determine whether the level of detail is appropriate or perhaps unnecessary. Could you please provide links to examples that you have in mind?
What do you do if you think you're running into a bug? Cisco makes it
possible for you to report bugs yourself. Learn how, and find out how
your contributions help us improve our software.Cisco publishes its
bugs. Before opening a TAC Support Case, use Bu...
Cisco Licensing is pleased to announce the new Licensing Portal. It
provides customers with an enhanced self-service experience by
stream-lining and automating many licensing activities. Please take a
moment to familiarize yourself with the features that ...