Engineering
Engineering MCQs With Answers
0 Engineering MCQs for CSS, PPSC, FPSC, NTS and entry-test preparation. Take a scored quiz instead →
The mythical law in software engineering stating that ‘adding manpower to a late software project makes it later’ is known as:
ABoehm's Law
BConway's Law
CBrooks' Law
DMoore's Law
Conway’s Law states that organizations design software systems that mirror:
AThe hardware limitations of host servers
BThe programming language design paradigms
CThe competitive market structures
DTheir own communication structures
In Object-Oriented Software Engineering, hiding internal state details of an object and restricting direct access via getter/setter methods is:
AEncapsulation
BPolymorphism
CAbstraction
DInheritance
The ability of different objects to respond to the same message or method call in their own unique manner is known as:
AEncapsulation
BPolymorphism
CAbstraction
DGeneralization
In object-oriented modeling, a relationship representing a ‘has-a’ whole-part connection where child components CAN exist independently of the whole container is:
AComposition
BGeneralization
CAggregation
DDependency
A strong whole-part ownership relationship where child objects CANNOT exist independently of their parent container (e.g., Building and Rooms) is:
AAggregation
BAssociation
CRealization
DComposition
In Requirements Engineering, the process of resolving conflicting requirements between different stakeholders is known as:
ARequirement Negotiation
BRequirement Elicitation
CRequirement Specification
DRequirement Validation
Which document serves as the formal contractual agreement between software developers and customers detailing system functionality?
ASoftware Architecture Document (SAD)
BSoftware Requirement Specification (SRS)
CTest Summary Report
DProject Charter
According to IEEE standards, an ideal Software Requirement Specification (SRS) document must be:
ABrief, Informal, Abstract, and Flexible
BCode-Centric, Technical, Complex, and Rigid
CUnambiguous, Complete, Verifiable, and Consistent
DRedundant, Variable, Dynamic, and Subjective
The phenomenon where software requirements continuously expand during development beyond original scope limits is termed:
AFeature Bloat
BRequirement Drift
CArchitecture Erosion
DScope Creep