Control Loop Sub Committee Dublin Release Planning
Functional Requirements
Functional Requirements | Owner | Projects Impacted for Dublin | Link(s) to High Level Design (HLD) /Low Level Design (LLD) (if any) | Priority (from SP perspective)? | 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
Ease of creating analytic components and on-boarding DCAE micro services | @Vijay Kumar @Adam Krysiak
Control Loop Sub Committee | SDC (DCAE-DS) CLAMP DCAE POLICY | Ease of creating analytic components and on-boarding DCAE micro services | ||||||||
vFirewall Use Case Upgrade | @Marco Platania @Pamela Dragosh Control Loop Sub Committee | CLAMP POLICY APPC | |||||||||
Model Driven Control Loop Design | @Gervais-Martial Ngueko @Alex Shatov @Igor Sklyar @Pamela Dragosh | SDC DCAE Policy CLAMP |