Case Study Almost Done

8/2/2019 Case Study Almost Done

http://slidepdf.com/reader/full/case-study-almost-done 1/21

CHAPTER 1

Introduction

NIKKO METALS PHILIPPINES, INC. is a Japanese firm which

manufactures copper foil primarily for printed circuit boards (PCBs). It is the first

and only copper foil manufacturing company here in the Philippines which has

been operating for over 10 years. It basically exports its products but has also

local clients here in the country. It is the first and only company here in the

Philippines manufacturing such kind of product for local and international

markets for over 10 years. It is an ISO 9001:2000 certified and just recently

received an Award of Excellence for Total Productive Maintenance (TPM).

NIKKO METALS PHILIPPINES, INC. is located at #117 E-Science

Avenue, SEPZ Laguna Technopark, Biñan Laguna.



Background of the study

The right Accounting system can save you time and money by automating

accounting processes, allowing multiple users to work with financial data,

implementing well-defined procedures to decrease accounting errors, refining

forecasting methodologies for improving efficiency, determining costs based on

output levels to improve pricing and improve order, inventory and asset

management, etc.

The system is divided into tables namely the account type, the account,

and the transaction per day. Gathering needed tools and information is

collected to ease out programming process. Collaborating to one another is

done to develop.

Objectives

The main purposed of the proposed system is to develop a computerized

accounting system for NIKKO METALS PHILIPPINES, INC., which will improve

the company’s conventional way of keeping transaction records.

This case study aims to:

1. develop a database system that manages the expenses of the said

company;

2. endow with a systematic approach of an efficient database system; and



3. easily retrieve company expenses records

Significance

The system is designed for easy access of records. Thus, updating,

monitoring, report generation are some of the operations that applied in the

system.

This study aims to decrease the time of processing transaction records of

the company. Transaction records can be easily updated every time. Retrieving

the Account types can be more efficient for the company.

Scopes and Limitations

Recently, the company had been encountering problems in managing the

record of the accounts and transactions. Using a traditional way of record

keeping, it took them lot of time to retrieve the record. The database main

purpose is to track the daily income and the expenses of the company. Given a

systematic approach of an efficient database, it is expected to give a clear and

concise data.

The proposed electronic database covers the account information and

account types and other transactions of the company.

Thus, it doesn’t focuses to often activities or record of the salon such as

employees’ files and etc.



CHAPTER 2

Conceptual Framework

Concept of the Study

The conceptual framework illustrates the Input-Process-Output (IPO)

Model applied in the study. The IPO Model determines and represents the

possible data that would be used as input to the system design and to the

system per se, the process that would be used in dealing with the said inputs

and the final output would be a fully functional system.

Input Process Output

Account Id

Account type

TransactionId

Transaction

type

Computerized

account records

and transaction

Testing and

evaluation of the

system design

Analysis of

gathered

information



Figure 2: Input-Process-Output Model

The first frame represents the input or initial stage where in the account

data must encode as well as the account type and the transactions.

The second frame represents the development stage which involves the

process to be utilized in the development of the system design. The information

gathered would be filtered and analyzed to identify and design the transaction

that would be integrated.

The third frame represents the final stage which is the implementation

stage. After detailed analysis and planning it directs to system design proposal.

The result would be computerized account records and transaction



Database decision

Contextual Model

The figure illustrates the context diagram used to present the different

entities to which in sequence is given to or expected from the system.

Transaction

Account

Type Account



Entity-Relationship Diagram

The Entity-Relationship Diagram of the develop system. All attributes

involved in each entity are shown above. The relationship between each entity

could also be seen in this diagram.

Account Type

Account type

IDAccount

type

Taxable

have

Account

TransactionI

D

AccountT

ypeID

AccountNa

me

AccountNum

ber

AccountI

D

Transaction

have

DepositAmount

WithdrawalAmou

nt

AccountID

TransactionDesc

ription

TransactionDate

TransactionNum

ber



Database Schema

This figure shows the database schema of the develop system. All the

fields or attributes with links are also shown here. Connections between tables

or entities through primary and foreign keys were presented in detailed manner.



Data Dictionary

• Table

A table is a collection of data about a specific topic that is stored in rows and

columns. You can categorize all available data, such as employees and

customers, and then store each category of data in a separate table.

• Record

A record is a row in a table. A record contains organized details about a

person, a location, or some other real-world entity.

• Field

A field is a column in a table. A field represents a defined attribute that is

stored for all the records in a table.

• Data type

A data type determines the type of data that the field can store. Jet data types

include the following:

o Text

o Memo

o Number

o Date/Time

o Currency

o AutoNumber

o Yes/No

o OLE object

o Hyperlink





Query

A query is an instruction to retrieve information that is in a set of rows. You can

use a query to retrieve information from a single table or from multiple tables

based on specific criteria. You can also use a query to modify the information

that you retrieve.

• Form

In Access, you can use a form as the graphical user interface to data. Forms do

not store any data. Forms only fetch data from tables or from queries and then

present this data to you.

• Control

A control is an object on a form, on a report, or on a data access page. You can

use a control to display data, to perform actions, or to enhance the representation

of data.

• Property

A property is a characteristic of a control object or a database object that is

defined. The value of a property defines the behavior of a control object or a

database object.



Report

A report presents the data from a table or from a query in a preformatted and

useful manner. You can control the appearance of a report.

Macro

A macro is a database object that lets you automate tasks in an Access

database. You can create macros that run when an event occurs and that

automatically perform specific actions.

• Design view

Design view is available for all database objects. Design view has tools and

shortcuts that you can use to design a database object. In Design view, you can

only modify the design of an existing database object. You cannot modify the

underlying data.

• Datasheet view

Datasheet view is available only for certain database objects, such as tables,

queries, and forms. Datasheet view displays the underlying data for a database



object in a tabular format. You can use Datasheet view to add data to a

database, to modify the data in a database, or to delete data from a database.

CHAPTER 3

Project Development



Procedure in developing the project

Observation /

Fact Finding /

Cost Analysis



Database Implementation

Tables

Table 1. Account type

This table has the fields; Account type ID and Account type.

The content of Account type are Expenses, Revenues, Liabilities and Other.

Table 1.1. Account type – Expenses



Table 1.2. Account type – Revenues

Table 1.3. Account type – Liabilities

Table 2. Accounts

This table includes the Account ID, Account Number, Account Name and

Account Type.



Table 2.1. Account with Transaction ID

Table 3. Reports

This table includes the Report ID, Report Name and Report description.



QUERIES

Query 1. View Transaction with Account

This query includes the Transaction Id, Transaction Number,

Transaction Date, Transaction Description, Account Id, Withdrawal Amount,

Deposit Amount, Taxable, and Account Name



Interface Design

Forms

Form 1. Account Ledger

Form 2. Account Lodging



Reports

Report 1. Account Summary

Report 2. Summary of Account Type



Report 3. Transaction Listing

Case Study Almost Done

Documents