Scribd
Upload
2 views2 pages

SE Module2 Questions

The document outlines various aspects of requirements engineering, including requirements elicitation techniques, requirements analysis, and the complete requirements engineering process. It discusses the importance of functional and non-functional requirements, feasibility analysis, use case modeling, user stories, and the Software Requirements Specification (SRS). Additionally, it covers the qualities of good requirements specifications and the concept of requirements traceability.

Uploaded by

biswajitbarik2006
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views2 pages

SE Module2 Questions

The document outlines various aspects of requirements engineering, including requirements elicitation techniques, requirements analysis, and the complete requirements engineering process. It discusses the importance of functional and non-functional requirements, feasibility analysis, use case modeling, user stories, and the Software Requirements Specification (SRS). Additionally, it covers the qualities of good requirements specifications and the concept of requirements traceability.

Uploaded by

biswajitbarik2006
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Long Questions

 Explain the process of requirements elicitation. Discuss various elicitation techniques


with suitable examples.

 What is requirements analysis? Explain its objectives, activities, and outcomes. How is
it different from requirements elicitation?

 Explain the complete Requirements Engineering process with a neat diagram.

 Describe feasibility analysis in requirements engineering. Explain technical, economic,


operational, and schedule feasibility.

 Define functional and non-functional requirements. Explain their differences with


suitable examples.

 Why are non-functional requirements critical to software success? Explain with real-
world examples.

 Explain Use Case Modeling in detail. Describe actors, use cases, system boundary, and
relationships.

 Draw and explain a use case diagram for a real-world system (ATM / Online
Shopping / Hospital Management).

 Explain the different relationships in use case diagrams (include, extend,


generalization) with examples.

 What are user stories? Explain their structure with examples.

 Explain the INVEST principle for writing good user stories.

 Compare user stories and use cases. Highlight their similarities and differences.

 What is Software Requirements Specification (SRS)? Explain its purpose and


importance.

 Discuss the qualities of a good requirements specification (correctness, completeness,


consistency, verifiability, traceability).

 What is requirements traceability? Explain forward and backward traceability with


examples.

Short Questions

 What is requirements elicitation?


 Define requirements analysis.

 Who are stakeholders in requirements engineering?

 Mention any two techniques used for requirements elicitation.

 What is a functional requirement?

 Give two examples of functional requirements.

 What is a non-functional requirement?

 Mention any two types of non-functional requirements.

 What is feasibility analysis?

 What is a use case?

 Who is an actor in a use case diagram?

 What is the purpose of a system boundary in a use case diagram?

 What is the difference between include and extend relationships in use case diagrams?

 Define user story.

 Write the standard format of a user story.

 What is the INVEST principle?

 What is Software Requirements Specification (SRS)?

 State any two characteristics of a good SRS.

 What is requirements traceability?

 What is requirements documentation?

You might also like