...
| 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? |
|---|
| Architecture
| Has the Project team reviewed the APIs with the Architecture Committee (ARC)? |
Review is scheduled for Tuesday Aug - 22nd. | Architecture walkthrough to understand how each project contributes on Release Use Case. ARC to organize the walkthrough.| Yes |
|
|
| Is there a plan to address the findings the API review? |
TBD. Review is scheduled for Tuesday Aug - 22nd. | 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.| I\ |
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. | | Yes |
| SDC has new repositories for the DCAE-D and ONAP-UI.
this is our stretch goal to deliver them in Beijing |
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. | SDC API |
|
|
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes |
Provide Link to Project backlog |
|
|
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes |
|
|
| Have all findings from previous milestones been addressed? |
Under invistigation | Provide link to JIRA findings | | Yes |
|
|
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | No | Goal: 30-50% for Incubation project |
Guidance on Code Coverage and Static Code Analysis Tools: Sonar | Provide link to evidenceProvide link to evidence | Provide link to evidence
|
|
Integration and Testing
| Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? |
No | Goal is to ensure the latest project commit has not broken the Integration Daily Build | N/A |
|
|
| Has the project code successfully passed the Daily Build process? |
|
