This paper examines the six essential technical requirements that network designers must assess when planning a network project: scalability, availability, network performance, security, manageability, and affordability. Drawing on Oppenheimer's top-down network design framework, the paper explains what each requirement means in practical terms, how to gather the relevant information from clients, and why each factor is critical to meeting customer expectations. The discussion covers topics such as uptime calculations, disaster recovery planning, performance metrics like throughput and latency, ISO network management categories, and budget-driven cost considerations.
Analyzing technical requirements for a customer is essential to fulfilling their expectations when designing a network. The process of gathering these requirements may differ from one organization to another, but the requirements themselves can be described using six core concepts: scalability, availability, network performance, security, manageability, and affordability. Each of these factors must be carefully assessed before a network design project proceeds.
Scalability refers to the capacity for growth that a network design can support. This is particularly important for large companies that are continuously adding users, applications, additional sites, and external network connections. The proposed network design should be able to adapt to any anticipated additions. It is therefore necessary to determine the projected number of networks, users, servers, and sites that may be added within the coming few years, so that these can be accommodated within the design from the outset.
Availability refers to the amount of time that a network is accessible to users. This is a major concern for larger and more complex organizations. In mathematical terms, availability can be expressed as the percentage of uptime per year, month, week, day, or hour, compared to the total time in that period. For example, a network that offers 24-hour, seven-days-a-week service but is only operational for 165 of the 168 hours in a given week has an availability rate of 98.21%.
In technical terms, availability is closely connected with resilience — the degree of stress a network can handle and the speed at which it recovers from disruptions. Good availability therefore requires good resilience. Customers should specify their availability requirements clearly so that design expectations can be met.
Related to availability is disaster recovery. Any network design must take this aspect into consideration. Plans must be established for how to protect and restore data in the event of outages, as well as natural or man-made disasters.
"Throughput, latency, and performance metrics"
"Protecting data, operations, and equipment"
"ISO management categories and budget-driven design"
You’re 43% through this paper. Sign up to read the remaining 3 sections.
Sign Up Now — Instant Access Already a member? Log inAlways verify citation format against your institution’s current style guide requirements.