...
M3 Release Architecture Milestone overview is available in wikiin wiki.
| 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 Providelinkto evidence (when necessary)
|
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|
| 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.| Yes |
|
|
| 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.| yes |
| no findings |
| Does the team clearly understand that no changes in the API |
definition is allowed | definitionisallowed 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. | | Yes |
| SDC has new repositories for the DCAE-D and ONAP-UI.
this is our stretch goal to deliver them in Beijing. |
| Providelinkto the API Documentation. | SDC API |
Provide link to the API Documentation. |
|
|
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? |
Provide Link to Project backlog| Yes |
|
|
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes |
|
|
| Have all findings from previous milestones been addressed? |
Provide link to JIRA findings| Yes |
|
|
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to |
artifacts available | artifactsavailable in Sonar) | No | Goal: 30-50% for Incubation project | work in |
BeijingGuidance on Code Coverage and Static Code Analysis Tools: Sonar | 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.Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | | No |
|
|
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? |
Provide link to evidenceProvide link to evidence| Yes |
|
|
Integration and Testing
| Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? |
Provide link to evidence| N/A |
|
|
| 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
