...
| Practice Area | Checkpoint | Yes/No | Evidences | Comment | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | In Progress | In Progress | In progress, request sent on 3/6/18. | |||||||
| Is there a plan to address the findings the API review? | TBC | TBCLink to plan | The plan could be as simple as a Jira issue to track the implementation of findings or a documented plan within the wiki. | ||||||||
| Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval? | Yes | NA | 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? | If Yes, please a link to the evidence of these changes. | 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. | No | NA. | All planned functionalities are still scheduled, at this time we are not aware of any change in plan/scope for clamp or its dependencies. | ||||||
| Provide link to the API Documentation. | Yes | http://onap.readthedocs.io/en/latest/submodules/clamp.git/docs/index.html | We don't expose api but uses api's from other project (policy, dcae and sdc). A story exists in Beijing to document CLAMP healthcheck API using SWAGGER, meanwhile API Documentation is provided in readthedocsProvide link to the API Documentation. | ||||||||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | YesProvide Link to Project backlog | Backlog | Yes | |||||||
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | Backlog | Yes | ||||||||
| Have all findings from previous milestones been addressed? | Yes | No specific findings | |||||||||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | Goal: 50% for Incubation project in Beijing Guidance on Code Coverage and Static Code AnalysisTools: Sonar | CLAMP is now above the 50% target. | |||||||
| Is there any pending commit request older than 36 Business hours in Gerrit? | No | ||||||||||
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | YesEnsure 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 |
| Currently only 5 Critical remains, an effort has already been done to remove most of them. | ||||||||
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | YesProvide link to evidence | Jenkins project tab | |||||||||
| Are all binaries available in Nexus? | Yes | Provide link to evidenceNexus project folder | SNAPSHOT Binaries at this stage. | ||||||||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | YesProvide link to evidence | Link to CLAMP CSIT | 29 out of 41 tests have been reworked and passed. | |||||||
| Has the project code successfully passed the Daily Build process? | Yes | Jenkins project tab | Goal is to ensure the latest project commit has not broken the Integration Daily Build . |