The following items are expected to be completed for the use case to Pass the M3 API Freeze Milestone.
M3 Release Architecture Milestone overview is available in wiki.
| 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 | Provide link to the API Documentation.| Checkpoint | List by each relevant project | Evidences | How to? |
|---|
ArchitectureHas the Use case/functional requirement’s corresponding APIs been included in 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? | 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? | 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? | If 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. | | List of not supported/wrongly supported etc. APIs along with the corresponding project name |
|
| In case some parts of use case/functional requirement implementation are broken, this will raise the flag
|
| Link to the API Documentation. |
|
| New APIs | | Interface | API Doc | JIRA |
|---|
| BSS ↔ External API | External API Doc New API: BBS Portal - Ext API Designv1.pptx | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | EXTAPI-98 |
|---|
|
| SO → SDN-C Policy → SDN-C | GenericResource API Doc | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SO-1578 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-695 |
|---|
|
| | DCAE RESTCONF Collector ← Domain Specific SDN M&C | dcaegen2/collectors/restconf | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | DCAEGEN2-1055 |
|---|
|
|
See interface description in BBS Broadband Service Use Case (Dublin)#FullSystemContextbbs-system-context |
|
| Additional information |
|
| This field is optional, will be filled in in case use case/functional requirements owner believes it can bring more clarity |