0% found this document useful (0 votes)
64 views9 pages

Network Requirements Analysis Guide

Network Requirement Analysis
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
64 views9 pages

Network Requirements Analysis Guide

Network Requirement Analysis
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Module 3: Network Requirement

Analysis
The Requirements Analysis Process

• Gather and List Requirements


• Develop Service Metrics

• Characterize Behavior

• Develop Requirements

• Map & Validate Requirements

Gathering and Listing Network Requirements

The Core Principle:

• "The first step is to determine the initial conditions on the network."

• "network" now includes cloud virtual networks and the internet.

Type of Network Project:

• Classic Types: New Network, Modification, Upgrade, Analysis.

• Modern Types: Cloud Migration, SASE Implementation, Zero Trust Deployment, SD-WAN
Overhaul, 5G FWA Integration.

Defining the Scope:

• Classic: Network Size, Number of Sites, Distance Between Sites.

• Modern: Number of Cloud Regions, SaaS Applications, Remote Users, IoT Devices.
Common Project Goals:

• Classic Goals: Improve performance, support new users/apps, increase security.

• Modern Goals: Enable Secure Hybrid Work, Optimize Cloud Costs, Achieve Compliance,
Automate Operations, Improve Sustainability.

Common Project Constraints:

• Timeless Constraints: Funding, Time, Organizational politics.

• Modern Constraints: Cloud Sprawl, Cybersecurity Skill Shortages, Integration Complexity,


Compliance Mandates (GDPR, CCPA).

Interacting with Users & Managing Expectations

The Principle:
• "Setting customer expectation is one important aspect of requirements gathering."

• Clear communication will never go out of style.

Classic Techniques:

• Surveys, phone calls, and face-to-face meetings are still invaluable for qualitative
feedback.

• Problem statements are still the best way to formally describe issues.

Modern Techniques:

• Digital Experience Monitoring (DEM): Passive, real-time analysis of user experience


without surveys.

• Virtual Whiteboard Sessions: Using tools like Miro or Microsoft Whiteboard for remote
collaboration.

• Data-Driven Insights: Analyzing aggregated data from tools like Microsoft Viva
Insights to understand real work patterns.
Performance Measurement & Requirement Management

The Principle:

• "Documents should be living documents, updated on a regular basis."

• Agile, iterative documentation is key.

Classic Measurement:

• Then: Use tools like Wireshark (successor to Ethereal) to capture traffic and measure
peak loads.

• Now: We still use Wireshark for deep-dive analysis! The skill is still critical.

Modern Measurement:

• Shift in Focus: From network speed to user experience.


• Key Metrics: Application response time, SaaS availability, user satisfaction scores.

• Modern Tools Platforms: Observability Suites like Datadog, Dynatrace, and Cloud-Native
Tools (Azure Monitor, AWS CloudWatch) provide a holistic view.

Managing Requirements:

• Then: A shared document on a network drive.

• Now: Collaborative Platforms like Azure DevOps, Jira, or Confluence to integrate


requirements with project management and DevOps workflows.

Developing Service Requirements: RMA

The Fundamentals:

The mathematical definitions of Reliability, Maintainability, and Availability have not


changed. They are engineering constants.

• Reliability: Measured by Mean Time Between Failures (MTBF).

• Maintainability: Measured by Mean Time To Repair (MTTR).

• Availability: A = MTBF / (MTBF + MTTR)

Modern Application:

• Beyond "Uptime": Availability now includes the performance of internet paths and cloud
services. Your network can be up, but if Microsoft 365 is slow, the user experience is poor.
• New Metrics: Mean Time to Detect (MTTD) is now as important as MTTR, highlighting
the need for excellent monitoring.

• SLOs are Key: Requirements are now formalized as Service Level Objectives (SLOs) with
cloud providers and internal teams.

Developing Service Requirements: Capacity & Delay

The Metrics:

The types of requirements remain the same: we need to define performance thresholds.

• Capacity: Peak Data Rate, Sustained Data Rate, Minimum Data Rate.

• Delay: End-to-end, Round-trip, Delay Variation (Jitter).

Modern Drivers:

• Capacity: Driven by video conferencing (Teams, Zoom), large file transfers, and datasets
for AI/ML.

• Delay (Latency): Critical for real-time [Link]/UC (Teams): < 150ms RTTCloud
Gaming / AR/VR: < 50ms RTTLow-Latency Trading: < 10ms RTT

• Jitter: The enemy of real-time voice and video quality.


Characterizing Behavior

The Principle:

• "It means representing how users and applications use the network."

• This is the heart of good design.

Then vs. Now:

• User Behavior (Then): Users at desks, 9-to-5.

• User Behavior (Now): Hybrid Work: Users anywhere, anytime, on any device. Traffic
patterns are global and asynchronous.

• Application Behavior (Then): Traffic was mostly "north-south" (client to server).

• Application Behavior (Now): Traffic is "east-west" (between cloud services) and to SaaS
applications. Understanding this flow is critical.

• New Behavior: IoT devices sending small, constant packets and AI workloads creating
massive, bursty data transfers.
Measurement Tools

The Stalwarts:

Some tools are forever essential for any network professional.

• ping & traceroute/pathping: The first step in any troubleshooting.

• Wireshark: The ultimate protocol analyzer.

• iperf3: The standard for bandwidth performance testing.

The Modern Arsenal:

• Observability Platforms: Datadog, Dynatrace

Common questions

Powered by AI

Service Level Objectives (SLOs) serve as formalized benchmarks for performance expectations both with cloud providers and internal teams, reflecting the importance of predefined service quality standards. They help align service delivery with user expectations and business goals, supporting continuous monitoring and improvement of service quality in an increasingly complex and cloud-centric environment .

Modern user behavior patterns, characterized by hybrid work with users located anywhere on any device and generating global and asynchronous traffic, necessitate network designs that accommodate more complex, dynamic conditions compared to the static, office-bound user behavior of the past. Past designs focused on predictable 'north-south' client-server traffic, while modern designs must consider 'east-west' traffic between cloud services and the Internet, including small constant packets from IoT devices and massive data transfers from AI workloads .

The types of network projects have evolved from classic projects like new network deployment, modification, and upgrade, to modern projects such as cloud migrations, SASE implementations, and SD-WAN overhauls. This evolution necessitates advanced requirement analysis techniques that incorporate emerging technologies, scalability considerations, and security frameworks to meet the demands of diverse and complex network environments .

Maintaining agile, iterative documentation in network performance management is important because it allows for continuous updates and refinements in response to changing conditions and requirements. This approach ensures that all stakeholders have access to the most current information, promoting transparency and flexibility, which enhances decision-making and responsiveness to emerging challenges and needs .

The focus of performance measurement has shifted from traditional metrics like network speed and capacity to user experience metrics such as application response time, SaaS availability, and user satisfaction scores. This shift aligns with the importance of cloud services in overall performance assessment, where tools like Datadog and Dynatrace are used for a holistic view, indicating a transition from isolated metrics to integrated user-centered performance evaluations .

Characterizing user and application behavior is crucial in modern network design as it ensures the network can support dynamic and diverse traffic patterns such as asynchronous global access, east-west traffic, and IoT data transfers. This understanding informs decisions about resource allocation, traffic management, and capacity planning, ultimately shaping a network that is both robust and optimized for current and future demands .

Digital experience monitoring (DEM) tools enhance the requirements gathering process by providing passive, real-time analysis of user experiences, eliminating the need for traditional surveys and manual data collection. They offer granular insights into actual user interactions and network performance, enabling teams to anticipate issues and proactively refine network requirements based on empirical data rather than assumptions .

Modern tools such as Azure DevOps and Jira integrate requirements with project management and DevOps workflows, providing collaborative platforms for requirement management. Unlike past practices that relied on shared documents restricted to network drives, these tools enable dynamic, real-time updates and visibility, facilitating more efficient and agile management of requirements throughout the project's lifecycle .

Modern network project constraints include cloud sprawl, cybersecurity skill shortages, integration complexity, and compliance mandates such as GDPR and CCPA, focusing on challenges associated with modern technologies and regulatory environments. Timeless constraints, on the other hand, are more universal and perennial, such as funding limitations, time restrictions, and organizational politics .

The core components of developing service requirements in network projects include defining metrics for reliability, maintainability, and availability, such as Mean Time Between Failures (MTBF) and Mean Time To Repair (MTTR). Additionally, new metrics like Mean Time to Detect (MTTD) are now important. These metrics help establish clear performance standards and expectations, ensuring that networks are designed to meet predefined service quality and uptime goals .

You might also like