This paper examines the iterative process of designing and redesigning computer networks within the broader internet ecosystem. It covers how to evaluate organizational needs before beginning any design work, how to characterize existing network infrastructure through physical inspection and documentation, and how to develop detailed network maps using diagramming tools. The paper also addresses key performance factors — including scalability, availability, and traffic flow — that guide engineers in determining whether enhancement of an existing network or a full redesign is warranted. The discussion draws on foundational texts in telecommunications and network planning to provide a structured overview of best practices for network engineers and IT planners.
The internet involves a number of autonomous networks that are intertwined together, providing users with end-to-end reachability and connection (Oppenheimer, 1998). Depending on the network that is designed, different functions and objectives apply — and those objectives depend on the needs of the user. A proper evaluation of needs must be conducted before anything is created (Farr, 1988). It is important to remember that networks have to intersect and coexist with each other.
Planning and designing a network structure is an iterative process. It involves a number of layers, and before the design is realized, it is essential to understand the needs of the subscriber and the capabilities of the operator. The existing structure must be understood before a better infrastructure can be designed, and the new network must fit within the broader internet ecosystem.
New networks are created every day. The ecosystem of the internet is highly dynamic and versatile. As new networks emerge, old ones are retired or refurbished to fit new technology. The health of networks can also depend on external or environmental factors. Elements such as the global economy and the popularity of certain applications all play a role in network health (Farr, 1988). All such changes have a dynamic impact on every network that exists, and the future of the internet ultimately relies on the people currently using its applications.
Businesses rely on networks to allow the organization to operate in an orderly way. The design of the network depends on the needs of the business or organization (Farr, 1988). Small businesses do not require overly complicated network infrastructure designs; it is best to remain true to the nature of the organization and create only the features that are actually needed.
Characterizing the network infrastructure involves creating or developing a network map. This includes identifying the locations of different internetworking devices and components. All names, addresses, and related information should be documented and labeled. Several methods exist for accomplishing this. Some engineers prefer to conduct documentation through the physical locations of cabling, which helps reveal the network architecture and any environmental constraints it faces.
"Evaluating existing network uses, performance, and constraints"
"Tools and methods for mapping network topology"
"Pre-design steps and organizational goals for redesign"
Always verify citation format against your institution’s current style guide requirements.