liveBook · Manning

Primary action sequence

A primary action sequence is the normal ordered set of interactions between an actor and an application during a use case.

How 2 Manning books explain it

Object-Oriented Software Design in C++

The expected ordered set of interactions that occurs during a use case.

How it is used
Structures detailed use case behavior after a triggering actor starts an interaction.
How deep it goes
Defines ordered interactions, limits them to about 10 steps, and defers failures to alternate action sequences.
Examples
Uses a customer searching a book catalogue through an attribute form and receiving matching books.
What you can do after
Evaluate whether a use case is practical and split it when its action sequence becomes too complex.

Read how Object-Oriented Software Design in C++ explains primary action sequence →

Software Design for Python Programmers

A primary action sequence is the normal ordered set of interactions between an actor and an application during a use case.

How it is used
Structures the normal interaction flow within a use case description.
How deep it goes
Defines ordered actor-facing steps and limits them to about ten, while deferring failures to alternate sequences.
Examples
Uses a customer searching a book catalogue through an online form as its concrete interaction example.
What you can do after
Apply it via use case descriptions to document practical normal interactions from an actor’s perspective.

Read how Software Design for Python Programmers explains primary action sequence →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.