SYSTEM ANALYSIS & DESIGN

INTIF1106

INFORMATION SYSTEM PROJECT SIMULATION :

Information System of Inventory Faculty

Of Science And Technology.

Team Member :
Aldi (1811102441104)
Arif Rahman Hakim (1811102441105)
Ayu Pujiastuti (1811102441106)
Muhammad Rizqi Ilhami (1811102441113)
Ricky Arun Saxena (1811102441118)

Teknik Informatika
Fakultas Sains & Teknologi
Universitas Muhammadiyah Kalimantan Timur
Samarinda, 2019
 System Analysis & Design (INTIF1106)

Content
Contents
Content........................................................................................................................................i
Introduction................................................................................................................................1
Information System.................................................................................................................1
Information System of Inventory............................................................................................2
Part 1: Planning..........................................................................................................................3
1.1. Project Identification & Selection...............................................................................3
1.2. Project Initiation & Planning.......................................................................................3
1.2.1. Project Scope Statement.......................................................................................3
1.2.2. Project Schedule...................................................................................................4
Part 2: Analysis..........................................................................................................................5
2.1. Proses Modeling..........................................................................................................5
2.1.1. Context Diagram..................................................................................................6
2.1.2. Data Flow Diagram..............................................................................................6
Part 3: Design.............................................................................................................................9
3.1. Database......................................................................................................................9
3.1.1. Design of Item Tables..........................................................................................9
3.1.2. Draft Inventory Table...........................................................................................9
3.1.3. Design of User Tables........................................................................................10
3.1.4. Draft Table of Reports.......................................................................................10
3.2. Reports & Form.........................................................................................................11
3.2.1. Reports...............................................................................................................11
3.2.2. Form...................................................................................................................12
Part 4: Implementation.............................................................................................................13
4.1. Coding.......................................................................................................................13
4.1.1. Pemrograman language......................................................................................13
4.2. Testing.......................................................................................................................15
4.2.1. Walkthrough.......................................................................................................15
4.2.2. Test Case Result Form.......................................................................................16
4.3. Installation.................................................................................................................16

Information System of Inventory Campus Teknik Informatika - UMKT |

 System Analysis & Design (INTIF1106)

4.3.1. Installation Guide...............................................................................................17

Part 5: Maintenance..................................................................................................................20
5.1. System Service Request form....................................................................................20
5.2. Sheduling maintenance..............................................................................................22

Information System of Inventory Campus Teknik Informatika - UMKT |

 System Analysis & Design (INTIF1106)

Introduction
The Faculty of Science & Technology (FST) is one of the faculties of Information
Technology (IT) at the Muhammadiyah University of East Kalimantan (UMKT). Established
since 2017 by having one of the study programs, namely Informatics Engineering. Although
the Faculty of IT, FST is also inseparable from administrative problems that have not been
computerized, resulting in a lack of efficiency in the process. Administrative issues such as
recording the facilities and infrastructure items that are still in the data manually. Recording
that is still done manually can complicate the data collection and data search process for a
particular item. This causes the existing data archive to be inaccurate, and because of the
limitations of the media used, a lot of data is not recorded up to date. This inventory planning
plays an important role in the managerial activities of an agency, as well as FST who really
need this system to record office items that have been purchased, received, shared and used
during lectures and campus administration activities. Based on the description above, we are
interested in building an inventory system entitled "Web-based Inventory Information System
at the Faculty of Science & Technology".

Information System
Information System (SI) is a combination of information technology and activities of
people who use that technology to support operations and management. In a very broad
sense, the term information system that is often used refers to interactions between people,
algorithmic processes, data, and technology. In this sense, this term is used to refer not only
to the use of information and communication technology (ICT) organizations, but also to the
ways in which people interact with this technology in supporting business processes.

Information System of Inventory Campus Teknik Informatika - UMKT |1

 System Analysis & Design (INTIF1106)

Information System of Inventory

Inventory is inventaris in Indonesian. Inventory, related to the logistics activities of a
company, is an activity that provides raw material stocks or semi-finished goods for finished
goods for the smooth production process and / or fulfillment of customer requests, in general,
inventory is a list that contains all the items owned by the office used in carrying out the task.
In the context of the SME business, inventory is assets owned in the form of products either
finished goods or raw goods which are then processed and sold to customers to make a profit.

In a simple sentence, this inventory almost resembles the inventory system in your
family to meet household consumption needs.

For example, in the monthly expenditure of household needs, we often buy some
consumer goods, not just 1 (one) fruit but can be several fruits, such as bath soap, laundry
soap, toothbrush, and so on.

Information System of Inventory Campus Teknik Informatika - UMKT |2

 System Analysis & Design (INTIF1106)

Part 1: Planning
1.1. Project Identification & Selection

Muhammadiyah University of East Kalimantan (UMKT) is a university that has B

accreditation, agreeing that of course this does not escape the infrastructure needed by
UMKT complete and its maintenance is very good than that by using an Inventory
Information System What is in an institution, UMKT, because this project produces a much-
needed information system in order to overcome problems and difficulties in collecting data
on the provision of existing infrastructure on campus, which of course will be questioned. this
project is very clear to be approved the method of recording which previously was a manual
that was very time dependent in the calculation process, therefore the reason for the Inventory
Information System was made and did not escape also from the very easy use of this system
or can be accessed by employees related to this Inventory Information System The web.

1.2. Project Initiation & Planning

1.2.1. Project Scope Statement

aMaRa.id Prepared by: Roy Kiyoshi

Project Scope Statement Date: May 21, 2019

General Project Information

Project Name : Information System of Inventory

Sponsor : Jack Ma, Alibaba

Project Manager : Roy Kiyoshi

Problem/Opportunity Statement:
 Behind the excellent infrastructure, of course there is an employee who runs the
recording and maintenance process. Then the need for a system that must be
developed by the company or agency in improving efficiency and achieving the
company's goals

Project Objectives:
 To enable employees of the UMKT equipment to improve performance,
efficiency, as well as facilitate the recording of infrastructure facilities in UMKT.

Information System of Inventory Campus Teknik Informatika - UMKT |3

 System Analysis & Design (INTIF1106)

This will also reduce the level of risk of errors in the recording process.

Project Description:
 The information system that will be built serves to record all the facilities of a
company easily and quickly, the appearance of the system Informasi ini berbasis
The web can be accessed anywhere by all employees and can only be changed or
edited by employees who have responsibility in the equipment section.

Business Benefits:
 Improve performance efficiency in the process of collecting equipment data
Makes it easy while accelerating employee performance
Reducing the risk of errors
Equipment data that is transparent and up to date
Can be accessed anywhere from internet connection

Project Deliverables:
 Analysis and design of equipment data recording systems
Equipment data calculation program
Documentation of results of equipment data
Training procedure

Estimated Project Duration:

 5 Months

1.2.2. Project Schedule

Feb-19 Mar-19 May-19 Jul-19 Aug-19 Oct-19 Dec-19 Jan-20

Preparatory Phase

Phase 1 Processing

Phase 2 Processing

Phase 3 Processing

Testing Phase

Delivery Phase

Information :
 Analysis and design of equipment data recording systems is done in May to June.
 The equipment data calculation program was carried out in June to August.
 Documentation of the results of equipment data is carried out during the project
processing process.
 Training procedures are carried out in September to October

Information System of Inventory Campus Teknik Informatika - UMKT |4

 System Analysis & Design (INTIF1106)

Part 2: Analysis
Based on the description above, then arises arising in the execution of this final
project Based on the description above, then arises arising in the execution of this final
project is developing a Tool / Item Inventory Information System at East Kaliamantan
Muhammadiyah University that can provide information about tools and items .

From the results of testing the application, the information obtained in the form of
items can be detected in the storage location, condition of the goods items can be detected in
case of damage per item. In addition, the results of testing that has been done can be seen that
overall web applications can run well on software and hardware. Applications that are built
are web-based applications and tomcat, Mysql, and JSP software can work well in visualizing
data. On the search page can display the query results as follows search by item name, search
by location save.

2.1. Proses Modeling

According to Rifky Nur Triyanto (2001: 67) waterfall is a software development
methodology that proposes an approach to systematic and sequential software that starts at
the level of system progress in all analysis, design, code, testing and maintenance.

This method is also called the waterfall method which explains the method of the
system from the earliest to the last groove with the shape from top to bottom following the
shape of the waterfall structure. With this waterfall method the author easily designs
applications that must be made by sorting the process from the first to the last.

Figure 2.0.1 Metode Waterfall

Information System of Inventory Campus Teknik Informatika - UMKT |5

 System Analysis & Design (INTIF1106)

2.1.1. Context Diagram

Context diagram is an event from a flow / data flow. Where one circle presents the
entire system and is the highest level in the data flow diagram and only contains one process
and shows the system as a whole.

ADMIN

Input Data Barang

Sistem
Inventaris

USER
Laporan Data Barang

Figure 2.0.2 Diagram Context

2.1.2. Data Flow Diagram

Data Flow Diagrams (DFD) are graphical representations of a system. DFD describes
the components of a system, the data streams where the components are, and the origin,
destination, and storage of the data. Following is the display of DFD from the Design of
Goods Inventory Information System at Muhammadiyah University of East Kalimantan :

Figure 2.0.3 Data Flow Diagrm Level 1 (Login)

Information System of Inventory Campus Teknik Informatika - UMKT |6

 System Analysis & Design (INTIF1106)

Figure 2.0.4 Data Flow Diagram Level 1 untuk Proses 2 (Barang)

Figure 2.0.5 Data Flow Diagram Level 1 untuk Proses 3 (Inventaris)

Figure 2.0.6 Data Flow Diagram Level 1 untuk Proses 4 (User)

Information System of Inventory Campus Teknik Informatika - UMKT |7

 System Analysis & Design (INTIF1106)

Figure 2.0.7 Data Flow Diagram Level 1 untuk Proses 5 (Laporan)

Information System of Inventory Campus Teknik Informatika - UMKT |8

 System Analysis & Design (INTIF1106)

Part 3: Design
In this sub-chapter, it discusses the implementation and display of programs that have
been made by the author. In this view there are several forms to make it easier for users to use
this application. With these forms, the display of this information system will be more
organized.

3.1. Database
As we know that PHP provides very complete facilities to build database applications.
A database application requires database files and their tables as data recorders. In this
system the author uses MySQL as a database because of the various advantages possessed by
MySQL.

The tables that I use in the Item Inventory Information System at Muhammadiyah
University of East Kalimantan are as follows :

3.1.1. Design of Item Tables

This table is used to record items at the Muhammadiyah University of East Kalimantan.
The table details are as follows below :

Table 3.1 Table Item

No Field Name Type Size Keterangan
1 Kd_Barang varchar 8 Kode Barang (PK)
2 NamaBarang varchar 25 Nama barang
3 Merk varchar 25 Merk Barang
4 NoSeri varchar 10 No Seri Barang
5 Berat varchar 10 Ukuran barang

3.1.2. Draft Inventory Table

This table is used to create an inventory code for each item that is valued as an asset in
each work unit. The table details are as follows below :

Information System of Inventory Campus Teknik Informatika - UMKT |9

 System Analysis & Design (INTIF1106)

Table 3.2 Table Inventory

No Field Name Type Size Keterangan
1 Kd_Inventaris varchar 10 Kode Inventaris (PK)
2 Kd_Barang varchar 8 Kode Barang (FK)
3 Tanggal date 8 Tgl inventaris

3.1.3. Design of User Tables

In order to maintain data security in this system, it is necessary to create a user table to
limit the number of users who will use this system. The table details are as follows below :
Table 3.3 Data User
No Field Name Type Size Keterangan
1 Id_user varchar 8 Id User (PK)
2 UserName varchar 25 user name
3 Password varchar 25 password

3.1.4. Draft Table of Reports

This report table is used to display or produce an output in the form of reports for
goods, inventory and users. The table details are as follows below :
Table 3.4 Table Report
No Field Name Type Size Keterangan
1 Id_Laporan varchar 8 Id Laporan (PK)
2 Kd_Barang varchar 25 Kode Barang (FK)
3 Kd_Inventaris varchar 25 Kode Inventaris (FK)
4 Tanggal date 8 Tgl Laporan

Information System of Inventory Campus Teknik Informatika - UMKT | 10

 System Analysis & Design (INTIF1106)

3.2. Reports & Form

3.2.1. Reports

Inventory UMKT
Jl. Juanda
Of UMKT Telephone: 785-864-3441
Fax: 785-864-5025
Report www.umkt.ac.id

Name: ..................................................................... Date: ......................................

Please use this form to report item data. Please use this item data report to report to your
supervisor.

Date of Take Description Of Item Date Of Return Item Code

I certify the above expenses are true and unpaid and have been incurred while engaged
in official Inventory activities.

Information System of Inventory Campus Teknik Informatika - UMKT | 11

 System Analysis & Design (INTIF1106)

_________________________________ _________________________________
SIGNATURE APPROVAL AUTHORITY SIGNATURE

Information System of Inventory Campus Teknik Informatika - UMKT | 12

 System Analysis & Design (INTIF1106)

3.2.2. Form

Information System of Inventory Campus Teknik Informatika - UMKT | 13

 System Analysis & Design (INTIF1106)

Part 4: Implementation
4.1. Coding

4.1.1. Pemrograman language

Visual Basic is the development of the BASIC (Beginner's All-purpose Symbolic

Instruction Code) computer language. BASIC language was created by Professor John
Kemeny and Thomas Eugene Kurtz of Dartmouth College in the mid-1960s. The language of
the program is arranged similar to English which is commonly used by programmers to write
simple computer programs that function as learning for the basic concepts of computer
programming. Software: Microsoft Visual Basic v6.0.

4.1.1.1 Process & Interface

Before entering this application the user must log in first for data security. With
this login menu we can minimize data damage and loss. Users who will later use this
application must be restricted for security reasons. Next is the login view of the Inventory
Information System at the East Kalimantan Muhammadiyah University :

Information System of Inventory Campus Teknik Informatika - UMKT | 14

 System Analysis & Design (INTIF1106)

Figure 4.0.8 Interface Login

This form is made to record / input items at East Kalimantan Muhammadiyah

University. Next is the display of the form :

Figure 4.0.9 Interface Input Barang

Information System of Inventory Campus Teknik Informatika - UMKT | 15

 System Analysis & Design (INTIF1106)

4.1.1.2 Database

The Muhammadiyah University Inventory System uses MySQL as its database

because of the many advantages that MySQL has. Examples of databases included such as
item data, inventory data and user / admin data.
Microsoft Office Access

4.2. Testing
Performance tests are designed to analyze differences in speed and application
performance in controlled environments and in the real world. There are many factors that
can affect the performance of an application and some of them are almost impossible to
reproduce in the lab.

1. Stated purpose: to find out whether and how to develop software meets its
intended purpose, and to identify any defects that prevent the software from
functioning in a way that is intended to function.
2. The unstated purpose: to perform just as possible to keep the speed and efficient

4.2.1. Walkthrough

GUIDELINES FOR CONDUCTING A CODE WALK-THROUGH

1. Have the review meeting chaired by the project manager or chief programmer,
who is also responsible for scheduling the meeting, reserving a room, setting the
agenda, inviting participants, and so on.

Information System of Inventory Campus Teknik Informatika - UMKT | 16

 System Analysis & Design (INTIF1106)

2. The programmer presents his or her work to the reviewers. Discussion should be
general during the presentation.
3. Following the general discussion, the programmer walks through the code in
detail, focusing on the logic of the code rather than on specific test cases.
4. Reviewers ask to walk through specific test cases.
5. The chair resolves disagreements if the review team members cannot reach
agreement among themselves and assigns duties, usually to the programmer, for
making specific changes.
6. A second walk-through is then scheduled if needed.

4.2.2. Test Case Result Form

aMaRa.id
Case Test Results

Test Case Number : 1

Date: 13/Mei/2019

Name of program : Information System of Inventory Faculty Of Science And Technology

Tested Modules : In testing the operating system the output results are in line with
expectations and can be trusted by using a program that has been created.

Suggestions for the next step : We recommend that the developer is not free of
responsibility such as there is damage to the information system and it is expected that
cooperation to carry out maintenance of information systems by the campus and makers.

4.3. Installation
Install is to install the program (software) into the computer. all software (for
example, Microsoft Windows, Microsoft Office and others,) we must install it first into the
computer, then it can be used, besides, install also functions to adjust the program with the

Information System of Inventory Campus Teknik Informatika - UMKT | 17

 System Analysis & Design (INTIF1106)

tools installed on our computer. Here we will install the inventory system in the form of an
exe file.

Information System of Inventory Campus Teknik Informatika - UMKT | 18

 System Analysis & Design (INTIF1106)

4.3.1. Installation Guide

To install this Application or Information System Software on Computers and

Laptops :

1. In general, the installation file for the Windows operating system has an .exe
extension even though the file is stored in a rar or zip file. To start installing
double click the software that you want to install.
2. You will be taken to the opening page, usually you will be given informed
consent to approve the license on the software. Read and click I Agree.
3. Some software, we are given the freedom to determine the type or format of the
installation. Or also we leave the default then click Next.
4. Select the display icon that usually appears on the desktop and Next.
5. Select the install location but leave the default because usually the software you
install is in the C: \ Program Files data. But if you want to place another didrive /
folder. If it's then then Next.
6. Then you click install and finish.
7. Check the software icon on your computer's desktop for the successful software
installation process.

4.3.1.1 Program Base

DBMS or database management system is a special application program designed

to create and also manage available databases. This system contains a collection of data and
set of programs used to access the database.

DBMS is software that plays a role in managing, storing, and retrieving data again.
The mechanism used as a complement is data security, data consistency and shared data
users.
Examples of DBMS are Microsoft Access, MySql, Oracle database, Sybase, Borland-
Interbasi, PostgreSQL etc.

Information System of Inventory Campus Teknik Informatika - UMKT | 19

 System Analysis & Design (INTIF1106)

4.3.1.2 Database

Instalasi mySQL
Step 1 : download MySQL

Download MySQL from dev.mysql.com/downloads/. Follow MySQL Community

Server, Windows and download the “Without installer” version.

Step 2 : extract the files

We will install MySQL to C:mysql, so extract the ZIP to your C: drive and rename
the folder from “mysql-x.x.xx-win32” to “mysql”.

Step 3: move the data folder (optional)

I recommend placing the data folder on another drive or partition to make backups
and re-installation easier. For the purposes of this example, we will create a folder called
D:MySQLdata and move the contents of C:mysqldata into it.

You should now have two folders, D:MySQLdatamysql and D:MySQLdatatest.

The original C:mysqldata folder can be removed.

Step 4 : create a configuration file

MySQL provides several configuration methods but, in general, it is easiest to to

create a my.ini file in the mysql folder.

Step 5 : test your installation

The MySQL server is started by running C:mysqlbinmysqld.exe. Open a command

box (Start > Run > cmd) and enter the following commands:

cd mysqlbin
mysqld

This will start the MySQL server which listens for requests on localhost port 3306.
You can now start the MySQL command line tool and connect to the database. Open another
command box and enter:

cd mysqlbin
mysql -u root
This will show a welcome message and the mysql> prompt. Enter “show
databases;” to view a list of the pre-defined databases.

Step 6 : change the root password

Information System of Inventory Campus Teknik Informatika - UMKT | 20

 System Analysis & Design (INTIF1106)

The MySQL root user is an all-powerful account that can create and destroy
databases. If you are on a shared network, it is advisable to change the default (blank)
password.

Step 7 : Install MySQL as a Windows service

The easiest way to start MySQL is to add it as a Windows service. From a

command prompt, enter:

cd mysqlbin
mysqld --install

Open the Control Panel, Administrative Tools, then Services and double-click
MySQL. Set the Startup type to “Automatic” to ensure MySQL starts every time you boot
your PC.

Alternatively, set the Startup type to “Manual” and launch MySQL whenever you
choose using the command “net start mysql”.

4.3.1.3 Network

The network used to run this software uses the internet because we need internet
access to connect directly to the database, and the advantages that can be gained if using this
internet network is the officer or admin can monitor this software at any time.

Information System of Inventory Campus Teknik Informatika - UMKT | 21

 System Analysis & Design (INTIF1106)

Part 5: Maintenance
In maintaining this operating system program, it is done at least once a month to
check whether there are still errors that need to be corrected in this operating system or just
need maintenance.

Several reasons why people maintain a system program include the following:

1. To keep visitors and customers updated or always follow our business to achieve
or build a professional image on a website.
2. To be able to always continue in updating our website to maintain a position in
the search engine or SEO optimization which will attract a lot of customers from
search engines. Imagine if our website disappears from the top position in SEO,
then most of the target customers will not be able to find the website and only
buyers who have known the website will come back. So it's very important to
keep our position always above to maintain the website for a long time.
3. To improvise the design of the website which is perhaps possible in the previous
design it cannot attract the attention of visitors or customers to continue doing
business with us. So it's good that we always pay attention to the appearance of
the website and who knows by making changes will be better.
4. To expand the business network when trading our online business has grown
rapidly.
5. And the last is to keep the website safe in this case it is necessary to avoid attacks
from hackers who can make our website destroyed or fall into their hands. In this
case it is very important if we back up data and maintenance to keep the business
and stay alive in the internet market.

5.1. System Service Request form

aMaRa.id
Information System of Inventory

REQUESTED BY : Roy Kiyosi DATE July, 02 2019

Information System of Inventory Campus Teknik Informatika - UMKT | 22

 System Analysis & Design (INTIF1106)

DEPARTMENT : Suka Sama Suka Company

LOCATION : Jl. Lumba – Lumba Gg.1 West Samarinda

CONTACT : Telp. 0822 5013 3431 Fax. 0542-765432

TYPE OF REQUEST URGENCY

[√] New System [ ] Immediate - Operations are impaired or opportunity lost
[ ] System Enhancement [√] Problems exist, but can be worked around
[ ] System Error Correction [ ] Business losses can be tolerated until the new system is installed

PROBLEM STATEMENT
Problems that occur when entering biodata and photo entries of prospective students occur a bug so
that prospective students when clicking save will repeat the page again and their biodata and
photos will be empty again.

SERVICE REQUEST
In overcoming the bugs that occur in the program, checking the programs made and checking the
program is done so that the bugs do not occur again in the process of filling in the biodata and
input photos.

IS LIAISON : Ricky Arun (Tel - 082250133431, email: arun@gmail.com)

SPONSOR : KFC (kfc@gmail.com)

---------------------- TO BE COMPLETED BY SYSTEMS PRIORITY BOARD ---------------------

[√] Request approved Assigned to Start date Mei 3, 2019
[√] Recommend revision
[ ] Suggest user development
[ ] Reject for reason

Information System of Inventory Campus Teknik Informatika - UMKT | 23

 System Analysis & Design (INTIF1106)

5.2. Sheduling maintenance

Maintenance planning and scheduling is one of the fastest and most effective
investments in can make organizations to improve productivity and availability. The
processes in this course provide the way for planning and control of maintenance resources.
Equipment reliability is increased. Waiting times, unnecessary parts and inaccurate
information are eliminated. Budgeting is easier and more accurate. Maintenance tasks are as
much as 50% more efficient in terms of costs and time.

Information System of Inventory

Faculty Of Science And Technology
Start Date End Date Description Duration (days)
05-Jul 17-Nov Analysis 150
18-Nov 18-Apr Framework 190
19-Apr 22-Oct Design 224
23-Oct 29-Jun Trial Phase & Maintanence 245
30-Jun 21-Sep Settlement 130

19-Jul 27-Oct 4-Feb 15-May 23-Aug 1-Dec 10-Mar 18-Jun 26-Sep

Analysis

Framework

Design

Trial Phase & Maintanence

Settlement

Information System of Inventory Campus Teknik Informatika - UMKT | 24

 System Analysis & Design (INTIF1106)

Figure 2.0.1 Metode Waterfall................................................................................................5

Figure 2.0.2 Diagram Context..................................................................................................6

Figure 2.0.3 Data Flow Diagrm Level 1 (Login).....................................................................6

Figure 2.0.4 Data Flow Diagram Level 1 untuk Proses 2 (Barang).......................................7

Figure 2.0.5 Data Flow Diagram Level 1 untuk Proses 3 (Inventaris)..................................7

Figure 2.0.6 Data Flow Diagram Level 1 untuk Proses 4 (User)...........................................7

Figure 2.0.7 Data Flow Diagram Level 1 untuk Proses 5 (Laporan).....................................8

Figure 4.0.1 Interface Login..................................................................................................14

Figure 4.0.2 Interface Input Barang.....................................................................................14

Table 3.1 Table Item................................................................................................................9

Table 3.2 Table Inventory.....................................................................................................10

Table 3.3 Data User................................................................................................................10

Table 3.4 Table Report..........................................................................................................10

Information System of Inventory Campus Teknik Informatika - UMKT | 25