A. Unit, integration, system and maintenance.

B. Unit, component, functional and alpha/beta.

C. Functional, glass box, incremental and maintenance.

D. Component, integration, system and acceptance.

A. c 및 d

B. 및 b

C. b 및 d

D. c 및 e

A. 기능 사양의 기술 검토.

B. 요구 사항 문서의 안내입니다.

C. 프로그램 사양의 비공식 검토.

D. 소프트웨어 모델의 정적 분석.

A. They should minimize the ratio of development levels to test levels to reduce project costs

B. They should be involved in reviewing requirements or user stories as soon as drafts are available

C. They should start test analysis when the corresponding development level is complete

D. They should ensure that the same test objectives apply to each test level

A. 오류

B. 결함

C. 실수

D. 실패

E. 결함