Software-requirements
Question 1 |
SRD stands for _____.
Software Requirements Definition | |
Structured Requirements Definition | |
Software Requirements Diagram | |
Structured Requirements Diagram | |
A and B |
Question 2 |
Which of the following is NOT the characteristic of a good Software Requirement Specification?
completeness | |
verifiability | |
modifiability | |
short size of code |
Question 3 |
Which of the following is not a requirement elicitation technique?
Interviews
| |
The use-case approach
| |
Facilitated Application Specification Technique (FAST)
| |
Data Flow Diagram
|
Question 4 |
Which one of the following is not the part of requirement management?
Features Traceability Table | |
Dependency Traceability Table | |
Interface Traceability Table | |
Page Traceability Table |
Question 5 |
Collaborative document inspection technique used for?
Requirement Validation Process | |
Requirement Verification Process | |
Integration Testing | |
Blackbox Testing |
Question 6 |
_______is intended to show that a system both conforms to its specifications and meets the expectations of the system customer.
Software specification
| |
Software design
| |
Software evaluation
| |
Software validation |
Question 6 Explanation:
"Software validation" is the process intended to show that a system both conforms to its specifications and meets the expectations of the system customer. It involves evaluating the software to ensure that it does what it's supposed to do and that it satisfies the customer's needs and requirements.
Question 7 |
The process to gather the software requirements from client, analyze and document is known as
Software Engineering Process
| |
User Engineering Process
| |
Requirement Elicitation Process
| |
Requirement Engineering Process |
There are 7 questions to complete.