Purpose
This template is to be used for the “Parallel Deep Dive Sessions to Align with architecture / Use cases” at the may ONAP developers event
Instructions.
The purpose of each section is to translate the use cases and functional architecture into specific identified needs for the components, and to identify potential projects to be proposed. There are three parts to this exercise:
- Identify needs based on the use case and architecture on this module, and potential dependencies on other modules or external artifacts.
- Group these into projects. Consider that coding, documentation, and testing is required. Include an initial scope for the project.
- If time, mapping the needs into the projects.
The need identification table has the following columns
- Identified need: <slogan for the identified need>
- Brief need description: <a few sentences describing the need>
- Driver:<Related use case or architecture change, if any>
- Dependencies:<identify dependencies on other modules or artifacts (e.g. other onap module, models, …)
- Project: <If time, after the projects are identified, suggest in which project the need would best fit>
Time keeping suggestion: The exercise time is 45 minutes. A good practice would be to split into 20 minutes on need identification and 20 minutes on project proposals.
Exercise output.
ONAP Meeting Session name: <insert onap module name>
Need Identification:
Identified Need | Description | Driver | Dependencies | Project fit |
| multiple VNF Guidelines documents contributed | multiple existent documents | ONAP release 1 aligned | 1 | |
| Refining VNF Guidelines to VNF test cases for certification/verification | certification/ verification required tests | ONAP VNF Certification process | 1 | |
| VNF Lifecycle | State Transitions | 1 | ||
| VNF Package lifecycle | how to handle updates to VNFs, updates to VNF Package version, VNF packaging use cases | changes happens | 1 | |
| Common VNF Packaging format | Beyond format this should include business, technical and operational life cycle information elements artifacts related to other ONAP projects e.g. policy, DCAE) operatonal boundaries , VNF benchmarks, digital signatures, attestations | align with ETSI & OASIS as needed | 1 | |
| VNF SDK & tooling to support onboarding | 1 | |||
reference VNFS as examples | 1 |
Project proposals.
[repeat for each project. Note: This is not a complete project proposal skeleton, only sufficient enough for this discussion]
Project 1: VNF Guidelines & SDK
Project Name:
- Provide a brief project name.
Project Description
- Provide a high level description of the project
Scope:
- Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionality.
- Note of any particular deliverables to highlight.
- If anything is out of scope, not it down
Other:
- Identify baseline code (if any)
Project 2:
Project Name:
- Provide a brief project name.
Project Description
- Provide a high level description of the project
Scope:
- Quickly identify scope, consider: documentation, APIs, models, testing, integration, functionality.
- Note of any particular deliverables to highlight.
- If anything is out of scope, not it down
Other:
- Identify baseline code (if any)