Functional Requirements
| Functional Requirements | Owner | Projects Impacted for Dublin | 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Event based Common API for Control Loop Operations | Control Loop Sub Committee | Policy CLAMP SO APPC | Event based Common Notification messaging format for Control Loop Operations | ||||||||
| Self Serve Control Loops - continuation from Dublin | Control Loop Sub Committee | SDC Policy CLAMP DCAE | Self Serve Control Loops | ||||||||
All Control Loop Policy Models should be TOSCA Compliant Operations, Guard Policies | Pamela Dragosh Control Loop Sub Committee | Policy CLAMP | TOSCA Compliant Policy Models | ||||||||
| PNF support in Control Loops | Control Loop Sub Committee | Policy CLAMP DCAE | PNF support in Control Loops | ||||||||
| PEP (Policy Enforcement Point) registration with Policy for updates on Decision Policies | Policy Framework | Policy DCAE | PEP Registration with Policy | ||||||||
CLAMP would provide arbitrary blueprints to DCAE instead of SDC. SDC flow would change to distribute a generic flow artifact. ? Possible for CLAMP artifact in a CSAR? | SDC CLAMP DCAE | Metadata Driven Control Loops |
