UNIT 33 DATA ANALYSIS AND DESIGN: Understanding Data Models and Database Technologies

UNIT 33 DATA ANALYSIS AND DESIGN
Introduction:
Data analysis and design: this is the method of organizing the data. These data types and
architectures are to implemented in a database management system. In order to define the data
modelling methods are applied to the data.
Managing of a big amount of data and that is maybe structured or may be in unstructured is the
primary key of the information system. Data models are defining the structure data for storage
purpose in database management systems such as hierarchical model, or relational model. and
they can not be defined as unstructured data, for example, word processing, a digital signal such
as audio and video, and pictures also. the design of data model can be logical if it can be in form
of physical.
Data model:
The term data model refers, that how to manage the structure data it shows the method in which
data is to be organized. Data model show the structure of data in particular domain. And there is
every data mode is different. A data model expresses the classes of entities, that contain the
information about the company, attribute of such information, and relationship among them.
Data structure
The model that define the data in a particular or wey that is called data model. In this data
structure, various components are available classes, entity and attribute al these contain the
information about the organization (McKay, 2018).

LO1
Understand data models and database technologies
1.1 Critically compare different data models and schemas
The logical design of the database is represented by the data model. Here few model are given.
Relational model: this type of database doesn’t have any problems with multiple to one and one
to multiple. In this type of model, data is managed in tabular forms and that are related to one
another that is known as a relational model.
Figure 1: Relation model Source (Chegg, 2018)

Hierarchical model: it is the simplest way of arranging the database. In this type of model, each
node has it a parent or root node but it has single or various children that are known as child
nodes. Also, it can be said that data is to be arranged in the form of the tree structure (Varela,
2016).
1.2 Critically discusses the benefits and limitations of different database technologies:
DBMS:
Generally, a collection of records is known as database management, and it is to design for
managing the data and records.
Basically, there is four type of database system are defining here:
Object-oriented database management
Network database management
Hierarchical database management
Relational database management
In point1.1 I have discussed Hierarchical database management and Relational database
management. Here I will discuss the limitations and benefits of the different type of database
management system.
Figure 2: Hierarchical model Source (Cs, 2018).

Problem with traditional database management system:
The even traditional database model is suitable for simple or easy structures; in a simple
structure, it can easily detect the problem if each and every child has only single parents. But
when a large amount of data would have to manage then it is too difficult to manage the data
through traditional management. For an example, if the database that includes parents and their
children in the same organization then it is to be difficult to describe that parents those have
single child both are worked here or not. In database language it is called many to one or many-
to-many if there are various children then the traditional model cannot describe them effectively.
Solving this database problem by using the relational database:
RDBMS:
 A relational database doesn’t have this problem, because it permits to apply the one
record at any number of tables. A child record is managed in the table as a child of
relationship and the similar record is managed in the table of children that are attending
the company.” by preventing the duplication of the records hence same information could
be used in various ways, Without changing the record (Panwar, 2018)
Figure 3: RDBMS Sources (Panwar, 2018)

Data redundancy: if database is not perfect for any design that contains redundancies which are
not well for any designer. In traditional DBMS data redundancy is present but in relational
database system, there is no redundancy present.
Data independence: a database system has a big amount of data such as metadata is stored in
DBMS for retrieving the data easily. And also it would be required to sometimes it changes. But
whole data is dependent then it would be a tedious and difficult job.
Logical Data Independence: How can be data is managed inside the database, such type of information is
stored by logical data. It is the type of mechanism in which data liberalize as an actual data that is
present on disk. I want to make changes in the table then it cannot be changed.
Physical Data Independence: generally the entire scheme is logical, and all the data is stored in
the form of the bit. Physical data independence means it is the strength of changing the physical
data without affecting the logical data (tutorialspoint, 2018).
Normalization: in traditional DBMS normalization is not present but in relational DBMS
normalization is present.
Data integrity: it means that how much data is accurate consistency, when I making the
database it is essential to maintain the data integrity.
Transaction processing: it is used by the small organizations for dealing with little data and it
supports single users. And RDBMS can deal with a large amount of data.
Storage: Basically DBMS has stored the data in a navigational form or in hierarchical form. And
in RDBMS data is be stored in tables in which identifier is known as a primary key.
Concurrency control: it is the essential part of DBMS this is a mechanism for correcting the
data when more than one data transaction that accesses the similar data that is executed
concurrently according to time.

1.3 analyse different approaches to database design:
Top-down approaches: it starts from the basic idea that what is essential for the system, and
turn to specific details. This process includes the reorganization process of different entities.
Figure 4 Top-down Approach Sources (Owlgen, 2018)
Bottom-up approach: it is the exact opposite of top-down model at begins from the more
special detail and turn down to normal detail. And also in this model reorganization of attributes
are before the entities
Figure 5: bottom-up approach Sources (Owlgen, 2018)