1. Requirements Definition
Chapter – 4
Requirements Definition

2. Outline User Requirements Items to be inventoried
Requirement categories
Traffic sizing
Traffic characteristics
Time and Delay consideration
Network Delay elements
Connectivity types
Availability and Reliability
Service Aspects
Budget constraints

3. User requirements
There are two basic steps that is to be fulfilled by the designer, that is - Performance and Documentation of an inventory of current network and requirements & documentation of the expectation of new network.
Cisco recommends 12 items is to be inventoried in the customers current network but we are taking only 7 items

4. The items to be inventoried
Inventory steps Description 1 Existing Application. Document current application across the network. 2 Existing network Document current protocol. protocol across the network.

5. Inventory steps Description 3 Network topology and Create a high level Addressing. topology map of the current network, including all major segments, routers, bridges, switches and other device 4 Potential bottlenecks Monitoring use of in current network. bandwidth and traffic patterns

6. Inventory steps Description 5 Existing network Measure network Performance. Performance between, various hosts and servers. Understand how application performance is driven by latency verses bandwidth. 6 Existing network Same as network topology use and addressing

7. Inventory steps Description 7 Status of existing Document revision levels, routers. Memory use, CPU use and buffer drops, determine if there is a processing limitation under load

8. Inventory steps Description 8 Existing Network Management system Document all network management tools being used and which platform they run.

9. Inventory steps Description 9 Over all health Of existing network Measure the perceived existing health of the network , based on specific criteria.

10. Requirement categories
Requirement are classified into three different categories, they are as follows
Business Requirements
Security Requirements
Manageability Requirements

11. Business Requirements
Business requirements includes the following items.
Timeline
Staffing
Training
Budgets and
Project approval

12. Security Requirements
Security requirements are very critical to most business, it includes the following.
Who can access the network?
Each resource.
What can be accessed and when?
Determine the appropriate security level for the resources and network you are trying to protect.

13. Manageability Requirements
Manageability Requirements can vary across the board from simple PING program documentation that each device in the network is alive to full blown network management system.

14. Performance Requirements
Performance Requirements cover bandwidth requirements and QoS ( lost packets, jitter, and latency) . Applications along with users drive performance requirements, but the final driver is budget justification .

15. Traffic sizing
Traffic comes in many sizes in many shapes and sizes. Which is having many protocols and formats. It travels in many types and patterns . It requires special methods of processing and handling.
The traffic is measured in two common formats
1. Units of measure and
2. Packaging of these units
1. Units of measure means, bits, bytes message block.
2.Packaging of these units means, file, packets, frames or cell.

16. Traffic characteristics
The traffic characteristics depends upon four network variables they are, delay, loss, jitter and throughput.
Characteristics Definition
Delay Measures the time for a packet to travel
between two network devices. PING
measures round -trip delay between two
network devices. Delay in networks might
not be symmetrical so the delay from A to
B might be different than the delay from
B to A.
Jitter Measures the difference in one way delay over
time for different packets sent between two
network points.

17. Traffic characteristics
Characteristics Definition
Lost Packet Measures the number of packets deleted or percentage dropped in the network due to any error
or congestion over the total number of
packets transmitted.
Burstiness Measures how infrequent a source send
traffic. Burstiness is defined as the ratio of
peak to average rate of traffic based on specific
sampling period for the data.
Throughput Measures how much data is required to be transmitted in a specified time frame.
Ex. bits/sec or packets/sec.

18. Protocol
The full suit of user protocols must be defined for both existing and planned applications.
This include all protocols serving all seven layers of OSI reference model
Which protocol is used on both side the application side and the network side.
This is because the network devices like routers, switches or bridges heavily depends on protocols.

19. Time and Delay considerations
Time and Delay considerations is most important aspects of data communications networking and How applications and protocols manage delay.
Response time : It is defined as the round trip delay from source to destination, or the time required it takes a user to send a request until he or she receives a reply.

20. Time and Delay considerations
There are three elements of delay.
Media access delay
Serialization delay
Network delay
They are explained in the picture on next slide.

21. Network Delay Elements

22. Network Delay Elements
Media Access Delay : It means to take access the media of or LAN. The time will be very small under normal conditions but under load and congestion, the delay could be factor. .
Serialization Delay : The time it takes to output onto a serial link.
Network Delay: The time it takes for a packet frame / cell to travel across the service provider's network. Network delay components can also include the software / hardware, switching / routing delays.

23. Connectivity
User connectivity will be defined by existing or available connectivity methods. For, example some remote locations might have only dial, xDSL, or cable access.

24. User-to-network
The following points are to be examined for user-to- network connectivity.
What is minimum speed required for connectivity?
What types of devices will be connected?
What type of data rates can they transmit?
What is distance involved between user equipment and data communication equipment?

25. What are the vendors software and hardware vendor specifics?
What mode of addressing is required for access?
What are protocols required for basic connectivity?

26. Network-to-network connectivity
Once the user-to-network interface has been defined, any network-to-network connectivity requirements for new or existing networks can also be defined
To what extent is everywhere connectivity required?
Will the connectivity be homogenous or heterogeneous?
Will private, public or hybrid network access be required?
What type of technology will be used for network interfaces and internetworking?
Some examples are:
Multipoint or point-to-point.
Multiplexing or concentration
Switched (Circuit, Packet or Cell)
Bridge or routed
Hybrid.

27. Service aspects
Service aspects such as network management, billing, security, user support and disaster recovery are important topic with range of standard and proprietary solutions.
Network designer must understand the capabilities offered by each technology and protocol.

28. Budget constraints It means the limitations of budget:
The designer must design the network within a given budget, accommodating the largest number of users and applications within the available budget. This becomes a balance between cost, capabilities and connectivity.
A network becomes cost justified if it improves operating efficiency, helps users meet corporate objectives.
There are two things who controls the network budget, the network manager and the users, but most often it is the network manager.
When user have budgetary control the question is, what is placed on the network?
When network manager has control and the user is a customer, the user tries to place everything possible over the network.

29. Videos