...
Risk | Prob/Impact | Mitigation |
---|---|---|
|
|
|
|
|
Comment : Decoupling the System Ready certification from the SOAFEE requirements renders this risk irrelevant. |
Timely availability of target hardware in sufficient quantities for the team to work with. | Low / High |
|
If the AVA platform is not working in an acceptable/suitable manner we may need to allocate changes for an alternative device under test hardware | Low/Medium |
|
Receiving timely information from SoC and peripheral vendors is at times difficult, which may impede productivity. | Low/Medium | Linaro and Arm will work with the relevant vendors to mitigate the impact on the project deliverables and key dates. |
Receiving timely information from SoC and peripheral vendors is at times difficult, which may impede productivity. | Low/Medium | Linaro and Arm will work with the relevant vendors to mitigate the impact on the project deliverables and key dates. |
|
|
|
|
|
|
Some features will require development from scratch (e.g. secure orchestration of containers). | Low/Medium | An investigative phase will be added to identify key deliverables and risks associated with such tasks and continued engagement with the Arm LoB will ensure continued alignment and minimize wasted work |
Lack of EWAOL contribution model will result in carrying patches that will require rebasing when new EWAOL releases are made which will cause additional maintenance burden on the team causing a delay in meeting other engineering deliverables. | Low/High | Have a contribution model/agreement in place by the start of the project
|