Non-functional requirements: from elicitation to modelling languages
Proceedings of the 24th International Conference on Software Engineering
Case Studies for Method and Tool Evaluation
IEEE Software
Using UML to reflect non-functional requirements
CASCON '01 Proceedings of the 2001 conference of the Centre for Advanced Studies on Collaborative research
Nonfunctional Requirements: From Elicitation to Conceptual Models
IEEE Transactions on Software Engineering
An investigation into the notion of non-functional requirements
Proceedings of the 2010 ACM Symposium on Applied Computing
| Hi-index | 0.00 |
The author discusses five problems that can contribute to a software project's failure. The five pitfalls are: inadequate system engineering during the proposal and during front-end development; inadequate tracing, tracking, and management of system and software requirements; improper sizing of the target hardware; selection of design, production, and integration and test methodologies that are inappropriate to a large software development; and failure to provide a metrics program that would let managers track the progress of software production and test.