Results 251 to 260 of about 1,440,432 (297)
Some of the next articles are maybe not open access.
Related searches:
Related searches:
Non-functional requirements: from elicitation to modelling languages
Proceedings of the 24th International Conference on Software Engineering. ICSE 2002, 2002Although 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.
Luiz Marcio Cysneiros +1 more
openaire +1 more source
Non-functional Requirements Prioritization: A Systematic Literature Review
2019 45th Euromicro Conference on Software Engineering and Advanced Applications (SEAA), 2019Continuous delivery and rapidly changing requirements in agile environments force the developers to put non-functional requirements (NFRs) on halt till maintenance phase. However, neglecting NFRs during prioritization phase may lead to inaccurate estimations for software projects resulting in high maintenance cost and failures.
Ijaz, Khush Bakht +2 more
openaire +2 more sources
Visualizing non-functional requirements patterns
2010 Fifth International Workshop on Requirements Engineering Visualization, 2010Properly dealing with non-functional requirements (NFRs), such as security and trustworthiness, requires a large body of knowledge about NFRs. Such knowledge can be captured as NFR patterns for reuse. Since knowledge of NFRs can have potentially complex structures and rules, it becomes hard to capture and reuse NFR patterns when they are represented ...
Sam Supakkul, Lawrence Chung
openaire +1 more source
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