Databases Reference
In-Depth Information
client's portfolio could constitute another sub-data model M2. There is now
a potential use for two data components: C1 corresponding to model M1
(historical performance data) and C2 corresponding to model M2 (client's
investment choices). Alternatively, it could start with use cases. For exam-
ple, consider the following use cases:
• U1 — Provide inquiry of client's investment elections.
• U2 — Provide investment election change update/change.
• U3 — Provide inquiry of investment performance data.
• U4 — Provide update of investment performance data.
• U5 — Calculate portfolio values for a given client.
U1 and U2 deal with the same information (a client's investment
choices). Similarly, U3 and U4 deal with the same information (investment
performance data). U5 deals with the client's investment choices as well as
investment performance data. Since investment performance data is inde-
pendent of a client's investment choices, the entities in the data model cor-
responding to investment performance data, can be said to be loosely cou-
pled with the entities pertaining to client investment elections. Therefore,
investment performance data as well as client investment choices are both
candidates for sub-data models with corresponding data components. The
implementation of U5 would then involve use of both data components.
CONCLUSION
The data component approach to data management can be valuable in
an environment involving object-oriented applications and relational data-
bases. The primary advantage provided by this approach is ensuring that
the application responsible for updating information is responsible for pro-
viding inquiry of the same information, thereby providing for superior
change management. This approach can be used in any environment that
allows development of component-based applications.
Search WWH ::
Custom Search