...
Info |
---|
|
- Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
- Fill out the Yes/No column
- Provide link to evidence (when necessary)
|
Practice Area | Checkpoint | Yes/No | Evidences | How to? |
---|
Architecture
| Has the Project team reviewed the APIs with the Architecture Committee (ARC)? |
Review is scheduled on Aug 29thYes |
| 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 | 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? | 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? |
NOJenkins Jobs, Releasing Artifacts to Nexus, Sonar and Implementing automated functional test case is pendingSonar for 2 components are pending. One functional test case has to be automated in Jenkins | Provide link to JIRA findings |
|
Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) |
In Progress | Goal: 30-50% for Incubation projectIn Progress | Provide link to evidence |
|
Are all binaries available in Nexus? |
No | Provide link to evidence |
|
Integration and Testing
| Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? |
No | Provide link to evidence |
|
Has the project code successfully passed the Daily Build process? |
In Progress