Need Re phrase the paper
keekov
module_7.docxDATA MODEL
The set of concepts that describes the structure of the database and the constraints of it is know as Data Model. This organises the data for various users.
ENTERPRISE DATA MODELLING
The Enterprise data modelling is the way to understand data elements and their relationships. It is also referred as Global Business Model. The entire information about the enterprise would be taken in the form of entities (anything about which data will be collected).
It is an integrated subject oriented data model which defines the essential data produced. Here essential means the enterprise data model provides the data which defines the importance of the enterprise. Integrated means that all the entities, attributes, rules in the model are defined once without redundancy.
Enterprise data modelling helps us to address the important requirements of the Vinyl Records and it has the ability to define how the data is stored, processed and accessed physically by administrator. It gives the clear idea about the database and explains how the data is maintained in different departments of store. This data from different departments of the store in the form of different entities. The basic business concepts of this store database are identified and explained by the enterprise data model and interrelates different data sets in-between the entities.
ENTERPRISE DATA MODEL FOR VINLY RECORDS:
VISUAL FORM OF ENTERPRISE DATA MODEL FOR VINLY RECORDS
OPERATING RULES OF ENTERPRISE DATA MODELLING
In this data model it facilitates interaction among the designer, the application programmer and the end user. EDM is a living model. One of the important things to be considered is that the attributes with same name may be present in several entities, so the attribute names and the data types should be standardised and should be connected to the same attribute present in several tables. Sometimes enterprise logical model transforms into physical model so according to requirements changes have to be done, so that standardization of data model can be maintained throughout the process.
RULE REFLECTION:
· Enterprise data model includes a large number of entities so sometimes it becomes complex to construct (or) design a data model that is useful.
· A general and a better approach are to start with top level data model with a limited number of entities.
· Hence data model built with the design of limited entities will complement the top level model which will allow us to cover a wide range of functionalities within the enterprise.
CONCLUSION:
The enterprise data model is the model which consists of enterprise-wide subject areas, fundamental entities and their relationships which helps to improve communication between IT and business organisations. The enterprise data model is the foundation of the data which is reusable, consistent and shareable. Being able to create enterprise data models will help you to handle the most challenging situations that might encounter for a data modeller.
REFERENCES:
Anna, M. (2008). Overview of Enterprise Data Architecture- What’s In YOUR Data Architecture? Retrieved from
http://www.dama-ncr.org/Library/20080513DataArchitectureAMS.pdf
barry, W. Enterprise Data Models Retrieved from
http://www.databaseanswers.org/downloads/Chapter_8_Enterprise_Data_Models.pdf
modeling, d. (2015, june 14). learndata model.com. Retrieved from http://www.learndatamodeling.com/edm.php
Mehdi, H. (2008, april 16). Information management: The value of an Enterprise Data Model Retrieved from
Inventory Relative Value SalesCsutomer Vendor Item Id PKItem Id PKCustomer ID PKCistomer ID PKVendor IdPKProduct Name VersionPriceSelling Product Invenstment Name of the recordVersion PriceDate of PurchasePurchase Id Item ID Selling and Buying Price Name Telephone Number Billing Address Value Of Treasue
Inventory Relative Value Sales Csutomer Vendor Item Id int FK PK Item Id int FK PK int FK PK Customer ID int FK PK Cistomer ID int FK PK Vendor Id int FK PK M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4 Product Name int FK PK Version int FK PK Price int FK PK Selling Product int FK PK Invenstment int FK PK Name of the record int FK PK Version int FK PK Price int FK PK Date of Purchase int FK PK Purchase Id int FK PK Item ID int FK PK Selling and Buying Price int FK PK Name int FK PK Telephone Number int FK PK Billing Address int FK PK M1 M2 M3 M4 M1 M2 M3 M4 Value Of Treasue int FK PK
