This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
September 1985 (vol. 11 no. 9)
pp. 934-938
M.S. Karasik, OASAS Limited
The problems of developing software requirements and quality assurance techniques have basically dealt with an environment where a single organization acts as the designer, developer, and user of the software product. Since the mid-1970' s, however, there has been a great increase in the use of "packaged" software products designed and developed by one organization for use in a variety of other organizations. The great profusion of products has resulted in many products being peddled for generic applications (accounting, manufacturing, etc.) which are of questionable quality and/or "fit" to a given organization's environment. This paper describes some techniques that are being used to certify software produced by third parties and how to determine if the "fit" is there. Current quality assurance techniques deal with the "correctness" of a program as compared to its specifications [2], [4], [7], [8], [12]. The real issue for a purchaser of software is whether the software is "correct" for its environment.
Index Terms:
test plans, Environmental testing, logical pathway, quality assurance, system testing, test generator
Citation:
M.S. Karasik, "Environmental Testing Techniques for Software Certification," IEEE Transactions on Software Engineering, vol. 11, no. 9, pp. 934-938, Sept. 1985, doi:10.1109/TSE.1985.232551
Usage of this product signifies your acceptance of the Terms of Use.