Software reliability: measurement, prediction, application
Software reliability: measurement, prediction, application
Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
Representing and using non-functional requirements: a process-oriented approach
Representing and using non-functional requirements: a process-oriented approach
Dealing with non-functional requirements: three experimental studies of a process-oriented approach
Proceedings of the 17th international conference on Software engineering
Handbook of software reliability engineering
Handbook of software reliability engineering
Software metrics (2nd ed.): a rigorous and practical approach
Software metrics (2nd ed.): a rigorous and practical approach
The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
Five Ways to Destroy a Development Project
IEEE Software
Identifying Quality-Requirement Conflicts
IEEE Software
A Framework for Scenario Evolution
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Integrating Non-Functional Requirements into Data Modeling
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
A comedy of errors: the London Ambulance Service case study
IWSSD '96 Proceedings of the 8th International Workshop on Software Specification and Design
Communications of the ACM - Two decades of the language-action perspective
Using Linguistic Knowledge to Classify Non-functional Requirements in SRS documents
NLDB '08 Proceedings of the 13th international conference on Natural Language and Information Systems: Applications of Natural Language to Information Systems
Toward sustainable software engineering (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
| Hi-index | 0.00 |
Although Non-Functional Requirements (NFRs) have been present in many software development methods, they have been presented as a second or even third class type of requirement, frequently hidden inside notes and therefore, frequently neglected or forgotten. Surprisingly, despite the fact that non-functional requirements are among the most expensive and difficult to deal with there are still few works that focus on NFRs as first class requirements. Although these works have brought a contribution on how to represent and deal with NFRs, two aspects remain not sufficiently explored: how to elicit NFRs and how to merge these NFRs with conceptual models. Our work aims at filling this gap, proposing a strategy to elicit NFRs and to integrate them into conceptual models We focus our attention on conceptual models expressed using UML, and therefore, we propose extensions to UML such that NFRs can be expressed. More precisely, we will show how to integrate NFRs to the Class, Sequence and Collaboration Diagrams. We will also show how Use Cases and Scenarios can be adapted to deal with NFRs. This work was validated by three case studies and their results suggest that by using our proposal we can improve the quality of UML models.