A question about Embedded Systems Development using SysML

[Volkan]

I just read a ebook named "Embedded Systems Development using SysML: An Illustrated Example using Enterprise Architect" downloaded from iconixsw.com. I have a question concerning Chapter 3 Audio Player Behavior of the book. When modeling the system behaviors, why don't we establish activity diagrams for the example Audio Player? Thank you!

[qwerty]

I guess you should ask that the author of the book. Or you need to post some more details here.

q.

[Geert Bellekens]

I don't think Doug visits this forum all too often.

Geert

[qwerty]

Indeed. His 2nd and last post is 3 years old: http://sparxsystems.com/forums/smf/index.php/topic,7602.msg136069.html#msg136069

q.

[PeterHeintz]

I belief it is just the preference of the author.
The languages to describe behavior in SysML are state machines, sequence diagrams, activities diagrams and use cases (depends on whether you interpreted use cases as behavior or not).
In the book mainly state machines and sequence diagrams are used for the system and activity diagrams are used to define the used modelling approach.
Several kind of behavior can be defined not only with one language type but with several. It often depends on the preference of the modeler. Especially for sequence diagrams and activity diagrams there are often no clear criteria what to use to define some behavior.
I even know people saying that there is no need for sequence diagrams at all, just use activity diagrams. Maybe the author goes in the other direction and prefers just sequences over activities.

[ChB]

I suggest it's simply a "weakness" of the book - nothing more than that.
I feel the weakness starts in Chapter 1, Figure 4, where the Model System Behaviour roadmap does not show Activity Diagram creation even though the text beneath states that Activity Diagrams are part of Behavioural modelling.

Activity Diagrams are mentioned in Chapter 3 (last paragraph between figures 11 and 12, and in second from last paragraph of Chapter 3) .

I think the book could be "improved" by including Activity Diagramming in the Chapter 1, Figure 4, roadmap and with an example in Chapter 3.

Activity Diagrams feature more heavily in Chapter 7 when discussing code generation.

I've found it a "good book" as it discusses a "process" or "methodology" that I can apply to the type of work I do.

(My opinions only. Hope this helps.)

[Volkan]

I belief it is just the preference of the author.
The languages to describe behavior in SysML are state machines, sequence diagrams, activities diagrams and use cases (depends on whether you interpreted use cases as behavior or not).
In the book mainly state machines and sequence diagrams are used for the system and activity diagrams are used to define the used modelling approach.
Several kind of behavior can be defined not only with one language type but with several. It often depends on the preference of the modeler. Especially for sequence diagrams and activity diagrams there are often no clear criteria what to use to define some behavior.
I even know people saying that there is no need for sequence diagrams at all, just use activity diagrams. Maybe the author goes in the other direction and prefers just sequences over activities.

Dear Peter, thank you very much for the reply!

[Volkan]

I suggest it's simply a "weakness" of the book - nothing more than that.
I feel the weakness starts in Chapter 1, Figure 4, where the Model System Behaviour roadmap does not show Activity Diagram creation even though the text beneath states that Activity Diagrams are part of Behavioural modelling.

Activity Diagrams are mentioned in Chapter 3 (last paragraph between figures 11 and 12, and in second from last paragraph of Chapter 3) .

I think the book could be "improved" by including Activity Diagramming in the Chapter 1, Figure 4, roadmap and with an example in Chapter 3.

Activity Diagrams feature more heavily in Chapter 7 when discussing code generation.

I've found it a "good book" as it discusses a "process" or "methodology" that I can apply to the type of work I do.

(My opinions only. Hope this helps.)

Thank you very much!