Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Practice AreaCheckpointYes/NoEvidencesHow to?

Has the Project team reviewed the APIs with the Architecture Committee (ARC)?Yes

Reviewed on 3/6/18

APPC M3 Arch Review v2.pptx

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?N/ANo findingsThe 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?YesNAIn 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?

YesTraffic Migration meeting notesNo

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.YesAPPC LCM API Guide
Release ManagementAre committed Sprint Backlog Stories been marked as "Done" in Jira board?YesAPPC Board
Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira?YesAPPC Board
Have all findings from previous milestones been addressed?N/ANo previous findings
DevelopmentHas the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)In-ProgressGoal: 50% for Incubation project in BeijingGuidance on Code Coverage and Static Code Analysis

Tools: Sonar

Is there any pending commit request older than 36 Business hours in Gerrit?No

Do you have a plan to address by M4 the Critical  vulnerabilities in the third party libraries used within your project?



Not all issues will be possible to resolve in Beijing. We will document those in the security template.

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)?YesProvide link to evidence
Are all binaries available in Nexus?YesProvide link to evidence
Integration and Testing

Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins?

Has the project code successfully passed the Daily Build process?One jjb being investigatedWe are currently having issues withGoal is to ensure the latest project commit has not broken the Integration Daily Build