Abstract
Software requirement specifications have been observed to largely impact the dependability and the cost of software systems in software development and certification phases. Inappropriate specification of software requirements can cause software developers' erroneous mental representations, thus leading to defects that propagate into subsequent development phases. Understanding the human error mechanisms of software requirement representation is significant for reducing the defects originated from requirements. This paper proposes a theory on the human error mechanism of software requirement, and derived two new criteria to avoid requirement specification triggering the human errors of developers. The criteria were validated by an experiment. Results show that: 1) once a requirement specification contained the error-prone scenarios of the two proposed criteria, developers indeed committed corresponding errors; 2) violating the proposed criteria tended to cause common defects, which are the defects introduced by two or more developers in the same way.
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.
