INFORMATION SYSTEM PLANNING ANALYSIS

GROUP 2

Arrange by :

1. Marsha Cantika 19080694012

2. Nurul Fitri Rizkina 19080694058
3. Ilham Amanatullah 19080694086
4. Ahmad Akbar Yahya 19080694103

S1 ACCOUNTING STUDY PROGRAM

FACULTY OF ECONOMICS AND BUSINESS

SURABAYA STATE UNIVERSITY

2021
1.1 DEVELOPING SYSTEMS

System development is the preparation of a new system to replace the old system as a
whole or improve an existing system.
• System Analyst Manager
• Chief Systems Analyst
• Senior Systems Analyst
• Junior Systems Analyst
• Senior Application Programmer
• Junior Application Programmer
The number of personnel of the above team is needed if the system to be developed is
large enough. If the system to be developed is small, then the personnel can be adjusted
based on needs.

A. THE NEED FOR SYSTEMS DEVELOPMENT

The old system needs to be repaired or replaced because of several things:

1. There are problems that arise in the old system. Problems that arise can be:

2. Irregularities of the old system

Irregularities or errors in the old system cause the old system to be unable to operate as
expected.

1. Growth of the organization

The need for information is increasing, the volume of data processing is increasing,
changes in new accounting principles cause the new system to be compiled, because
the old system is no longer effective and can no longer meet all the information needs
needed by management.

2. To seize the opportunities

In a state of intense market competition, information speed or time efficiency

determines the success or absence of strategies and plans that have been drawn up to
achieve market opportunities and opportunities, so that information technology needs
to be used to improve the provision of information in order to support the decision-
making process carried out by management.

3. There are instructions from the leadership or the existence of government

regulations

B. INDICATOR OF THE NEED FOR SYSTEM DEVELOPMENT

A system needs to be developed in case of several indicators such as the following:

 a) Customer complaints. e) The contents of reports are
often wrong.
b) Delivery of goods that are often
delayed. f) Excessive working time.

c) Late pay. g) Cash irregularities.

d) Untimely reports. h) Low labor productivity.

C. OBJECTIVES OF INFORMATION SYSTEMS DEVELOPMENT

a) Improved performance, which can be measured from throughput and response time.
Throughput is the amount of work that can be done at any given moment. Response
time is the average delay time between two transactions.
b) Quality of information presented.
c) Profit (decreased cost). It relates to the amount of resources used.
d) Control (control).

D. PRONCIPLES OF SYSTEMS DEVELOPMENT

The principles of information system development are:

1. The system developed is for management.

2. The system developed is a large capital investment. So every capital investment
must consider the following 2 things:
3. All alternatives must be investigated.
4. The best investment should be worth it.
5. The system that is developed requires an educated person.
6. New work stages and tasks are carried out in the system development process.
7. The system development process does not have to be sorted.
8. There should be guidelines in system development.

1.2 HIERARCHICAL INPUT-PROCESS-OUTPUT (HIPO) MODELING

HIPO (Hierarchy Input Process Output) is a methodology developed and supported by

IBM. HIPO is actually a program documentation tool. Today, however, it is widely used as
a design tool and documentation technique in the system development cycle based on the
function, i.e. each module in the system is described by its main function.

According to Jogiyanto HM in the book Analysis &Design of Information Systems

(2005:787) HIPO (Hierarchy plus Input-Process-Output) is a design tool and documentation
technique in the system development cycle. HYPO (Hierarchy plus Input-Process-Output)
has the following main objectives:

a. To provide a structure to understand the functions of the program.

 b. To further emphasize the functions that must be completed by the program,
instead of showing the program statements used to carry out those functions.

c. To provide a clear explanation of the inputs to be used and the outputs that each
function must produce at each level of the HYPO diagrams.

d. To provide the right output and in accordance with the needs of the user.

• HIPO (Hierarchical Input/ Process/ Output) Chart

THE HYPO Chart is used as a tool for analyzing problems and visualizing solutions

using a top-down design approach. Starting from the global level (macro), the diagram is

gradually expanded to its detailed form (logicalbuilding blocks or functionsidentified):

The functions of the system are described by the HYPO in three levels (diagrams), namely:

1. Visual table of content

It consists of one or more hierarchical diagrams. This diagram illustrates the
relationship of functions in a tiered visual table of contents describing the entire HYPO
program both in detail and a structured summary. In this diagram the names and
numbers of the HYPO program are identified. Packet structure diagrams and function
relationships are also identified in hierarchical form. Information each function is given
in the explanatory section included in this diagram.
 Summary diagram is a series of functional diagrams. Each diagram is connected to one
of the system functions.

a) Shows broadly the relationships of inputs, processes and outputs

b) The input section shows the data items to be used by the process section

c) The process section contains a number of steps that describe the work of a
function.

d) The output section contains with data items generated or modified by process
steps

e) Summary diagrams describe the main functions and references of a system.

These functions and references are required by the program to extend the
function to the smallest description. This diagram contains the inputs,
processes and outputs of special functions.

f) The input in this diagram contains data items used by the process, while the
process is a sequence of steps that imitate the function that is being executed
to produce an output. The output contains data items generated and changed
by the process.

The arrows in the summary diagram from input to process show the relationship
between the data items in the input and the process steps, while the arrows from process
to output show the relationship of process stages and output data items.

▪
2. Diagram details

A detailed diagram is a series of functional diagrams and each diagram is connected

to a sub-function of the system. The detailed diagram is the lowest diagram in the diagram

contained in the HIPO package. Detailed diagrams contain basic package elements. The

function of this diagram is to describe specific functions, show special output and input

items and show other detailed diagrams.

1.3 BASIC CONCEPTS OF DATA FLOW DIAGRAMS

A. THE DEFINITION OF DFD

A DFD is a diagram that describes the flow of data from a process often referred to as
an information system. The data flow diagram also provides information about the inputs
and outputs of each entity and the process itself.
In the data flow diagram also has no control over its flow, so there are no rules related
to decisions or repetitions. The form of depiction in the form of flowchart data with a more
specific scheme. According to Kenneth Kozar, the purpose of dfd itself is as a provider or
bridging between users and the system.
Data flow diagram is different from UML (Unified Modelling Language), where the
fundamental thing that distinguishes between the two schemes lies in the flow and objective
delivery of information in it..

B. DFD FUNCTION

1. Submit a System Plan

With the creation of DFD, the process of conveying information becomes easier
with a simple visual display and can be understood by each stakeholder. Where, the
 data presented is able to describe the data flow in a structured manner with a more
efficient approach.
2. Describes a system
The second function, DFD can help the process of portraying the system as
functional network. The point is, in the network there are various components that
are connected to each other using data flow.
3. Model Planning
The latter function, this diagram can also create a new model design by
emphasizing the function of a particular system. This can be used to see a more
detailed part of the data flow diagram.

C. NOTATION OF DFD

1. Data Store
A data store is a file for storing data that is used for subsequent processes. It can be
said, too, just like a database. In general, data stores are tables that can be processed,
and are able to connect with at least one input and one output. Depiction or symbol of
data store in the form of two parallel lines.

2. Data Flow
Data flow is the flow of data that flows between the terminator, the process, and
the data store. Data flow is depicted with arrow symbols, and its main function is to
flow information from one system to another.
3. External Entity
External entities or more commonly called terminators are parties outside the
system, can be individuals, divisions, companies, or other systems. Terminator can
provide input or output to the system. The symbol of an external entity is denoted by a
rectangle or square.
4. Process
The process is done by the machine by converting the input into an output with a
different format. Process symbols are depicted in the form of a circle, oval, or rectangle
with additional rounded corners.

D. TYPES OF DFD

1. Diagram Level 0 (Diagram Konteks)

 A context diagram or level 0 is the lowest level diagram, which describes a
system interacting with an external entity. The context diagram will be numbered for
each process that runs, starting from the number 0 first.
So, for each data flow will be directly directed towards the system. And the
characteristic of a level 0 diagram lies in the absence of information related to data
stored in the data store.
2. Diagram Level 1
DFD level 1 is a continuation of the context diagram, where each process that runs
will be detailed at this level. Thus, the main process will be broken down into even
smaller sub-processes.
3. Diagram Level 2
DFD level 2 is the advanced level of the previous level, which in this phase will be
explained in more detail related to each process. However, for this level is rarely done
and more only apply two levels below it.

E. HOW TO CREATE A DFD

1. Data Store Must Be Processed

First, what you need to pay attention to is that every data store store must be
processed further to be used as output (output).

2. Make sure the amount of Input dan Output

Second, each DFD has at least one input and one output. Because the data flow
diagram must reflect the flow of the system from the initial stage to the end.
3. Relationships in the Data Store
Third, each data store must be connected with at least one input and one output
in order to store incoming data to the system..
4. Process Position Location
The final rule, any process that has occurred on a data flow diagram must go
through the process to produce the corresponding output.

F. THE EXAMPLE OF DFD

1.4 EXPLAIN 1 CASE

LIST ACTIVITY OF ONLINE PURCHASE ORDER

1. Consumers register members.
2. Consumers make purchases of goods.
3. Consumers get a note/receipt for proof of payment.
4. owner/admin can view item data reports, sales reports, and inventory reports.
CONTEXT DIAGRAM

DFD 0 LEVEL

DFD 1.0 LEVEL FOR REGISTER

DFD 2.0 LEVEL FOR PURCHASE ORDER

DFD 2 LEVEL FOR 2.4 PROCESS