Results 251 to 260 of about 2,062,977 (296)
Evaluating administrative compliance as a predictor of nursing home postdisaster outcomes in the USA. [PDF]
Festa N +11 more
europepmc +1 more source
Scenario-based functional modularization framework for consumer electronics using MFD and AHP: A case study on audio products. [PDF]
Wu Z, Zhang J.
europepmc +1 more source
Some of the next articles are maybe not open access.
Related searches:
Related searches:
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 +3 more sources
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

