Q: What is the full form of SRS? A: Software Requirements Specification — the document
that defines what the software should do. - Software Resource Specification - Software Requirements Specification - System Requirement Schedule - Standard Requirements Specification
Q: Which is a Non-Functional Requirement? A: “System should process 1000 transactions per
second” — a performance (non-functional) requirement. - User should be able to login - System should process 1000 transactions per second - System should allow photo uploads - None of the above
Q: The process of gathering requirements from stakeholders is called: A: Elicitation — the
first phase of requirements engineering. - Elicitation - Implementation - Maintenance - Testing
Q: IEEE 830 is a standard for: A: SRS Document — it defines the recommended structure and
content for a Software Requirements Specification. - Coding - Hardware - SRS Document - Testing
Q: At which CMM level are processes quantitatively managed? A: Level 4 — Managed.
Processes have defined metrics and are controlled statistically. - Level 2 — Repeatable - Level 3 — Defined - Level 4 — Managed - Level 5 — Optimizing
Q: What does a traceability matrix ensure? A: Every requirement is linked to its source,
design, code, and test — proving full coverage and no orphaned work. - Code is well-documented - Every requirement is addressed and testable - The project is on schedule - All bugs are fixed
Q: Which elicitation technique is best when requirements are very unclear? A: Prototyping
— building a mock-up helps users discover and articulate what they actually need. - Surveys - Prototyping - Document analysis - Observation
Premium Content
Unlock SRS & Requirements Quiz and all premium lessons with a subscription.
From ₹199.99/year — See plans