Page History

...

Provides a well-structured organization of visual design & testing tools, templates and catalogs to model and create resources, and services. The output of the SDC is a set of models which drives the orchestration.
SDC in ONAP WIKI

Full and comprehensive VNF/Software Application(VF), and service design, which includes, not limited to:
- Onboarding VNF/VF
- Workflow design
  - lifecycle flows
  - change management flows
- Close loop design
- policy design
- Service function chaining Design
- VNF/VF License Design
- VF/VNF deployment flavor design
Collaborative design
- versioning
- Design Lifecycle
VNF/VF/SERVICE testing and certification
Distribution to ONAP
- TOSCA parser
External API- for VNF/VF and service design
Image management
Describe the functionality to be provided by the project. Please provide the full intended scope of the project; not just what is intended for the project's first release.
Specify any interface/API specification proposed,
Identity a list of features and functionality will be developed.
Identify what is in or out of scope. During the development phase, it helps reduce discussion.

Scope

Architecture Alignment

How the existing functionality is going to align in ONAP
- How it will integrate with:
  - VNF-SDK
  - ICE (VNF certification)
  - Modeling
What kind of dependency other projects will have with SDC, e.g SO modeling?
How will multi VIM project influence on the input/ output we have for SDC?
How to align to standards like ETSI VNF packaging?

How does this project fit into the rest of the ONAP Architecture?
- Please Include architecture diagram if possible
- What other ONAP projects does this project depend on?
How does this align with external standards/specifications?
- APIs/Interfaces
- Information/data models
Are there dependencies with other open source projects?
- APIs/Interfaces
- Integration Testing
- etc.

...

Space shortcuts