Collaborative document inspection technique used for?
Requirement Validation Process
Requirements validation checks that the requirements document actually defines the system the customer wants. Sommerville lists requirements reviews as the principal validation technique: a team of stakeholders and engineers reads the requirements document together and systematically looks for errors, ambiguities, omissions and conflicts.
Such a review is a collaborative document inspection: the participants jointly inspect a document rather than executing code. Pressman likewise names the technical review as the primary requirements validation mechanism, with other techniques being prototyping and test-case generation.
Verification refers to checking that a product conforms to its specification (building the product right); it is not the name used for the stakeholder inspection of the requirements document itself.
Integration testing and black-box testing are dynamic testing activities that execute software, not inspections of a document.
Requirement Validation Process option is correct.
Similar Questions
To compute function points (FP), the following relationship is used
FP = Count – total × (0.65 + 0.01 × Σ(Fi)) where Fi (i = 1 to n) are value adjustment factors (VAF) based on n questions. The value of n is
Which one of the following statements, related to the requirements phase in Software Engineering, is incorrect ?
In CRC based design, a CRC Team consists of :
(a) one or two users representatives
(b) several programmers
(c) project co-ordinators
(d) one or two system analysts
Codes :
Which one of the following non-functional quality attributes is not highly affected by the architecture of the software ?
Requirements prioritisation and negotiation belongs to :
Match the following :
(a) Size-oriented metrics (i) uses number of external interfaces as one of the measurement parameter. (b) Function-oriented metrics (ii) originally designed to be applied to business information systems. (c) Extended Function Point metrics (iii) derived by normalizing quality and/or productivity measures by considering the size of the software. (d) Function point (iv) uses algorithm characteristics as one of the measurement parameter. Codes :
Match the following :
List - I List - II a. Correctness i. The extent to which a software tolerates the unexpected problems b. Accuracy ii. The extent to which a software meets its specifications c. Robustness iii. The extent to which a software has specified functions d. Completeness iv. Meeting specifications with precision Consider a project with the following functional units :
Number of user inputs = 50
Number of user outputs = 40
Number of user enquiries = 35
Number of user files = 06
Number of external interfaces = 04
Assuming all complexity adjustment factors and weighing factors as average, the function points for the project will be
In function point analysis, the number of complexity adjustment factors is
Which one of the following is not the part of requirement management?
Important Questions from Software Requirement
What is the other name of Data Flow Diagram (DFD)?
- Which of the followings belongs to MaCall's quality factors?
A. Maintainability
B. Usability
C. Integrity
D. Functionality
Choose the correct answer from the options given below: - Which of the following is not a requirement elicitation Technique
The process followed in order to find difficult, unknown and hidden information about a software system is called
- Which of the followings is NOT a software characteristic?
