Practical software metrics for project management and process improvement
Practical software metrics for project management and process improvement
The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
The unified software development process
The unified software development process
Integrating Informal and Formal Approaches to Requirements Modeling and Analysis
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
The Automated Extraction of Requirements from UML Models
RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
The Evaluation of Large, Complex UML Analysis and Design Models
Proceedings of the 26th International Conference on Software Engineering
Information and Software Technology
Reengineering a scientific software and lessons learned
Proceedings of the 4th International Workshop on Software Engineering for Computational Science and Engineering
A domain specific requirements model for scientific computing (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
| Hi-index | 0.00 |
There appears to be a real dichotomy in the use of the UML vs. text based Use Case development for requirements elicitation and documentation, that is, on those projects where use cases are work products. Not only are there different processes in place for text and graphical use case modeling, but also there are a variety of approaches and philosophies in each camp. This paper will discuss the prose vs. graphical approaches to requirements elicitation, observed advantages and disadvantages of each, and suggest best practices for improving and/or creating effective processes for requirements elicitation.