Abstract

Requirements are defined as the desired set of characteristics of a product or a service. In the world of software development, it is estimated that more than half of the failures are attributed towards poor requirements management. This means that although the software functions correctly, it is not what the client requested. Modern software requirements management methodologies are available to reduce the occur-rence of such incidents. This paper performs a review on the available literature in the area while tabulating possible methods of managing requirements. It also highlights the benefits of following a proper guideline for the requirements management task. With the introduction of specific software tools for the requirements management task, better software products are now been developed with lesser resources.

Highlights

  • The term ‘Requirement’ is used to describe the set of desired characteristics and attributes possessed by a particular product or a service

  • Software Configuration Management (SCM) or the change control process is considered as the perfect solution for tackling changes in the software development life cycle

  • Depending on the literature available, it is clear that the use of requirements management techniques is highly beneficial to the software industry

Read more

Summary

INTRODUCTION

The term ‘Requirement’ is used to describe the set of desired characteristics and attributes possessed by a particular product or a service. It is estimated that about 50% - 60% of software malfunctions are caused as a consequence of bad software management This means that the problem is not associated with programming and the development team is by no means at blame, rather, the problem is purely due to the final product not meeting the customer’s requirement. It involves the determination of requirements for an innovative or a changed organization while being mindful about probable incompatibilities. The fourth chapter introduces the requirements traceability matrix, which is essentially one of the best methods available for the task at hand. It discusses the advantages posed by the use of various tools for the task. The final chapter concludes the paper while briefly noting the potential work for the future

Overview of Software Requirements Management Principles and Practices
Key Principles
PRACTICES IN REQUIREMENTS MANAGEMENT
Managing Change Requests
Defining Requirements for Requirements Management Practice
Change Control Approach
REQUIREMENTS TRACEABILITY MATRIX
Tools for Requirements Management
CONCLUSION
Benefits of using Tools
Recommendations
Future Work
Full Text
Paper version not known

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 call

Disclaimer: 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.