...
M3 Release Architecture Milestone overview is available in wiki.
Arch review 20180814 - editing this page this week
| Info | ||
|---|---|---|
| ||
|
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Yes | 20180814 Pomba Casablanca Architecture Alignment | 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? | Yes | 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 (Some content may slip to Dublin) | 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. | ||||||||||||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | As completed |
| |||||||||
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | As completedYes | |||||||||||
| Have all findings from previous milestones been addressed?No findings | N/A | Provide link to JIRA findings | ||||||||||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes (except one component sitting at 49.3) | Goal: 50% for Incubation project in Beijing
| Guidance on Code Coverage and Static Code Analysis | ||||||||
| Is there any pending commit request older than 36 Business hours in Gerrit? | TBDNo | |||||||||||
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | Yes |
| 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. | |||||||||
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | TBDYes | Provide link to evidence | ||||||||||
| Are all binaries available in Nexus? | As completedYes | Provide link to evidence | ||||||||||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Yes | Provide link to evidence
| |||||||||
| 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 |