Here is the synopsis of our sample research paper on Software Testing Metrics. Have the paper e-mailed to you 24/7/365.
Essay / Research Paper Abstract
A 9 page paper considering this question: “Are testing and quality assurance the cause of productivity impacts, or are they the effect?” Whether good or bad, positive or negative, there are instances when the answer to this question can be “Both.” Greater productivity attributable to higher quality certainly causes positive productivity effects. Conversely, attention to quality as part of the corporate mission is likely to result in greater quality in production as well. The paper examines quality, efficiency of operation, costs and customer focus. Bibliography lists 11 sources.
Page Count:
9 pages (~225 words per page)
File: CC6_KSitSoftMetric.rtf
Buy This Term Paper »
Unformatted sample text from the term paper:
the story of an exchange between a director and a tester in 1987. The director asked if a new software product had been tested and if it were ready
to go into production. The tester replied, that yes, the software had been tested. "What did you test?" "I tested it" (Hutcheson, 2003; p. 1). With
an engineering background, Hutcheson (2003) was determined to never again give such a poor answer to that question. Quality in Software Engineering Cole
and Cole (2000) ask, "Why, after all that has been written about the importance of teamwork, are working relationships plagued with frustration and disappointment" (p. 56)? When people are
working together - or even when theyre not - communication is the one crucial factor that all involved need to practice. Deming (1986) identified this factor long ago, long
before publication of Out of the Crisis. One MIS manager flatly stated in his departments mission statement that it was the departments aim
to "Control our own destiny" (Martin, et al., 2002; p. 137). Though there are positive aspects to such a position, some of those in software engineering appear to concentrate
on this mission to the detriment of customers needs. Kan, Basili and Shapiro (1994) report that the "the 1960s and the years prior
to that decade could be viewed as the functional era of software engineering, the 1970s as the schedule era, and the 1980s as the cost era" (p. 4). By
the 1990s, the focus more frequently was on customers and their use of the products of software engineering. In years before the decade of the 1990s, quality was less
...