Abstract
A survey on implicit requirements management practices in small and medium-sized enterprises
Highlights
The requirements of a software system are essential for effective performance of its functions and effective requirements engineering is crucial for the success of software development projects [1].From the perspective of requirements elicitation, requirements can be classified into explicit requirements and implicit or tacit requirements, which are assumed or unspoken requirements that are not stated or documented [2, 3]
Some of the concerns addressed in this aspect of validity are: Low statistical power: In a highly technical domain such as requirements management, having a large number of respondents is not so much of a strength as identifying persons that are truly knowledgeable on the issue of managing implicit requirements
The 56 respondents that are located in 38 distinct organisations and across 23 countries is sufficient for a small scale empirical study that seeks to give a first empirically based opinion on the handling of implicit requirements in small and mediumsized software organisations
Summary
The requirements of a software system are essential for effective performance of its functions and effective requirements engineering is crucial for the success of software development projects [1].From the perspective of requirements elicitation, requirements can be classified into explicit requirements (clearly stated requirements) and implicit or tacit requirements, which are assumed or unspoken requirements that are not stated or documented [2, 3]. Authors in [11] indicated that the quality of software cannot be adjudged good, and guaranteed to meet customer’s satisfaction if only explicit requirements are satisfied while implicit requirements are ignored. Because of their relevance, different researchers have proposed different approaches, methods and tools to efficiently identify and manage IMR from different sources. Different researchers have proposed different approaches, methods and tools to efficiently identify and manage IMR from different sources These include [3, 12, 13, 14], which considered how to identify and handle IMR. The works in [8, 15, 16, 17, 18] focussed on dealing with tacit/implicit knowledge in requirements; while [9, 19, 20, 21, 22] dealt with handling ambiguity in requirements
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
