• Corpus ID: 212454057

Requirements Volatility in Software Development Process

@inproceedings{Singh2012RequirementsVI,
  title={Requirements Volatility in Software Development Process},
  author={Munindar P. Singh and Rajnish Vyas},
  year={2012}
}
Changes in requirements do occur during the software development life cycle. The changes may take place from the initial design phase up to the implementation phase. These change that creep during the development process pose risk to cost and quality of the product, but at the same time provide an opportunity to add value. This paper discusses the requirement, volatility in requirements, causes of requirement volatility and then the impact of requirement volatility on Project Schedule, Project… 

Figures from this paper

Identify and Manage the Software Requirements Volatility Proposed Framework and CaseStudy
TLDR
This research paper has analysed the root causes of requirements volatility through a proposed framework presenting the requirements volatility causes and how to manage requirements volatility during the software development life cycle.
A Multistep Approach for Managing the Risks of Software Requirements Volatility
TLDR
This research highlights the importance of managing requirement changes, classify them, and control the impact risks of requirement volatility on software project by designing a model based on software requirements risks factors and how to reduce their impacts.
Requirements volatility in software architecture design: an exploratory case study
TLDR
The study identified the challenges that requirements volatility posed to SW architecture design, including scheduling and architectural technical debt and means of mitigating the factors that cause requirements volatility and addressing the challenges posed by requirements volatility.
A Change Impact Size Estimation Approach during the Software Development
TLDR
A new Change Impact Size Estimation (CISE) approach for the software development phase is introduced and a prototype tool has been developed to support the implementation of the approach and evaluation.
An Empirical Study on the Current Practice in Software Project Management – the Requirement Specifications
Requirements specification is one of the most crucial processes in software development projects. Without well-specified requirements, the project manager could not planning and design a good project
An algorithmic-based software change effort prediction model using change impact analysis for software development
TLDR
This research proposed an algorithmic change effort prediction model that used change impact analysis method to improve the accuracy of the effort estimation and applicability for both Traditional and Agile methodologies.
Complex Project Management: Using Complexity and Volatility to Guide Hybrid Methodological Practices
TLDR
With organisational problems of increasing complexity and volatility, there is a growing recognition that better PM methodologies should be developed to deal with these characteristics and that PM should be seen as a form of complex problem solving.
Applying Layering Concept to the Software Requirements Analysis and Architectural Design
TLDR
This paper applies layering concept to the software requirements analysis and architectural design in order to provide a method to define a robust software architecture but to be adaptable to the presence of changing requirements.
A Systematic Literature Review Of Multi-Criteria Risk Factors (VUCA) In Requirement Engineering
TLDR
This work aims to study available work in requirement risk management along with their pros and cons and to propose approaches to effectively manage requirement engineering challenges.
A review of practice and problems in requirements engineering in small and medium software enterprises in Thailand
  • Supha Khankaew, S. Riddle
  • Business, Computer Science
    2014 IEEE 4th International Workshop on Empirical Requirements Engineering (EmpiRE)
  • 2014
TLDR
Results show that software firms in Thailand encounter common problems such as clarity, correctness, completeness, change management, and customer communication, and development needs in SMEs such as software process improvement, RE knowledge, requirements management tools, training, and knowledge transfer.
...
1
2
...

References

SHOWING 1-8 OF 8 REFERENCES
Managing the Impact of Requirements Volatility Master Thesis, 2005
TLDR
The causes of requirements volatility are described and how these causes will affect the different phases of software development life cycle and how to Manage and control requirements volatility in different software development phases are suggested.
A study of the impact of requirements volatility on software project performance
TLDR
An extensive survey based empirical study of requirement volatility and its impact on software project performance reveals that requirement volatility has a significant impact on schedule overrun and cost overrun in software projects.
Requirements Volatility and Its Impact on Change Effort: Evidence-based Research in Software Development Projects Return to Published Papers
TLDR
Evidence-based research on RV and its impact on software development effort demonstrates that changing requirements, particularly adding new requirements, at the later phases is considered a high risk because it will cost the organisation in terms of budget overruns or schedule delays.
An examination of the effects of requirements changes on software maintenance releases
TLDR
Using data collected from one organization on 44 software releases spanning seven products, this paper presents two quantitative techniques for dealing with requirements change in a maintenance environment that can help an organization provide a focus for management action during the software maintenance process.
Requirements engineering in the year 00: a research perspective
TLDR
The initial description of a complex safety-critical system is used to illustrate a number of current research trends in RE-specific areas such as goal-oriented requirements elaboration, conflict management, and the handling of abnormal agent behaviors.
Software quality - analysis and guidelines for success
TLDR
The need for a multi-faceted approach to achieve high-levels of software quality, utilizing quality measurements, protest inspections and testing by trained testing experts as tools to achieve success is demonstrated.
A Longitudinal Study of Requirements Volatility in Software Development
  • in the ASMA/SQA Meeting,
  • 2005