Vous êtes sur la page 1sur 13

ACCOUNTING INFORMATION SYSTEM II

(DATA BASE MANAGEMENT SYSTEM)

CREATED BY:
KRISNAWATI BR HOMBING (2016031128)
MONIKA DESI DERIA BR GINTTING (2016031090)

LECTURER:
SWESTI MAHARDINI

SEKOLAH TINGGI ILMU EKONOMI YAI


2018/2019
DAFTAR ISI

DAFTAR ISI ………………………………………………………………………………….

Pengenalan Basis Data ……………………………………………………………………

1.1 Definisi Basis Data ………………………………………………………………………

1.2 Model Basis Data………………………………………………………………………...

Basis Data Relasional ……………………………………………………………………..

2.1 Perancangan Basis Data Relasional ………………………………………………….

2.2 Metodologi Perancangan Basis Data………………………………………………….

Basis data dalam lingkungan terdistribusi…………………………………………….

3.1 Definisi Basis Data Terdistribusi………………………………………………………..

3.2 Struktur Basis Data Terdistribusi……………………………………………………….

3.3 Ciri Ciri Basis Data Terdistribusi………………………………………………………..

3.4 Keuntungan dan Kerugian yang diberikan oleh sistem basis data terdistribusi…..

3.5 Desain Basis Data Terdistribusi ……………………………………………………….

DAFTAR PUSTAKA …………………………………………………………………………


INTRODUCTION TO DATA BASIS

In an institution, data is one of the most important things. Each part / division of the
institution has its own data. But every part also needs some data from other parts. This
is commonly known as "shared data". Each division has its own application in
manipulating and retrieving the data. Each application has files in the operating system
that are used to store data. Along with the development of institutions, increasing parts /
divisions, also increases data and applications used. Increased application, also added
files created.

The style of the file-processing system causes each data to be stored in the form of
records in various kinds of files, and different applications are needed to retrieve
records from, and add records to the file. This applies in the period before the existence
of the Database System.

1.1 Definition of Database

The database is the storage of a collection of information systematically in a computer


so that it can be checked using a computer program to obtain information from the
database. The software used to manage and call queries (database queries) is called a
database management system (Database Management System, DBMS). DBMS has
the following characteristics:

• Software program
• Supplements operating sistem
• Manages data
• Queries data and generates reports
• Data security
1.2 Database Model

 Hierarchical
Having a tree structure where fields only have one parent, each parent has many
children. This model has a good speed.

 Network
Relationship is made using a linked list (pointer). Unlike the hierarchical model one child
can have several parents. This model has high flexibility.

 Relational
This model is represented in a two-dimensional table, these tables have a relationship
called a relation. This model has high flexibility and speed.Object oriented

Object Oriented Database is a database system that combines all object oriented
concepts such as inheritance, abstraction, encapsulation, etc. This model can interact
well with object-oriented programming languages such as java and C ++.

Database Model

RELATIONAL DATA BASE


In recent years, database management systems (DBMS) have become the choice
in terms of data storage for information systems ranging from processing large
commercial transaction applications to desktop PC-based applications. Most of those
used at this time are relational database models using the Relational Database
Management System (RDBMS). RDBMS provides easy data organizing services but has
the ability to handle huge amounts of data. Some examples of RDBMS include:

 SQL Server, made by Microsoft.


 MS Access, made by Microsoft.
 Oracle Database, made by Oracle.
 MySQL, made by MySQLAB.
 Firebird, made by the open source community based on the Interbase code.
 PostgreSQL, made by the open source community.
 DB2, made by IBM.

The relational database has a "logical" structure called Relations. Relationship structure
is a 2-dimensional data structure and at the "physical" level in the form of a table (table).
An attribute represents an element of data related to a relation. For example, Student
relations have attributes such as nim, name, place of birth. birth date, and address.

In textbooks about database design, a relation is denoted conventionally with Relation


(attribute1, attribute2, ..) with rules: names of relations and attributes of relations that are
in parentheses.

For example: Students (NIM, Name, Address, Jenis_kelamin ...).


Data values of attributes of a relation will be stored in tuples or rows from the table. The
picture below is an illustration of a relation.

2.1 Design of a Relational Database

It is a process to represent the desired real world facts into a computer system, so that
the user is easily understood by considering the ease of implementation and processing.

The purpose of database design:

• Meet the information needs at this time and in the future

• Ease of development in accordance with organizational development

• Implementation of data security mechanisms

The term 'real world' is meaningful to all unstructured data that is real / related in the
scope of the system being reviewed. The real world here can be said to be a domain as
a whole / full or subdomain, for example if we consider a company as a domain then we
can assume the units in the company are subdomains or it could be a business process
or activity in we can also consider the company as a subdomain and even a domain.
Every real world that exists has unequal characters. For example the real world for the
banking system is definitely not the same as the real world for the hospital system.

2.2 Database Design Methodology

Is a way of how a database is made through certain stages, starting from the problem
investigation stage to the implementation stage.

In general there are two stages of the database design process, namely:

 designing database logic


 physical database design

1. Designing database logic

 Is a process of defining entities and relations (Relationship) from the real world
that are designed, based on information needs and processing data from the
organization concerned.
 Entity / entity is a set of objects that can be identified and distinguished in the user
environment
 Relations are relationships that occur between groups of entities.
 The goal of designing database logic is the flexibility of the data model generated
and the efficiency of its implementation in the computer.

2. Physical design of the database

It is a process to implement the results of logic design into a computer physically that
depends on the DBMS software selected. The process carried out:

• Send input

• History

• Determine the structure for each table, including field names, types, widths and key
fields.
• Determine the name of the database and the name of each table, as well as the location
of the storage (drive, directory / folder).

• Calculate the approximate space needed for all tables and for the entire index.

• Implementation using DBMS software.

There are two approaches in the design:

1. Conventional approach

Database design without going through the conceptual design stage. In general, the
design steps are as follows:

• Modeling relationships

• Normalization

• Implementation using certain DBMS (Access, SQL, etc.). Table structure, key
attributes, integrity rules, relationships between tables
Implementasi
Pembuatan melalui DBMS
Normalisasi
REAL Model Skema Basis
WORLD Data Basis Data
Model
Relasi Data
relasi

Conventional approach

2. Entity-Relationship approach

Using the conceptual model approach. In general, it has the following stages:

- Conceptual modeling (E-R model)


- Identify the entity and its attributes
- Defining relationships between entities
- Determination of relationship attributes between entities
- Draw an E-R diagram
- Transformation into a relationship model
- Nomination
- Implementation using certain DBMS (Access, SQL, etc.). Table structure, key
attributes, integrity rules, relationships between tables
Imple-
mentasi
Normalisasi melalui
Pembuatan
Model Model Skema DBMS
REAL Data Data Basis Basis
WORLD E-R Relasi Data Data
Model
Kon-
septual

DATA BASE IN DISTRIBUTION ENVIRONMENT

3.1 Definition of Distributed Databases

Distributed Database is a collection of logical data that are interconnected physically


distributed in a computer network, which does not depend on the current and future
application programs.

A file is a data set that is designed for an application or a set of applications that are
close to it.

Example of a Distributed Database

For example a bank that has many branches, even in a city can consist of several
branches / offices. Each location has its own local network, and all local networks are
connected to each other to form a national network.

3.2 Distributed Database Structure

A distributed database system may only be built into a computer network system.

Network Topology
a. Star topology

b. Ring Topology

c. Bus Topology

The main difference between the various topologies above lies in:

a. Cost of Installing Costs in establishing link relationships) between nodes.

b. Communication Costs Time and costs in operating the system are in the form of
sending data from one node to another.

c. Reliability Frequency / level of communication failure that occurs.

d. Availability of Level of data readiness that can be accessed in anticipation of


communication failure.

3.3 Characteristics of Distributed Databases

Data is stored in a number of places

Processors in different places are connected to computer networks

Distributed database systems do not consist of a set of files that are in various places
but in a database in various places

Each place independently processes user requests that need access to data in that
place and are also able to process data stored elsewhere.

3.4 Advantages and Disadvantages provided by distributed database systems

Advantages:

Transparent management of distributed data

Refer to the organizational structure

Increase for sharing and local autonomy


Increase data availability

Increase reliability

Improve work performance

Facilitate system development

Disadvantages:

- Management complexity
- Integrity control is more difficult
- Development costs
- Security
- Difficulty in standardization
- Increase storage requirements
- More difficult in managing the data environment

3.5 Distributed Database Design

There are several approaches related to storing data / tables in a distributed database
system, namely:

1. Replication

2. Fragmentation

3. Replication and Fragmentation

1. Replication

The system maintains a number of copies / duplicate data tables.

Each copy is stored in a different node, which results in data replication

2. Fragmentation
The data in the table is sorted and distributed into a number of fragments.

Each fragment is stored in a number of different nodes.

Fragmentation can take the form of horizontal fragmentation (sorting of data records) or
vertical fragmentation of sorting data / attribute data)

3. Replication and Fragmentation

- Is a combination of replication and fragmentation.

- Data / tables are sorted in a number of fragments.

The system then manages a number of copies of each of these fragments in a number
of nodes.

Data Replication

Advantages: 1. High availability. 2. Increasing Parallels (Increased parallelism) 3.


Increasing the burden of changing data (Increased overhead on upate)
DAFTAR PUSTAKA

1. Raghu Ramakrishnan / Johannes Gehrke “Database Management System”


Second edition.

2. Silberschatz-Korth-Sudarshan: DatabaseSistem Concepts, Fourth Edition.2001

3. Handbook Telkom Polytechnic : Database Management Systems

4. Oracle Database 10g: Administration Workshop I, volume I: Student Guide

Vous aimerez peut-être aussi