A. To define data flows
B. To indicate functional requirements
C. To link requirements to the physical elements that realize them
D. To show system behavior
A. To capture the flow of data
B. To specify the movement from one state to another based on conditions
C. To define a sequence of events
D. To represent a state that a system can enter
A. Generalization
B. Composition
C. Satisfy Relationship
D. Dependency
A. Control Flow
B. Message
C. Fork Node
D. Join Node
A. Activity
B. Actor
C. Package
D. State
A. To indicate the number of instances of the part within the system
B. To define the constraints on the part's behavior
C. To specify the sequence of actions for the part
D. To define the data type of the part
A. It shows the detailed flow of data between blocks
B. It represents physical hardware components
C. It defines specific system behaviors
D. It allows the grouping of related model elements to structure the system model
