Software Engineering
Software Engineering MCQs with Answers
Software engineering MCQs with answers and detailed explanations for NTS, GAT, university tests and IT job interviews. SDLC, testing and design covered. Take a scored quiz instead →
The Software Configuration Management process of creating a record of changes, release notes, and build manifests for audit compliance is:
AVersion Branching
BConfiguration Audit & Status Accounting
CCode Refactoring
DRegression Testing
In Object-Oriented metrics, Coupling Between Object Classes (CBO) measures:
AThe total methods in a class hierarchy
BThe depth of the inheritance tree
CThe number of unit tests written for a class
DThe number of other non-inherited classes to which a class is coupled
In Software Cost Estimation, COCOMO II replaces KLOC with which alternative early-stage size metric when source code is not yet written?
AUnadjusted Function Points (UFP) / Object Points
BCyclomatic Complexity
CNumber of Database Tables
DClass Inheritance Depth
In Software Maintenance, Lehman’s Law of Increasing Complexity states that as an evolving system changes, its structural complexity:
ADecreases automatically with each patch
BIncreases unless active work is done to maintain or simplify it
CRemains perfectly static
DIs unaffected by bug fixes
In Object-Oriented metrics, the Lack of Cohesion in Methods (LCOM) metric measures:
AThe number of subclasses
BThe execution speed of class methods
CThe degree of dissimilarity or un-relatedness among methods in a class based on shared instance variables
DThe total lines of code in a class
In Software Maintenance, Lehman’s Law of Continuing Change states that a software application used in a real-world environment must:
AContinually evolve and adapt, or become progressively less useful
BDecrease in complexity over time automatically
CMaintain fixed cost structures
DRequire zero corrective patches
In Object-Oriented Design, the principle that clients should not be forced to depend on interface methods they do not use is the:
ADependency Inversion Principle (DIP)
BSingle Responsibility Principle (SRP)
CInterface Segregation Principle (ISP)
DOpen-Closed Principle (OCP)
In Object-Oriented Design, the principle that high-level modules should not depend on low-level modules, but both should depend on abstractions is the:
AInterface Segregation Principle (ISP)
BLiskov Substitution Principle (LSP)
CSingle Responsibility Principle (SRP)
DDependency Inversion Principle (DIP)
In Object-Oriented Design, the principle that derived classes must be completely substitutable for their base classes without breaking system behavior is the:
ALiskov Substitution Principle (LSP)
BSingle Responsibility Principle (SRP)
COpen-Closed Principle (OCP)
DInterface Segregation Principle (ISP)
In Object-Oriented Design, the principle that software entities should be open for extension but closed for modification is the:
ALiskov Substitution Principle (LSP)
BOpen-Closed Principle (OCP)
CDependency Inversion Principle (DIP)
DSingle Responsibility Principle (SRP)