The most common pattern for this is to use a companion extension for your module, as extensions get a built-in settings screen for "free", avoiding the need to a separate table.

I'll update this answer with an example shortly.

If you only have a few settings, the most common pattern for this is to use a companion extension for your module, as extensions get a built-in settings screen for "free", avoiding the need for a separate table.

As Adrian says though, the native extension settings are stored as a serialised array, so if you have a large amount of settings data a separate table is the way to go.