Abstract
The most common cause of software product failure or dissatisfaction of end users with the delivered product is missing requirements or badly implemented requirements. Some of the requirements are forgotten, or changed, or deleted or poorly implemented especially in made-to-order software development projects. So, we need to trace, track and report the transition of requirements into a software product all through the software development life cycle. This chapter discusses these topics.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2013 Springer Science+Business Media New York
About this chapter
Cite this chapter
Chemuturi, M. (2013). Requirements Tracing, Tracking and Reporting. In: Requirements Engineering and Management for Software Development Projects. Springer, New York, NY. https://doi.org/10.1007/978-1-4614-5377-2_9
Download citation
DOI: https://doi.org/10.1007/978-1-4614-5377-2_9
Published:
Publisher Name: Springer, New York, NY
Print ISBN: 978-1-4614-5376-5
Online ISBN: 978-1-4614-5377-2
eBook Packages: Computer ScienceComputer Science (R0)