先試後買

A. To indicate that one block refers to another without owning it

B. To automate a behavior flow

C. To define an inheritance relationship between blocks

D. To describe a whole-part relationship

A. A system requirement

B. An event

C. A behavior

D. A class or component in the system that defines its structure and properties

A. The number of instances of a part that are allowed or required in the system

B. The number of times a behavior occurs

C. The performance attributes of the part

D. The sequence of events involving the part

A. Stereotype

B. Requirement

C. Block

D. Allocation relationship

A. Stereotypes define new types of allocation relationships.

B. Allocation relationships are used to apply stereotypes.

C. Both allocation and stereotype application are customization techniques but serve different purposes.

D. Both can only be applied to blocks in SysML.

A. To model the flow of items such as data, energy, or materials between parts

B. To represent the hierarchy of system components

C. To establish a dependency between requirements

D. To describe the behavior of a system

A. To represent a state that a system can enter

B. To define a sequence of events

C. To specify the movement from one state to another based on conditions

D. To capture the flow of data

A. It represents physical hardware components

B. It allows the grouping of related model elements to structure the system model

C. It defines specific system behaviors

D. It shows the detailed flow of data between blocks

A. UML Sequence Diagram

B. BPMN

C. Flowchart

D. Data Flow Diagram