41672019 CChaplor 1, Analyzing Businoss Goals and Consiraints NET 226 - Designing Internetwork Solutions chapter 1, Analyzing Business Goals and Constraints Objectives: This lesson introduces the ideas behind top-down network design. Objectives important to this lesson: 1. Top-down methodology 2. Analyzing business goals 3. Scope of a network project 4, Identifying network applications 5. Analyzing business constraints Concepts: Chapter 1 Top-down methodology The chapter begins with the very realistic idea that a network can be a mess. This can be due to poor planning, or to patching and replacing hardware and software without an eye on the big picture. The author's purpose for her text is to show us a method that may avoid unnecessary complexity and mystery in network design. We are given a hint about the meaning of "top-down" on page 4, where the author tells us that we will begin our design at the top (upper) layers of the ISO-OS! Network Model. The seven layers of the model are usually written in a list, numbering the top as layer seven and the bottom as layer one. lLayer INumber ISO Layer Functional Description 7 __ [Application services and programs Presentation [translation across networks [setting up and ending lconnections 6 5 |/Session 4 |[fransport guarantee delivery 3 2 Network ifind other networks Data-Link _ ||Media access and links inside la network [wiring, bit transmission, 1 [Physical _|sending and receiving network lsignals The author explains that this approach begins with questions about what the users will do on this network. We want to know, as layer 7 suggests, what applications will run on this network. We also want to know who will use those applications and what the goals are for their usage. Although the author has not really explained either approach yet, she allows that we could hitpsistevevincent.infoWNET226_2016_1.him 1841672019 CChaplor 1, Analyzing Businoss Goals and Consiraints us a bottom-up approach (which she calls "connect the dots") if our user's applications and goals are well known. The top-down approach should seem familiar to you if you have taken classes about structured approaches to creating applications or computer systems. An introduction to a structured approach appears on page 5: Use a top-down approach Model the current system (if any exists) and the new system. Collect information on data, data flows, and data processes. Learn what the users need from their processes and their data. Develop a model of how the organization works and how it can make the best use of its data. + Develop a logical mode! about what the system must do, then a physical model about how the system will do it. Logical models are based on a big picture or strategic view of what the company does. Physical models are based implementing functions with hardware and software. The creation of a logical model before the physical model supports the concept of starting at a high level and working into the details after you define the big picture The text continues its background material with a discussion of the Systems Development Life Cycle model. This model can be used to create a new system or to revise an old one. It s a cycle because it is meant to be repeated any time a change is needed or desired The author tells us on page 6 that there are four phases in the design part of the life cycle version she favors. She shows six phases in the graphic on page 7, which include two phases for implementation and monitoring. Those phases are not included in the discussion in this chapter. hitpsistevevincentinfoINET226_2016_1.him 28CChaplor 1, Analyzing Businass Goals and Consiraints 41672019 ert td Peis ts (cd N BN onice tI ines) Pa tate Perce ete) Implement tt) and test pitas Beata erect pet The four phases in the design portion of the cycle (top to bottom, clockwise) are discussed briefly: + Analyze requirements - What are the business goals for this network? What are the constraints we must include? Do we need to balance the goals against what we think we can or can't do? Does the existing network perform as desired? + Logical network design - This is about the things you can do beefore you choose hardware. What shall we pick for a logical topology? How many networks do we want? What should be our address range, and how will we name our devices? Will we use WAN links, and if so, how do the constraints limit our choice of vendors? + Physical network design - What brands, models, and actual devicees will make our network functional? Which ISP or data carrier have we selected, and how does that affect what we use to connect to them? + Test, optimize, and document - Build a prototype, write a test plan, and test the new network model. Document everything about it as a proposal for the full scale network build. Note: at this stage it it still only a plan. The new network has not yet been built. The text also presents a Cisco version of a network life cycle which condenses the logical and physical design steps above into one step. This may cause the reader to wonder whether each phase of such a project is the same length or importance as the other phases. The Cisco version separates the Test and Optimize phase in the model above into two separate phases. It also adds an eventual Retirement phase, placed in the center of their cycle wheel because it could happen at any time. All computer hitpsistevevincentinfoINET226_2016_1.him 38