Requirements engineering: elicitation, SRS, use cases and requirement modelling. - One Line Questions

1. In requirement engineering, what is the difference between 'what' and 'how'? — 'What' refers to the system's required functionality, 'how' refers to the implementation strategy.
2. What does an 'external entity' represent in a DFD? — A source or destination of data outside the system boundary
3. What does a 'relationship' represent in an ERD? — An association between two entities.
4. In a DFD, what does a 'process' bubble represent? — A transformation of incoming data into outgoing data
5. What is a user story, often used in Agile methodologies? — A short, simple description of a feature told from the perspective of the person who desires the new capability.
6. What is a 'scenario' in requirements engineering? — A specific sequence of actions or events that illustrates how a system is used.
7. What is a 'business rule' in the context of requirements? — A policy or guideline that governs business operations and is often reflected in system requirements.
8. In a use case diagram, what does an 'actor' typically represent? — A user or external system that interacts with the system
9. What is a 'data store' in the context of a DFD? — A place where data is held for later use
10. What does a 'trigger' represent in a State Machine Diagram? — An event that causes a transition from one state to another
11. What is a 'transition' in a State Machine Diagram? — A movement from one state to another, often triggered by an event
12. What is an 'exception condition' in a use case description? — A situation where the normal flow of events is interrupted or fails.
13. Which of the following is a key characteristic of a well-defined requirement? — Testability
14. A good SRS document should be: — Unambiguous, complete, and verifiable
15. What does a 'state' represent in a State Machine Diagram? — A stable condition or status of an object
16. What does an 'entity' represent in an ERD? — A thing about which data is stored (e.g., a customer, a product).
17. What does the term 'domain analysis' refer to in requirements engineering? — Studying the specific subject area or industry for which the software is being developed.
18. Which elicitation technique involves observing users in their natural work environment? — Ethnography
19. Which of the following is a common method for requirement validation? — Requirement reviews and walkthroughs
20. Which of the following is a common technique for requirements elicitation? — User interviews
21. Which modeling technique is most suitable for visualizing the relationships between different classes in an object-oriented system? — Class Diagram
22. Which requirement modeling technique uses a graphical representation of system functionality and user interactions? — Use Case Diagrams
23. What is a functional requirement? — Specifies a function that the system must perform.
24. Which elicitation technique is useful for understanding user preferences and gathering feedback on specific features? — Surveys and questionnaires
25. Which type of requirement specifies performance, security, and reliability characteristics? — Non-functional requirements
26. What is the main benefit of using a structured SRS document? — It provides a clear, agreed-upon basis for development and testing.
27. What is the purpose of an 'optional' step in a use case description? — It is performed only under specific conditions or is not essential for the main goal.
28. What does the 'extend' relationship signify between two use cases? — One use case conditionally adds behavior to another use case under specific circumstances.
29. What does the 'include' relationship signify between two use cases? — One use case always incorporates the functionality of another use case.
30. What is a 'stakeholder' in the context of requirements engineering? — Anyone who is affected by or can affect the system.
31. What does SRS stand for in the context of software requirements? — Software Requirements Specification
32. Which elicitation technique involves bringing together stakeholders to discuss and generate ideas or requirements? — Brainstorming sessions
33. What is the primary focus of a Data Flow Diagram (DFD)? — The movement of data through a system.
34. What does a 'Class Diagram' depict? — The structure of a system in terms of classes, attributes, operations, and relationships.
35. What is the 'cardinality' of a relationship in an ERD? — The number of instances of one entity that can be associated with instances of another entity.
36. What is requirements traceability? — The ability to track the origin, usage, and changes of requirements throughout the development lifecycle.
37. Which of the following is an example of a non-functional requirement? — The system shall process 100 transactions per second.
38. What is the purpose of a use case in requirements engineering? — To illustrate how an external actor interacts with the system to achieve a goal.
39. What is the primary goal of requirements elicitation in software engineering? — To identify and understand the needs and constraints of stakeholders.
40. What is the primary purpose of requirement validation? — To confirm that the requirements accurately reflect the stakeholders' needs and are consistent.
41. What is the purpose of prototyping in requirements engineering? — To provide a working model for user feedback and validation of requirements.
42. In requirement modeling, what is the purpose of an Entity-Relationship Diagram (ERD)? — To model the structure of data and relationships between data entities.
43. What is a key benefit of involving end-users in the requirements engineering process? — To ensure the software meets their actual needs and is usable.
44. What is the purpose of a 'System Context Diagram' (Level 0 DFD)? — To illustrate the system as a single process and its interactions with external entities.
45. Which requirement modeling technique focuses on the data entities and their relationships, often used for database design? — Entity-Relationship Diagram
46. Which modeling technique is best suited for representing the dynamic behavior of a system, focusing on states and transitions? — State Machine Diagrams
47. The format 'As a <type of user>, I want <some goal> so that <some reason>' is typical for: — User Stories
48. Which of the following is a form of requirements elicitation that involves asking a set of questions to a group of stakeholders? — Surveys
49. What is the main challenge in requirements elicitation? — Understanding and capturing the true needs of diverse stakeholders.
All One Line Questions
E-Book Requirements engineering: elicitation, SRS, use cases and requirement modelling. Online Test Requirements engineering: elicitation, SRS, use cases and requirement modelling. Question Bank Requirements engineering: elicitation, SRS, use cases and requirement modelling.