opnvf_testbed_infrastructure
Differences
This shows you the differences between two versions of the page.
| — |
opnvf_testbed_infrastructure [2014/11/06 04:53] (current) Trevor Cooper created |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ==== Project Name: ==== | ||
| + | |||
| + | * Proposed name for the project: ''project-name'' | ||
| + | * Proposed name for the repository: ''repo-name'' | ||
| + | * Project Categories: ''(Documentation, Requirements, Integration & Testing, Collaborative Development)'' | ||
| + | * | ||
| + | ==== Project description: ==== | ||
| + | * Provide high level description of intended project and OPNFV use case and benefit, if needed. | ||
| + | * Include any architecture diagrams or specifications, reference to OPNFV requirements list. | ||
| + | |||
| + | ==== Scope: ==== | ||
| + | |||
| + | * Describe the problem being solved by project | ||
| + | * Specify any interface/API specification proposed, | ||
| + | * Specify testing and integration: | ||
| + | * Debugging and Tracing | ||
| + | * Unit/Integration Test plans | ||
| + | * Client tools developed for status shows etc. | ||
| + | * Identity a list of features and functionality will be developed. | ||
| + | * Identify what is in or out of scope. So during the development phase, it helps reduce discussion. | ||
| + | * Describe how the project is extensible in future | ||
| + | |||
| + | ==== Testability: ''(optional, Project Categories: Integration & Testing)'' ==== | ||
| + | |||
| + | * Specify testing and integration like interoperability, scalability, high availablity | ||
| + | * What QA and test resources will be available? | ||
| + | |||
| + | ==== Documentation: ''(optional, Project Categories: Documention)'' ==== | ||
| + | |||
| + | * API Docs | ||
| + | * Functional block description | ||
| + | |||
| + | ==== Dependencies: ==== | ||
| + | |||
| + | * Identify similar projects is underway or being proposed in OPNFV or upstream project | ||
| + | * Identify any open source upstream projects and release timeline. | ||
| + | * Identify any specific development be staged with respect to the upstream project and releases. | ||
| + | * Are there any external fora or standard development organization dependencies. If possible, list and informative and normative reference specifications. | ||
| + | * If project is an integration and test, identify hardware dependency. | ||
| + | |||
| + | ==== Committers and Contributors: ==== | ||
| + | |||
| + | * Name of and affiliation of the maintainer | ||
| + | * Names and affiliations of the committers | ||
| + | * Any other contributors | ||
| + | |||
| + | ==== Planned deliverables ==== | ||
| + | |||
| + | * Described the project release package as OPNFV or open source upstream projects. | ||
| + | * If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables. | ||
| + | |||
| + | ==== Proposed Release Schedule: ==== | ||
| + | |||
| + | * When is the first release planned? | ||
| + | * Will this align with the current release cadence | ||
opnvf_testbed_infrastructure.txt ยท Last modified: 2014/11/06 04:53 by Trevor Cooper
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
