...
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Y |
| Architecture walkthrough to understand how each project contributes on Release Use Case. ARC to organize the walkthrough. | ||||||||
| Is there a plan to address the findings the API review? | N/A | N/A | Responded to all questions raised during the review. No leftover issues to address from the API review | |||||||||
| Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval? | Y | N/A | In the case some changes are necessary, bring the request to the TSC for review and approval. | |||||||||
Is there any changes in the scope, functionalities, deliverable, dependency, resources, API, repositories since M1 milestone? | Y | We will add PNF Registration Handler microservice for supporting PNF registration function of the 5G use case. DCAE R2 has a number of stretch goals identified at earlier milestones. Among these stretch goals, we will de-scope dcaegen2/analytics/flink due to resource availability change. | Critical point to understand is that change is inevitable, and that right timing and clear communication to the community will ease the process of accepting changes. | |||||||||
| Provide link to the API Documentation. | https://git.onap.org/dcaegen2/collectors/ves/plain/swagger_vescollector.yaml https://git.onap.org/dcaegen2/platform/deployment-handler/plain/deployment-handler-API.yaml https://git.onap.org/dcaegen2/platform/configbinding/plain/config_binding_service/swagger/swagger.yaml https://git.onap.org/dcaegen2/platform/inventory-api/plain/swagger_inventory.yaml | |||||||||||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | N | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=49&view=planning | |||||||||
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Y | |||||||||||
| Have all findings from previous milestones been addressed? | Y | |||||||||||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | N | Goal: 50% for Incubation project in Beijing | Guidance on Code Coverage and Static Code Analysis | ||||||||
| Is there any pending commit request older than 36 Business hours in Gerrit? | N | |||||||||||
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | Y | The remaining security vulnerabilities are all from 2 external dependencies: fasterxml.jackson and httpcomponent. We will try to upgrade to newer revisions that do not have security vulnerabilities if the reference is directly from DCAE code. In the case that there is no secure revision available, we will try to identify alternative. If the violation is deep in dependency chain that we cannot replace, we will identify methods to contain the thread and file the reporting template. | Ensure by M4 the Nexus-IQ report from “Jenkins CLM” shows 0 critical security vulnerability. Open the Nexus-IQ report for the details on each repo. | |||||||||
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Y | https://jenkins.onap.org/view/dcagen2/ | ||||||||||
| Are all binaries available in Nexus? | Y | Provide link to evidence | ||||||||||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | NY | The CSIT job failed in the middle due to what appears to be an error in testing scriptthe test plan for one of the tests, which caused an inf loop in testing and eventually Jenkins marks the whole job as failure due to time timed out. Reason under investigation. | |||||||||
| Has the project code successfully passed the Daily Build process? | Y | Goal is to ensure the latest project commit has not broken the Integration Daily Build |