Using Abuse Case Models for Security Requirements Analysis
ACSAC '99 Proceedings of the 15th Annual Computer Security Applications Conference
Goal-Oriented Requirements Engineering: A Guided Tour
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
From quality in use to value in the world
CHI '04 Extended Abstracts on Human Factors in Computing Systems
Proceedings of the third Nordic conference on Human-computer interaction
Foundations of Empirical Software Engineering: The Legacy of Victor R. Basili
Foundations of Empirical Software Engineering: The Legacy of Victor R. Basili
Value-Based Software Engineering
Value-Based Software Engineering
Non-Functional Requirements in Industry - Three Case Studies Adopting an Experience-based NFR Method
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Evaluating the Effectiveness of a Goal-Oriented Requirements Engineering Method
CERE '06 Proceedings of the Fourth Internationa Workshop on Comparative Evaluation in Requirements Engineering
A framework to support alignment of secure software engineering with legal regulations
Software and Systems Modeling (SoSyM)
| Hi-index | 0.00 |
It is not easy to choose a method for eliciting, detailing and documenting non-functional requirements (NFR) among the variety of existing methods. In order to explore typical characteristics of such methods, we compare two approaches which specify NFR: MOQARE and the IESE-NFRmethod. Both aim at deriving detailed requirements from quality attributes, but use different concepts and processes. Our analysis led to ideas for incremental improvement of each method and also to deeper insight into NFR methods.