Technical details, frequently found within ERDs, such as optionality and specific numerical cardinalities, are omitted. ▪ĭata abstractions, such as referring to business objects in a more generic and general way, are not performed as they often lose the business intent and then become less recognizable to the business.
#Define yed code
▪īusiness data points are simply associated with the data objects they would belong to and are not taken through the data engineering process called “normalization” to separate attributes into code tables. ▪ĭiagramming conventions are that which emphasize what an individual can comfortably view and comprehend on an individual page. The names of the objects in the model are strictly restricted to language used within the business, excluding any and all technical terminology related to automation jargon. The scope of the model is from the perspective of a business subject area of data, as opposed to the scope of an automation project, automation application, automation database, or automation interface. The objective of the model is to communicate business knowledge to any individuals who are unfamiliar to the business. The characteristics of conceptual data models that are specific to it include the following: ▪
0 kommentar(er)
