Abstract
On many software development projects, software system testing takes considerably longer than predicted. Even worse, the resultant product often fails to meet customer expectations. It is well understood and documented that the requirements specification process as currently practised is grossly inadequate. Perhaps this inadequate requirements process is a cause of the apparent inadequate software system testing process. The paper explores the qualities of a well written requirements specification. It also provides insight into how the lack of each of these qualities can have profound effects on the potential success or failure of software system testing. More attention to quality during the requirements specification process can help alleviate these problems.
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.
