<ruby id="h6500"><table id="h6500"></table></ruby>
    1. <ruby id="h6500"><video id="h6500"></video></ruby>
          1. <progress id="h6500"><u id="h6500"><form id="h6500"></form></u></progress>
            • 軟件測試技術(shù)
            • 軟件測試博客
            • 軟件測試視頻
            • 開(kāi)源軟件測試技術(shù)
            • 軟件測試論壇
            • 軟件測試沙龍
            • 軟件測試資料下載
            • 軟件測試雜志
            • 軟件測試人才招聘
              暫時(shí)沒(méi)有公告

            字號: | 推薦給好友 上一篇 | 下一篇

            Entry Criteria and Exit Criteria

            發(fā)布: 2011-3-15 13:24 | 作者: 不詳 | 來(lái)源: 領(lǐng)測軟件測試網(wǎng)采編 | 查看: 27次 | 進(jìn)入軟件測試論壇討論

            領(lǐng)測軟件測試網(wǎng)

              Entry Criteria and Exit Criteria   軟件測試

              Entry Criteria: The conditions that must exist before a unit of project work can commence.

              Exit Criteria: The conditions that must exist before a unit of project work can be deemed complete.

              Entry Criteria for Unit testing phase are:

              The following documents have been completed, reviewed and approved:

              1. Business Requirement Document complete

              2. Program Required Documents complete

              3. Preliminary Software Development Project Plan

              4. Phase 1 Planning

              5. Functional Specification

              6. High-Level Design Specifications

              7. Software Development Project Plan approved

              8. Software Verification Plan approved

              9. Software Configuration Management Plan

              10. Quality Assurance Plan approved.

              Exit criteria for the Unit testing phase are:

              1. Unit test has been passed

              2. The module resides in a baseline directory

              3. The project is code-complete. There are no missing features or media elements

              4. All priority a bug have been fixed and closed

              5. Internal documentation has been updated to reflect the current state of the product. Note: Unit testing will be performed mostly by the Developer.

              Entry Criteria for Integration testing phase are:

              1. The project is code-complete. There are no missing features or media elements

              2. The product satisfies the performance and memory requirements specified by the Functional Spec.

              3. Software/Curriculum have run and passed a Sanity Test that has been provided by the QA group.

            延伸閱讀

            文章來(lái)源于領(lǐng)測軟件測試網(wǎng) http://kjueaiud.com/

            21/212>

            關(guān)于領(lǐng)測軟件測試網(wǎng) | 領(lǐng)測軟件測試網(wǎng)合作伙伴 | 廣告服務(wù) | 投稿指南 | 聯(lián)系我們 | 網(wǎng)站地圖 | 友情鏈接
            版權所有(C) 2003-2010 TestAge(領(lǐng)測軟件測試網(wǎng))|領(lǐng)測國際科技(北京)有限公司|軟件測試工程師培訓網(wǎng) All Rights Reserved
            北京市海淀區中關(guān)村南大街9號北京理工科技大廈1402室 京ICP備10010545號-5
            技術(shù)支持和業(yè)務(wù)聯(lián)系:info@testage.com.cn 電話(huà):010-51297073

            軟件測試 | 領(lǐng)測國際ISTQBISTQB官網(wǎng)TMMiTMMi認證國際軟件測試工程師認證領(lǐng)測軟件測試網(wǎng)

            老湿亚洲永久精品ww47香蕉图片_日韩欧美中文字幕北美法律_国产AV永久无码天堂影院_久久婷婷综合色丁香五月
              <ruby id="h6500"><table id="h6500"></table></ruby>
              1. <ruby id="h6500"><video id="h6500"></video></ruby>
                    1. <progress id="h6500"><u id="h6500"><form id="h6500"></form></u></progress>