Versions Compared

Key

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

...

Info
titleUsage
  1. Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
  2. Fill out the Yes/No column
  3. Provide link to evidence (when necessary)
Practice AreaCheckpointYes/NoEvidencesHow to?
Architecture


Has the Project team reviewed the APIs with the Architecture Committee (ARC)?
Review is scheduled on Aug 29th
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?
Once review is done, we will update
NANo issues were found.
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.
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
NoIf 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.YesAAF API
Release ManagementAre committed Sprint Backlog Stories been marked as "Done" in Jira board?Yes
Provide Link to Project backlog
https://jira.onap.org/secure/RapidBoard.jspa?rapidView=69&view=planning&selectedIssue=AAF-37&versions=visible&epics=visible
Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira?Yeshttps://jira.onap.org/secure/RapidBoard.jspa?rapidView=69&view=planning&selectedIssue=AAF-37&versions=visible&epics=visible
Have all findings from previous milestones been addressed?
Jenkins Jobs, Releasing Artifacts to Nexus, Sonar and Implementing automated functional test case is pending
Sonar for 2 components are pending. One functional test case has to be automated in JenkinsProvide link to JIRA findings
DevelopmentHas the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)
In Progress
Yes

https://sonar.onap.org/overview?id=46017

inno - 43.1%

https://sonar.onap.org/overview?id=54083

Authz - 32.6%

https://sonar.onap.org/overview?id=45529

Cadi - 32.2%

Goal: 30-50% for Incubation project

Guidance on Code Coverage and Static Code Analysis

Tools: Sonar

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

Are all the Jenkins jobs successfully passed ( Merge-Jobs)?
In Progress
Done

https://jenkins.onap.org/view/aaf/job/aaf-authz-master-merge-java/

https://jenkins.onap.org/view/aaf/job/aaf-cadi-master-merge-java/

https://jenkins.onap.org/view/aaf/job/aaf-inno-master-merge-java/

Provide link to evidence


Are all binaries available in Nexus?
No
Yeshttps://nexus.onap.org/index.html#view-repositories;snapshots~browsestorage~/org/onap/aaf
Provide link to evidence

Integration and Testing

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

No
Yes

Completed 100% functional test cases

https://jenkins.onap.org/view/aaf/job/aaf-master-csit-aafapi/

Provide link to evidence


Has the project code successfully passed the Daily Build process?
In Progress
Yeshttps://jenkins.onap.org/view/aaf/Goal is to ensure the latest project commit has not broken the Integration Daily Build