The page is intended to summarize all the requirements for El-Alto Release.
These requirements will be prioritized by the TSC to realistically fit within the El-Alto Release Timeline.
The Release Scope will be finalized at the Release Kick-Off on xxx
TSC Prioritization (Ranking)
- RANK #0 – Special GO - fully covered by involved companies
- RANK #1 – GO “Must Have”
- RANK #2 - GO “Continuity of previous releases”
- RANK #3 – GO if PTLs are OK since the impacted applications are less “stretched” i.e. CLAMP, Policy, DCAE etc.
- RANK #4 – NO GO – Mostly new requirements/features/projects
Non-Functional Requirements
M1 Scorecard:
- Green: The non-functional requirement will be fully implemented and tested
- Yellow: The non-functional requirement will be partially implemented. It is possible to identify capabilities for this non-functional requirement can be tested (phasing approach).
- Red: The non-functional requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy
| Non Functional Requirement | Owner | Project Impacted | Priority | M1 Scorecard | TSC M1 Approval | M3 Scorecard | M3 TSC Approval | M4 Scorecard | TSC M4 Approval | Link(s) to HLD/LLD if any | 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, what are gaps/ project (people/FTEs; HLD/LLD; etc) |
|---|
| Document as You Code | | ALL |
|
|
|
|
|
|
|
|
|
|
|
|
| | Security by Design | Security Subcommittee | ALL |
|
|
|
|
|
|
| Update to the latest oParent version and update of milestones checklists. |
|
|
|
|
| | Fixing penetration tests OJSI related issues | Security Subcommittee | All |
|
|
|
|
|
|
| Solve vulnerabilities identified with penetration tests. |
|
|
|
|
| | Perform upgrades of vulnerable components | Security Subcommittee | All |
|
|
|
|
|
|
| Agree on the target version and assess the level of impact, coordinate upgrade between dependent projects. |
|
|
|
|
| | Execute replacement of vulnerable components | Security Subcommittee | All |
|
|
|
|
|
|
| example: json-> gson replacement done by CLAMP. |
|
|
|
|
| | Move Helm Chart (OOM) at project level | | OOM + ALL |
|
|
|
|
|
|
|
|
|
|
|
|
| | Additional functional tests delivered per project on OOM | | |
|
|
|
|
|
|
| | Infrastructure capacity |
|
|
|
| Inject Auto-generated Configs and Certs realtime | | AAF + ALL |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.
El-Alto POC / Experimentation
POC Definition - (In Progress)
| Type | Requirement | Owner | Project Impacted | Link(s) to HLD/LLD if any | Dependency (from/to) another project(s) | T-Shirt Size (XS, S, M, L, XL) | Project's Impact: Test Only (TO), Code (C) | Company Engagement | Notes | M4 Status |
|---|
| Non-Functional Requirement | CI/CD Magic word "run-helm-deploy" in queue at LF, Orange and Log team Move to POC | |
OOM + Integration (Infrastructure) | OOM Gating |
|
|
|
|
|
| | Non-Functional Requirement | Multi-Architecture Support | | Components used by vFW | -Healthcheck -vFW |
|
|
|
|
|
| | Non-functional requirements | S3P - Provide Upgrade Capabilities PH1
| | OOM supported by A&AI, SO, SDC and SDNCWaiting for inputs |
|
|
|
|
|
|
|
|
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.