A. Activity model
B. State-transition model
C. Flow model
D. Process model
A. User authentication and authorization
B. Database schema design
C. Business logic
D. Code comments and documentation
A. text
B. verification method
C. id
D. rationale
A. The vendor of specific tools (e.g. Cameo)
B. The SysML specification
C. The Systems Engineer
A. Yes but it is incomplete
B. No
C. Yes
A. To specify the sequence of messages between system components
B. To represent the dynamic behavior of a system in terms of states and transitions
C. To depict the static structure of a system in terms of components and their relationships
D. To illustrate the interactions between actors and the system
A. To identify stakeholders
B. To document the implementation details
C. To ensure project completion on schedule
D. To prioritize project risks
A. Something used in Behavior Diagrams
B. Something used in Kanbans
C. There is no such concept in SysML
A. True
B. False
A. The allocation of software components to hardware nodes
B. The interactions between actors and the system over time
C. An overview of the flow of control between system components
D. The dynamic behavior of a system in terms of states and transitions
A. Object Diagram
B. Activity Diagram
C. State Machine Diagram
D. Use Case Diagram
A. No
B. Yes
