📋 Chapter 5: Requirements Engineering & System Modeling Quiz

Test your comprehensive knowledge on Requirements and System Modeling

Part 1: Requirements Engineering Fundamentals

Q1 (2 points) What is the primary purpose of requirements engineering?
Q2 (2 points) Which of the following is a functional requirement?
Q3 (2 points) Non-functional requirements can be classified into three types. Which is NOT one of them?
Q4 (2 points) Which requirements elicitation technique involves watching people do their job?
Q5 (2 points) What is a user story in agile development?

Part 2: Requirements Validation & Management

Q6 (2 points) Which validation check ensures that a requirement clearly describes the functions needed?
Q7 (2 points) Requirements management is important because:

Part 3: System Modeling Fundamentals

Q8 (2 points) What is the primary purpose of system modeling?
Q9 (2 points) Which UML diagram shows the interactions between actors and the system?
Q10 (2 points) A sequence diagram shows:

Part 4: UML Diagram Types

Q11 (2 points) In a class diagram, what does a filled diamond represent?
Q12 (2 points) What is the difference between aggregation and composition?
Q13 (2 points) In a use case diagram, what does the <> relationship indicate?
Q14 (2 points) Activity diagrams are used to model:

Part 5: Context & Interaction Models

Q15 (2 points) What is the purpose of a context model?
Q16 (2 points) In a sequence diagram, what represents an object or participant?

Part 6: Behavioral Models & State Diagrams

Q17 (2 points) State diagrams (state machines) are used to model:
Q18 (2 points) In a state diagram, what represents the initial state?
Q19 (2 points) What is a "swimlane" in an activity diagram?

Part 7: True/False Questions

Q20 (1 point) User requirements should be written in technical language so developers can understand them.
Q21 (1 point) Ethnography is effective for understanding existing processes but cannot identify new features.
Q22 (1 point) In a class diagram, an empty diamond represents composition.
Q23 (1 point) The <> relationship in use cases is used for optional or exceptional behavior.
Q24 (1 point) Requirements validation should only be done after the system is implemented.
Q25 (1 point) A scenario is a structured form of a user story that includes starting situation, flow of events, and ending state.

Part 8: Match the UML Diagram to Its Purpose

Q26 (6 points) Match each UML diagram type with its primary purpose. Enter the letter (A-F) in the box next to each number.

Diagram Types:

Purposes:

A. Shows object classes and their associations
B. Shows interactions between actors and system
C. Shows sequence of interactions over time
D. Shows workflow and activities in a process
E. Shows how objects respond to events and change state
F. Shows system boundaries and external entities

Part 9: Multiple Selection Questions

Q27 (3 points) Select ALL that are generic activities in the requirements engineering process:
Q28 (3 points) Select ALL system perspectives that models can represent:

Your Score

0/50