Results 161 to 170 of about 2,053,904 (198)
Some of the next articles are maybe not open access.
Tracing Non-Functional Requirements
2011Non-functional requirements, describing quality concerns such as performance, security, and availability, often exhibit complex interdependencies and trade-offs and have broad-reaching impacts across the architectural design of a software intensive system.
Mehdi Mirakhorli, Jane Cleland-Huang
openaire +1 more source
Non-Functional Requirements Elicitation
2004Software developers are constantly under pressure to deliver code on time and on budget. As a result, many projects focus on delivering functionalities at the expense of meeting non-functional requirements such as reliability, security, maintainability, portability, accuracy, among others.
Luiz Marcio Cysneiros, Eric Yu
openaire +1 more source
Impact of Non-functional Requirements on Requirements Evolution
2013 6th International Conference on Emerging Trends in Engineering and Technology, 2013Software impacts almost every aspect of modern society. Developers of a software system are responsible for identifying the requirements of the application, developing software that implements the requirements, and for allocating appropriate resources (processors and communication networks).
Kiran Khatter, Arvind Kalia
openaire +1 more source
Components for Non-Functional Requirements
1998Building distributed applications is very hard as we not only have to take care of the application semantics, but of non-functional requirements such as distributed execution, security and reliability as well. A component-oriented approach can be a powerful technique to master this complexity, and to manage the development of such applications. In such
Bert Robben +4 more
openaire +1 more source
Software requirement prioritization based on non-functional requirements
2017 7th International Conference on Cloud Computing, Data Science & Engineering - Confluence, 2017Requirements can be characterized as needs or demands. In software, requirements are a portrayal of what a system is ought to do. Software requirements describe what must be produced and delivered [1]. System may have few to many requirements. In case of shortage of time or budget prioritizing requirements become a necessity.
Umang Garg, Abhishek Singhal
openaire +1 more source
Resolving requirement conflicts through non-functional decomposition
Proceedings. Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 2004), 2004A lack of insight into the relationship between (non) functional requirements and architectural solutions often leads to problems in real life projects. This paper presents a model that concentrates on the mapping of nonfunctional requirements onto functional requirements for architecture design.
Poort, E.R., With, de, P.H.N.
openaire +2 more sources
Automated classification of non-functional requirements
Requirements Engineering, 2007This paper describes a technique for automating the detection and classification of non-functional requirements related to properties such as security, performance, and usability. Early detection of non-functional requirements enables them to be incorporated into the initial architectural design instead of being refactored in at a later date.
Jane Cleland-Huang +3 more
openaire +1 more source
Extending UML with Non-functional Requirements Modelling
2011Non-Functional Requirements (NFR) have been for too long overlooked during the development of software systems, leading in numerous cases to failure, an over budget or even cancellation of projects. In this paper, we propose a solution to integrate the modelling of NFRs into the UML diagrams.
Krishna, Aneesh, Gregoriades, Andreas
openaire +2 more sources
Automated testing of non-functional requirements
Companion to the 23rd ACM SIGPLAN conference on Object-oriented programming systems languages and applications, 2008We present an open-source toolkit that enables automated testing of non-functional requirements. Our toolkit offers an alternative to current approaches (e.g. testing suites) by being lightweight, flexible, free and by reusing libraries and executables found on common operating systems and platforms. The toolkit provides developers and project managers
Kristoffer Dyrkorn, Frank Wathne
openaire +1 more source
Explainability as a Non-Functional Requirement
2019 IEEE 27th International Requirements Engineering Conference (RE), 2019Recent research efforts strive to aid in designing explainable systems. Nevertheless, a systematic and overarching approach to ensure explainability by design is still missing. Often it is not even clear what precisely is meant when demanding explainability.
Kohl, Maximilian A. +5 more
openaire +1 more source