The following items are expected to be completed for the project to Pass the M3 API Freeze Milestone.
|Practice Area||Checkpoint||Yes/No||Evidences||How to?|
|Architecture||Has the Project team reviewed the APIs with the Architecture Committee (ARC)?||Yes||AAI R2 Architecture Review - complete 3/6|
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/A||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?
|Yes||Some new microservices, mostly related to data integrity and data validation in the graph db, have been deferred to Casablanca. This does not change any agreed scope or APIs with other ONAP systems.||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.||AAI v13 API|
|Release Management||Are committed Sprint Backlog Stories been marked as "Done" in Jira board?||Yes||AAI Jira Board|
|Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira?||No|
|Have all findings from previous milestones been addressed?||Yes||Provide link to JIRA findings|
|Development||Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)||No||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?||No|
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project?
We are in the process of migrating off AJSC to Spring Boot - Our first microservice has been converted and (aai/resources) has 0 security and 0 policy violations. The other microservices will be similarly converted. This should clear the overwhelming majority of the current exceptions on the other repos.
|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||AAI in Jenkins|
|Are all binaries available in Nexus?||Yes||AAI in Nexus|
|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?||Yes||Goal is to ensure the latest project commit has not broken the Integration Daily Build|