PERANCANGAN SISTEM INFORMASI PENGADAAN PADA PT X MENGGUNAKAN METODE STANDARD PACKAGE
PT X is a company that provides digital payment services in Indonesia. PT X does the process of procurement to fulfill their 11 subsidiaries’s business requirement. However, the process is still done manually and not integrated. It causes some problems, such as typing mistake, long processing time,...
Saved in:
| Main Author: | |
|---|---|
| Format: | Final Project |
| Language: | Indonesia |
| Online Access: | https://digilib.itb.ac.id/gdl/view/67734 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| Institution: | Institut Teknologi Bandung |
| Language: | Indonesia |
| Summary: | PT X is a company that provides digital payment services in Indonesia. PT X does the process of procurement to fulfill their 11 subsidiaries’s business requirement. However, the process is still done manually and not integrated. It causes some problems, such as typing mistake, long processing time, less integrated data, less integrated communication media with vendor, etc. Therefore, PT X needs an integrated information system to make the procurement process to be more effective and efficient.
This research aims to design an integrated information system for PT X procurement process. The designing process applies standard package method following the steps of information system development life cycle based on Whitten & Bentley (2007). Standard package method is chosen because PT X does not have enough resources with the ability to develop their own application.
The process of designing information system in this research is done by mapping current business process, identifying problem, defining system improvement objectives, identifying system requirement, choosing standard package software vendor, installation, mapping proposed business process, and designing information system prototype by configuring Odoo software. The prototype is then tested if it functions well by design and verified based on the proposed business process. The prototype is also validated by system user based on identified functional requirement, non-functional requirement, and system improvement objectives.
|
|---|