By Topic

Putting software terminology to the test

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Steven, John ; Cigital, Dulles, VA, USA

Project management relies on testing personnel's expertise to ensure software quality. However, contractual and management issues also determine a project's quality. Such issues might even control testing itself. Consider the situation in which a client hires a vendor to build a piece of software. The client could specify the type, schedule, and extent of testing in its contract. Such terms might include compressing the time allotted to quality assurance or substituting certain tests for others. To successfully meet software quality goals, all parties involved must fully understand what testing the contract requires. However, testing literature, practitioners, and project management often have different understandings of common testing concepts. I describe two specific inconsistencies in testing vocabulary that can put a software project at risk

Published in:

Software, IEEE  (Volume:19 ,  Issue: 3 )