Based on timeplan of modeling subcommittee, high level requirements need to be finished by M0/M1, around Oct. 2019 (because M0 in Frankfurt milestone hasn't been decided yet)
Below High Level Requirements have been agreed by modeling subcommitee with code commitment promise to Frankfurt release, modeling subcommittee request related to projects to approve those related submission.
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Mapping to M1 requirement | Owner |
|---|---|---|---|---|---|---|---|---|---|
There are other 4 categories of high level requirement,
- 1) Will be documented only and included in the Dublin Frankfurt release, but no implementation promised.
- 2) Documentation after implemented, or implemented but not in the release
- 3) Lower Priority
- 4) Experimental
The first category is that those requirement will be documented only in Dublin in Frankfurt release
the second category will document the current implementation in those projects.
...
1) Will be documented only and included in the Frankfurt release
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Mapping to M1 requirement | Owner |
|---|
2
...
...
N/A
related to DM SOL001 progress
...
...
...
...
...
...
impact R4 DM?
...
...
NSD - the ONAP internal data model should be able to reflect ETSI SOL001 NSD provided for onboarding
...
SDC, SO, VFC
...
)
...
...
...
2) Documentation after implemented, or implemented but not in the release
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Mapping to M1 requirement | Owner |
|---|
Service
Kevin ScaggsN/AHighguochuyi
To document the onboarding NS IM as supported by the usecase
Former user (Deleted)
To document the allotted resource IM as implemented by SDC
N/A
Below tables are not downgrade, but casablanca won't make it
3) Lower Priority:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
|---|
Service
Common
Policy
create policy IM, reflect current policy project implementation
N/A
N/A
Infrastructure
4) Experimental:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
|---|
Common
License
create super classes for current models
Per discussion in Paris, requirements can be based on:
...