Re: Modeling User/Accounts


Daniel T. wrote:
mySpamB8@xxxxxxxxx wrote:

I have a system with the following concepts:
*Programs (As in social service programs)
*Program Contacts (people who are associated with programs)
*Application Users (most users are Program Contacts, but some users are
system admins who aren't associated with a program)

All the above is fairly easily modeled, I think. However, I hit a snag
with the following spec:
*Application Users need an email address (for password retrieval
purposes).

So, all users have an email address, some users are Program Contacts,
others are System Admins. A couple of questions, are these two User
sub-types mutually exclusive? (i.e., can a System Admin also be a
Program Contact?) Can a User that is one, later become the other?

I generally will assume that "roles" can be independent traits because
requirements changing from mutually-exclusive to independence is fairly
common. Thus, my recommendation is to go ahead and assume they will be
independent. One can put in restrictions when they start out mutually
exclusive, but should make it easy to change to indie.

-T-

.

Relevant Pages

  • Re: Modeling User/Accounts
    ... *Programs (As in social service programs) ... system admins who aren't associated with a program) ... with the following spec: ... purposes). ...
    (comp.object)
  • Re: Modeling User/Accounts
    ... Daniel T. wrote: ... *Programs (As in social service programs) ... system admins who aren't associated with a program) ... username, and password. ...
    (comp.object)
  • Re: Modeling User/Accounts
    ... Matt McGill wrote: ... *Programs (As in social service programs) ... system admins who aren't associated with a program) ... ought to be shared somehow, but I can't figure out how to model it. ...
    (comp.object)
  • Re: Modeling User/Accounts
    ... *Programs (As in social service programs) ... system admins who aren't associated with a program) ... ought to be shared somehow, but I can't figure out how to model it. ...
    (comp.object)