Question no 1

Entity type:
The entity type is the fundamental building block for describing the structure of data with
the Entity Data Model (EDM). An entity type represents the structure of top-level
concepts, such as customers or orders.

Entity Relationship Model (ER Modeling):

entity Relationship Model (ER Modeling) is a graphical approach to database design. ...
An Entity is a thing or object in real world that is distinguishable from surrounding
environment. For example, each employee of an organization is a separate entity.
Following are some of major characteristics of entities.

instance:
The data stored in database at a particular moment of time is
called instance of database. Database schema defines the variable declarations in tables
that belong to a particular database; the value of these variables at a moment of time is
called the instance of that database.

Attribute:
In a database management system (DBMS), an attribute refers to a database component, such
as a table. It also may refer to a database field. Attributes describe the instances in the row of a
database.

Relationship type:
A relationship type is the type of association between two or more entities. For example
teacher teaches student where teacher and student are two entities and the relationship
type between them is teaches.

Identifier:
A database identifier is a database object name. Tables, views, columns, indexes,
triggers, procedures, constraints, and rules can have identifiers.

Multivalued attribute:
An attribute that can hold multiple values is known as multivalued attribute. It is
represented with double ovals in an ER Diagram. For example – A person can have more
than one phone numbers so the phone number attribute is multivalued.

Associative entity:
An associative entity is a term used in relational and entity–relationship theory. A
relational database requires the implementation of a base relation (or base table) to
resolve many-to-many relationships. A base relation representing this kind of entity is
called, informally, an associative table

Cardinality constraint:
Cardinality constraint defines the maximum number of relationship instances in which an
entity can participate.

weak entity:
weak entity is one that can only exist when owned by another one. For example: a room
can only exist in a building. On the other hand, a tire might be considered as a strong
entity because it also can exist without being attached to a car.

identifying relationship:
An identifying relationship is when the existence of a row in a child table depends on a
row in a parent table. This may be confusing because it's common practice these days to
create a pseudo key for a child table, but not make the foreign key to the parent part of
the child’s primary key. Formally, the right way to do this is to make the foreign key part
of the child's primary key. But the logical relationship is that the child cannot exist without
the parent.

derived attribute:
A derived attribute is an attribute whose value is calculated (derived) from
other attributes. The derived attribute need not be physically stored within the database
instead it can be derived by using an algorithm.

business rule:
A business rule is a statement that imposes some form of constraint on a specific aspect
of the database, such as the elements within a field specification for a particular field or
the characteristics of a given relationship.

Question no 2
Data Dependence:
An application program that deals with data stored externally to it (such as in a file or a
database) includes in its source code some structural definition of that data. The extent
to which that program is exposed to changes made to that external source is called data
dependence.

Data independence:
Data independence is the type of data transparency that matters for a centralized DBMS.
It refers to the immunity of user applications to changes made in the definition and
organization of data. is the type of data transparency that matters for a centralized DBMS
It refers to the immunity of user applications to changes made in the definition and
organization of data?

Structured data:
Structured data is highly-organized and formatted in a way so it's easily searchable in
relational databases

Unstructured data:
Unstructured data has no pre-defined format or organization, making it much more
difficult to collect, process, and analyze .

Data and information:

Data can be something simple and seemingly random and useless until it is organized.
When data is processed, organized, structured or presented in a given context so as to
make it useful, it is called information.

Entity and Enterprise Data Model:

The main difference between Entity and Enterprise Data Model is that Entity Data Model is a
model that describes the structure of data despite the stored form, while Enterprise Data Model is
a model used by an organization

ERP and Data Warehousing:

Data warehouses are required because ERP systems don’t store the data in a manner
that supports analysis and reporting. They also do not always gather all available data
because of system incompatibilities and increasing amounts of information from systems
external to the enterprise.

Two tier and three tier:

In a 3 tier coach, there are 8 berth in 1 compartment. Precisely lower, middle, upper berth,
side lower and side upper. Whereas, in a 2 tier coach, there are 6 berth in 1 compartment.
They are lower, upper berth, side lower and side upper.

Prototyping and SDLC:

Prototyping produces an early, rapidly constructed working version of the proposed
information system known a prototype contrast, SDLC is a system
development approach which follows step-by-step procedures.

Conceptual Data Models – Highest-level relationships between different entities.

Enterprise Data Models – Addresses unique requirements of a specific business .