...
For usability, we should constrain the number of pulldowns and the number of requirements per pulldown to a similar order of magnitude e.g. pulldowns < 10, reqts/pulldown <20
The VNF Requirements in Ch7 as of mid August (there are some changes pending for section 7.4 and 7.5 in
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Number of Reqts
...
Naively mapping sections to pulldowns would still have (Red) sections with more than 20 reqts, and would need some further breakdown or summarization. pulldowns with 0 or 1 requirement do not make sense, and should be consolidated. This would suggest ~16 pulldowns with an addition pulldown to consolidate the 4 sections with a single reqt, and some further breakdown/ summarization of the 44 reqts in 7.3.2.1.2. Something like:
...
Num. of reqts
...
Scoring with simple counts of Met/Unmet will not be sufficient:
...
Eliminating the requirements that are inspectable in the xNF Package would reduce the number of requirements in the table above - ~30 of the 190 requirements are on the xNF or VNF Package ie ~15%
Some Analysis of candidates for VNF Badging are discussed below:
| Child pages (Children Display) |
|---|