Practice Area | CheckpointYes/No | List by each relevant project | Evidences | How to? | |||||
Architecture | Has the Use case/functional requirement’s corresponding APIs were included to all relevant projects reviews with the Architecture Committee (ARC)? |
|
| 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? |
|
|
| ||||||
Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval? |
|
| In the case some changes are necessary, bring the request to the TSC for review and approval. | ||||||
List of not supported/wrongly supported etc. APIs along with the corresponding project name |
| Links to the corresponding project’s information | In case some parts of use case/ functional requirement implementation are broken, this will raise the flag | ||||||
Link to the API Documentation |
|
| This field is optional, will be filled in in case use case/functional requirements owner believes it can bring more clarity | ||||||
Additional information |
|
| This field is optional, will be filled in in case use case/functional requirements owner believes it can bring more clarity | Is there any changes in the scope, functionalities, deliverable, dependency, resources, API, repositories since M1 milestone? |
|
| Provide link to the API Documentation. |
|
|