FEASIBILITY STUDY

[Project or System Name]

[Company Name]
Month, Year

Revision Sheet

Revision Sheet
Release No.
Rev. 0
Rev. 1
Rev. 2

Feasibility Study

Date

Revision Description

Page i

Authorization Memorandum

Feasibility Study Authorization

Memorandum

I have carefully assessed the Feasibility Study for the (System Name).
MANAGEMENT CERTIFICATION - Please check the appropriate statement.
______ The document is accepted.
______ The document is accepted pending the changes noted.
______ The document is not accepted.
We fully accept the changes as needed improvements and authorize initiation of work to proceed. Based on
our authority and judgment, the continued operation of this system is authorized.
_______________________________
NAME
Project Leader

_____________________
DATE

_______________________________
NAME
Operations Division Director

_____________________
DATE

_______________________________
NAME
Program Area/Sponsor Representative

_____________________
DATE

_______________________________
NAME
Program Area/Sponsor Director

_____________________
DATE

Feasibility Study

Page ii

FEASIBILITY STUDY
TABLE OF CONTENTS
Page #
1.0

GENERAL INFORMATION.............................................................................................1-1

1.1

Purpose...........................................................................................................................1-1

1.2

Scope...............................................................................................................................1-1

1.3

System Overview............................................................................................................1-2

1.4

Project References..........................................................................................................1-2

1.5

Acronyms and Abbreviations........................................................................................1-3

1.6

Points of Contact............................................................................................................1-3

1.6.1
1.6.2

2.0

Information............................................................................................................................................1-3
Coordination..........................................................................................................................................1-3

MANAGEMENT SUMMARY...........................................................................................2-1

2.1

Environment...................................................................................................................2-1

2.1.1
2.1.2
2.1.3
2.1.4

3.0

Organizations Profile and Its Current Conditions................................................................................2-1

Organizations Potential Problems.........................................................................................................2-1
IT/IS Utilizations (Contributions)........................................................................................................2-1
The Need Analysis................................................................................................................................2-2

PROPOSED SYSTEM.......................................................................................................3-1

3.1

Description of Proposed System...................................................................................3-1

3.2

Improvements.................................................................................................................3-1

3.3

Time and Resource Costs..............................................................................................3-1

3.4

Impacts...........................................................................................................................3-1

3.5

Rationale for Recommendations..................................................................................3-2

3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6
3.4.7

4.0

Equipment Impacts...............................................................................................................................3-1
Software Impacts...................................................................................................................................3-1
Organizational Impacts.........................................................................................................................3-1
Operational Impacts..............................................................................................................................3-2
Developmental Impacts.........................................................................................................................3-2
Site or Facility Impacts.........................................................................................................................3-2
Security and Privacy Impacts................................................................................................................3-2

4.x

ALTERNATIVE SYSTEMS...............................................................................................4-1
Description of [Alternative System Name]..................................................................4-1

Feasibility Study

Page iii

1.0 General Information

1.0

Feasibility Study

GENERAL INFORMATION

1.0 General Information

NOTE TO AUTHOR: Highlighted, italicized text throughout this template is provided solely as
background information to assist you in creating this document. Please delete all such text, as well as
the instructions in each section, prior to submitting this document. ONLY YOUR PROJECTSPECIFIC INFORMATION SHOULD APPEAR IN THE FINAL VERSION OF THIS
DOCUMENT.
The Feasibility Study is used to provide an analysis of the objectives, requirements, and system concepts
of the proposed system, including justification, schedule, and end products. During this analysis, the
objectives of the system are defined based on the needed functions described previously. Included in
these system objectives are the high-level functional and performance objectives and any assumptions
and constraints. When the system objectives have been identified, the various alternatives for satisfying
those objectives are determined. For each alternative, the costs in time and resources are estimated. A
determination is then made as to the most feasible development alternative.

1.0

GENERAL INFORMATION

1.1

Purpose

Describe the purpose of the Feasibility Study.

1.2

Scope

Describe the scope of the Feasibility Study as it relates to the project.

Feasibility Study

Page 1

1.0 General Information

1.3

System Overview

Provide a brief system overview description as a point of reference for the remainder of the document. In
addition, include the following:

Responsible organization

System name or title

System code

System category

Major application: performs clearly defined functions for which there is a readily
identifiable security consideration and need

General support system: provides general ADP or network support for a variety of users
and applications

Operational status

Operational

Under development

Undergoing a major modification

System environment or special conditions

1.4

Project References

Provide a list of the references that were used in preparation of this document. Examples of references
are:

Previously developed documents relating to the project

Documentation concerning related projects

HUD standard procedures documents

Feasibility Study

Page 2

1.0 General Information

1.5

Acronyms and Abbreviations

Provide a list of the acronyms and abbreviations used in this document and the meaning of each.

1.6

Points of Contact

1.6.1 Information
Provide a list of the points of organizational contact (POC) that may be needed by the document user for
informational and troubleshooting purposes. Include type of contact, contact name, department, telephone
number, and e-mail address (if applicable). Points of contact may include but are not limited to helpdesk
POC, development/maintenance POC, and operations POC.

1.6.2 Coordination
Provide a list of organizations that require coordination between the project and its specific support
function (e.g., installation coordination, security, etc.). Include a schedule for coordination activities.

Feasibility Study

Page 3

2.0 Management Summary

2.0

Feasibility Study

MANAGEMENT SUMMARY

2.0 Management Summary

2.0

MANAGEMENT SUMMARY

2.1

Environment

2.1.1 Organizations Profile and Its Current Conditions

1. Profil Organisasi
Nama Perusahaan

: Toko Visi Media

Bidang Usaha

: Media Informasi

Jenis Produk/Jasa

: Apple Computer, Gadget, Laptop

Alamat

: Jalan Hos Cokroaminoto no.122/36 Pekanbaru,Riau.

2. Kondisi Saat Ini

Setiap harinya toko ini selalu dikunjungi oleh beberapa pelanggan yang berasal dari
berbagai kalangan, namun dalam kesehariannya pelanggan didominasi oleh penduduk asli
pekanbaru dan beberapa lainnya dari luar kota dan bahkan sebagian ada beberapa orang
asing yang datang ke toko ini , rata rata orang asing itu adalah orang yang bekerja selama
beberapa bulan di kota Pekanbaru.
Bedasarkan hasil wawancara antara develop dengan client, disimpulkan bahwa
setiap harinya toko ini memiliki pemasukan yang selalu meningkat. Karena toko ini
berkecimpung pada penjualan media teknologi, pelanggan dari toko ini terbilang cukup
banyak dan memiliki selera yang berbeda-beda. Banyaknya proses jual-beli antar client
dengan consumer menyebabkan toko ini memiliki beberapa latar masalah. Masalah
utamanya adalah terkait transaksi jual-beli yang tidak dapat di handle oleh perseorangan
dan manual menggunakan nota/kwitansi.
Berdasarkan latar belakang kondisi tersebut toko ini sangat membutuhkan sebuah
program aplikasi yang dapat membantu dan mengatur sebagian besar dari proses bisnis
yang terjadi dalam struktur transaksi penjualan produk yang diharapkan mampu
mendapatkan profit yang lebih tinggi.
3. Proses Bisnis
Tujuan Pembuatan SI

: Memudahkan pemilik toko dalam mengelola data dan

keuangan toko.

Input

: Data admin/user, pelanggan, barang

Output

: Memberi informasi berupa data barang, data pelanggan,

data admin, data transaksi, laporan keuangan dan statistic

Stakeholder

Feasibility Study

: Pemilik toko, pegawai/karyawan

Page 1

2.0 Management Summary

2.1.2 Organizations Potential Problems

Problem

Timing
(H/M/L)
1. Pengolahan data user, H
pelanggan
dan
barang
dilakukan secara manual

Trend
(H/M/L)
H

Impact
(H/M/L)
H

2. Transaksi jual-beli barang M

dan jasa masih menggunakan
nota/kuitansi yang masih
ditulis tangan, penulisan
harga masih harus mencari
pada list daftar harga,
perhitungan total biaya
masih
menggunakan
kalkulator/manual
3. Laporan dilakukan secara H
pembukuan
dan
ditulis
tangan
sesuai
dengan
nota/kuitansi yang ada

.4. Rekap nota masih manual M

5. Kurangnya pemanantauan H
barang yang habis terjual
dengan barang yang sulit
terjual

Next Process
Membuat
system
informasi yang digunakan
untuk pembukuan data
user,
pelanggan
dan
barang.
Membuat
system
informasi yang dapat
dengan mudah secara
otomatis
menampilkan
harga perbarang dan
meng-output-kan jumlah
total transaksi
Membuat
system
informasi
pembukuan
laporan
secara
terkomputerisasi
berdasarkan
history
transaksi
Membuat
system
informasi rekap transaksi
penjualan berupa history
penjualan
Membuat
system
informasi yang dapat
merekap stok barang
yang
keluar
dengan
menampilkan
statistic
penjualan barang

2.1.3 IT/IS Utilizations (Contributions)

1. Sistem informasi dirancang untuk mengurangi proses transaksi secara manual seperti
pembukuan data barang, penggunaan nota pada proses transasksi, laporan keuangan
perusahaan. Dengan menerapkan system ini, maka proses manual dapat dikelola secara
terkomputerisasi.

Feasibility Study

Page 2

2.0 Management Summary

2. Mengatur rekap nota transaksi, keuangan dan data barang agar lebih mudah di kontrol
oleh pemilik Toko Visi Media. Dengan menggunakan metode manual, proses kontrol
mungkin saa terjadi kesalahan seperti nota yang hilang, kecurangan pegawai dan
kesalahan-kesalahan lainnya. Dengan system ini, kesalahan-kesalahan dalam proses control
dapat diminimalisir.
3. Sistem informasi dirancang memiliki fungsional statistic dimana tercatat produk mana yang
lebih banyak terjual setiap minggunya sehingga pemilik toko tidak perlu lagi menyuplai
barang yang sulit atau bahkan tidak banyak terjual. Dalam proses ini, kerugian toko dalam
supply barang yang tidak diperlukan dapat diminimalisir.
2.1.4 The Need Analysis
Bagian 1: Tujuan Strategis Perusahaan
Visi :
Misi :
Tujuan Sistem :
Bagian 2. Identifikasi dan Analisa Anggaran
Dalam perancangan system informasi ini, pihak UKM Toko Visi Media tidak menyediakan
anggaran.

Bagian 3 : Stakeholder
Dalam perancangan system informasi ini terdapat pihak-pihak yang berkepentingan dalam
penggunaan system.
1. Pemilik toko
Pada penggunaan system, pemilik toko tetap dapat menggunakan system. Selain
bertanggung jawab dalam sumber dari requirment analysis system, pemilik toko juga
dapat mengakses system untuk memantau jalannya proses transaksi selama pemilik toko
tidak ada ditempat.
2. Pegawai/Karyawan
Pada penggunaan system, pegawai/karyawanlah yang berperan sebagai user. Mereka yang
mengelola perusahaan dari mulai supply barang, penjualan hingga proses transaksi.
3. Pembeli
Pada penggunaan system, pembeli tidak langsung berperan sebagai user namun pembeli
inilah yang menjadi sumber data dari system informasi toko.
Bagian 4 : Spesifikasi Outputan
Dalam perancangan dan pembangunan system informasi untuk UKM Toko Visi Media
terdapat fungsional system yang memberikan outputan berupa :
1. Proses transaksi yang lebih efisien dan mudah. Transaksi dilakukan secara kalkulasi
otomatis oleh system.
Feasibility Study

Page 3

2.0 Management Summary

2. Pendataan barang dan stok yang masih tersedia, serta statistik penjualan barang terlaris

agar memudahkan pemilik toko dalam menyuplai persediaan barang tanpa harus
mengalami kerugian karena kesalahan supply barang.
3. Rekap transaksi penjualan setiap minggu atau bulan yang tujuannya untuk dijadikan
laporan keuangan.
4. Pelaporan keuangan terdata secara otomatis berdasarkan rekap transaksi.
Bagian 5 : Batasan Ruang Lingkup
mengingat luasnya jangkauan dalam perancangan system, system informasi yang akan
dirancang dan dibangun hanya meliputi :
1. sistem dirancang berbasis aplikasi kasir
2. system mampu melakukan proses transaksi jual-beli (pembelian barang), kalkulasi total
biaya.
3. sistem mampu menerima mengelola data admin, pelanggan/pembeli dan barang.
4. sistem mampu melakukan statistika berdasarkan penjualan setiap harinya.
5. sistem mampu memberikan laporan keuangan berdasarkan rekap transaksi sesuai keinginan
pemilik toko (perminggu, perbulan atau pertahun).

Feasibility Study

Page 4

3.0 Proposed System

3.0

Feasibility Study

PROPOSED SYSTEM

3.0 Proposed System

3.0

PROPOSED SYSTEM

3.1

Description of Proposed System

Present the overall system concept and describe how the requirements will be met.

3.2

Improvements

Describe the improvements of the system in terms of the objectives.

3.3

Time and Resource Costs

For time allocation please build a expected timeline to accomplished the project and outline the time and
resource costs, including the time and funding required for all activities of the lifecycle, from definition
through operation and system retirement. It is imperative to use realistic estimates. When making the
estimates, remember to include such factors as the current workload of personnel, staff absences due to
vacation and illness, lead time for procurement of equipment and software, and staff training. Methods
that might help are NPV and/or ROI analysis.

3.4

Impacts

In the following subsections, describe the anticipated impacts of the proposed system, including potential
conversion problems.

3.4.1 Equipment Impacts

Describe new equipment requirements and changes to currently available equipment.

3.4.2 Software Impacts

Describe any additions or modifications to existing applications and support software in order to adapt
them to the proposed system.

3.4.3 Organizational Impacts

Describe any organizational, personnel, and skill requirement changes.

Feasibility Study

Page 1

3.0 Proposed System

3.4.4 Operational Impacts

Describe the effects on operations, such as:

User operating procedures

Operating center procedures

Operating center/user relationships

Source data processing

Data entry procedures

Data retention requirements, information storage and retrieval procedures

Output reporting procedures, media, and schedules

System failure contingencies and recovery procedures

3.4.5 Developmental Impacts

Describe the developmental impacts, such as:

Specific activities to be performed by the user in support of development of the system

Resources required to develop databases

Computer processing resources required to develop and test the new system

Privacy and security implications

3.4.6 Site or Facility Impacts

Describe building or office modification requirements.

3.4.7 Security and Privacy Impacts

Describe security and privacy factors that may influence the development, design, and continued operation
of the proposed system.

3.5

Rationale for Recommendations

State the reasoning that supports the recommendation of the proposed system over the alternative systems.

Feasibility Study

Page 2

4.0 Alternative Systems

4.0

Feasibility Study

ALTERNATIVE SYSTEMS

4.0 Alternative Systems

4.0

ALTERNATIVE SYSTEMS

This section provides a description of the alternative systems considered in this feasibility study. Each
alternative system should be under a separate section header, 4.1 - 4.x.

4.x

Description of [Alternative System Name]

Describe the alternative system, following the outline described for the proposed system in the previous
section. State the reasons that the alternative system was not selected.

Feasibility Study

Page 1