Logical Data Model - Clients
3 posters
Page 1 of 1
Logical Data Model - Clients
Hi
I am trying to create a logical data model for the following scenario
A client can over time be one or more types but at one time period only one (Member or Beneficiary )
A client is a of type "Member" if the client has one or more current "Member Accounts"
The primary key of a Client is Client ID
The Primary Key of the member account is Member Id and Fund
What should my data logical model look like
Regards
Tim
I am trying to create a logical data model for the following scenario
A client can over time be one or more types but at one time period only one (Member or Beneficiary )
A client is a of type "Member" if the client has one or more current "Member Accounts"
The primary key of a Client is Client ID
The Primary Key of the member account is Member Id and Fund
What should my data logical model look like
Regards
Tim
tim_goodsell- Posts : 49
Join date : 2010-09-21
Re: Logical Data Model - Clients
I would create a single client dimension and a bridge. The bridge would contain the member ID, member accout ID, and relationship type, with an effective and expiration date value, and a current flag. The member ID would reference the 'parent' client and the member account ID would reference the children client IDs.
Re: Logical Data Model - Clients
A logical model or a dimensional model? There's really no such thing as a logical dimensional model, even though Kimball Group folks occasionally use the term. Here's what I came up with based on your post.
![Logical Data Model - Clients Diagra12](https://i.servimg.com/u/f48/13/68/93/59/diagra12.jpg)
![Logical Data Model - Clients Diagra12](https://i.servimg.com/u/f48/13/68/93/59/diagra12.jpg)
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
CLIENT - MEMBERSHIPS LOGICAL DATA MODEL
Thanks for feedback chaps
The requirements have firmed up a bit
At a moment in time a CLIENT can be either a "Member" and a "Beneficiary", just a "Member", just a "Beneficiary", or "Neither"
A CLIENT is a of type "Member" if he has one or more active "Member Accounts" during the time period. A CLIENT can therefore be a "Member" many times (just over different non-overlapping time periods). I suppose you can say a CLIENT has many MEMBERSHIPS, each membership is over a different time period
A "Member Account" is unique to a MEMBERSHIP
The primary keys for the entities are:
CLIENT ( CLIENT ID)
MEMBERSHIP (CLIENT ID, START DATE )
MEMBER ACCOUNT ( PK: FUND ID, MEMBER ID, FK : CLIENT ID)
The requiremets for "Beneficiary" are still to be established.
Can you please suggest a logical model for the above
Regards
Tim
The requirements have firmed up a bit
At a moment in time a CLIENT can be either a "Member" and a "Beneficiary", just a "Member", just a "Beneficiary", or "Neither"
A CLIENT is a of type "Member" if he has one or more active "Member Accounts" during the time period. A CLIENT can therefore be a "Member" many times (just over different non-overlapping time periods). I suppose you can say a CLIENT has many MEMBERSHIPS, each membership is over a different time period
A "Member Account" is unique to a MEMBERSHIP
The primary keys for the entities are:
CLIENT ( CLIENT ID)
MEMBERSHIP (CLIENT ID, START DATE )
MEMBER ACCOUNT ( PK: FUND ID, MEMBER ID, FK : CLIENT ID)
The requiremets for "Beneficiary" are still to be established.
Can you please suggest a logical model for the above
Regards
Tim
tim_goodsell- Posts : 49
Join date : 2010-09-21
![-](https://2img.net/i/empty.gif)
» difference between data mart and data warehouse at logical/physical level
» Logical Dimensional Model
» Tool to capture physical metadata, logical business model and relationship between the two?
» Conceptual and Logical Data Models
» Model Data
» Logical Dimensional Model
» Tool to capture physical metadata, logical business model and relationship between the two?
» Conceptual and Logical Data Models
» Model Data
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|