Q.1 What does SRS stand for in software engineering?
Software Requirement Specification
System Resource Sheet
Software Revision Schedule
System Requirement Setup
Explanation - SRS stands for Software Requirement Specification, which is a detailed description of the software system to be developed.
Correct answer is: Software Requirement Specification
Q.2 Which of the following is NOT a characteristic of a good SRS?
Unambiguous
Incomplete
Consistent
Verifiable
Explanation - A good SRS must be complete, unambiguous, consistent, and verifiable. 'Incomplete' is not a desirable characteristic.
Correct answer is: Incomplete
Q.3 SRS is typically created during which phase of the software development lifecycle?
Design Phase
Requirement Analysis Phase
Coding Phase
Testing Phase
Explanation - SRS is created during the Requirement Analysis phase to document the requirements before design and implementation.
Correct answer is: Requirement Analysis Phase
Q.4 Which of the following is a functional requirement?
The system shall generate monthly reports
The system shall respond within 2 seconds
The system shall be available 99% of the time
The system shall be scalable to 10,000 users
Explanation - Functional requirements specify what the system should do, such as generating reports, whereas others are non-functional requirements.
Correct answer is: The system shall generate monthly reports
Q.5 Which document acts as a contract between customer and developer?
Design Document
Software Requirement Specification
Test Plan
Project Charter
Explanation - SRS serves as the agreement between customer and developer, ensuring both parties have a clear understanding of requirements.
Correct answer is: Software Requirement Specification
Q.6 Which of the following is NOT part of an SRS?
Functional requirements
Non-functional requirements
User manual
System constraints
Explanation - A user manual is a separate document, while SRS contains functional, non-functional requirements, and constraints.
Correct answer is: User manual
Q.7 What is the primary purpose of SRS?
To design software architecture
To define requirements clearly
To code the software
To test the system
Explanation - SRS is mainly used to clearly define and document the requirements of the software system.
Correct answer is: To define requirements clearly
Q.8 Which quality of SRS ensures that all requirements are stated only once?
Completeness
Consistency
Non-redundancy
Correctness
Explanation - Non-redundancy in SRS ensures no repetition of requirements, reducing confusion and errors.
Correct answer is: Non-redundancy
Q.9 Which of these describes non-functional requirements?
System performance and reliability
User authentication module
Payment gateway integration
Report generation
Explanation - Non-functional requirements specify quality attributes like performance, security, and reliability.
Correct answer is: System performance and reliability
Q.10 Who is the main audience for SRS?
End users only
Software testers only
Developers, testers, and stakeholders
System administrators only
Explanation - SRS is written for all parties including developers, testers, and stakeholders to ensure shared understanding.
Correct answer is: Developers, testers, and stakeholders
Q.11 Which of the following is a benefit of SRS?
Faster coding without bugs
Better communication between stakeholders
Elimination of the need for testing
Automatic system deployment
Explanation - SRS improves communication between stakeholders by providing a clear and agreed-upon document of requirements.
Correct answer is: Better communication between stakeholders
Q.12 Ambiguity in SRS leads to:
Clear requirements
Misinterpretation of requirements
Faster development
Reduced documentation
Explanation - Ambiguity in SRS results in misinterpretation and conflicts during development.
Correct answer is: Misinterpretation of requirements
Q.13 Which model is often used for writing SRS?
Waterfall model
Prototype model
IEEE 830 standard
Agile methodology
Explanation - The IEEE 830 standard provides guidelines for writing well-structured SRS documents.
Correct answer is: IEEE 830 standard
Q.14 Which requirement specifies 'how well' the system should perform?
Functional requirement
Non-functional requirement
Business requirement
Domain requirement
Explanation - Non-functional requirements describe quality attributes such as performance, scalability, and usability.
Correct answer is: Non-functional requirement
Q.15 Which type of diagram is often included in SRS?
Flowcharts
Use Case Diagrams
ER Diagrams
Class Diagrams
Explanation - Use Case Diagrams are included in SRS to depict system interactions with users.
Correct answer is: Use Case Diagrams
Q.16 Correctness of SRS means:
Requirements match user needs
Requirements are technically feasible
Requirements are testable
Requirements are minimal
Explanation - Correctness in SRS ensures that the documented requirements accurately reflect user needs.
Correct answer is: Requirements match user needs
Q.17 Which of these is a non-functional requirement?
System shall allow login
System shall store student data
System shall encrypt passwords
System shall print results
Explanation - Encryption relates to security, which is a non-functional requirement.
Correct answer is: System shall encrypt passwords
Q.18 Why should SRS be verifiable?
So developers can test requirements
So SRS can be reused
So SRS can be written quickly
So SRS can reduce cost
Explanation - A verifiable SRS allows requirements to be tested and validated objectively.
Correct answer is: So developers can test requirements
Q.19 Which of these is NOT a common problem in SRS?
Ambiguity
Inconsistency
Redundancy
Automation
Explanation - Automation is not a problem in SRS, but ambiguity, inconsistency, and redundancy often occur.
Correct answer is: Automation
Q.20 The completeness property of SRS ensures:
All possible inputs are handled
All necessary requirements are specified
All test cases are defined
All bugs are fixed
Explanation - Completeness in SRS means all necessary requirements are included and nothing essential is missing.
Correct answer is: All necessary requirements are specified
Q.21 Which of these is a constraint in SRS?
System must be delivered within 6 months
System must process payments
System must generate invoices
System must allow registration
Explanation - Delivery time is a constraint, while the others are functional requirements.
Correct answer is: System must be delivered within 6 months
Q.22 Who is responsible for preparing the SRS?
Project Manager
System Analyst
Software Tester
End User
Explanation - System Analysts usually prepare the SRS by gathering and documenting requirements from stakeholders.
Correct answer is: System Analyst
Q.23 Traceability in SRS means:
Each requirement can be tracked throughout development
Each requirement is coded once
Each requirement is tested only once
Each requirement is verified by user
Explanation - Traceability ensures that each requirement is tracked from its origin to final implementation.
Correct answer is: Each requirement can be tracked throughout development
Q.24 Which standard is widely used for SRS documentation?
ISO 9001
IEEE 830
CMMI
ISO 27001
Explanation - IEEE 830 is the standard that provides guidelines for SRS documentation.
Correct answer is: IEEE 830
Q.25 What is the role of feasibility study before SRS?
To check coding standards
To check design models
To check whether the project is viable
To check system testing approach
Explanation - Feasibility study ensures that the project is technically, economically, and legally viable before creating SRS.
Correct answer is: To check whether the project is viable