representing_properties_textually

Capability (C080):— representing_properties_textually

Date: 2007/06/22 12:22:11
Revision: 1.39

Cover Contents Intro.Overview Info. model Templates Capabilities.Issues

Issue raised against: representing_properties_textually

GENERAL issues

Issue: TJT-1 by Tim Turner (04-03-22) minor_technical issue
Resolution: Accept. Status: closed

There are no entities, types or functions defined for this capability (in the usage section). This means that DEX1, for example, cannot use this capability while the entities to be used are missing/undefined.

Comment: (Ian Bailey 2004-03-29)
Patience is a virtue.

Issue: THX-1 by Tom Hendrix (04-05-10) minor_technical issue
Resolution: Accept. Status: closed

*Representing Properties* should be *Representing Properties Textually*

Comment: (Ian Bailey 2004-07-29)
Done

Issue: THX-2 by Tom Hendrix (04-05-10) minor_technical issue
Resolution: Accept. Status: closed

rep item text includes *shall be less than * The rep item has the requirement semantic in its text, which means there are three ways to represent *required* : classification, qualification, and embedded descriptive text. Suggest using one of first two , consistently with other capabilities, and just putting the value in the rep item, thus *less than 5 kg.*

Comment: (Ian Bailey 2004-07-29)
All this is doing is capturing the text produced by a requirements management tool. Most requirements start with "the thing shall...". This is the way we handle requirement text, and it would be inappropriate to expect pre-processors to change the requirements text produced by systems engineers.

Comment: (Mike Ward 2005-01-05)
Issue closed for reasons provided in IBY's comment of 2004-07-29.

Issue: THX-3 by Tom Hendrix (04-05-10) minor_technical issue
Resolution: Accept. Status: closed

Figure 7 missing. Need to commit and check the reference

Comment: (Ian Bailey 2004-07-29)
This seems to be OK now.

Issue: THX-4 by Tom Hendrix (04-05-10) minor_technical issue
Resolution: Accept. Status: closed

Missing some ul tags. I fixed.

Issue: THX-5 by Tom Hendrix (04-05-10) minor_technical issue
Resolution: Accept. Status: closed

*EXAMPLE A required property may be represented with a text string; * The laptop shall weigh less than 5kg.* Suggest explaining in the vicinity of figure 6 that the rep item does not include all this text, and does not identify the item. See also THX-2

Comment: (Tom Hendrix 04-05-10)
EXAMPLE The laptop shall be grey in colour. Suggest an illustration that shows both colour and mass as two separate instances of assigned_property.

Comment: (Ian Bailey 2004-07-29)
Made a small change. Again, this is valid text, as it would have come from a requirements tool. There may not be a laptop product anywhere that this is assigned to - in fact this is often the case with requirements specs.

Issue: NN-1 by Nigel Newling (05-11-17) minor_technical issue
Resolution: Accept. Status: closed

Is the mandatory recording of the date and time when a property was assigned a value necessary? This is not always known or relevant. It would require a lot of extra entity instances to represent an unknown value. Same applies to person and organization characterisation.

Comment: (Peter Bergström 2006-04-18)
I agree, there is no need to make things overly complicated and force people and applications to 'invent' data. I suggest a change of wording to 'strongly recommended' or such. The new templates have them optional, currently.

Comment: (Peter Bergström 2006-05-27)
Date and time, as well as organization and person, have been made optional.

Issue: NN-2 by Nigel Newling (05-11-17) minor_technical issue
Resolution: Accept. Status: closed

Make it clear that the name of the property maps to Assigned_property.name and the value of the property maps to String_representation_item.string_value.

Comment: (Peter Bergstrom 2006-04-18)
I think this is clear from the new templates.

Issue: NN-3 by Nigel Newling (05-11-17) minor_technical issue
Resolution: Accept. Status: closed

Instantiation diagrams need to reflect the developments in reference data and how classification is handled i.e. apply general rule that id and name not populated but contained in External_class. Indeed, new template notation could be used in the diagrams.

Comment: (Peter Bergström 2006-05-29)
fixed.

Issue: PBM-1 by Peter Bergstrom (2006-04-28) major_technical issue
Resolution: Accept. Status: closed

Templates for the following capabilities must be harmonized:
C076: assigning_product_properties
C077: assigning_process_properties
C078: assigning_resource_properties
C080: representing_properties_textually
C079: representing_properties_numerically
C084: representing_property_value_ranges
C056: representing_evolution_of_property_values.
If possible, the document property capability C087: assigning_document_properties should also be harmonized with other properties.
In order to minimize the number of total templates for properties, the following structures of templates has been proposed:
1. assignment of the property (product, process, or resource)
2. association of a representation with an assigned property (i.e. associate a text property with a product property)
3. representation of a value (text, numerical, or a numerical range)
Number 1 and 2 above would exist in three different 'flavours', for products, processes (activities) and resources. Number 3 would be generic, and applicable to all.
If the current division of properties would be used, as in the capability C079: representing_properties_numerically where number 2 and 3 above are collapsed in one template, we would need agreat number of templates to represent all different types of numerical ranges in C084: representing_property_value_ranges, and we would not re-use the value representations at all.
See templates in capability C080: representing_properties_textually for an example of the propsed solution.

Comment: (Peter Bergström 2006-05-27)
Harmonization done. Only document properties have not been harmonized yet, but they should be inline with what has been done with other properties.