Issue 17553: AttributeDefinition should allow mutliplicities for attribute values (reqif-rtf)
Source: Fraunhofer FOKUS (Mr. Marc-Florian Wendland, marc-florian.wendland(at)fokus.fraunhofer.de)
Nature: Clarification
Severity: Minor
Summary: Section 10.3 says: "What is actually shared among the requirements is the requirement attribute definitions (the number of attributes, the names of the attributes, the default values for the attributes, and the datatypes of the attributes.)"


However, there is no possibility to allow more than one value for an attribute of a SpecType. This is a very fundamental conecept and should be provided by ReqIF 1.1.


A potential solution might be the following:


- Add a metaattribute upperValueBoundary to AttributeDefinition with default set to 1 (meaning, the attribute is allowed to have exactly one entry).


- Add two more metaattributes to AttributeDefinition: isOrdered:Boolean = true and isUnique:Boolean = true to enable the user specifying the nature of a list of attribute values

- Add a constraint to AttributeValue that ensures that the upperValueBoundary of the corresponding AttributeDefinition must be respected by an implementation
Resolution: 
Revised Text: 
Actions taken:
August 20, 2012: received issue
Discussion: 
An implementation of the above requirements would require a change to the ReqIF model. The impact of such a change on the existing ReqIF implementations is unclear and needs further analysis. The ReqIF1.1 RTF, including the issue’s author Marc-Florian Wendland, agreed that changes to the ReqIF model should currently be omitted for standard stability.
Parts of the requested functionality can already be achieved using the ReqIF1.0.1 standard: by using an AttributeDefinitionEnumeration element with multiValued set to true, multiple string literals can be referenced from each SpecObject instance.
This issue will be reconsidered in a future RTF.
Disposition: Deferred
End of Annotations:=====

m: webmaster@omg.org
Date: 20 Aug 2012 02:53:51 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Marc-Florian Wendland
Employer:        Fraunhofer FOKUS
mailFrom:        marc-florian.wendland@fokus.fraunhofer.de
Terms_Agreement: I agree
Specification:   ReqIF
Section:         10.8.3
FormalNumber:    formal/2011-04-02
Version:         1.0.1
Doc_Year:        2011
Doc_Month:       April
Doc_Day:         02
Page:            40
Title:           AttributeDefinition should allow mutliplicities for attribute values
Nature:          Clarification
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


Section 10.3 says: "What is actually shared among the requirements is the requirement attribute definitions (the number of attributes, the names of the attributes, the default values for the attributes, and the datatypes of the attributes.)"


However, there is no possibility to allow more than one value for an attribute of a SpecType. This is a very fundamental conecept and should be provided by ReqIF 1.1.


A potential solution might be the following:


- Add a metaattribute upperValueBoundary to AttributeDefinition with default set to 1 (meaning, the attribute is allowed to have exactly one entry).


- Add two more metaattributes to AttributeDefinition: isOrdered:Boolean = true and isUnique:Boolean = true to enable the user specifying the nature of a list of attribute values

- Add a constraint to AttributeValue that ensures that the upperValueBoundary of the corresponding AttributeDefinition must be respected by an implementation