Engineering
Engineering MCQs With Answers
0 Engineering MCQs for CSS, PPSC, FPSC, NTS and entry-test preparation. Take a scored quiz instead →
The software maintenance metric representing the percentage of software changes that introduce new defects into the system is the:
AMean Time To Repair
BCode Turnover Ratio
CFix Latency Index
DChange Error Rate (Defect Injection Rate)
According to Lientz and Swanson, which category accounts for the largest proportion (over 50%) of total software maintenance effort?
ACorrective Maintenance
BAdaptive Maintenance
CPerfective Maintenance
DPreventive Maintenance
Modifying software to enhance user features, improve code performance, or optimize execution speed based on user feedback is:
APerfective Maintenance
BCorrective Maintenance
CAdaptive Maintenance
DPreventive Maintenance
Modifying software proactively to detect and fix latent software faults before they manifest as operational failures is:
ACorrective Maintenance
BPreventive Maintenance
CAdaptive Maintenance
DEmergency Maintenance
Modifying a software application to keep it functional in response to changes in operating systems, hardware, or database environments is:
ACorrective Maintenance
BPerfective Maintenance
CPreventive Maintenance
DAdaptive Maintenance
In Software Maintenance, modifying software to fix bugs and operational failures discovered during production execution is:
AAdaptive Maintenance
BPerfective Maintenance
CCorrective Maintenance
DPreventive Maintenance
Verification checking that an SRS contains all necessary functional descriptions required by the customer is checking for:
AConsistency
BCompleteness
CModifiability
DPortability
A prototyping approach where software begins as a simple core model and is iteratively refined until it becomes the final production system is:
AThrowaway Prototyping
BPaper Prototyping
CStatic Mockup
DEvolutionary Prototyping
In Requirements Validation, verifying that software requirements do not contradict each other across different documentation sections is checking for:
AConsistency
BCompleteness
CTraceability
DVerifiability
In Requirements Engineering, a prototype built solely to clarify ambiguous requirements and discarded after requirement validation is a:
AEvolutionary Prototype
BIncremental System
CThrowaway Prototype
DProduction Baseline
