Engineering
Engineering MCQs With Answers
0 Engineering MCQs for CSS, PPSC, FPSC, NTS and entry-test preparation. Take a scored quiz instead →
The Critical Path Method (CPM) in software project scheduling determines:
AThe sequence of dependent tasks that defines the minimum total time required to complete the project
BThe path with the highest financial cost
CThe tasks with maximum buffer slack time
DThe sequence of unassigned developer tasks
What is the difference between Software Verification and Software Validation?
AVerification involves dynamic code execution; Validation involves static code inspection
BVerification ensures building the product right; Validation ensures building the right product
CVerification is done by end-users; Validation is done by developers
DVerification checks non-functional performance; Validation checks functional specifications
In project management network diagrams, total float (or slack time) represents:
AThe time required to compile the software codebase
BThe amount of time a task can be delayed without delaying the project completion date
CThe total overtime worked by software engineers
DThe total buffer reserved for bug fixing
Static software verification techniques performed without executing program code include:
AUnit Testing and Integration Testing
BStress Testing and Load Testing
CCode Inspections, Walkthroughs, and Static Analysis
DAlpha and Beta Acceptance Testing
Tasks located on the Critical Path in a PERT/CPM software project network diagram always have a Total Float of:
AMaximum Float
BPositive Float equal to 10 days
CZero Float
DNegative Float
In Integration Testing, combining all software modules simultaneously to test the entire system at once without incremental integration is called:
ATop-Down Integration
BBottom-Up Integration
CSandwich Integration
DBig-Bang Integration
In Function Point Analysis (FPA), software functionality is evaluated across five primary components: External Inputs, External Outputs, External Inquiries, Internal Logical Files, and:
ADatabase Table Constraints
BSystem Call Routines
CHardware Memory Allocation
DExternal Interface Files
In Top-Down Integration Testing, dummy control routines used to simulate lower-level modules that are not yet developed are called:
AStubs
BDrivers
CMocks
DSpies
Which SOLID principle states that software entities (classes, modules, functions) should be open for extension, but closed for modification?
ALiskov Substitution Principle (LSP)
BOpen-Closed Principle (OCP)
CInterface Segregation Principle (ISP)
DSingle Responsibility Principle (SRP)
According to the Liskov Substitution Principle (LSP), objects of a superclass should be replaceable with objects of its subclasses without:
AIncreasing execution time
BChanging database schemas
CAltering the correctness of the program
DModifying compiler settings