Software Engineering MCQs (Set-1)

Which activity establishes required system capabilities?

A Source-code compilation
B Requirements analysis
C System deployment
D User training

Why is an SRS prepared?

A Generate executable code
B Measure test coverage
C Assign developer salaries
D Record agreed requirements

During a feasibility study, what is assessed?

A Project viability
B Screen color choices
C Code formatting
D Test pass rate

What maps an actor's goal to system interactions?

A Class variable
B Build script
C Use case
D Release note

Which requirement specifies required system behavior?

A Functional requirement
B Quality target
C Design constraint
D Test fixture

Where are response-time limits usually recorded?

A Functional requirement
B Design pattern
C Test fixture
D Nonfunctional requirement

Who counts as a project stakeholder?

A Compiler output
B Database table
C Affected or influencing party
D Test environment

How can a prototype help a team?

A Replace code review
B Clarify user expectations
C Measure code coverage
D Approve production release

Which lifecycle model orders phases sequentially?

A Spiral model
B Scrum framework
C Waterfall model
D Kanban method

What characterizes iterative development?

A Repeated refinement cycles
B One final delivery
C No user feedback
D Fixed design forever

Under Scrum, who is accountable for maximizing product value?

A Scrum Master
B Developers
C Project sponsor
D Product Owner

For Scrum, what is a Sprint?

A Unplanned release window
B Fixed-length work cycle
C One testing technique
D A project budget

Where is the product work kept and ordered?

A Product Backlog
B Sprint Review
C Definition of Done
D Release report

What does the Daily Scrum help Developers do?

A Approve the project budget
B Assign all product roles
C Inspect Sprint Goal progress
D Release every code change

Why use version control?

A Replace requirements analysis
B Guarantee defect-free code
C Choose user-interface colors
D Preserve change history

How is a code review usually performed?

A Automatic deployment
B Peer examination
C User acceptance testing
D Database normalization

Why divide software into modules?

A Increase global dependencies
B Avoid all testing
C Manageable separate components
D Remove user requirements

When responsibilities in a module are closely related, it has?

A High cohesion
B High fan-out
C Low cohesion
D External coupling

Which coupling level is generally preferred?

A Common coupling
B Content coupling
C Global coupling
D Low coupling

Which tests focus on one small component?

A System tests
B Acceptance tests
C Unit tests
D Operational tests

Integration testing examines what?

A Component interactions
B Stakeholder priorities
C Source formatting
D Project feasibility

What does system testing evaluate?

A One code statement
B Complete integrated system
C A single developer
D A project estimate

How does acceptance testing judge a solution?

A Against coding style
B Against build speed
C Against team roles
D Against acceptance criteria

After a change, regression testing checks that?

A New requirements are elicited
B The project is feasible
C Existing behavior remains intact
D Modules are renamed

After release, software maintenance involves?

A Initial stakeholder interviews
B Changes after delivery
C First architecture design
D Only source compilation