NATIONAL INSTITUTE OF TECHNOLOGY, CALICUT

DEPARTMENT OF ARCHITECTURE AND PLANNING

AR 4006 – COMPUTER APPLICATION IN ARCHITECTURE

DRIYA G HARI | B150809AR | SEM VIII

IJAZ AHMED | B150609AR | SEM VIII
 Data
 It is a collection of information.
 The facts that can be recorded and which have implicit meaning known as 'data'.
 Example: Customer ----- 1.cname.
2.cno.
3.ccity.
Database
INTRODUCTION
DATA
 It is a collection of interrelated data.

DATABASE
 These can be stored in the form of tables.
 A database can be of any size and varying complexity.
 A database may be generated and manipulated manually or it may be
computerized.
 Example: Customer database consists the fields as cname, cno, and ccity

CNAME CNO CCITY

  It is computerized system, whose overall purpose is to maintain the
information and to make that the information is available on demand.
 Advantages
1.Redundency can be reduced.
DATA BASE 2.Inconsistency can be avoided.
SYSTEM 3.Data can be shared.
4.Standards can be enforced.
5.Security restrictions can be applied.
6.Integrity can be maintained.
7.Data gathering can be possible.
8.Requirements can be balanced.

1950s and early 1960s:
 Data processing using magnetic tapes
for storage
 Tapes provide only sequential access
 Punched cards for input
DATA BASE Late 1960s and 1970s:
 Hard disks allow direct access to data
SYSTEM  Network and hierarchical data models
1980s:
 Research relational prototypes evolve
into commercial systems
 Parallel and distributed database
systems
 Object-oriented database systems
1990s:

HISTORY in widespread use  Large decision support and data-mining

 Ted Codd defines the relational data
model
 Would win the ACM Turing Award for
this work
 IBM Research begins System R
prototype
 UC Berkeley begins Ingres prototype
 High-performance (for the era)
transaction processing
applications
 Large multi-terabyte data warehouses
 Emergence of Web commerce
2000s:
 XML and XQuery standards
 Automated database administration
  It is a collection of programs that enables user to create and maintain a
database.
DBMS  In other words it is general-purpose software that provides the users with
DATA BASE MANAGEMENT
SYSTEM
the processes of defining, constructing and manipulating the database for
various applications.

DBMS
CHARACHTERISTICS
Traditionally, data was organized in
file formats. DBMS was a new
concept then, and all the research
was done to make it overcome the
deficiencies in traditional style of
data management. A modern
DBMS has the following
characteristics:
 Real-world entity: A modern DBMS is more realistic and uses real-world
entities to design its architecture. It uses the behaviour and attributes too. For
example, a school database may use students as an entity and their age as an
attribute.
 Relation-based tables: DBMS allows entities and relations among them to
form tables. A user can understand the architecture of a database just by
looking at the table names.
 Isolation of data and application: A database system is entirely different
than its data. A database is an active entity, whereas data is said to be passive,
on which the database works and organizes. DBMS also stores metadata,
which is data about data, to ease its own process.
 Less redundancy: DBMS follows the rules of normalization, which splits a
relation when any of its attributes is having redundancy in values.
Normalization is a mathematically rich and scientific process that reduces
data redundancy.
 Consistency: Consistency is a state where every relation in a database
remains consistent. There exist methods and techniques, which can detect
attempt of leaving database in inconsistent state. A DBMS can provide
greater consistency as compared to earlier forms of data storing applications
like file-processing systems.
 Query Language: DBMS is equipped with query language, which makes it
more efficient to retrieve and manipulate data. A user can apply as many and
as different filtering options as required to retrieve a set of data. Traditionally
it was not possible where file-processing system was used.
  ACID Properties: DBMS follows the concepts of Atomicity, Consistency,
Isolation, and Durability (normally shortened as ACID). These concepts are
applied on transactions, which manipulate data in a database. ACID properties
help the database stay healthy in multi-transactional environments and in
case of failure.
 Multiuser and Concurrent Access: DBMS supports multi-user environment
and allows them to access and manipulate data in parallel. Though there are
restrictions on transactions when users attempt to handle the same data item,
but users are always unaware of them.
 Multiple views: DBMS offers multiple views for different users. A user who is
DBMS in the Sales department will have a different view of database than a person
CHARACTERISTICS working in the Production department. This feature enables the users to have
a concentrate view of the database according to their requirements.
 Security: Features like multiple views offer security to some extent where
users are unable to access data of other users and departments. DBMS offers
methods to impose constraints while entering data into the database and
retrieving the same at a later stage. DBMS offers many different levels of
security features, which enables multiple users to have different views with
different features. For example, a user in the Sales department cannot see the
data that belongs to the Purchase department. Additionally, it can also be
managed how much data of the Sales department should be displayed to the
user.
  Disadvantages
1. Data redundancy and inconsistency.
2. Difficult in accessing data.
3. Data isolation.
4. Data integrity.
5. Concurrent access is not possible.
DBMS 6. Security Problems. .
ADVANTAGE & DISADVANTAGES  Advantages
1. Data Independence.
2. Efficient Data Access.
3. Data Integrity and security.
4. Data administration.
5. Concurrent access and Crash recovery.
6. Reduced Application Development Time.
  Banking: all transactions
 Airlines: reservations, schedules
 Universities: registration, grades
DBMS  Sales: customers, products, purchases
APPLICATIONS
 Online retailers: order tracking, customized recommendations
 Manufacturing: production, inventory, orders, supply chain
 Human resources: employee records, salaries, tax deductions

END
USERS
ADMINI-
DBMS STARTORS
USERS
A typical DBMS has users with
different rights and permissions
who use it for different purposes.
Some users retrieve data and some
back it up. The users of a DBMS can
be broadly categorized as follows:
DESIGNERS
• End users are those who
actually reap the benefits of
having a DBMS. End users can
range from simple viewers who
pay attention to the logs or
market rates to sophisticated
users such as business
analysts.
• Administrators maintain the
DBMS and are responsible for
administrating the database.
They are responsible to look
after its usage and by whom it
should be used. They create
access profiles for users and
apply limitations to maintain
isolation and force security.
• Designers are the group of
people who actually work on the
designing part of the database.
They keep a close watch on what
data should be kept and in what
format. They identify and design
the whole set of entities,
relations, constraints, and views.
  The design of a DBMS depends on its architecture. It can be
centralized or decentralized or hierarchical.
 The architecture of a DBMS can be seen as either single tier or
multi-tier. An n-tier architecture divides the whole system into
related but independent n modules, which can be independently
modified, altered, changed, or replaced.
DBMS  Eg: A 3-tier architecture separates its tiers from each other based
on the complexity of the users and how they use the data present
ARCHITECTURE
in the database. It is the most widely used architecture to design a
3-TIER ARCHITECTURE DBMS.

PRESENTATION APPLICATION DATABASE

TIER TIER TIER
  Database (Data) Tier: At this tier, the database resides along with
its query processing languages. We also have the relations that
define the data and their constraints at this level.
 Application (Middle) Tier: At this tier reside the application server
and the programs that access the database. For a user, this
3 TIER application tier presents an abstracted view of the database. End-
users are unaware of any existence of the database beyond the
ARCHITECTURE application. At the other end, the database tier is not aware of any
other user beyond the application tier. Hence, the application
layer sits in the middle and acts as a mediator between the end-
user and the database.
 User (Presentation) Tier: End-users operate on this tier and they
know nothing about any existence of the database beyond this
layer. At this layer, multiple views of the database can be provided
by the application. All views are generated by applications that
reside in the application tier.
  The entire structure of a database can be described using a data
model.
 A data model is a collection of conceptual tools for describing.
 Data models can be classified into following types.

1.Object Based Logical Models.

DATA MODELS These models can be used in describing the data at the logical and
view levels. These models are having flexible structuring capabilities.
INTRODUCTION
2.Record Based Logical Models.
These models can also be used in describing the data at the logical and
view levels. These models can be used for both to specify the overall
logical structure of the database and a higher-level description.
3.Physical Models.
These models can be used in describing the data at the lowest level,
i.e. physical level.
 DATA
MODELS

Object Based Record Based

Physical
Logical Logical
Models
Models Models

Entity- Object- Frame

Semantic Functional Relational Network Hierarchal Unifying
relationship oriented memory
data model data model model model. mode model
model model model.
  Entity-Relationship (ER) Model is based on the notion of real-
1. world entities and relationships among them. While formulating
real-world scenario into the database model, the ER Model
Entity- creates entity set, relationship set, general attributes, and
Relationship constraints.

Model  ER Model is based on:

 Entities and their attributes.
 Relationships among entities
  Entity
An entity in an ER Model is a real-world entity having properties
called attributes. Every attribute is defined by its set of values
called domain.

Entity- For example, in a school database, a student is considered as an

entity. Student has various attributes like name, age, class, etc.
Relationship  Relationship
Model The logical association among entities is called relationship.
Relationships are mapped with entities in various ways.
Mapping cardinalities define the number of association between
two entities. Mapping cardinalities:
 one to one
 one to many
 many to one
 many to many
  The most popular data model in DBMS is the Relational Model. It
is more scientific a model than others. This model is based on first-
order predicate logic and defines a table as an n-ary relation.

2.
Relational
Model

 Data is stored in tables called relations.

 Relations can be normalized.
 In normalized relations, values saved are atomic values.
 Each row in a relation contains a unique value.
 Each column in a relation contains values from a same domain.
 Apache Giraph
 Apache Giraph is real-time graph processing software that is mostly
used to analyze social media data. Giraph was developed by Yahoo!
and given to the Apache Software Foundation for future
management.
column database management system (CDBMS)
 There are different types of CDBMS offerings, with the common
DBMS defining feature being that data is stored by column (or column
families) instead of as rows.
SOFTWARES CouchDB
 CouchDB is an open source document-oriented database based on
common web standards. NoSQL databases are useful for very large
sets of distributed data, especially for the large amounts of non-
uniform data in various formats that is characteristic of Web-based
data.
data catalog
 A data catalog is a metadata management tool designed to help
organizations find and manage large amounts of data – including
tables, files and databases – stored in their ERP, human resources,
finance and e-commerce systems as well as other sources like social
media feeds.
 Google Cloud Spanner
 Google Cloud Spanner is a distributed relational database service that
runs on Google Cloud.
MariaDB
 MariaDB is an open source relational database management system
(DBMS) that is a compatible drop-in replacement for the widely used
MySQL database technology.
DBMS NoSQL (Not Only SQL database)
SOFTWARES  NoSQL is an approach to database design that can accomodate a
wide variety of data models, including key-value, document, columnar
and graph formats. NoSQL, which stand for "not only SQL," is an
alternative to traditional relational databases in which data is placed
in tables and data schema is carefully designed before the database is
built.
NuoDB
 NuoDB is a SQL-oriented transactional database management
system designed for distributed deployment in the cloud.
THANK YOU