Network Analysis, Architecture & Design, Second Edition
This book works through the processes of analysis, architecture, and design step by step, giving network designers a solid resource for making good design decisions.
TABLE OF CONTENTS Network Analysis, Architecture & Design, Second Edition
3.3: Gathering and Listing Requirements
3.3 Gathering and Listing Requirements
Service requirements are gathered and developed with initial conditions on the architecture and design, with input from users, administration, and management and then refined by applying our experience and knowledge about the analysis process. Some guidelines for quantifying requirements and developing thresholds and limits are given in this chapter, but first you must communicate with the users to gather their requirements, so we begin with a discussion of the initial conditions on the network.
3.3.1 Determining Initial Conditions
Initial conditions are the basis for the start of the analysis process. They help determine what you are designing toward, as well as the reasons for the architecture and design. Initial conditions consist of the type of network project, the scope of the architecture and design, initial architecture/design goals, and any outside forces acting on the network. Understanding these initial conditions is important because they will influence the network architecture and design and will often act as constraints on the architecture/design. The initial conditions could also be considered the current state of the existing network's architecture and design.
Before starting the process of gathering and analyzing requirements, you will likely have some notion of the initial conditions for the network project you are undertaking. For example, you will probably know the type of network project and the scope of the project. Some examples of these are as follows:
| Type of Network Project | Scope of Network Project |
|---|---|
|
Copyright Elsevier Science (USA) 2003 under license agreement with Books24x7
