-
Key: QFTP-33
-
Legacy Issue Number: 7815
-
Status: closed
-
Source: BAE SYSTEMS ( Mr. Kevin Dockerill)
-
Summary:
The RiskTheme suggests a grouping, but this is different to packaging. For example, we would define a theme (e.g. user input), but package risks according to a different criteria (e.g. user groups). Following this definition, it seems unnecessary to define RiskTheme as a specialisation of AbstractRisk. A RiskTheme sounds like a theme. It enables the user to categorise risks in some way. Values are held for each risk (frequency and consequence). It may thus be useful to consider having threshold values within the RiskTheme (for Frequency and Consequence). So, a 'user input' theme has a threshold 'low' so that you can run checks to see that all risks of this theme are also low.
-
Reported: QFTP 1.0b1 — Thu, 30 Sep 2004 04:00 GMT
-
Disposition: Resolved — QFTP 1.0
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
QFTP — The RiskTheme suggests a grouping, but this is different to packaging
- Key: QFTP-33
- OMG Task Force: UML Profile for QoS and FT FTF