Software Testing Verification and Validation:软件测试验证和确认.ppt.ppt

Software Testing Verification and Validation:软件测试验证和确认.ppt.ppt

  1. 1、本文档共14页,可阅读全部内容。
  2. 2、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
  3. 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  4. 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
Software Testing Verification and Validation:软件测试验证和确认.ppt

Ch.19 - Verification Validation Software Testing: Verification and Validation Verification “Are we building the product right?” Validation “Are we building the right product?” Barry Boehm, 1979 Verification and Validation Techniques Static Techniques Software Inspections (against source code) Dynamic Techniques Software Testing (requires executable program) Verification and Validation Static techniques Software Inspections of requirements documents of design documents (design reviews) of source code (code reviews) automated static analysis Verification and Validation Dynamic techniques Software Testing specification vs. implementation Defect testing [Ch.20] verifying non-functional requirements (e.g. performance; reliability) Statistical testing [Ch.21] automated dynamic analysis (if applicable) Verification and Validation Goals Establish that software is fit for purpose, not “bug-free” “Good enough” depends on: Software function (critical nature?) User expectations Market competition, price Testing vs. Debugging Verification and Validation looking and categorizing existence of system defects [example] [bug list] “What?” Debugging locating and correcting these defects “Why?” Regression Testing Canned test runs to verify that new defects were not introduced during “debugging” session. Not exhaustive Targeted to a particular interface components, sub-systems, integrated system Different levels (lengths) of regression tests Targeted regressions The Test Plan Planning should begin right after requirements specification Acceptance tests can be written then System, sub-system tests can be written against designs The Test Plan Software Inspections (code reviews) 60% of program errors can be detected in code review [Fagan86] 90% if more formal approach used (e.g. “Cleanroom” process) [Mills87] (We’ll talk about Cleanroom later) Software Inspections (code reviews) Why are reviews more effective for finding defects in systems/subsystems (i.e., before acceptance testin

文档评论(0)

almm118 + 关注
实名认证
内容提供者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档