Requirement Engineering

A. Consistent
B. Verifiable
C. Non-verifiable
D. Correct

A. black-box
B. white-box
C. grey-box
D. none of the mentioned

A. its structure and style are such that any changes to the requirements can be made easily while retaining the style and structure
B. every requirement stated therein is one that the software shall meet
C. every requirement stated therein is verifiable
D. no subset of individual requirements described in it conflict with each other

A. Verifiable
B. Ambiguous
C. Complete
D. Traceable

A. JAD
B. Traceability
C. FAST
D. Both JAD and Traceability

A. Primary
B. Secondary
C. Ternary
D. Both Primary and Secondary

A. Known, Unknown, Undreamed
B. User, Developer
C. Functional, Non-Functional
D. Normal, Expected, Exciting

A. Identifying Stakeholder
B. Listing out Requirements
C. Requirements Gathering
D. All of the mentioned

A. Object Oriented Design (by Booch)
B. Use Cases (by Jacobson)
C. Fusion (by Coleman)
D. Object Modeling Technique (by Rumbaugh)

i. Consolidation
ii. Prioritization
iii. Requirements Gathering
iv. Evaluation

A. iii, i, ii, iv
B. iii, iv, ii, i
C. iii, ii, iv, i
D. ii, iii, iv, i