Results 21 to 30 of about 473,501 (260)
Obsolete software requirements
Context: Coping with rapid requirements change is crucial for staying competitive in the software business. Frequently changing customer needs and fierce competition are typical drivers of rapid requirements evolution resulting in requirements obsolescence even before project completion.
Krzysztof Wnuk +2 more
openaire +2 more sources
Tackling Requirements Uncertainty in Software Projects: A Cognitive Approach
In this era of dynamic technological phase shift, management and estimation of client's requirements in software project development has been established as one of the most crucial steps from the point of view of research.
Mohd. Haleem +2 more
doaj +1 more source
A hybrid multi-objective optimization algorithm for software requirement problem
The process of selecting software requirements aims to identify the optimal set of requirements that enhances the value of a software release while keeping costs within the budget.
M.H. Marghny +3 more
doaj +1 more source
IMPACT ANALYSIS MODEL FOR SOFTWARE REQUIREMENT CHANGE
Software requirement changes are inevitable due to the dynamic needs of business process and environment. Such changes in requirement need to be managed accordingly by determining the influencing factors as well as assessing their impacts ...
Marfizah Abdul Rahman +2 more
doaj +1 more source
A Metamodel for Software Requirement Patterns [PDF]
[Context and motivation] Software Requirement Patterns (SRP) are a type of artifact that may be used during requirements elicitation that also impact positively in other activities like documentation and validation. In our experiences, SRP show a great percentage of reuse for the non-functional requirements needed in call-for-tender requirement ...
Franch Gutiérrez, Javier +4 more
openaire +2 more sources
SIoT Framework: Towards an Approach for Early Identification of Security Requirements for Internet-of-things Applications [PDF]
Background: Security has become more of a concern with the wide deployment of Internet-of-things (IoT) devices. The importance of addressing security risks early in the development lifecycle before pushing to market cannot be over emphasized.
Ronald Jabangwe, Anh Nguyen-Duc
doaj +1 more source
The illusion of requirements in software development [PDF]
5 pages, 1 table, 1 figure; accepted for publication in Requirements Engineering: http://link.springer.com/article/10.1007%2Fs00766-012-0161 ...
openaire +2 more sources
Cognitive impact validation of requirement uncertainty in software project development
Currently, the most important factor which is receiving more attention is the requirements uncertainty in software projects development. Requirements uncertainty during the development of software project is identified as the most significant threat, and
Mohd. Haleem +2 more
doaj +1 more source
Ontology and its role in both software engineering and knowledge management fields have been widely reported in the literature. Numerous studies have proven the effectiveness of using ontologies to support the process of requirements engineering.
Abeer Abdulaziz Alsanad +2 more
doaj +1 more source
Theory as a Source of Software Requirements [PDF]
Today, when undertaking requirements elicitation, engineers attend to the needs and wants of the user groups considered relevant for the software system. However, answers to some relevant question (e.g., how to improve adoption of the intended system) cannot always be addressed through direct need and want elicitation. Using an example of energy demand-
Ruzanna Chitchyan, Caroline Bird
openaire +3 more sources

