Requirement

Analysis
The Process
Objective
learn about gathering and managing user, application, device and
network requirements
learn about determining the variables to measure and how to make
measurement
learn about developing performance requirement for capacity,delay
and RMA
learn about general and environment specific threshold and limist and
how to determine them
learn about mapping requirements to geographic locations to prepare
for traffic flow analysis
Requirement Analysis Process
Gather and List Requirement

Develop Service Metrics

Characterize Behavior

Develop Requirements Map Requirements

Gathering and Listing Requirements
1.Determining Initial Conditions

Type of Network Project

New Network
Modification of an existing network
Analysis of network problems
Outsourcing
Consolidation
Upgrade
Gathering and Listing Requirements
Scope of Network Project
Network Size
Number of sites
Distance between sites
Gathering and Listing Requirements
Initial Architecture - Design Goal
Upgrade technology/vendor
Improve performance to part or all of network
Support new users, applications or devices
Solve perceived problems within system
Increase security
Support a new capability in system
Common constraint
Funding limitation
working with various organization within one
organization
Rules and regulations
Time schedule
Technical constraints
Setting customer expectation
consist of:
a rapid, initial evaluation of the problem, and
estimating resources and schedule

Not intended to be an in-depth estimate, but

rather a quick evaluation to catch obvious
problems
Working with users
to understand user behavior pattern and
environment
to help them understand what you are trying
to accomplish
Example
developing a survey to email, FAX, or mail to users
following up on the survey with one-on-one telephone calls or
conference calls
Following up calls with face-to-face meetings with selected
individuals or groups
Whiteboard sessions to elicit ideas from users
Spending time with users while they work to better understand
what they do and how they do it
=> key trade-off: amount of time spent versus the quality of
information gathered
Taking Performance Measurements
Tracking and Managing Requirements

Example
NR - 1.0-102.
All (technology A 3/7/2007) network equipment
shall be capable of software (or firmware
4/1/2000) (deleted 4/17/2007) based upgrades
to allow it to support changes to high speed
(any 5/20/2007) data service features and
functions.
Another Example
Mapping Location Information
Developing Service Metrics
Analyze these requirements in order to
distinguish between various performance
levels in the network.

Measurement Tools
ping, tcpdump, patchar, traceroute, etc
Using Ping and IP Packet Loss as Service Metrics for
RMA
Characterizing Behavior
Representing how users and applications use
the network, in order to develop and
understand their requirements

Type:
User behavior; Application behavior; Network
behavior
Developing RMA Requirement
Reliability
Maintanability
Availability

A = (MTBCF)/(MTCBF + MTTR) or
A = (MTBF)/(MTBF + MTTR)