Skip to end of metadata
Go to start of metadata
Practice AreaCheckpointYes/NoEvidencesHow to?
Architecture


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

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?NA
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?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?

No
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.YesHolmes API Documentation - Beijing
Release ManagementAre committed Sprint Backlog Stories been marked as "Done" in Jira board?YesHolmes Backlog
Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira?Yes

Have all findings from previous milestones been addressed?NA

DevelopmentHas the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)Yes
Guidance 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?

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)?Yes

Holmes Jenkins Page


Are all binaries available in Nexus?YesHolmes Nexus Repo
Integration and Testing

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

YesHolmes CIST Page in Jenkins
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