15.12.2012 Views

deploying and managing ip over wdm networks - Index of

deploying and managing ip over wdm networks - Index of

deploying and managing ip over wdm networks - Index of

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

102 Deploying <strong>and</strong> Managing IP <strong>over</strong> WDM Networks<br />

6.3.2 Nonfunctional Requirements<br />

The most important nonfunctional requirements are the following:<br />

• The WINMAN design <strong>and</strong> implementation shall be based on specific<br />

st<strong>and</strong>ards, so as to be able to interoperate with other systems <strong>over</strong> welldefined<br />

interfaces.<br />

• The WINMAN solution should be tested in real conditions before<br />

being put into operation.<br />

Interactions between WINMAN components shall be minimized in order<br />

to minimize the b<strong>and</strong>width required by the system.<br />

6.4 WINMAN UCs<br />

After the requirements capture, the next step in defining the system’s architecture<br />

consists <strong>of</strong> the identification <strong>and</strong> descr<strong>ip</strong>tion <strong>of</strong> appropriate UCs that illustrate<br />

the basic functionality <strong>of</strong> the target system. The architecture can only be<br />

fully defined when the MSCs <strong>and</strong> class diagrams are defined. Appropriate terminology<br />

has been used for building the UCs. Relevant references include (but are<br />

not limited to) [2–6].<br />

6.4.1 Identification <strong>and</strong> Classification <strong>of</strong> UCs<br />

Table 6.1 depicts the names <strong>and</strong> allocation <strong>of</strong> UCs into appropriate categories.<br />

The horizontal classification <strong>of</strong> UCs relates to the functional grouping <strong>of</strong> UCs<br />

<strong>and</strong> is compliant to [1] in terms <strong>of</strong> the terminology used. However, the policies<br />

provision <strong>and</strong> scheduler groups <strong>of</strong> UCs are WINMAN specific. The vertical<br />

classification <strong>of</strong> UCs is according to the level <strong>of</strong> abstraction <strong>and</strong> related context<br />

<strong>and</strong> modularity <strong>of</strong> the UCs.<br />

An identifier is allocated to each UC (in parenthesis). The scheme adopted<br />

is XYZ, where X denotes the horizontal classification (functional grouping), Y<br />

denotes the vertical classification (level), <strong>and</strong> Z is a sequential number.<br />

6.4.2 UCs Overview<br />

This section presents an <strong>over</strong>view <strong>of</strong> all identified UCs. Critical aspects regarding<br />

their context are briefly discussed, while UCs interrelations are depicted in<br />

UML diagrams, according to the previous classification. Due to the nature <strong>of</strong><br />

interactions, some UCs appears in mult<strong>ip</strong>le diagrams. A short descr<strong>ip</strong>tion <strong>of</strong> the<br />

goal <strong>and</strong> context <strong>of</strong> each UC is also provided.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!