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: Modeling
Need Identification:
Identified Need | Description | Driver | Dependencies | Project fit |
| Informational and Data Models | How are info/data models split? Infrastructure and topology modeling needs. | |||
| Configuration Models | ||||
| Service Infrastructure Models | ||||
| Service/Resource Models | ||||
| Is there a need to address BPMN/TOSCA | There is a need to model business processes and a need to define datacenter automation processes. | |||
| TOSCA Parsers | Which TOSCA parsers should be used/adopted ? | |||
| Translators between TOSCA to YANG? and Tosca and Heat |
Project proposals.
[repeat for each project. Note: This is not a complete project proposal skeleton, only sufficient enough for this discussion]
Project 1:
Project Name:
- Information and Data Modeling
Project Description
- Creation of Information models
- Creation of Data models
Scope:
- How do we split information and data models?
Infrastructure layer and service layer modeling
- Northbound/Southbound API models
Other:
- Identify baseline code (if any)
Project 2:
Project Name:
- Declarative and Imperative Processing (BPMN - TOSCA interworking)
Project Description
- Workflow (BPMN) and TOSCA interworking
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 3:
Project Name:
- Tooling: Parser
Project Description
- Identify the tools needed for modeling
Scope:
- Tosca Parsers.
- YANG VNF Parsers.
- If anything is out of scope, not it down
Other:
- Identify baseline code (if any)
Project 4:
Project Name:
- Tooling: Model Translators
Project Description
- There are some translator tools which translate among tosca, YANG, HOT
Scope:
- Translator between Heat and Tosca
- Translator between Tosca and Yang for some subset
Other:
- Identify baseline code (if any)