deploying and managing ip over wdm networks - Index of

98 Deploying and Managing IP over WDM Networks
Moreover, each requirement is prioritized (different levels of priorities are
defined), classified as mandatory (for requirements that must be implemented)
or desirable (for requirements that provide some value added to the system but
do not need to be implemented for the system unless we want a fully functional
system).
The following sections describe briefly the groups of requirements. Under
another point of view, the requirements are split in two main categories:
1. Functional requirements, describing the requirements of the external
actors of the WINMAN solution with respect to configuration, fault,
and performance management functionality;
2. Nonfunctional requirements, such as interoperability, implementation,
and integration specific requirements among others.
As described in Section 6.2.3, the requirements identification is based on
the TMF TOM approach. This means that the requirements are also categorized
per functionality belonging to business processes defined in TOM.
In this section, the WINMAN solution requirements are presented in
detail according to the TOM business processes. We start giving an overview
on the WINMAN data repositories, and we end with a set of testing
requirements.
6.3.1.1 Data Repositories
The WINMAN solution shall consist of three types of databases used for network
configuration purposes at different levels and another two types for fault
and performance data:
• Network inventory or physical database. The network inventory database
is managed by the network inventory management (NIM) subsystem
(according to the TOM processes) and maintains the physical inventory
of the network resources. The database repository resembles a hierarchical
structure, representing the equipment in the network. Minimally,
the following attributes are found for each network resource of the network
inventory database: cards, ports, fiber conduits, and location.
• Logical database. The logical database is managed by the network provisioning
(NP) system. The logical database maintains the logical inventory
of the network resources and consists of entries representing logical
paths, which are supported by the physical resources of the network.
Each path is specified by an entry in the database having at least the following
attributes: protection of the path, available bandwidth, and network
quality expressed in terms of delay and delay variation.