Here is the synopsis of our sample research paper on Software testing. Have the paper e-mailed to you 24/7/365.
Essay / Research Paper Abstract
A paper which looks at the problems associated with software testing, particularly for small companies, and considers ways in which these might be alleviated in order to provide better quality software and allow greater competitiveness in relation to larger firms. Bibliography lists 5 sources.
Page Count:
4 pages (~225 words per page)
File: JL5_JLsoftes.rtf
Buy This Term Paper »
Unformatted sample text from the term paper:
of Standards and Technology as stating that American corporations are currently spending in excess of fifty billion dollars a year in repairing problems which software, usually after the application has
been released and when repairs are therefore more expensive to carry out. The NIST asserts that costs could be reduced by a third if proper pre-release testing had been carried
out. Syntel also makes the point that companies should regard testing as a quality gain, as opposed to simply a cost saving; it is
evident that given the high degree of competition between small software firms, gaining this kind of competitive edge in terms of quality could make a vital difference to the companys
performance. As Norden (2002) points out, software testing and quality are inextricably linked: without pre-release testing the designers do not know whether or
not the software will perform as it is supposed to do. If it fails, then this does not bode well for future relations with the customer. However, Tamares (2002) paints
a bleak picture of the usual pattern of software testing in most companies. She comments that management only starts to think about testing as the deadline approaches, and that some
unfortunate programmer is accordingly assigned to testing, which "is often viewed as being transferred to purgatory" since there is no help or guidance available. Management is determined that the product
will be finished and shipped, come what may, and the testers job is basically to exert some degree of damage limitation on the "surprises that could manifest themselves after the
product is installed (by the customer)" (Tamares, 2002, npa). Management, she states, tend to be under the impression that software testing is intuitive, that
...