Re: Modeling User/Accounts

Responding to MySpamB8...

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).

I think you have already answered the question. B-) All Application Users have email addresses, including those not associated with Programs. So the email address is an attribute of Application User, not Program Contact. IOW,

[ApplicationUser]
+ emailAddress
... <common properties>
A
| R1
+-----------+--------------+
| |
[ProgramContact] [SysAdmin]
.... <contact properties> ... <admin properties>
| *
|
| R2
|
| related to
| 1
[Program]
... <program properties>


*************
There is nothing wrong with me that could
not be cured by a capful of Drano.

H. S. Lahman
hsl@xxxxxxxxxxxxxxxxx
Pathfinder Solutions
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
"Model-Based Translation: The Next Step in Agile Development". Email
info@xxxxxxxxxxxxxxxxx for your copy.
Pathfinder is hiring: http://www.pathfindermda.com/about_us/careers_pos3.php.
(888)OOA-PATH



.