'validation'에 해당되는 글 1건

  1. 2008/04/05 V&V : Verification and validation 1/3 (2)
본 포스트는 개인 스터디 용으로 작성된 Ian Sommerville의 Software Engineering, 8/E의 요약본입니다.
1. Verification vs validation
- Verification : "Are we building the product right?". conform to its specification
- Validation : "Are we building the right product?". do what the user really requires

2. The V&V process
- Whole life-cycle process : V&V must be applied at each stage in the S/W process
- Principal objectives
  1) The discovery of defects in a system
  2) The assessment of whether or not the system is useful and useable in an operational situation

3. V&V goals
- V&V should establish confidence that the S/W is fit for purpose
- This does NOT mean completely free of defects

4. V&V confidence (leveling of confidence)
- depends on system's purpose, user expectations and marketing environment
1) S/W function : The level of confidence dependes on how critical the S/W is to an organisation
2) User expectations : User may have low expectations of certain kinds of S/W
3) Marketing environment : Getting a product to market early may be more important than finding defects in the program

5. Static and dynamic verification
- S/W inspections : concerned with analysis of the static system representation to discover problems(static verification)
- S/W testing : concerned with exercising and observing product behaviour(dynamic verification)
사용자 삽입 이미지

6. Program testing
- reveal the presence of errors NOT their absence
- The only validation technique for non-functional requirements as the S/W has to be executed to see how it behaves(??)
- Types of testing
  1) Defect testing : tests designed to discover system defects
  2) Validation testing : intended to show that the S/W meets its requirements

7. Testing and debugging
- V&V is concerned with establishing the existence of defects in a program.
- Debugging is concerned with locating and repairing these errors
사용자 삽입 이미지

8. V-model of development
사용자 삽입 이미지
사용자 삽입 이미지사용자 삽입 이미지

9. S/W test plan (things to consider)
- Test testing process
- Requirements traceability
- Tested items
- Testing schedule
- Test recording procedures
- H/W and S/W requirements
- Constraints
2008/04/05 15:02 2008/04/05 15:02

트랙백 주소 :: http://anyflow.net/trackback/378

댓글을 달아 주세요

  1. Qastation 2008/04/14 16:26  댓글주소  수정/삭제  댓글쓰기

    Excellent post