Capability (C048):— representing_condition_evaluated Date: 2012/05/23 17:48:01
Revision: 1.31
CoverContentsIntro.Overview Info. modelCapabilities.Ref. dataIssues

Issue raised against: representing_condition_evaluated

OTHER issues

Open issue Issue: TJT-1 by Tim Turner (06-04-15) major_technical issue
Resolution: Accept. Status: open

The state of this capability is in question. Most of the reference data previously defined for use with the logical expressions defined within has been removed, which makes the the use of both the logical expressions and the reference data questionable. Similarly, the issue raised in RBN-1 implies that the logic used is also suspect in this capability and should be regarded as a major technical issue against the capability - with greater detail about the inadequacies.

Open issue Issue: TJT-2 by Tim Turner (06-04-15) editorial issue
Resolution: Accept. Status: open

This capability needs a template to allow the assignment of a condition_evaluation to an item, to relate it to a condition and to allow a related instance of condition_evaluation_parameter to be assigned a parameter item.

Open issue Issue: TJT-3 by Tim Turner (06-04-15) minor_technical issue
Resolution: Accept. Status: open

This capability needs reference data for the condition_evaluation, the condition_evaluation_assignment, and the condition_evaluation_parameter.

Open issue Issue: TJT-4 by Tim Turner (06-04-15) minor_technical issue
Resolution: Accept. Status: open

This capability needs to reference the use of a document to capture condition_evaluation statements, and associated reference data.

Open issue Issue: RBN-1 by Rob Bodington (03-11-04) minor_technical issue
Resolution: Accept. Status: open

I am not sure that the logical expressions will work.

OTHER issues

Closed issue Issue: MRI-1 by Tom Hendrix (04-08-02) minor_technical issue
Resolution: Accept. Status: closed

Raise section Evaluated condition characterization to top level. Rename "Characterization"
Comment: (Rob Bodington 05-03-08)
Corrected

Closed issue Issue: MRI-2 by Tom Hendrix (04-08-02) minor_technical issue
Resolution: Accept. Status: closed

Create somewhere subsection called Identification.
Comment: (Rob Bodington 05-03-08)
Corrected

Closed issue Issue: MRI-3 by Tom Hendrix (04-08-02) minor_technical issue
Resolution: Accept. Status: closed

In section Representing an evaluated condition, the result is either true or false (or unknown?). No need to distinguish the types. I dont mind the two Figures 2, 3, especially since the ines in representing_condition are unreadible. But the text should just say that conditions and parameters are described in the related dex, and then talk about relating the evaluation to the condition parameter(s).

Closed issue Issue: MRI-4 by Tom Hendrix (04-08-02) minor_technical issue
Resolution: Accept. Status: closed

Figure 3 caption should say Example of evaluation of a comparison expression
Comment: (Mike Ward 2005-02-12)
Fixed.

Closed issue Issue: MRI-5 by Tom Hendrix (04-08-02) minor_technical issue
Resolution: Accept. Status: closed

Figure 2 caption should say Example of evaluation of a text based expression.
Comment: (Mike Ward 2005-02-12)
Fixed.

Closed issue Issue: MRI-6 by Tom Hendrix (04-08-02) minor_technical issue
Resolution: Accept. Status: closed

Reference data that describes a condition should be left to the related capability representing_condition. In this capability just have evaluation reference data.
Comment: (Rob Bodington 05-03-08)
Corrected