Users and Tasks

See Also

In a USoft client/server application, every application user is also a database user. If no authorization is implemented, all application users are able to do everything. In practice, however, users will not need all tables, and they will not be allowed to use all tables. They will need certain tables to do their job, while other tables are beyond their scope of work.

The best way to get an overview of the authorization you need is to identify user tasks. Try to anticipate the various user tasks when making and changing your data model.

After you have made an inventory of user tasks, divide these tasks into packages that you assign to certain user groups. Each user group has its own package - resulting, for example, in a menu system that only shows the possible tasks.