You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This centralized page, for all Casablanca projects, is aimed at identifying the risks as they are foreseen within the release life cycle.

A Risk that materialized becomes an Issue.

Status:

  • Identified: a risk that has been identified, but has not yet been analyzed / assessed yet 
  • Assessed: an identified risk which currently has no risk response plan 
  • Planned: an identified risk with a risk response plan
  • In-Process: a risk where the risk response is being executed 
  • Closed: a risk that occurred and is transferred to an issue or the risk was solved/avoided
  • Not occurred: a risk that was identified but that did not occur 
  • Rejected: created and kept for tracking purposes but considered not to be used yet


Risk IDProject Team or person identifying the riskIdentification DateRisk (Description and potential impact)Team or component impacted by the risk

Mitigation Plan

(Action to prevent the risk to materialize)


Contingency Plan - Response Plan

(Action in case of the risk materialized)

Probability of occurrence (probability of the risk materialized)

High/Medium/Low

Impact

High/Medium/Low

Status
1Katel346/27/2018

CII Badging - Casablanca Release Criteria is about addressing test coverage (including JS)

Therefore some projects might not pass their CII Badging.

Any Project team who has JS as part of their code and who will not have enough bandwidth

Find an alternative to the current proposal

https://lists.onap.org/g/Onap-seccom/topic/cii_badging_passing_level/22721721?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,22721721

If it is confirmed that the solution (https://lists.onap.org/g/Onap-seccom/topic/cii_badging_passing_level/22721721?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,22721721) is the right way to move forward then we believe that we should split the JS test coverage into several phases that will be implemented across multiple ONAP releases depending on each project’s bandwidth:

Phase 1 – Setup the infrastructure

Phase 2-  Analyze the SONAR test coverage and build a plan to meet JS test coverage criteria

Phase 3- Add test cases to meet the JS test coverage criteria

HighHigh

In-Process

6/27/18 update:

  • Current proposal presented to the Security Subcommittee to provide awareness
  • No labels