Is correct to represent setting options using use cases?
For example the user can: - enable background updates - change map color - change interval updates
A use case is a kind of behaviored classifier that specifies a [complete] unit of [useful] functionality performed by [one or more] subjects to which the use case applies in collaboration with one or more actors, and which [for complete use cases] yields an observable result that is of some value to those actors [or other stakeholders] of each subject.
I think options I listed are "useful" and yield to "an observable results that is of some value" . Am I wrong?
How should I represent this kind of actions?