Multiple Choice Questions (MCQs)

1. What is the primary purpose of a Requirements Specification?

o a) Writing user manuals
o b) Defining what a system should do
o c) Designing the system architecture
o d) Writing test cases
o Answer: b
2. Which of the following should user requirements be?
o a) Written in technical terms
o b) Understandable by non-technical stakeholders
o c) Written in programming language
o d) Only used by developers
o Answer: b
3. What type of requirement includes system performance and constraints?
o a) Functional requirements
o b) Non-functional requirements
o c) User requirements
o d) Business rules
o Answer: b
4. Which document formally states what is required of system developers?
o a) Design Document
o b) Software Requirements Specification (SRS)
o c) User Manual
o d) Test Plan
o Answer: b
5. Which notation is commonly used for Graphical Models in Requirements Engineering?
o a) UML
o b) JSON
o c) XML
o d) HTML
o Answer: a
6. Which specification method is commonly used in structured specifications?
o a) Natural language only
o b) Tabular format
o c) Code snippets
o d) Randomized documentation
 o Answer: b
7. Which of the following is a key disadvantage of natural language requirements?
o a) Clear precision
o b) Lack of clarity and ambiguity
o c) Easy formal verification
o d) Simple structure
o Answer: b
8. Which keyword is used for mandatory requirements in specifications?
o a) Should
o b) Could
o c) Shall
o d) Might
o Answer: c
9. Which requirement representation is best suited for defining operational models?
o a) Mathematical notations
o b) Graphical models
o c) Structured language
o d) Random sentences
o Answer: a
10. What is a Use Case?
• a) A sequence of interactions between users and the system
• b) A programming function
• c) A testing procedure
• d) A database schema
• Answer: a
11. Which element is NOT part of a use case description?
• a) Pre-condition
• b) Post-condition
• c) Code implementation
• d) Main success scenario
• Answer: c
12. Which of the following best describes a system boundary in use cases?
• a) Separates the system from external entities
• b) Represents an actor
• c) A step in a use case scenario
• d) A specific software function
• Answer: a
13. What does a dashed arrow in a use case diagram indicate?
• a) Data flow
• b) Inclusion or extension relationships
• c) Mandatory steps
• d) Code dependencies
• Answer: b
14. Which of the following is NOT a valid use case element?
• a) Actor
• b) Use Case Name
• c) Source Code
• d) Pre-condition
• Answer: c
15. Which relationship in use case modeling is conditional?
• a) Include
• b) Extend
• c) Mandatory
• d) None
• Answer: b
16. Which type of diagram represents the interaction between actors and the system?
• a) Use Case Diagram
• b) Class Diagram
• c) Data Flow Diagram
• d) Sequence Diagram
• Answer: a
17. Which is a typical reason for using use case models?
• a) Capturing requirements
• b) Programming logic
• c) Database indexing
• d) Network configuration
• Answer: a
18. What does "actor generalization" in UML indicate?
• a) A specific actor can inherit behavior from another
• b) Actors cannot share behaviors
• c) It defines class inheritance
• d) It is only used in coding
• Answer: a
19. Which UML stereotype is used for mandatory inclusion?
• a) Extend
• b) Include
• c) Generalize
• d) Inherit
• Answer: b
20. What is a common advantage of using use cases?
• a) Defines system scope clearly
• b) Eliminates need for testing
• c) Replaces system architecture
• d) Used only for small systems
• Answer: a
21. Which use case relationship is used when behavior must always occur?
• a) Extend
• b) Include
• c) Generalize
• d) Inherit
• Answer: b
22. Which element is NOT required in a Use Case Diagram?
• a) Actors
• b) System boundaries
• c) Use Case IDs
• d) Relationships
• Answer: c
23. Which UML diagram is best suited for modeling sequential interactions?
• a) Use Case Diagram
• b) Class Diagram
• c) Sequence Diagram
• d) Activity Diagram
• Answer: c
24. What is the primary use of a system boundary in UML?
• a) To define actors
• b) To separate system elements from external entities
• c) To define relationships
• d) To create constraints
• Answer: b
25. Which is an example of a pre-condition for a Use Case?
• a) "The user must be logged in."
 • b) "The system must save the data."
• c) "The transaction must be recorded."
• d) "The output is displayed."
• Answer: a
26. What does the "extend" relationship allow in a Use Case?
• a) To add conditional behavior
• b) To remove actors
• c) To modify system boundaries
• d) To execute all functions at once
• Answer: a
27. Which element defines the completion status of a Use Case?
• a) Actor
• b) Pre-condition
• c) Post-condition
• d) Relationship
• Answer: c
28. Which of the following best describes an actor in a Use Case?
• a) A database entry
• b) A system user or external entity interacting with the system
• c) A software module
• d) A test script
• Answer: b
29. What is the purpose of a scenario in a Use Case?
• a) To define system behavior
• b) To replace UML diagrams
• c) To document system failures only
• d) To describe database relationships
• Answer: a
30. Which best describes an unsuccessful scenario?
• a) A sequence of events where the Use Case does not complete successfully
• b) A completed Use Case
• c) A system crash
• d) An error in the code
• Answer: a

True/False Questions
1. A use case always has only one success scenario. (False)
2. Use case diagrams should always include pre-conditions. (False)
3. System boundaries help distinguish actors from internal system processes. (True)
4. An actor in a use case diagram represents a role, not an individual user. (True)
5. The "include" relationship in use case diagrams represents optional behavior. (False)
6. Natural language specifications are always precise and clear. (False)
7. A system requirements document defines "what" a system should do, not "how". (True)
8. All functional requirements must be documented in use case diagrams. (False)
9. An actor can interact with multiple use cases in a system. (True)
10. Graphical models like UML diagrams are used to reduce ambiguity in requirements. (True)
11. "Extend" relationships are always used for mandatory behavior. (False)
12. The Software Requirements Specification (SRS) document includes both functional and non-functional
requirements. (True)
13. A structured specification provides a rigid template for documenting requirements. (True)
14. A use case diagram alone is sufficient for all software documentation. (False)
15. Use case diagrams are primarily used during the coding phase. (False)
16. Stakeholders play a role in defining user requirements. (True)
17. A pre-condition defines what must be true before a use case is executed. (True)
18. A post-condition defines the final state after a use case is executed. (True)
19. A use case must have at least one actor. (True)
20. Scenarios help capture real-world interactions with the system. (True)