Results 11 to 20 of about 2,053,904 (198)
Visualizing non-functional requirements [PDF]
2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop), 2006 Information systems can be visualized with many tools. Typically these tools present functional artifacts from various phases of the development life-cycle; these include requirements models, architecture and design diagrams, and implementation code. The syntactic structures of these artifacts are often presented in a textual language using symbols, or
Neil Ernst, Yijun Yu, John Mylopoulos
openaire +1 more source
Applied Sciences, 2023 Requirements Engineering (RE) is an important step in the whole software development lifecycle. The problem in RE is to determine the class of the software requirements as functional (FR) and non-functional (NFR). Proper and early identification of these
Fatih Yucalar
doaj +1 more source
IEEE Access, 2023 The incorporation of sustainability principles during the requirements engineering phase of the development life cycle constitutes greening software requirements.
Ahmad F. Subahi
doaj +1 more source
Integrating User eXperience practices into software development processes: implications of the UX characteristics [PDF]
PeerJ Computer Science, 2017 User eXperience (UX) is a key factor in the success of software systems. Many software companies face challenges in their work with UX. Existing research does not analyze UX practices and challenges in relation to other software quality characteristics ...
Pariya Kashfi +2 more
doaj +2 more sources
Using real options to select stable Middleware-induced software architectures [PDF]
, 2005 The requirements that force decisions towards building distributed system architectures are usually of a non-functional nature. Scalability, openness, heterogeneity, and fault-tolerance are examples of such non-functional requirements.
Bahsoon, R., Emmerich, W., Macke, J.
core +1 more source
Journal of King Saud University: Computer and Information Sciences, 2023 Requirements classification is a key component of software development life cycle. It enhances our understanding about project requirements, which in turn enables us to effectively identify and mitigate risks that could lead to project failure.
Summra Saleem +3 more
doaj +1 more source
How do software architects consider non-functional requirements: an exploratory study [PDF]
, 2012 © 2012 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes,creating new ...
Ameller, David +3 more
core +1 more source
Non-functional Requirements Documentation in Agile Software Development: Challenges and Solution Proposal [PDF]
, 2017 Non-functional requirements (NFRs) are determinant for the success of software projects. However,they are characterized as hard to define, and in agile software development(ASD), are often given less priority and usually not documented. In this paper, we
Behutiye, Woubshet +4 more
core +2 more sources
Systematic formulation of non-functional characteristics of software [PDF]
, 1998 This paper presents NoFun, a notation aimed at dealing with non-functional aspects of software systems at the product level in the component programming framework.
Franch Gutiérrez, Javier
core +1 more source
A Qualitative Study on Non-Functional Requirements in Agile Software Development
IEEE Access, 2021 Context: Widespread use of agile software development (ASD) methods can be observed nowadays. Non-functional requirements (NFRs) are often reported to be a problematic issue for agile projects, since ASD methods tend to neglect NFRs while focusing on ...
Aleksander Jarzebowicz, Pawel Weichbroth
doaj +1 more source