making and the problems to be resolved must be
clearly defined because this will affect the system
used.
There are three objectives or levels in decision
making, namely strategic planning, management
control, and operational control (Bodnar & Hopwood,
1995). While in decision making, there are several
forms of problems faced that determine the form of
decisions taken, namely structured problems,
unstructured problems, and semi-structured problems
(Boockholdt, 1999).
According to Romney & Steinbart (2018), there
are various reasons for an organization to make a
system change, that change in user and organizational
needs, technological changes, business process
improvements, creating competitive advantages,
increasing productivity, integrating systems, and old
systems that have expired and need to be replaced.
In analyzing and evaluating the problems
contained in the system, there is a framework that can
be used to group system problems. Wetherbe &
Vitalari (1994) as referred to by Whitten & Bentley
(2007) developed a framework that can group system
problems called PIECES Framework. PIECES
Framework includes Performance, Information (and
Data), Economics, Control (and Security),
Efficiency, and Service.
According to Whitten & Bentley (2007), system
design methods ensure that a consistent and
repeatable approach has been applied to all
information system projects; the risk of errors and
shortcuts has been minimized; Project documentation
has been fully and consistently documented; analysts,
designers, and system builders can be immediately
assigned to the project; and the results of previous
work can be easily obtained and analyzed by a new
system design team. The system design method is
basically developed from the system design life cycle
(SDLC).
Satzinger et al. (2012) develop system design in
six processes, namely:
1. Identify problems and needs.
2. Plan and monitor the project - what will be
done, how it will be done, and who will do it.
3. Discover and understand the details of the
problem or need.
4. Design system components to solve problems
or meet needs.
5. Build, test, and integrate system components.
6. Complete the system test and launch the
resulting solution.
There are several tools that can be used to review,
analyze, and design systems. These tools include
interviews, flowcharts, several forms of system
documentation, and project management tools
(Boockholdt, 1999).
1. Interview. Interviews are needed in system
design to evaluate existing systems and identify
new system requirements.
2. Flowcharts. Flowcharts describe business
processes and document flows within an
organization (Romney & Steinbart, 2018).
Agile Methodologies and Iterative Development.
One of the weaknesses of the existing system design
process is the failure to maintain the time and budget
of the system design. Most system development is
used to solve complex organizational problems that
require a lot of planning in executing projects
(Satzinger et al., 2012). In addition, the application of
the SDLC method with a waterfall approach that is
generally used assumes that the requirements that
have been made at the outset in system design do not
change until the end of the system design process or
also called plan-driven approaches (Cobb, 2015).
In fact, many requirements in a system design
project change because users often don't understand
what is desired in the system (Romney & Steinbart,
2018). Users will find out and find other requirements
that are different when the system design process is
running. In addition, very rapid technological
changes drive the product cycle to be shorter so that
the system design method that requires a long time is
no longer appropriate. Based on this, the system
designer (system developer) requires an agile
method, which is a method in which the system
developer is open to changes in system design.
Agile methodologies or agile development is a
system development process that focuses on
flexibility in dealing with changes in system design
(Satzinger et al., 2012). The basic philosophy of agile
development is that either the system developer or
user alike does not fully understand the problems and
complexity of a new system so that project planning
and execution must be able to deal with changes that
occur in system design. The design of the system
must be agile and flexible.
According to Satzinger et al. (2012), an agile
system design is carried out iteratively and
incrementally. Iterative development is a system
design in which the system is arranged part by part
through a series of iterations. Six core processes in
system development are carried out simultaneously
and are repeated continuously to add value to the
entire system designed. Thus, in a system project
there are several subproject systems to support the
system.