Feature Requirements Models : Understanding Interactions
Identifieur interne : 001D75 ( Crin/Corpus ); précédent : 001D74; suivant : 001D76Feature Requirements Models : Understanding Interactions
Auteurs : Jean-Paul GibsonSource :
English descriptors
Abstract
This paper states that many of the problems which arise when features combine (i.e. feature interactions) are due to badly developed requirements models for individual features. With sufficiently good requirements models, in which each feature is formally modelled and validated against customer understanding, the feature interaction problem is much more tractable. We analyse some of the standard feature interactions and show that, in most cases, the notion of interaction is used to signify that the requirements are not fully understood, properly recorded or rigorously validated. In contrast, we then show how good requirements models could resolve the problems that arise when combining features. An interaction is said to occur if and only if requirements are contradictory. The problem which the paper addresses is how to avoid, detect and resolve such contradictions during requirements development.
Links to Exploration step
CRIN:gibson97aLe document en format XML
<record><TEI><teiHeader><fileDesc><titleStmt><title xml:lang="en" wicri:score="3">Feature Requirements Models : Understanding Interactions</title></titleStmt><publicationStmt><idno type="RBID">CRIN:gibson97a</idno><date when="1997" year="1997">1997</date><idno type="wicri:Area/Crin/Corpus">001D75</idno></publicationStmt><sourceDesc><biblStruct><analytic><title xml:lang="en">Feature Requirements Models : Understanding Interactions</title><author><name sortKey="Gibson, Jean Paul" sort="Gibson, Jean Paul" uniqKey="Gibson J" first="Jean-Paul" last="Gibson">Jean-Paul Gibson</name></author></analytic></biblStruct></sourceDesc></fileDesc><profileDesc><textClass><keywords scheme="KwdEn" xml:lang="en"><term>Keyword 1</term><term>Keyword 2</term></keywords></textClass></profileDesc></teiHeader><front><div type="abstract" xml:lang="en" wicri:score="1211">This paper states that many of the problems which arise when features combine (i.e. feature interactions) are due to badly developed requirements models for individual features. With sufficiently good requirements models, in which each feature is formally modelled and validated against customer understanding, the feature interaction problem is much more tractable. We analyse some of the standard feature interactions and show that, in most cases, the notion of interaction is used to signify that the requirements are not fully understood, properly recorded or rigorously validated. In contrast, we then show how good requirements models could resolve the problems that arise when combining features. An interaction is said to occur if and only if requirements are contradictory. The problem which the paper addresses is how to avoid, detect and resolve such contradictions during requirements development.</div></front></TEI><BibTex type="inproceedings"><ref>gibson97a</ref><crinnumber>97-R-022</crinnumber><category>3</category><equipe>MODEL</equipe><author><e>Gibson, Jean-Paul</e></author><title>Feature Requirements Models : Understanding Interactions</title><booktitle>{Feature Interaction Workshop 1997, Montreal, Canada}</booktitle><year>1997</year><series>Feature Interaction Workshop</series><month>jun</month><publisher>U.S. Press</publisher><keywords><e>Keyword 1</e><e>Keyword 2</e></keywords><abstract>This paper states that many of the problems which arise when features combine (i.e. feature interactions) are due to badly developed requirements models for individual features. With sufficiently good requirements models, in which each feature is formally modelled and validated against customer understanding, the feature interaction problem is much more tractable. We analyse some of the standard feature interactions and show that, in most cases, the notion of interaction is used to signify that the requirements are not fully understood, properly recorded or rigorously validated. In contrast, we then show how good requirements models could resolve the problems that arise when combining features. An interaction is said to occur if and only if requirements are contradictory. The problem which the paper addresses is how to avoid, detect and resolve such contradictions during requirements development.</abstract></BibTex></record>Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Wicri/Lorraine/explor/InforLorV4/Data/Crin/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 001D75 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Crin/Corpus/biblio.hfd -nk 001D75 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien
|wiki= Wicri/Lorraine
|area= InforLorV4
|flux= Crin
|étape= Corpus
|type= RBID
|clé= CRIN:gibson97a
|texte= Feature Requirements Models : Understanding Interactions
}}
| This area was generated with Dilib version V0.6.33. |  |