Abstract
A requirements document tends to be full of requirements thatare no longer meaningful, descriptions that are unnecessarilylong-winded and complicated, and duplicated information,among other shortcomings. These problems hinder the overallunderstandability of the requirements document and mightcompromise the subsequent development phases. Arequirements document quality evaluation strategy shouldincorporate also guidelines to help practitioners to effectivelymeasure and improve their requirements documents. In thisposter paper we brief describe a process that supports theevaluation and improvement of use case models namedAIRDoc.
Original language | Unknown |
---|---|
Title of host publication | ACM SAC |
Pages | 708-709 |
DOIs | |
Publication status | Published - 1 Jan 2011 |
Event | ACM SAC - Duration: 1 Jan 2011 → … |
Conference
Conference | ACM SAC |
---|---|
Period | 1/01/11 → … |