Capability (C026):— representing_condition Date: 2010/11/28 21:16:39
Revision: 1.17
CoverContentsIntro.Overview Info. modelTemplatesCapabilitiesRef. dataIssues

Issue raised against: representing_condition

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 against representing_condition_evaluated 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: THX-1 by Tom Hendrix (04-05-13) minor_technical issue
Resolution: Accept. Status: open

I find the text in the figure graphics hard to read, that is, the names of entities that are instantiated. Figure 2 is the least legible. Is there a way to make it bigger or a better font?

Open issue Issue: THX-3 by Tom Hendrix (04-08-02) minor_technical issue
Resolution: Accept. Status: open

Need an example that shows the instance diagram for a two level nested condition, one logical, one numeric conparison, such as (temp > 20 ) AND (alt > 5000 ft). Ref RBN-1. Should make it clear how to generalize to n levels. Or should say there are only two levels possible. NOTE I looked at C026 but cant decipher the figure 2. From the model, it looks like a condition_parameter must be a Condition_relationship, thsu two more conditions. Then at some point you get to the bottom

OTHER issues

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

This capability needs a template to allow the assignment of a condition to an item and a related instance of condition_parameter to be assigned a parameter item.
Comment: (Leif Gyllstrom 2007-05-02)
Added template assigning_condition.

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

This capability needs reference data for the condition, the condition_assignment, and the condition_parameter.
Comment: (Leif Gyllstrom 2007-05-02)
Yes, and so is the case !

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

This capability needs to reference the use of a document to capture condition statements, and associated reference data.
Comment: (Leif Gyllstrom 2007-05-02)
There might be additional characterizations that include the assignment of documents. Raised an issue GYL-1 against the AP239 long form.

Closed issue Issue: TJT-5 by Tim Turner (06-04-15) minor_technical issue
Resolution: Accept. Status: closed

It is not clear where the actual condition text/reasons are to be recorded - either in the justification.description attribute, or through the use of assigning_descriptors..
Comment: (Leif Gyllstrom 2007-05-02)
This is described in the templates assigning_condition and assigning_condition_text_based respectively.

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

Figure 2 I believe shows a condition_parameter that has an Assigned_property as parameter. This is not possible because in the model only Condition_relationship can be a parameter.
Comment: (Leif Gyllstrom 2007-05-02)

The Condition module only defines that the condition_parameter_item SELECT contains the Condition_relationship ENTITY. However, the AP239 long form includes the following:

TYPE condition_parameter_item = SELECT (Activity, Activity_method, Activity_property, Activity_property_representation, Approval, Approval_assignment, Assigned_property, Calendar_date, Certification_assignment, Classification_assignment, Condition_relationship, Contract_assignment, Date_or_date_time_assignment, Date_time, Document_assignment, Hierarchical_interface_connection, Identification_assignment, Independent_property_representation, Interface_connection, Interface_connector_occurrence, Interface_definition_connection, Managed_resource, Organization_or_person_in_organization_assignment, Product , Product_as_individual, Product_category_assignment, Product_concept, Product_definition_element_relationship, Product_version, Product_view_definition, Property_representation, Representation, Required_resource, Resource_as_realized, Resource_as_realized_relationship, Resource_event, Resource_property, Resource_property_representation, State, State_definition, View_definition_relationship); END_TYPE; (* declared in: Condition_arm *)