Software Metrics: A Rigorous and Practical Approach
Software Metrics: A Rigorous and Practical Approach
Controlling Requirements Evolution: An Avionics Case Study
SAFECOMP '00 Proceedings of the 19th International Conference on Computer Safety, Reliability and Security
Change Analysis: A Step towards Meeting the Challenge of Changing Requirements
ECBS '96 Proceedings of the IEEE Symposium and Workshop on Engineering of Computer Based Systems
Understanding Project Sociology by Modeling Stakeholders
IEEE Software
Analysis of Requirements Volatility during Software Development Life Cycle
ASWEC '04 Proceedings of the 2004 Australian Software Engineering Conference
A Case Study: Requirements Elicitation Processes throughout a Project
RE '08 Proceedings of the 2008 16th IEEE International Requirements Engineering Conference
Proceedings of the the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Using FLOW to Improve Communication of Requirements in Globally Distributed Software Projects
CIRCUS '09 Proceedings of the 2009 Collaboration and Intercultural Issues on Requirements: Communication, Understanding and Softskills
| Hi-index | 0.00 |
The success of a project is often affected by imperfect requirements. In order to cope with this risk, a requirements analyst needs to communicate with a client. However, communication between the requirements analyst and the client is not enough to prevent requirements imperfection, since requirements come from various sources, e.g. environment, laws, documents, actual usage, etc. The process of requirements elicitation is affected by the requirements stability, the ability of a requirements analyst, and accessibility of the source of requirements. This paper focuses on the distance between the source of requirements and a requirements analyst, and clarifies how the distance influences the requirements maturation. Requirements maturation represents the degree to which the requirements are elicited completely. We define a measure for observing requirements maturation and analyzing the accessibility of the source of the requirements. Then, we define a hypothesis. A case is analyzed in order to verify the hypothesis. As a result, there is a correlation between the requirements maturation efficiency and the accessibility of the source of the requirements.