| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | YES | ARC Review | 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? | NA | Link 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? | NO | 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. | |
| Provide link to the API Documentation. | YES | R2 APIs that are carried forward to R3: https://onap.readthedocs.io/en/beijing/submodules/dcaegen2.git/docs/sections/apis/inventory.html https://onap.readthedocs.io/en/beijing/submodules/dcaegen2.git/docs/sections/apis/dcaecdap.html R3 APIs that are new or updated: https://git.onap.org/dcaegen2/services/prh/tree/swagger.yaml https://git.onap.org/dcaegen2/collectors/ves/tree/swagger_vescollector_1.3.1.yaml https://git.onap.org/dcaegen2/platform/configbinding/tree/app/app/swagger.yaml | ||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | YES | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=49&sprint=677 | |
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | YES | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=49&view=planning | ||
| Have all findings from previous milestones been addressed? | NA | |||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Guidance on Code Coverage and Static Code Analysis | ||
| Is there any pending commit request older than 36 Business hours in Gerrit? | YES | They are DRAFTs, or the ones with negative reviews and waiting for contributor response. | ||
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | YES | https://jenkins.onap.org/view/dcagen2/ | ||
| Are all binaries available in Nexus? | YesYES | |||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | YesYES | https://jenkins.onap.org/view/dcagen2/job/dcaegen2-master-verify-csit-prh-testsuites/ (4 cases) https://jenkins.onap.org/view/dcagen2/job/dcaegen2-master-verify-csit-testsuites/ (12 cases) | |
| Has the project code successfully passed the Daily Build process? | YES | Goal is to ensure the latest project commit has not broken the Integration Daily Build |
Page Comparison
General
Content
Integrations