issues on properties

[Peter Bergström <peter.bergstrom@eurostep.com>]

I have added the following issue against capabilities representing_properties_textually,  representing_properties_numerically, representing_property_value_ranges, and representing_evolution_of_property_values:

 

    <issue id="PBM-1" type="general" status="open" category="major_technical" by="Peter Bergstrom" date="2006-04-28">

        <description>

Templates for the following capabilities must be harmonized:

<br/><capability_ref linkend="assigning_product_properties"/>

<br/><capability_ref linkend="assigning_process_properties"/>

<br/><capability_ref linkend="assigning_resource_properties"/>

<br/><capability_ref linkend="representing_properties_textually"/>

<br/><capability_ref linkend="representing_properties_numerically"/>

<br/><capability_ref linkend="representing_property_value_ranges"/>

<br/><capability_ref linkend="representing_evolution_of_property_values"/>.

<br/>If possible, the document property capability <capability_ref linkend="assigning_document_properties"/> should also be harmonized with other properties.

<br/>In order to minimize the number of total templates for properties, the following structures of templates has been proposed:

<br/>1. assignment of the property (product, process, or resource)

<br/>2. association of a representation with an assigned property (i.e. associate a text property with a product property)

<br/>3. representation of a value (text, numerical, or a numerical range)

<br/>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.

<br/>If the current division of properties would be used, as in the capability <capability_ref linkend="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 <capability_ref linkend="representing_property_value_ranges"/>, and we would not re-use the value representations at all.

<br/>See templates in capability <capability_ref linkend="representing_properties_textually"/> for an example of the propsed solution.

 

 

 

I intend to make these changes in the near future to capabilities representing_properties_textually,  representing_properties_numerically, and representing_evolution_of_property_values (I have no funding to create the templates in representing_property_value_ranges).

 

 

Furthermore, I have added two issues against assigning_document_properties:

 

    <!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->

    <issue id="PBM-1" type="general" status="open" category="major_technical" by="Peter Bergstrom" date="2006-04-28">

        <description>

It appears that a file or document_definition is only allowed to have one property assigned. See

<express_ref linkend="document_properties:arm:Document_properties_arm.Assigned_document_property"/>.

If this is true, properties for documents must be handled similarly as properties for all other subtypes of Product, i.e. using the

<capability_ref linkend="assigning_product_properties"/> .

</description>

    </issue>

 

    <!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->

    <issue id="PBM-2" type="general" status="open" category="minor_technical" by="Peter Bergstrom" date="2006-04-28">

        <description>

If possible, document properties should be harmonized with other properties:

<br/><capability_ref linkend="assigning_product_properties"/>

<br/><capability_ref linkend="assigning_process_properties"/>

<br/><capability_ref linkend="assigning_resource_properties"/>

<br/><capability_ref linkend="representing_properties_textually"/>

<br/><capability_ref linkend="representing_properties_numerically"/>

<br/><capability_ref linkend="representing_property_value_ranges"/>

<br/><capability_ref linkend="representing_evolution_of_property_values"/>.

        </description>

    </issue>

 

 

 

Peter Bergström

Eurostep AB