1. **What do functional requirements primarily describe?

**

a) System performance metrics

b) Core functionalities and features of the system

c) Budget constraints of the project

d) User interface aesthetics

**Answer:** b) Core functionalities and features of the system

2. **Functional requirements are typically expressed from whose perspective?**

a) Developer’s perspective

b) Stakeholder’s perspective

c) User’s perspective

d) Project manager’s perspective

**Answer:** c) User’s perspective

3. **Which statement best defines functional requirements?**

a) They describe how fast the system should respond.

b) They outline what the system must do under specific conditions.

c) They specify the programming language to be used.

d) They define the color scheme of the user interface.

**Answer:** b) They outline what the system must do under specific conditions.

---

### **Examples of Functional Requirements**

4. **Which of the following is an example of a functional requirement?**

a) The system must load within 2 seconds.

 b) Users must log in with a valid username and password.

c) The software must be compatible with all browsers.

d) The database must be encrypted.

**Answer:** b) Users must log in with a valid username and password.

5. **Generating monthly financial reports in PDF format is an example of:**

a) A non-functional requirement

b) A functional requirement

c) A system constraint

d) A user story

**Answer:** b) A functional requirement

6. **Which requirement ensures integration with third-party payment services?**

a) Login functionality

b) Report generation

c) Payment gateway integration

d) User registration

**Answer:** c) Payment gateway integration

7. **"Processing orders and calculating total costs with tax" is associated with:**

a) Security requirements

b) Functional requirements

c) Performance requirements

d) Legal requirements

**Answer:** b) Functional requirements

---

### **Importance of Functional Requirements**

8. **Why are functional requirements critical for testing?**

a) They define the system’s scalability.

b) They serve as the basis for validating system correctness.

c) They outline the project timeline.

d) They specify hardware requirements.

**Answer:** b) They serve as the basis for validating system correctness.

9. **Functional requirements help align development with:**

a) Budget constraints

b) Stakeholder expectations

c) Marketing strategies

d) Team-building activities

**Answer:** b) Stakeholder expectations

10. **How do functional requirements guide developers?**

a) By specifying system aesthetics

b) By directing the design of system features

c) By defining team roles

d) By setting deadlines

**Answer:** b) By directing the design of system features

---
### **Documentation Formats**

11. **Which format describes interactions between users and the system to complete tasks?**

a) User stories

b) System specifications

c) Use cases

d) Flowcharts

**Answer:** c) Use cases

Here are **True/False** and **Fill-in-the-Blanks** questions based on the provided document
about **Requirement Engineering**:

---

### **True/False Questions**

1. **True/False:** Requirements engineering is a one-time phase that ends before

development begins.

**Answer:** False

2. **True/False:** The feasibility study evaluates technical, economic, and operational viability.

**Answer:** True

3. **True/False:** Prototyping is a technique used during requirement validation.

**Answer:** True

4. **True/False:** The Waterfall Model is highly flexible for changing requirements.

**Answer:** False

5. **True/False:** Ambiguous requirements can lead to design flaws and delays.

 **Answer:** True

6. **True/False:** Overemphasis on documentation speeds up development in Agile

methodology.

**Answer:** False

7. **True/False:** Traceability ensures links between requirements and testing phases.

**Answer:** True

8. **True/False:** The Spiral Model ignores risk management.

**Answer:** False

9. **True/False:** Non-functional requirements include performance and security.

**Answer:** True

10. **True/False:** Scope creep reduces project delays and costs.

**Answer:** False

---

### **Fill-in-the-Blanks Questions**

1. **________ is the phase where requirements are validated through expert reviews or
prototyping.**

**Answer:** Software Requirement Validation

2. **The ________ document serves as a blueprint for development and includes functional
and non-functional requirements.**
 **Answer:** Software Requirement Specification (SRS)

3. **________ tools like Microsoft Visio help create use case diagrams and data flow
diagrams.**

**Answer:** Diagramming

4. **Uncontrolled additions to requirements leading to project delays are called ________.**

**Answer:** Scope creep

5. **The ________ Model combines iterative development with risk management.**

**Answer:** Spiral

6. **________ feasibility assesses whether a project aligns with organizational workflows.**

**Answer:** Operational

7. **________ requirements specify constraints like system performance and security.**

**Answer:** Non-functional

8. **________ tools like IBM DOORS support version control and traceability.**

**Answer:** Requirements Management

9. **The ________ approach prioritizes working software over comprehensive

documentation.**

**Answer:** Agile

10. **________ involves observing users to understand their workflow during requirement
elicitation.**
 **Answer:** Observation

---

### **Mixed Format (Advanced)**

1. **True/False:** Use Case-Driven RE focuses on technical architecture rather than user

interactions.

**Answer:** False

2. **Fill-in-the-Blank:** Detecting issues in requirements early prevents ________ errors and

misunderstandings later in development.

**Answer:** costly

3. **True/False:** The SRS includes details about data storage and processing.

**Answer:** True

4. **Fill-in-the-Blank:** ________ tools like Balsamiq create interactive UI mockups for

stakeholder feedback.

**Answer:** Prototyping

5. **True/False:** Neglecting non-functional requirements can compromise system security.

**Answer:** True

---

Let me know if you need more questions or adjustments! 😊

12. **"As a user, I want to reset my password to regain account access." This is an example
of:**

a) A use case

b) A system specification

c) A user story

d) A non-functional requirement

**Answer:** c) A user story

13. **Which document details inputs, outputs, and error management for a system?**

a) User manual

b) System specifications

c) Project charter

d) Risk assessment

**Answer:** b) System specifications

---

### **Advanced Questions**

14. **Functional requirements are LEAST likely to describe:**

a) User registration steps

b) System response time

c) Order processing rules

d) Report generation features

**Answer:** b) System response time (non-functional)

15. **Which is NOT a method to document functional requirements?**

 a) Use cases

b) User stories

c) Gantt charts

d) System specifications

**Answer:** c) Gantt charts

16. **A use case primarily focuses on:**

a) Technical architecture

b) User-system interactions

c) Budget allocation

d) Coding standards

**Answer:** b) User-system interactions

---

### **Scenario-Based Questions**

17. **A banking app must allow users to transfer funds between accounts. This is a:**

a) Functional requirement

b) Performance requirement

c) Security requirement

d) Compliance requirement

**Answer:** a) Functional requirement

18. **If a system fails to calculate tax during checkout, which requirement is violated?**

a) Functional

b) Usability
 c) Reliability

d) Scalability

**Answer:** a) Functional

---

### **True/False as MCQs**

19. **True or False: Functional requirements define how the system should behave under
specific conditions.**

a) True

b) False

**Answer:** a) True

20. **True or False: User stories are written from the developer’s perspective.**

a) True

b) False

**Answer:** b) False (user’s perspective)

---

### **Fill-in-the-Blank Style**

21. **"Users must register by providing name, email, and password" is a ________
requirement.**

a) Functional

b) Non-functional

c) Technical

d) Regulatory
 **Answer:** a) Functional

22. **________ clarify system features to align developers with stakeholder needs.**

a) User manuals

b) Functional requirements

c) Risk assessments

d) Budget plans

**Answer:** b) Functional requirements

---

### **Bonus Questions**

23. **Which requirement type is directly tied to user interactions?**

a) Functional

b) Performance

c) Security

d) Compliance

**Answer:** a) Functional

24. **A system’s ability to generate invoices falls under:**

a) Functional requirements

b) Quality attributes

c) Constraints

d) Assumptions

**Answer:** a) Functional requirements

25. **What do user stories emphasize?**

a) Technical implementation

b) User goals and tasks

c) System architecture

d) Budget tracking

**Answer:** b) User goals and tasks

Here are **25 MCQs** based on **Non-Functional Requirements (NFRs)**:

---

### **Definition & Basics**

1. **Non-functional requirements primarily define:**

a) What the system does

b) How the system performs its functions

c) User registration steps

d) Business goals

**Answer:** b) How the system performs its functions

2. **Which of the following is a key focus of non-functional requirements?**

a) Core system features

b) Quality attributes like security and performance

c) User story creation

d) Functional testing

**Answer:** b) Quality attributes like security and performance

3. **Non-functional requirements ensure the system meets:**

a) Stakeholder expectations for system behavior

b) Functional use cases

c) User interface design guidelines

d) Marketing strategies

**Answer:** a) Stakeholder expectations for system behavior

---

### **Examples of Non-Functional Requirements**

4. **"The system must support 1,000 concurrent users" is an example of:**

a) Performance

b) Scalability

c) Availability

d) Usability

**Answer:** a) Performance

5. **Horizontal scaling to handle increased users is related to:**

a) Security

b) Scalability

c) Compliance

d) Maintainability

**Answer:** b) Scalability

6. **GDPR compliance falls under which type of requirement?**

a) Functional
 b) Usability

c) Compliance

d) Performance

**Answer:** c) Compliance

7. **"Data must be encrypted during transfer" is a:**

a) Security requirement

b) Functional requirement

c) User story

d) Use case

**Answer:** a) Security requirement

8. **A system requiring 99.9% uptime yearly addresses:**

a) Availability

b) Maintainability

c) Usability

d) Performance

**Answer:** a) Availability

9. **"Users should reach any major feature in three clicks" relates to:**

a) Usability

b) Scalability

c) Compliance

d) Performance

**Answer:** a) Usability
---

### **Importance of Non-Functional Requirements**

10. **NFRs help steer:**

a) User story creation

b) Architectural and design decisions

c) Functional testing

d) Marketing campaigns

**Answer:** b) Architectural and design decisions

11. **Which benefit is directly tied to non-functional requirements?**

a) Defining core features

b) Enhancing user satisfaction through performance

c) Outlining budget constraints

d) Writing code documentation

**Answer:** b) Enhancing user satisfaction through performance

12. **Non-functional requirements establish:**

a) System functionalities

b) Quality standards (e.g., security, reliability)

c) User registration workflows

d) Project timelines

**Answer:** b) Quality standards

---
### **Documentation Formats**

13. **Service Level Agreements (SLAs) typically document:**

a) User stories

b) Uptime and response time metrics

c) Use cases

d) Functional specifications

**Answer:** b) Uptime and response time metrics

14. **Quality Attribute Scenarios describe:**

a) User interactions

b) System behavior under specific conditions (e.g., traffic surges)

c) Budget allocation

d) Coding standards

**Answer:** b) System behavior under specific conditions

15. **Technical Architecture Documents focus on:**

a) User interface design

b) Security and scalability standards

c) Marketing strategies

d) Stakeholder interviews

**Answer:** b) Security and scalability standards

---

### **Advanced Questions**

16. **Which is NOT a non-functional requirement?**

 a) "The system must load in 2 seconds."

b) "Users must log in with a password."

c) "The code must be modular for easy updates."

d) "Data backups must occur daily."

**Answer:** b) "Users must log in with a password." (Functional)

17. **Maintainability ensures:**

a) Fast system performance

b) Easy code updates and debugging

c) GDPR compliance

d) User-friendly navigation

**Answer:** b) Easy code updates and debugging

18. **Non-functional requirements are LEAST likely to address:**

a) System security

b) User registration steps

c) Response time

d) Scalability

**Answer:** b) User registration steps (Functional)

---

### **Scenario-Based Questions**

19. **A banking app crashes when 500 users log in simultaneously. Which NFR is violated?**

a) Performance

b) Usability
 c) Compliance

d) Maintainability

**Answer:** a) Performance

20. **A system takes 10 seconds to load a page. This violates:**

a) Security

b) Performance

c) Compliance

d) Availability

**Answer:** b) Performance

---

### **True/False as MCQs**

21. **True or False: Non-functional requirements define what the system does.**

a) True

b) False

**Answer:** b) False (They define *how* it does it)

22. **True or False: Usability focuses on user satisfaction with system performance.**

a) True

b) False

**Answer:** a) True

---
### **Fill-in-the-Blank Style**

23. **"The system must encrypt data during transfer" is a ________ requirement.**

a) Functional

b) Security (Non-functional)

c) Compliance

d) Performance

**Answer:** b) Security

24. **________ define standards for system reliability and uptime.**

a) User stories

b) Non-functional requirements

c) Functional specifications

d) Risk assessments

**Answer:** b) Non-functional requirements

---

### **Bonus Questions**

25. **Which document would specify "99.9% uptime" as a requirement?**

a) Use case

b) Service Level Agreement (SLA)

c) User story

d) Functional specification

**Answer:** b) Service Level Agreement (SLA)

Here are **25 MCQs** based on **Requirements Engineering**:

---

### **Overview & Basics**

1. **What is the primary goal of Requirements Engineering?**

a) Writing code for the software

b) Bridging stakeholder needs with software development

c) Designing user interfaces

d) Testing the final product

**Answer:** b) Bridging stakeholder needs with software development

2. **Which phase ensures that requirements are accurate and achievable?**

a) Coding

b) Iterative refinement and validation

c) Deployment

d) Debugging

**Answer:** b) Iterative refinement and validation

3. **Requirements Engineering is critical to prevent:**

a) User satisfaction

b) Scope creep and project failure

c) Faster development

d) Increased stakeholder involvement

**Answer:** b) Scope creep and project failure

---
### **Feasibility Study**

4. **Which feasibility evaluates if a project can be developed with available technology?**

a) Economic feasibility

b) Technical feasibility

c) Operational feasibility

d) Legal feasibility

**Answer:** b) Technical feasibility

5. **Economic feasibility primarily assesses:**

a) Alignment with organizational workflows

b) Cost-benefit analysis

c) Compliance with laws

d) User interface design

**Answer:** b) Cost-benefit analysis

6. **Operational feasibility ensures the system works within:**

a) Budget constraints

b) Existing organizational processes

c) Coding standards

d) Marketing strategies

**Answer:** b) Existing organizational processes

---

### **Requirement Elicitation & Analysis**

7. **Which technique involves direct communication with stakeholders?**

a) Surveys

b) Prototyping

c) Interviews

d) Observation

**Answer:** c) Interviews

8. **Distributing questionnaires to collect user preferences is part of:**

a) Workshops

b) Surveys

c) Prototyping

d) Observation

**Answer:** b) Surveys

9. **Building a preliminary software version to gather feedback is called:**

a) Observation

b) Prototyping

c) Brainstorming

d) Feasibility study

**Answer:** b) Prototyping

10. **Analyzing requirements for consistency and completeness happens in:**

a) Feasibility study

b) Requirement validation

c) Requirement elicitation

d) Requirement analysis
 **Answer:** d) Requirement analysis

---

### **Software Requirement Specification (SRS)**

11. **The SRS document serves as a:**

a) Marketing plan

b) Blueprint for development

c) User manual

d) Budget report

**Answer:** b) Blueprint for development

12. **Which component of the SRS describes system functions?**

a) Non-functional requirements

b) User interfaces

c) Functional requirements

d) Data requirements

**Answer:** c) Functional requirements

13. **Constraints like performance and security are part of:**

a) Non-functional requirements

b) User stories

c) Feasibility study

d) Data requirements

**Answer:** a) Non-functional requirements

14. **Details about stored and processed data are covered under:**

a) User interfaces

b) Functional requirements

c) Data requirements

d) Use cases

**Answer:** c) Data requirements

---

### **Process & Techniques**

15. **Which step comes FIRST in Requirements Engineering?**

a) Requirement analysis

b) Feasibility study

c) SRS documentation

d) Prototyping

**Answer:** b) Feasibility study

16. **Group sessions to brainstorm requirements are called:**

a) Interviews

b) Workshops

c) Surveys

d) Observation

**Answer:** b) Workshops

17. **Observing users to understand workflows is part of:**

a) Prototyping
 b) Requirement elicitation

c) Feasibility study

d) Coding

**Answer:** b) Requirement elicitation

---

### **Scenario-Based Questions**

18. **A project is canceled due to high costs. Which feasibility was overlooked?**

a) Technical

b) Economic

c) Operational

d) Legal

**Answer:** b) Economic

19. **Conflicting stakeholder needs are resolved during:**

a) Requirement analysis

b) Coding

c) Deployment

d) Debugging

**Answer:** a) Requirement analysis

---

### **True/False as MCQs**

20. **True or False: Requirements Engineering ends after the initial phase.**
 a) True

b) False

**Answer:** b) False (It’s ongoing throughout the lifecycle)

21. **True or False: The SRS includes both functional and non-functional requirements.**

a) True

b) False

**Answer:** a) True

---

### **Fill-in-the-Blank Style**

22. **________ involves validating if the system aligns with organizational workflows.**

a) Technical feasibility

b) Operational feasibility

c) Economic feasibility

d) Legal feasibility

**Answer:** b) Operational feasibility

23. **The ________ document details how users interact with the system.**

a) SRS

b) Feasibility report

c) User manual

d) Budget plan

**Answer:** a) SRS
---

### **Bonus Questions**

24. **Which phase translates stakeholder needs into specific software requirements?**

a) Feasibility study

b) Requirement elicitation

c) Coding

d) Testing

**Answer:** b) Requirement elicitation

25. **Iterative refinement ensures requirements are:**

a) Fixed and unchangeable

b) Accurate and achievable

c) Developed quickly

d) Ignored during testing

**Answer:** b) Accurate and achievable

---

Let me know if you need more questions or edits! 😊

Here are **25 MCQs** based on **Requirement Validation, Management, and Challenges**:

---

### **Requirement Validation**

1. **What is the primary goal of requirement validation?**

 a) Writing code for the system

b) Ensuring requirements match stakeholders’ needs

c) Designing the user interface

d) Finalizing the project budget

**Answer:** b) Ensuring requirements match stakeholders’ needs

2. **Which technique involves building a working model to validate requirements?**

a) Simulation

b) Prototyping

c) Reviews

d) Surveys

**Answer:** b) Prototyping

3. **Simulating software behavior to test alignment with requirements is part of:**

a) Requirement elicitation

b) Requirement validation

c) Feasibility study

d) Change control

**Answer:** b) Requirement validation

4. **Expert walkthroughs to identify SRS issues are called:**

a) Prototyping

b) Reviews

c) Traceability

d) Prioritization

**Answer:** b) Reviews
---

### **Requirement Management**

5. **Version control in requirement management refers to:**

a) Tracking changes to the codebase

b) Managing different versions of requirements documents

c) Prioritizing stakeholder needs

d) Simulating system behavior

**Answer:** b) Managing different versions of requirements documents

6. **Which activity ensures that changes to requirements are documented and assessed?**

a) Traceability

b) Change control

c) Prototyping

d) Simulation

**Answer:** b) Change control

7. **Traceability links requirements to:**

a) Marketing strategies

b) Design, implementation, and testing

c) Budget reports

d) User manuals

**Answer:** b) Design, implementation, and testing

8. **Assigning priorities to requirements helps:**

 a) Increase project costs

b) Guide development efforts

c) Delay testing

d) Reduce stakeholder involvement

**Answer:** b) Guide development efforts

9. **Effective requirement management ensures stakeholders are:**

a) Excluded from decision-making

b) Informed about requirement changes

c) Responsible for coding

d) Focused on marketing

**Answer:** b) Informed about requirement changes

---

### **Challenges & Risks**

10. **Incomplete requirements often result in systems that:**

a) Exceed user expectations

b) Fail to address critical functionalities

c) Reduce development costs

d) Speed up project timelines

**Answer:** b) Fail to address critical functionalities

11. **Ambiguous requirements can lead to:**

a) Clear communication

b) Design flaws and delays

 c) Faster approvals

d) Reduced testing

**Answer:** b) Design flaws and delays

12. **Scope creep is typically caused by:**

a) Fixed requirements

b) Frequent requirement changes

c) Strict change control

d) Clear traceability

**Answer:** b) Frequent requirement changes

13. **Conflicting requirements arise when stakeholders have:**

a) Identical priorities

b) Misaligned needs

c) No budget constraints

d) Limited communication

**Answer:** b) Misaligned needs

14. **Poor traceability makes it difficult to:**

a) Verify requirement implementation

b) Write user manuals

c) Conduct interviews

d) Design prototypes

**Answer:** a) Verify requirement implementation

---
### **Scenario-Based Questions**

15. **A stakeholder requests a new feature mid-development. This is a challenge related to:**

a) Incomplete requirements

b) Changing requirements

c) Ambiguous requirements

d) Poor prioritization

**Answer:** b) Changing requirements

16. **A requirement states, "The system should be fast." This is an example of:**

a) Clear requirement

b) Ambiguous requirement

c) Non-functional requirement

d) Validated requirement

**Answer:** b) Ambiguous requirement

17. **A team struggles to link requirements to test cases. This indicates poor:**

a) Prototyping

b) Traceability

c) Prioritization

d) Feasibility analysis

**Answer:** b) Traceability

---

### **True/False as MCQs**

18. **True or False: Requirement validation occurs after development is complete.**

a) True

b) False

**Answer:** b) False (It occurs before development begins)

19. **True or False: Change control prevents all requirement modifications.**

a) True

b) False

**Answer:** b) False (It manages changes, not prevents them)

---

### **Fill-in-the-Blank Style**

20. **________ involves assessing the impact of requirement changes.**

a) Version control

b) Change control

c) Prototyping

d) Simulation

**Answer:** b) Change control

21. **"The system must handle 10,000 users" is a ________ requirement.**

a) Functional

b) Non-functional

c) Ambiguous

d) Incomplete

**Answer:** b) Non-functional
---

### **Advanced Questions**

22. **Which challenge is hardest to resolve during late-stage development?**

a) Incomplete requirements

b) Changing requirements

c) Clear traceability

d) Stakeholder agreement

**Answer:** b) Changing requirements

23. **Prioritization helps mitigate risks related to:**

a) Budget constraints

b) Conflicting requirements

c) User manuals

d) Code modularity

**Answer:** b) Conflicting requirements

---

### **Bonus Questions**

24. **Which tool is used to track requirement changes systematically?**

a) Prototype

b) Traceability matrix

c) Survey

d) Feasibility report
 **Answer:** b) Traceability matrix

25. **A project faces delays due to vague requirements. This is caused by:**

a) Operational feasibility

b) Ambiguity in requirements

c) Effective prioritization

d) Strong traceability

**Answer:** b) Ambiguity in requirements

---

Here are **25 MCQs** based on **Tools Involved in Requirement Engineering**:

---

### **Document Editors & Spreadsheets**

1. **Which tool is commonly used to create textual requirement documents like use cases?**

a) Microsoft Excel

b) Balsamiq

c) Microsoft Word

d) IBM DOORS

**Answer:** c) Microsoft Word

2. **Spreadsheet tools like Excel are BEST suited for:**

a) Creating interactive prototypes

b) Managing requirement traceability matrices

 c) Simulating system behavior

d) Writing code

**Answer:** b) Managing requirement traceability matrices

---

### **Diagramming & Modeling Tools**

3. **Use case diagrams are typically created using:**

a) Microsoft Teams

b) Lucidchart

c) Jama Connect

d) Axure

**Answer:** b) Lucidchart

4. **Which tool provides a standardized way to represent system requirements using diagrams
like UML?**

a) Confluence

b) Unified Modeling Language (UML)

c) Google Sheets

d) Helix RM

**Answer:** b) Unified Modeling Language (UML)

5. **A data flow diagram (DFD) is most likely created using:**

a) Balsamiq

b) Microsoft Visio

c) SharePoint
 d) Formal methods

**Answer:** b) Microsoft Visio

---

### **Requirements Management Tools**

6. **Which tool supports version control and traceability for requirements?**

a) Microsoft Excel

b) IBM Engineering Requirements Management DOORS

c) Sketch

d) Surveys

**Answer:** b) IBM Engineering Requirements Management DOORS

7. **Jama Connect is primarily used for:**

a) Prototyping user interfaces

b) Managing and tracking requirements

c) Writing code documentation

d) Conducting stakeholder interviews

**Answer:** b) Managing and tracking requirements

---

### **Prototyping & UI Tools**

8. **Interactive UI mockups are best created with:**

a) Axure

b) Microsoft Word
 c) UML

d) Static analysis tools

**Answer:** a) Axure

9. **Balsamiq is an example of a:**

a) Requirements management tool

b) Prototyping tool

c) Collaboration platform

d) Validation tool

**Answer:** b) Prototyping tool

---

### **Collaboration & Elicitation Tools**

10. **Which tool facilitates team discussions and document sharing for requirements?**

a) Microsoft Teams

b) IBM DOORS

c) LaTeX

d) Simulation tools

**Answer:** a) Microsoft Teams

11. **Workshops and interviews are examples of:**

a) Validation tools

b) Requirement elicitation techniques

c) Diagramming tools

d) Traceability methods
 **Answer:** b) Requirement elicitation techniques

---

### **Validation & Verification Tools**

12. **Formal methods and static analysis tools are used for:**

a) Creating use case diagrams

b) Validating requirement correctness

c) Managing stakeholder feedback

d) Generating financial reports

**Answer:** b) Validating requirement correctness

13. **Simulation tools help:**

a) Track requirement changes

b) Test system behavior against requirements

c) Prioritize user stories

d) Design UML class diagrams

**Answer:** b) Test system behavior against requirements

---

### **Traceability Tools**

14. **Traceability matrices ensure:**

a) All requirements are linked to design and testing

b) Prototypes are user-friendly

c) Stakeholders attend workshops

 d) Code is modular

**Answer:** a) All requirements are linked to design and testing

15. **Which tool helps maintain links between requirements and testing phases?**

a) Helix RM

b) Balsamiq

c) Microsoft Excel

d) Draw.io

**Answer:** a) Helix RM

---

### **Scenario-Based Questions**

16. **A team needs to track changes to requirements across versions. Which tool is most
suitable?**

a) Google Sheets

b) IBM DOORS

c) Axure

d) Confluence

**Answer:** b) IBM DOORS

17. **Stakeholders want to visualize system interactions. Which tool should the team use?**

a) Microsoft Word

b) UML diagrams

c) Surveys

d) Formal methods
 **Answer:** b) UML diagrams

18. **A project requires GDPR compliance checks. Which tool would validate this requirement?
**

a) Prototyping tools

b) Static analysis tools

c) Spreadsheets

d) Collaboration platforms

**Answer:** b) Static analysis tools

---

### **True/False as MCQs**

19. **True or False: Microsoft Excel is ideal for creating entity-relationship diagrams.**

a) True

b) False

**Answer:** b) False (Diagramming tools like Visio are used)

20. **True or False: Confluence is a collaboration tool for sharing requirement documents.**

a) True

b) False

**Answer:** a) True

---

### **Fill-in-the-Blank Style**

21. **________ tools like Jama Connect prioritize features like version control and
traceability.**

a) Prototyping

b) Requirements management

c) Validation

d) Diagramming

**Answer:** b) Requirements management

22. **________ are non-software tools used to gather requirements through group
discussions.**

a) Workshops

b) Simulation tools

c) Spreadsheets

d) UML diagrams

**Answer:** a) Workshops

---

### **Advanced Questions**

23. **Which tool bridges the gap between textual requirements and visual system behavior?**

a) Traceability matrix

b) Use case diagrams

c) Axure prototypes

d) Formal methods

**Answer:** b) Use case diagrams

24. **Prioritizing requirements to guide development is a feature of:**

 a) Spreadsheet tools

b) Requirements management tools

c) Prototyping tools

d) Collaboration tools

**Answer:** b) Requirements management tools

---

### **Bonus Question**

25. **Which tool ensures that a requirement like "99.9% uptime" is tracked through testing?**

a) Balsamiq

b) Traceability matrix

c) Microsoft Word

d) Surveys

**Answer:** b) Traceability matrix

---

Here are **25 MCQs** based on the **Advantages and Disadvantages of Requirements
Engineering**:

---

### **Advantages of Requirements Engineering**

1. **Which advantage ensures software aligns with user needs?**

a) Risk mitigation
 b) Customer satisfaction

c) Overemphasis on documentation

d) Dependency on tools

**Answer:** b) Customer satisfaction

2. **Early detection of issues in requirements helps:**

a) Increase project costs

b) Prevent costly errors in later stages

c) Delay stakeholder involvement

d) Simplify coding

**Answer:** b) Prevent costly errors in later stages

3. **Clear requirements reduce scope creep, leading to:**

a) Higher costs

b) Time and resource savings

c) Ambiguous goals

d) Increased resistance to change

**Answer:** b) Time and resource savings

4. **Requirements traceability aids in:**

a) Marketing strategies

b) Impact analysis during changes

c) User interface design

d) Budget overruns

**Answer:** b) Impact analysis during changes

5. **Which benefit ensures compliance with industry standards?**

a) Validation and verification

b) Regulatory compliance

c) Effective planning

d) Collaboration

**Answer:** b) Regulatory compliance

6. **Thorough requirements facilitate:**

a) Scope creep

b) Risk identification and mitigation

c) Miscommunication

d) Tool dependency

**Answer:** b) Risk identification and mitigation

7. **User involvement ensures the final product:**

a) Exceeds budget

b) Aligns with stakeholder expectations

c) Ignores non-functional requirements

d) Uses obsolete tools

**Answer:** b) Aligns with stakeholder expectations

8. **Formalized requirements help manage:**

a) Ambiguity

b) Project scope

c) Overemphasis on documentation

d) Changing tools
 **Answer:** b) Project scope

9. **Requirements documentation supports:**

a) Increased resistance to change

b) Ongoing maintenance and enhancements

c) Scope creep

d) Neglecting non-functional needs

**Answer:** b) Ongoing maintenance and enhancements

10. **Which advantage ensures software quality through rigorous testing?**

a) Collaboration

b) Quality assurance

c) Time-consuming processes

d) User involvement challenges

**Answer:** b) Quality assurance

---

### **Disadvantages of Requirements Engineering**

11. **Poorly defined requirements often lead to:**

a) Enhanced collaboration

b) Ambiguity and misinterpretation

c) Cost savings

d) Effective planning

**Answer:** b) Ambiguity and misinterpretation

12. **Uncontrolled additions to requirements cause:**

a) Scope creep

b) Regulatory compliance

c) Early issue detection

d) Traceability

**Answer:** a) Scope creep

13. **Shifting requirements during development result in:**

a) Delays and rework

b) Improved user satisfaction

c) Better risk mitigation

d) Simplified documentation

**Answer:** a) Delays and rework

14. **Overemphasis on documentation can:**

a) Speed up development

b) Slow down development and limit agility

c) Enhance user involvement

d) Reduce ambiguity

**Answer:** b) Slow down development and limit agility

15. **Neglecting non-functional requirements risks overlooking:**

a) User stories

b) Performance and security

c) Stakeholder expectations

d) Use case diagrams

 **Answer:** b) Performance and security

16. **Difficulty in engaging users may lead to:**

a) Missed requirements

b) Enhanced collaboration

c) Effective planning

d) Tool dependency

**Answer:** a) Missed requirements

17. **Resistance to change often stems from stakeholders’:**

a) Overemphasis on documentation

b) Emotional attachment to initial requirements

c) Focus on non-functional needs

d) Dependency on tools

**Answer:** b) Emotional attachment to initial requirements

18. **Overreliance on requirement management tools can cause issues if tools:**

a) Are updated regularly

b) Fail or become obsolete

c) Include traceability matrices

d) Support collaboration

**Answer:** b) Fail or become obsolete

---

### **Scenario-Based Questions**

19. **A project faces delays due to frequent requirement changes. This reflects which
disadvantage?**

a) Scope creep

b) Changing requirements

c) Miscommunication

d) Tool dependency

**Answer:** b) Changing requirements

20. **Stakeholders struggle to agree on priorities, leading to conflicts. This highlights:**

a) Effective planning

b) Scope management

c) Ambiguous requirements

d) Risk mitigation

**Answer:** c) Ambiguous requirements

---

### **True/False as MCQs**

21. **True or False: Requirements engineering guarantees no scope creep.**

a) True

b) False

**Answer:** b) False

22. **True or False: Clear requirements reduce the need for rework.**

a) True

b) False
 **Answer:** a) True

---

### **Fill-in-the-Blank Style**

23. **________ links software components to specific requirements for impact analysis.**

a) Traceability

b) Validation

c) Prototyping

d) Compliance

**Answer:** a) Traceability

24. **________ occurs when stakeholders add features mid-project without control.**

a) Risk mitigation

b) Scope creep

c) User involvement

d) Quality assurance

**Answer:** b) Scope creep

---

### **Bonus Question**

25. **Which disadvantage arises when teams focus only on "what the system does" and ignore
"how it performs"?**

a) Overemphasis on documentation

b) Neglecting non-functional requirements

 c) Dependency on tools

d) Ambiguity

**Answer:** b) Neglecting non-functional requirements

Here are **25 MCQs** comparing **Requirement Engineering Approaches**:

---

### **Waterfall Model**

1. **The Waterfall Model is BEST described as:**

a) Iterative and flexible

b) Sequential and linear

c) Risk-driven and cyclical

d) Prototype-focused

**Answer:** b) Sequential and linear

2. **A key limitation of the Waterfall Model is:**

a) Difficulty incorporating changes after a phase is completed

b) Lack of documentation

c) Overemphasis on user feedback

d) High adaptability to evolving requirements

**Answer:** a) Difficulty incorporating changes after a phase is completed

---

### **Agile Methodology**

3. **Agile prioritizes:**

a) Comprehensive documentation

b) Working software over documentation

c) Fixed requirements

d) Risk management phases

**Answer:** b) Working software over documentation

4. **Agile is MOST suitable for projects with:**

a) Stable, well-defined requirements

b) Frequently changing requirements

c) High regulatory compliance needs

d) Minimal stakeholder involvement

**Answer:** b) Frequently changing requirements

---

### **Prototyping**

5. **Prototyping is primarily used to:**

a) Eliminate all risks upfront

b) Gather feedback on unclear requirements

c) Finalize code early

d) Avoid stakeholder collaboration

**Answer:** b) Gather feedback on unclear requirements

6. **A risk of prototyping is:**

a) Improved user satisfaction

 b) Scope creep if unmanaged

c) Reduced documentation

d) Faster development

**Answer:** b) Scope creep if unmanaged

---

### **Spiral Model**

7. **The Spiral Model combines iterative development with:**

a) Risk management

b) Strict phase completion

c) Minimal documentation

d) Fixed budgets

**Answer:** a) Risk management

8. **The Spiral Model is MOST useful for:**

a) Projects with low uncertainty

b) High-risk, evolving requirement projects

c) Simple, short-term projects

d) Avoiding user involvement

**Answer:** b) High-risk, evolving requirement projects

---

### **Use Case-Driven Approach**

9. **Use Case-Driven RE focuses on:**

 a) Technical architecture

b) User-system interactions

c) Budget constraints

d) Coding standards

**Answer:** b) User-system interactions

10. **Use cases are MOST effective for capturing:**

a) Non-functional requirements

b) Functional requirements and user behavior

c) Risk mitigation strategies

d) Tool dependencies

**Answer:** b) Functional requirements and user behavior

---

### **Comparison-Based Questions**

11. **Which approach is LEAST flexible to requirement changes?**

a) Agile

b) Waterfall

c) Spiral

d) Prototyping

**Answer:** b) Waterfall

12. **Which method uses iterative cycles with risk assessment?**

a) Waterfall

b) Spiral
 c) Use Case-Driven

d) Prototyping

**Answer:** b) Spiral

13. **Agile differs from Waterfall by emphasizing:**

a) Strict phase completion

b) Adaptability over documentation

c) Finalizing requirements upfront

d) Avoiding user feedback

**Answer:** b) Adaptability over documentation

14. **Which approach is MOST likely to involve creating mockups early?**

a) Waterfall

b) Prototyping

c) Spiral

d) Use Case-Driven

**Answer:** b) Prototyping

15. **Use Case-Driven RE is similar to Agile because both:**

a) Avoid documentation

b) Focus on user interactions

c) Prioritize risk management

d) Require fixed budgets

**Answer:** b) Focus on user interactions

---
### **Scenario-Based Questions**

16. **A project with unclear requirements uses mockups to validate ideas. Which approach is
this?**

a) Waterfall

b) Prototyping

c) Spiral

d) Agile

**Answer:** b) Prototyping

17. **A team building a high-risk medical software prefers iterative development with risk
analysis. Which model do they use?**

a) Waterfall

b) Spiral

c) Use Case-Driven

d) Agile

**Answer:** b) Spiral

18. **A startup wants frequent user feedback and adaptable requirements. Which approach is
BEST?**

a) Waterfall

b) Agile

c) Prototyping

d) Use Case-Driven

**Answer:** b) Agile

---
### **True/False as MCQs**

19. **True or False: The Waterfall Model supports easy mid-project requirement changes.**

a) True

b) False

**Answer:** b) False

20. **True or False: The Spiral Model includes phases dedicated to risk management.**

a) True

b) False

**Answer:** a) True

---

### **Fill-in-the-Blank Style**

21. **The ________ model requires completing all documentation before development.**

a) Agile

b) Waterfall

c) Spiral

d) Prototyping

**Answer:** b) Waterfall

22. **________ expresses requirements as user-system interaction scenarios.**

a) Spiral Model

b) Use Case-Driven Approach

c) Agile Methodology
 d) Waterfall Model

**Answer:** b) Use Case-Driven Approach

---

### **Advanced Questions**

23. **Which approach is MOST likely to cause delays if requirements evolve mid-project?**

a) Agile

b) Waterfall

c) Prototyping

d) Spiral

**Answer:** b) Waterfall

24. **Prioritizing risk management is a key feature of the:**

a) Waterfall Model

b) Spiral Model

c) Use Case-Driven Approach

d) Prototyping

**Answer:** b) Spiral Model

---

### **Bonus Question**

25. **Which approach is BEST for a project where stakeholders struggle to articulate their
needs?**

a) Waterfall
 b) Prototyping

c) Use Case-Driven

d) Spiral

**Answer:** b) Prototyping

---

Here are **True/False** and **Fill-in-the-Blanks** questions based on the provided content
about **Functional and Non-Functional Requirements**:

---

### **True/False Questions**

1. **True/False:** Functional requirements define how the system performs its functions.

**Answer:** False (Non-functional requirements define "how")

2. **True/False:** "Users must log in with a valid username and password" is a functional
requirement.

**Answer:** True

3. **True/False:** Non-functional requirements include usability and performance.

**Answer:** True

4. **True/False:** Use cases document non-functional requirements.

**Answer:** False (They document functional requirements)

5. **True/False:** Service Level Agreements (SLAs) are used to document non-functional

requirements.
 **Answer:** True

6. **True/False:** GDPR compliance is an example of a functional requirement.

**Answer:** False (It is a non-functional/compliance requirement)

7. **True/False:** Non-functional requirements are expressed from the user’s perspective.

**Answer:** False (Functional requirements are user-centric)

8. **True/False:** Functional requirements guide the testing process.

**Answer:** True

9. **True/False:** Scalability is a functional requirement.

**Answer:** False (It is a non-functional requirement)

10. **True/False:** User stories follow the format: "As a [user], I want [action] to achieve
[goal]."

**Answer:** True

---

### **Fill-in-the-Blanks Questions**

1. **"The system must process orders and calculate total costs" is an example of a __________
requirement.**

**Answer:** functional

2. **Non-functional requirements such as "99.9% uptime" are documented in __________.**

**Answer:** Service Level Agreements (SLAs)

3. **User stories describe __________ requirements using the format: "As a [user], I want to
[action]."**

**Answer:** functional

4. **__________ requirements ensure the system can handle 1,000 concurrent users.**

**Answer:** Non-functional

5. **The __________ document defines technical standards like security and scalability.**

**Answer:** Technical Architecture and Design

6. **"All data must be encrypted during transfer" is a __________ requirement.**

**Answer:** security (non-functional)

7. **Non-functional requirements related to GDPR compliance fall under __________.**

**Answer:** compliance

8. **__________ scenarios describe expected system behavior during traffic surges.**

**Answer:** Quality Attribute

9. **Functional requirements clarify system features to align with __________ expectations.**

**Answer:** stakeholders’

10. **The __________ phase resolves conflicts and ambiguities in gathered requirements.**

**Answer:** Requirement Analysis

---

### **Mixed Format (Bonus)**

1. **True/False:** Maintainability ensures code can be easily updated.

**Answer:** True

2. **Fill-in-the-Blank:** "The interface must allow navigation in three clicks" relates to

__________.

**Answer:** usability (non-functional)

---

Let me know if you need more questions or adjustments! 😊