...
| Info |
|---|
|
- Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
- Fill out the Yes/No column
- Provide link to evidence (when necessary)
|
| Practice Area | Checkpoint | Yes/No | Evidences |
|---|
How to?| Note |
|---|
| Architecture
| Has the Project team reviewed the APIs with the Architecture Committee (ARC)? |
Architecture walkthrough to understand how each project contributes on Release Use Case. ARC to organize the walkthrough. | Y | Presented during ARC meeting on 08/22 10AM EDT |
|
| Is there a plan to address the findings the API review? |
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 | 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 |
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? | N | 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 Tools: Sonar| changes. |
|
| Provide link to the API Documentation. | DCAE API Documentation |
|
|
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? |
| Provide Link to Project backlog |
|
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? |
|
|
|
| Have all findings from previous milestones been addressed? |
| Provide link to JIRA findings |
|
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | N | Goal: 30-50% for Incubation project |
Guidance on Code Coverage and Static Code Analysis| Because most of DCAEGEN2 codebase is NOT Java/Mvn, integration with SONAR is still in progress.
|
| Is there any pending commit request older than 36 Business hours in Gerrit? | N |
|
|
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? |
| Provide link to evidence | Because most of DCAEGEN2 codebase is NOT Java/Mvn, integration with ONAP CICI process is still in progress. |
| Are all binaries available in Nexus? | N | Provide link to evidence | Because most of DCAEGEN2 codebase is NOT Java/Mvn, integration with ONAP CICI process is still in progress. Awaiting LF to setup Pypi server. |
Integration and Testing
| Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? |
| Provide link to evidence |
|
| Has the project code successfully passed the Daily Build process? |
|
| [Goal is to ensure the latest project commit has not broken the Integration Daily Build ] |