Abstract
An interesting phenomenon occurred a couple of months ago when I elicited thoughts and feedback on meaningful requirements engineering (RE) metrics from a few RE practitioners and peers. Project teams across industry are often expected to put forth some sort of indicators for management indicating that their company's investment in the work of writing requirements provides some sort of payoff in the end. As I began my career in RE, I pored over a study from Raytheon1 that comfortably concluded that yes, it is far better to discover lack of alignment or shared understanding in what a team is to develop early. Defects cost less to fix when the system to be released is still in its definition phases, rather than when development hours have been expended, when potential releases are being tested, and certainly before a product is released to its customers as complete. The cost of quality in the form of better practice is lower than the cost of cleanup later.
Sign-in/Register to access full text options 
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.
