Software Engineering II MCQs with Answers
Practice important Software Engineering II MCQs with answers and explanations.
Chapter: 37
Q1061:
The purpose of requirement traceability is to _______.
A. Manage the origin and implementation of requirements
B. Track project costs
C. Test individual software components
D. Increase the number of requirements
Correct Answer:
A
Chapter: 37
Q1062:
Traceability in requirements management is important for _______.
A. Certification and testing
B. Budgeting and scheduling
C. Code optimization
D. User interface design
Correct Answer:
A
Chapter: 37
Q1063:
In requirement traceability, the rationale of requirements must also be _______.
A. Traced
B. Deleted
C. Ignored
D. Reviewed
Correct Answer:
A
Chapter: 37
Q1064:
Managing change activity involves tracking the _______ of change requests.
A. Number, origin, and status
B. Time and effort
C. Implementation and verification
D. Stakeholder approval
Correct Answer:
A
Chapter: 37
Q1065:
Requirement traceability is essential for _______.
A. Maintenance and reengineering
B. Advertising and marketing
C. Managing user interfaces
D. Managing external vendors
Correct Answer:
A
Chapter: 37
Q1066:
Change impact analysis benefits from _______ traceability.
A. Both ways (origin to implementation)
B. Project to testing
C. Design to coding
D. Testing to release
Correct Answer:
A
Chapter: 37
Q1067:
The status of a requirement that has been requested but not yet analyzed is _______.
A. Proposed
B. Approved
C. Implemented
D. Verified
Correct Answer:
A
Chapter: 37
Q1068:
The number of changes proposed and made in each requirement is tracked after it is _______.
A. Baseline
B. Verified
C. Deleted
D. Proposed
Correct Answer:
A
Chapter: 37
Q1069:
Tracking requirement changes by origin helps in _______.
A. Strengthening future project processes
B. Increasing the project timeline
C. Reducing project scope
D. Managing project budgets
Correct Answer:
A
Chapter: 37
Q1070:
A Software Requirement Specification (SRS) must be _______ for effective change management.
A. Traceable
B. Ignored
C. Detached
D. Deleted
Correct Answer:
A
Chapter: 37
Q1071:
Measuring the total effort devoted to handling changes is part of tracking _______.
A. Change activity
B. Requirement status
C. Software testing
D. User feedback
Correct Answer:
A
Chapter: 37
Q1072:
The change request status that indicates the requirement has been implemented and unit tested is _______.
A. Implemented
B. Approved
C. Proposed
D. Deleted
Correct Answer:
A
Chapter: 37
Q1073:
The impact of a change request is analyzed by the _______.
A. Evaluator
B. Originator
C. Developer
D. Tester
Correct Answer:
A
Chapter: 37
Q1074:
The status of a requirement that has been analyzed and allocated to a baseline is _______.
A. Approved
B. Proposed
C. Implemented
D. Deleted
Correct Answer:
A
Chapter: 37
Q1075:
Change requests can originate from _______.
A. Various sources such as customers and developers
B. The project manager only
C. The testing team only
D. External vendors
Correct Answer:
A
Chapter: 37
Q1076:
A requirement is considered complete after it has been _______.
A. Verified
B. Proposed
C. Deleted
D. Approved
Correct Answer:
A
Chapter: 37
Q1077:
Requirements that have not been traceable can _______.
A. Be hard to manage effectively
B. Be implemented easily
C. Not require approval
D. Be ignored during testing
Correct Answer:
A
Chapter: 37
Q1078:
Traceability of requirements is a continuous _______ throughout the project.
A. Process
B. Review
C. Analysis
D. Approval
Correct Answer:
A
Chapter: 38
Q1079:
What is a system called that has been in operation for many years?
A. Current system
B. New system
C. Legacy system
D. Modern system
Correct Answer:
C
Chapter: 38
Q1080:
Which of the following is a component of a legacy system?
A. Business processes
B. Internet router
C. Mobile apps
D. Cloud servers
Correct Answer:
A