Goal-directed requirements acquisition
6IWSSD Selected Papers of the Sixth International Workshop on Software Specification and Design
Writing Effective Use Cases
Use Case Pitfalls: Top 10 Problems from Real Projects Using Use Cases
TOOLS '99 Proceedings of the Technology of Object-Oriented Languages and Systems
Modelling strategic relationships for process reengineering
Modelling strategic relationships for process reengineering
Use Cases: Patterns and Modeling Problems
Use Cases: Patterns and Modeling Problems
Refactoring Use Case Models on Episodes
Proceedings of the 19th IEEE international conference on Automated software engineering
Hi-index | 0.00 |
A requirements document tends to be full of requirements that are no longer meaningful, descriptions that are unnecessarily long-winded and complicated, and duplicated information, among other shortcomings. These problems hinder the overall understandability of the requirements document and might compromise the subsequent development phases. A requirements document quality evaluation strategy should incorporate also guidelines to help practitioners to effectively measure and improve their requirements documents. In this poster paper we brief describe a process that supports the evaluation and improvement of use case models named AIRDoc.