...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | 0 | 1 | Run performance basic test, depends on performance criteria availability for level 1 |
|
| Stability | 0 | 1 | Participate to Stability runs Level 1 |
|
| Resiliency | 1 | 1 |
| |
| Security | 0 | 1 | Reach CII passing badge, increasing test coverage as remaining item |
|
| Scalability | 0 | 1 | Reach Level 1 single site horizontal scaling |
|
| Manageability | 1 | 1 | Using LOG4J common framework for logging |
|
| Usability | 1 | 1 | API documentation provided |
|
...
API Incoming Dependencies
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
API Name
API Description
API Definition Date
API Delivery date
API Definition link (i.e.swagger)
...
None None None None None API Outgoing Dependencies
API this project is delivering to other projects.
API Name
API Description
API Definition Date
API Delivery date
API Definition link (i.e.swagger)
...
Provisining API for creating,deleting and listing the administrative objects Aug 02 2017 March 08 2018 AAF API Admin API API for the admin access Aug 02 2017 March 08 2018 AAF API CADI CADI ( CODE ACCESS DATA IDENTITY) Aug 02 2017 March 08 2018 AAF API Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).Name
Description
Version
...
Docker Container engine 1.12 Cassandra database container 2.1.16 In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
Testing and Integration Plans
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.AAF will invest in CSIT tests to allow further integration testing, AAF already provided some tests as part of R1.
Gaps
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.Gaps identified
Impact
...
Testing/Integration limited testing of final product Known Defects and Issues
Provide a link toward the list of all known project bugs.
...
Risks
No known risks so far.
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
This section may be used to document internal milestones that the team agreed on.
Also, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, provide these agreements and dates in this section.
It is not expected to have a detailed project plan.
Date
Project
Deliverable
To fill out AAF AAF - CertMan,oAuth Documentation, Training
http://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/index.html
...