Database use case in a use case diagram

UML
#1

Hi,

When including a database as a use case in a system in a use case diagram, would you use an include arrow to the database if something will save information to the database if it happens every time, or would you just use an association?

Thanks

#2

would you use an include arrow to the database if something will save information to the database if it happens every time

The frequent commits suggests that the database is actually part of your system. For the purpose of a use case diagram, I suggest treating the database as one with your system but consider whether you even need to model the database in your use case diagram. Does the database affect system behaviour in terms of interaction?

For example, if you need to model that the database system can detect errors and the system needs to react and behave a certain way, then that’s a case where the database acts on the system but personally, something like that is where I draw the line on how detailed my use cases need to be.