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.

Yes, that's all correct, and Program Contacts have a dozen more
properties than System Admins, who don't have much more than email,
username, and password.

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?

They are indeed mutually exclusive, and a Program Contact can never
become a Sys Admin (and vice-versa).

Thanks,
Jamie

.

Relevant Pages

  • Re: Modeling User/Accounts
    ... Daniel T. wrote: ... *Programs (As in social service programs) ... system admins who aren't associated with a program) ... purposes). ...
    (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)
  • 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)