...
| Practice Area | Checkpoint | Yes/No | Evidences | Note | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Y | Presented during ARC meeting on 08/22 10AM EDT | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Is there a plan to address the findings the API review? | Y | Discussion during ARC call. Decision: waiting for integration team decision on ONAP deployment plan. | The most concerning issue brought up was integration with MSB and OOM. The action items will be very different if Integration deploys ONAP using Heat template v.s. using OOM. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval? | Y | NA | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Is there any changes in the scope, functionalities, deliverable, dependency, resources, API, repositories since M1 milestone? | N | If Yes, please a link to the evidence of these changes. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Provide link to the API Documentation. | DCAE API Documentation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Y | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Y | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Have all findings from previous milestones been addressed? | Y | Provide link to JIRA findings | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Y | Goal: 30-50% for Incubation project | Three Java projects (dcaegen2-analytics-tca, dcaegen2-collectors-ves, dcaegen2-platform-inventory-api) coverage rates are show on SONARQUBE server. Additional projects coverages are verified by running coverage.py or language local tool on local dev machines: Python projects
32% | | dcaegen2/
, Other languages
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Is there any pending commit request older than 36 Business hours in Gerrit? | N | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Y | Provide link to evidence | Because most of DCAEGEN2 codebase is NOT Java/Mvn, integration with ONAP CICD process is still in progress. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are all binaries available in Nexus? | Y | Provide link to evidence | Because most of DCAEGEN2 codebase is NOT Java/Mvn, integration with ONAP CICD process is still in progress. Awaiting for LF to setup Pypi server. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Y | https://jenkins.onap.org/view/CSIT/job/dcaegen2-master-verify-csit-testsuites/ https://jenkins.onap.org/view/CSIT/job/dcaegen2-master-csit-testsuites/ | 12/12 test cases passed | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Has the project code successfully passed the Daily Build process? | Y | Because most of DCAEGEN2 codebase is NOT Java/Mvn, integration with ONAP CICD process is still in progress. |
