Functional Requirements
Functional Requirements | Owner | Projects Impacted for CasablancaDublin | Link(s) to High Level Design (HLD) /Low Level Design (LLD) (if any) | Priority
| Dependency (from/to) another project(s) | T-Shirt Size (XS, S, M, L, XL)* | Project's Impact: Test Only (TO), Code (C) | Committed (C)/Partially Committed (P) or not (N) per Impacted projects | If Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc) | Company Engagement | Notes | |||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Defining and Modeling Control Loop for LCM Operations | Volunteer? Control Loop Sub Committee | Control Loop for LCM Operations | Event based Common API for Control Loop Operations | Control Loop Sub Committee | Policy CLAMP SO APPCEase of creating analytic components and on-boarding DCAE micro services |
Control Loop Sub Committee | SDC (DCAE-DS) CLAMP DCAE POLICY | Ease of creating analytic components and on-boarding DCAE micro services | ||||||||
Volunteer?vFirewall Use Case Upgrade | SDC (DCAE-DS) CLAMP DCAEPOLICYPOLICY APPC | vFirewall Use Case Upgrade | Volunteer? Control Loop Sub Committee | |||||||||||||
CLAMP POLICY APPCModel Driven Control Loop Design | SDC DCAE Policy CLAMP | Model driven Control Loop Design |