Embedded Systems Development using SysML - Enterprise Architect

Chapter 3 – Audio Player Behavior
Behavior Modeling Roadmap
Behavior Modeling describes the dynamic behavior of the System as it interacts with users
and with the environment. You’ll use interaction diagrams and use cases to model
interactions between users and the system, and state machines to describe event-driven
behavior that’s not user-centric. Figure 1 shows the Roadmap activities.
act Model System Behavior
Start Behavior Modeling
Model Use Cases
Model Finite State
Behav ior
Allocate Requirements to
Use Cases
Allocate Requirements to
State Machines
Model Interactions for Use
Cases
Complete Behaior Modeling
Figure 1 – Behavior Modeling Roadmap
As you can see, you approach behavior modeling in two parallel branches, one for use cases
and the other for state machines. Each branch includes allocation of Requirements to model
elements (use cases or states). Use cases are described in natural language at the high
level, and are detailed on interaction (sequence) diagrams.
We’ll follow the roadmap through the remainder of this chapter by exploring the dynamic
behavior of our Audio Player example. Then in Chapter 4 we’ll explore the system structure
that supports the desired behavior. We use the terms “static” and “dynamic” to describe the
structural and behavioral parts of the model; structure is static in that it doesn’t change once
it’s defined, while behavior is dynamic – changing based on user actions or external events.