20
By: Devi Sumadi - 26406016 The The Administration Administration information system information system design design and construction of UD. Usaha and construction of UD. Usaha Jaya Engineering Equipment Jaya Engineering Equipment Company Company

By: Devi Sumadi - 26406016 The Administration information system design and construction of UD. Usaha Jaya Engineering Equipment Company

Embed Size (px)

Citation preview

By:Devi Sumadi - 26406016

The The Administration information system Administration information system design and construction of UD. design and construction of UD.

Usaha Jaya Engineering Equipment Usaha Jaya Engineering Equipment CompanyCompany

Background of The StudyBackground of The Study

In the purchases system, the store makes the purchase order by typing it using a previously created template in Microsoft Word.

In the sales system, firstly the administration must confirm the warehouse inventory, whether the goods that the customer order is sufficient or not.

Background of The StudyBackground of The Study

In the inventory recording, the warehouse worker needs to write it in the stock card. So if something goes wrong can cause invalid of data.

The salary recording is also written in the book so there is a possibility of error.

When the stock of the goods is approaching the minimum limit, there is no warning to make the order for the supplier .

Making the report usually takes a long time because the recording system is still using the manual method.

Statement of The ProblemStatement of The Problem

This thesis will discuss some issues such as:

How to create the administration Information system of sales and purchase which is useful and appropriate for the UD. Usaha Jaya company.

How the UD. Usaha Jaya company can find out about the payment of salary for the workers.

How to record the stock of the goods.

How to make an automatic purchase order. So, if the stock is approaching the minimum limit, the system will give an alert.

Statement of The ProblemStatement of The Problem

How to match the coming goods with an existing purchase order.

How to create a data structure for the goods which are received by the company. This includes the item codes, item names, quantity of the goods, prices, and details of the other goods.

How the system can give useful information or report for the company

ScopeScope The scope of this study are :

Making an access rights for the users of this system which consists of :- Owner- Administrator- Warehouse worker or employee

Purchase- The recording of suppliers’ data- The purchase transaction- The preparation and listing of purchase order (PO)- The reception of goods that come and the match with the existing purchase order- The Listing of Debt

ScopeScopeSales

- The recording of customers’ data- The sales transaction- The record of returned sales- The making and recording of sales orders, delivery orders and invoices- The Listing of customers’ accounts receivable

Inventory- The Recording of the goods transfer and delivery order- Stock card

ScopeScope Inventory

- Unit Conversions (from box to the grain)- The Listing of the inventory using the First In First Out method

(FIFO)- The Stock of Opname that is performed two times in a year.

Payroll for the permanent employees- Position / title- Basic salary- Daily meal money- Transportation money- Commission (sales)- Attendance for permanent employees

ScopeScope Payroll for daily employees

- Daily Salary- Daily meal money

Reports- Sales report- Purchase report- Profit and loss- Inventory- Stock card- Debt and account receivable - Permanent employee’s absent report- and other reports

The purpose of the StudyThe purpose of the Study

The purpose of this study are to design and to produce an information system application that can handle the purchases, sales, inventory, payroll, and also provides the required reports quickly and easily.

New Design System CompanyNew Design System CompanyData Flow DiagramData Flow Diagram (DFD) (DFD)

Context DiagramContext Diagram

Data Pegawai

Laporan Harga Pokok Penjualan

Laporan Piutang

Laporan Hutang

Laporan Gaji Pegawai

Laporan Kartu Stok

Laporan Penjualan

Laporan Pembelian

Laporan Laba Rugi

Laporan Inventori

Pembayaran Piutang

Bukti Retur

Data Customer

Bukti Pembayaran piutangData Supplier

Retur Penjualan

Nota Penjualan

Pembayaran Hutang

Purchase Order

Bukti Pembayaran Hutang

Nota Pembelian

1

Sistem Informasi Administrasi UD

USAHA JAYA

Customer

Owner

Supplier

Pegawai

Data Flow DiagramData Flow Diagram (DFD) (DFD) Level 0Level 0

Data Flow DiagramData Flow Diagram (DFD) Level (DFD) Level 1 Purchases Transaction1 Purchases Transaction

Data Stok

data penerimaan barang

data pesanan

data pesanan

Penerimaan Hutang

Nota Pembelian

Data Permintaan Barang

Data Hutang

Pembayaran

Pemesanan

Data SupplierSupplier

Hutang

Owner

Supplier

1

Pesanan Barang

2

Penerimaan Barang

3

Pembayaran

PesanPembelian

Pembelian

Stok

1.1

Pemesanan Barang Ke Supplier

1.2

Penerimaan Barang

1.3

Pembayaran Ke Supplier

Data Flow DiagramData Flow Diagram (DFD) Level (DFD) Level 1 1

Sales TransactionSales Transaction

retur

Retur Penjualan

Pesan Barang

Pesanan

Data Stok Barang

Retur Penjualan

Data Penjualan

Penerimaan Piutang

Update Piutang

Pembayaran

beli barang

Data Piutang

Data Customer

Nota Penjualan

Customer

Customer

Piutang

1

Penjualan

3

Pembayaran

4

Retur Penjualan

Pesanan Penjualan

2

Pesanan

Penjualan

Stok

returpenjualan

2.2

Pesanan

2.1

Penjualan

2.3

Pembayaran

2.4Retur

Penjualan

Data Flow DiagramData Flow Diagram (DFD) Level (DFD) Level 1 1

Employee Administration Employee Administration

[Absen]

Data Pegawai

Data Absensi

Data Absensi

Data Gaji

Lap Gaji Pegawai

Data Pegawai[Data Pegawai][Data Gaji]

[Lap Gaji Pegawai]

PegawaiPenggajian

Owner

Pegawai

3.1

Penggajian Pegawai Tetap

3.2

Penggajian Pegawai Harian

3.3

Absensi

Absensi

Entity Relationship DiagramEntity Relationship Diagram (ERD) (ERD) Conceptual Data Modelling Conceptual Data Modelling (CMD)(CMD)

Entity Relationship DiagramEntity Relationship Diagram (ERD) (ERD) Physical Data Modelling Physical Data Modelling (PMD)(PMD)

ConclusionConclusionFrom the test of case study which is implemented in the application, the writer comes to some conclusions:

The Applications that is made is suitable for the company’s needs and the listing process is conducted in a structured transaction.

From the example of the case study that has been conducted and compared with the manual calculation, the system is able to make an accurate profit and loss report.

Overall, the look of the program, presentation of information, ease of using the program, speed the process, provided features and compatibility with the existing systems, the user considers it "Good" from the maximum value of "Very Good“. It is seen from the results of the questionnaire about the overall evaluation of this application.

RecommendationRecommendationThe recommendations for the program developer of the administration information system application are:

The Display of the program can be made more user friendly with the aim of accelerating the process.

The Reports that are made in this application can be developed more according to the user’s needs.

The system making can be developed with web-based.

Thank You