Network Analysis, Architecture and Design 

1 2 3 4

• 1. Table of Contents

• 2. BackCover

• 3. Network Analysis, Architecture, and Design, Second Edition

• 4. Foreword

• 5. Preface

  Approach

• 6. Roadmap

  Roadmap

• 7. Acknowledgments

  answers for network analysis, architecture, and design book questions

• 8. Chapter 1: Introduction

  1.1 Objectives

• 9. 1.2 Preparation

  1.2 Preparation

• 10. 1.3 Background

  1.3 Background

• 11. 1.4 Overview of Analysis, Architecture, and Design Processes

  1.4 Overview of Analysis Architecture and Design Processes 1.4.1 Hierarchy and Interconnectivity 1.4.2 Importance of Network Analysis 1.4.3 Model for Network Analysis Architecture and Design

• 12. 1.5 A Systems Methodology

  1.5 A Systems Methodology

• 13. 1.6 System Description

  1.6 System Description

• 14. 1.7 Service Description

  1.7 Service Description

• 15. 1.8 Service Characteristics

  1.8 Service Characteristics 1.8.1 Service Levels 1.8.2 System Components and Network Services 1.8.3 Service Requests and Requirements 1.8.4 Service Offerings 1.8.5 Service Metrics

• 16. 1.9 Performance Characteristics

  1.9 Performance Characteristics 1.9.1 Capacity 1.9.2 Delay 1.9.3 RMA 1.9.4 Performance Envelopes

• 17. 1.10 Network Supportability

  1.10 Network Supportability

• 18. 1.11 Conclusion

  1.12 Exercises answers network analysis

• 19. 1.12 Exercises

  1.12 Exercises

• 20. Chapter 2: Requirements Analysis: Concepts

  2.1 Objectives

• 21. 2.2 Preparation

  2.2 Preparation

• 22. 2.3 Background

  2.3 Background 2.3.1 Requirements and Features 2.3.2 The Need for Requirements Analysis

• 23. 2.4 User Requirements

  2.4 User Requirements

• 24. 2.5 Application Requirements

  2.5 Application Requirements 2.5.1 Application Types 2.5.2 Application Groups 2.5.3 Application Locations

• 25. 2.6 Device Requirements

  2.6 Device Requirements 2.6.1 Device Types 2.6.2 Performance Characteristics 2.6.3 Device Locations

• 26. 2.7 Network Requirements

  2.7 Network Requirements 2.7.1 Existing Networks and Migration 2.7.2 Network Management and Security

• 27. 2.8 Other Requirements

  2.8 Other Requirements 2.8.1 Supplemental Performance Requirements 2.8.2 Financial Requirements 2.8.3 Enterprise Requirements

• 28. 2.9 The Requirements Specification and Map

  2.9 The Requirements Specification and Map

• 29. 2.10 Conclusion

  2.10 Conclusion

• 30. 2.11 Exercises

  Why is requirements analysis important to network architecture and design? Give three reasons. List the top 10 applications that you expect to use in your (or your customer’s) network, or that you currently use in the existing network. List the actual or estimated performance characteristics for each application and try to place them into groups. You can also try to map them to the application groups listed in Section 2.4.2. exercise solution McCabe - Network Analysis, Architecture and Design 3e Why is requirements analysis important to network architecture and design? Givethree reasons.

• 31. Chapter 3: Requirements Analysis: Process

  3.1 Objectives

• 32. 3.2 Preparation

  3.2 Preparation

• 33. 3.3 Gathering and Listing Requirements

  3.3 Gathering and Listing Requirements 3.3.1 Determining Initial Conditions 3.3.2 Setting Customer Expectations 3.3.3 Working with Users 3.3.4 Taking Performance Measurements 3.3.5 Tracking and Managing Requirements 3.3.6 Mapping Location Information

• 34. 3.4 Developing Service Metrics

  3.4 Developing Service Metrics 3.4.1 Measurement Tools 3.4.2 Where to Apply Service Metrics

• 35. 3.5 Characterizing Behavior

  3.5 Characterizing Behavior 3.5.1 Modeling and Simulation 3.5.2 User Behavior 3.5.3 Application Behavior

• 36. 3.6 Developing RMA Requirements

  3.6 Developing RMA Requirements 3.6.1 Reliability 3.6.2 Maintainability 3.6.3 Availability 3.6.4 Thresholds and Limits

• 37. 3.7 Developing Delay Requirements

  round trip delay for omline applications

• 38. 3.8 Developing Capacity Requirements

  3.8 Developing Capacity Requirements 3.8.1 Estimating Data Rates

• 39. 3.9 Developing Supplemental Performance Requirements

  3.9 Developing Supplemental Performance Requirements 3.9.1 Operational Suitability 3.9.2 Supportability 3.9.3 Confidence

• 40. 3.10 Environment-Specific Thresholds and Limits

  3.10 Environment-Specific Thresholds and Limits 3.10.1 Comparing Application Requirements

• 41. 3.11 Requirements for Predictable and Guaranteed Performance

  high performance network architecture book

• 42. 3.12 Requirements Mapping

  network requirement specification and map

• 43. 3.13 Developing the Requirements Specification

  3.13 Developing the Requirements Specification

• 44. 3.14 Conclusion

  3.14 Conclusion

• 45. 3.15 Exercises

  Consider a network project where you cannot talk to users or staff. What resources can you use to gather user, application, device, and network requirements? Briefly outline a method for gathering and deriving requirements in the absence of user/staff involvement how to make an uptime requirement of 99.999% more precise describe two ways to make an uptime requirement of 99.999% more precies Your customer is a hospital that wants to upgrade its LAN. Develop a questionnaire to gather requirements from users, hospital management, and staff. What kinds of questions would you ask to better understand their environment? describe two ways to make an uptime requirement of 99.999% more precise

• 46. Chapter 4: Flow Analysis

  4.1 Objectives

• 47. 4.2 Preparation

  4.2 Preparation

• 48. 4.3 Background

  4.3 Background

• 49. 4.4 Flows

  4.4 Flows 4.4.1 Individual and Composite Flows 4.4.2 Critical Flows

• 50. 4.5 Identifying and Developing Flows

  4.5 Identifying and Developing Flows 4.5.1 Focusing on a Particular Application 4.5.2 Developing a Profile 4.5.3 Choosing the Top N Applications

1 2 3 4