Versions Compared

Old Version 4

changes.mady.by.user Randa Maher

Saved on

compared with

New Version Current

changes.mady.by.user Randa Maher

Saved on

Key

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

...

Practice AreaCheckpointYes/NoEvidencesHow to?
Architecture


Has the Project team reviewed the APIs with the Architecture Committee (ARC)?YesAPPC Presentationplanned for 8/22

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?TBDLink to planN/ASee Note

Note: There were no  findings coming out of the API review meeting; however, there is an item being addressed between MultiVIM and CDP-PAL around https support that needs to be resolved. CDP-PAL uses https, MultiVIM currently does not support it - both teams investigating to determine which solution would be most feasible in the short time we have.

Update 8-22-17: Per CDP-PAL, they can support http, so at this stage, we have a plan forward

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?

YesIf Yes, please a link to the evidence of these changes.

Two key items have increased the scope from what was understood at M1:

  1. SDNC upgrade to Carbon ODL version: APPC-158
  2. Integration with MultiVIM was originally anticipated to be a test-only activity for APPC with the impacts being mostly on CDP-PAL side; however, changes in URL format and AAI interface require development on APPC. APPC-123
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.Yes

R3 API Documents


Release ManagementAre committed Sprint Backlog Stories been marked as "Done" in Jira board?YesProvide Link to Project backlog

APPC JIRA Board

Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira?Yes
APPC JIRA Board
Have all findings from previous milestones been addressed?In-ProgressYesProvide link to JIRA findings
DevelopmentHas the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)No, work In-PogressGoal: 30-50% for Incubation projectGuidance 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)?YesProvide link to evidenceAPPC Gerrit
Are all binaries available in Nexus?YesProvide link to evidenceAPPC Snapshot on Nexus
Integration and Testing

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

No. In ProgressYesProvide link to evidence

APPC-104


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