Identifying Requirements Conflicts and Cooperation: How Quality Attributes and Automated Traceability Can Help

Egyed, Alexander; GrÃ¼nbacher, Paul

doi:10.1109/MS.2004.40

Identifying Requirements Conflicts and Cooperation: How Quality Attributes and Automated Traceability Can Help

by Alexander Egyed, Paul GrÃ¼nbacher

Abstract:

Requirements about software attributes have numerous complex and nontrivial interdependencies. Requirements conflict with each other when they make contradicting statements about common software attributes, and they cooperate when they mutually enforce such attributes. Because software developers rarely apply formal requirements specification techniques in practice, and because reliable techniques for natural language understanding aren't available, it's generally infeasible to automatically identify conflicts and cooperation among requirements. In software development and maintenance, identifying conflicts and cooperation among requirements is challenging. Fortunately, quality attributes can help. In addition, automated traceability techniques can eliminate falsely identified conflicts and cooperation efficiently.

View PDF

Reference:

Alexander Egyed, Paul GrÃ¼nbacher, "Identifying Requirements Conflicts and Cooperation: How Quality Attributes and Automated Traceability Can Help", In IEEE Software, vol. 21, no. 6, pp. 50-58, 2004.

Bibtex Entry:

@Article{dblp:journals/software/EgyedG04,
  Title                    = {Identifying Requirements Conflicts and Cooperation: How Quality Attributes and Automated Traceability Can Help},
  Author                   = {Alexander Egyed and Paul GrÃ¼nbacher},
  Journal                  = {IEEE Software},
  Year                     = {2004},
  Number                   = {6},
  Pages                    = {50-58},
  Volume                   = {21},

  Abstract                 = {Requirements about software attributes have numerous complex and nontrivial interdependencies. Requirements conflict with each other when they make contradicting statements about common software attributes, and they cooperate when they mutually enforce such attributes. Because software developers rarely apply formal requirements specification techniques in practice, and because reliable techniques for natural language understanding aren't available, it's generally infeasible to automatically identify conflicts and cooperation among requirements. In software development and maintenance, identifying conflicts and cooperation among requirements is challenging. Fortunately, quality attributes can help. In addition, automated traceability techniques can eliminate falsely identified conflicts and cooperation efficiently.},
  Doi                      = {10.1109/MS.2004.40},
  File                     = {Identifying Requirements Conflicts and Cooperation:Journals\\IEEE Software 2004 - Identifying Requirements Conflicts and Cooperation\\Identifying Requirements Conflicts and Cooperation.pdf:PDF},
  Keywords                 = {traceability, analysis},
  Owner                    = {paul},
  Timestamp                = {2015.09.12},
  Url                      = {http://doi.ieeecomputersociety.org/10.1109/MS.2004.40}
}