Results 261 to 270 of about 2,062,977 (296)
Some of the next articles are maybe not open access.
Dealing with non-functional requirements
Proceedings of the 17th international conference on Software engineering - ICSE '95, 1995Quality characteristics are vital for the success of software systems. To remedy the problems inherent in ad hoc development, a framework has been developed to deal with non-functional requirements (quality requirements or NFRs). Taking the premise that the quality of a product depends on the quality of the process that leads from high-Ievel NFRs to ...
Lawrence Chung, Brian A. Nixon
openaire +1 more source
Towards Optimising Non-functional Requirements
2009 Ninth International Conference on Quality Software, 2009Non-functional requirements are an important, and often critical, aspect of any software system. However, determining the degree to which any particular software system meets such requirements and incorporating such considerations into the software design process is a difficult challenge.
Christopher Burgess +2 more
openaire +1 more source
Non-functional Avionics Requirements
2008Embedded systems in aerospace become more and more integrated in order to reduce weight, volume/size, and power of hardware for more fuel-effi ciency. Such integration tendencies change architectural approaches of system ar chi tec tures, which subsequently change non-functional requirements for plat forms.
Michael Paulitsch +2 more
openaire +1 more source
Quantification of non-functional requirements
2014 Seventh International Conference on Contemporary Computing (IC3), 2014Requirements Analysis is considered as the most important phase for the development of quality software because errors caused by poor and inadequate requirement analysis are likely to creep in design and implementation phase. These errors are observed as time-consuming and most expensive to repair.
Kiran Khatter, Arvind Kalia
openaire +1 more source
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