Back to the Data Model.
The Draft Business Rules have been defined and are listed below.
The Area being Modelled is :-
A General Design for an Insurance Database
Question: I am developing db 4 insurance association.
The db will enable member upload the transaction.
now a policy contain unique like policyno,effectivedate, expirydate, category where
category are motor, marine properties,etc
each category has different schema. eg motror store engineno,chasis no e.t.c. while
marine store shiptype e.tc the system will be used mainly 4 verification say by
engineno and it return whether the car is insured
with the detail.it will also give some statististal information like number of policy by category.
what will be the best db design
1) store the category information as xml
2)create seperate table for each category
3) any other idea
A. DESIGN NOTES :
From the User Requirements defined above, we can derive the following Business Rules :-
B. The Things of Interest, ('THINGS'), include :-
B.2 Insurance Policies.
B.4 Others to be determined.
C. These THINGS are Related as follows :-
D. Other Characteristics of these THINGS include :-
E. Sample Data includes :-
F. Typical Enquiries include :-
December 26th. 2010