Universiti Teknologi MARA
Development of Karisma Enterprise Inventory Management System (KIMS)
Muhammad Firdaus Bin Md Fadzil
Thesis submitted in fulfilment of the requirements for Bachelor of Information Technology (Hons.) Faculty
of Computer and Mathematical Sciences
July 2016
ACKNOWLEDGEMENT
Alhamdulillah, I am really grateful to Allah S.W.T for giving me healthy, strength, idea and opportunity to complete my final year project for this semester as a fulfillment of the requirements for the course CSP650. Without his blessing and permission, this project could not have been completed.
First of all, my utmost gratitude to the Almighty Allah for His blessings and guidance throughout time. I would like to take the opportunity to thank those who have helped and supported me all this while. My very first thanks goes to Puan Jamaliah Taslim, the ever patient advisor. Without her guidance and help, this thesis would not have been a successful one.
Also to my family who is always there whenever I'm in need, mentally and financially.
Last but not least, I treasure the streaming help and support from friends and classmates.
It has been such a wonderful year being with all of you, through all the bitter and sweet memories.
IV
ABSTRACT
Karisma Enterprise Inventory Management System (KIMS) is developed for the management of Karisma Enterprise Menara Condong, Teluk Intan, Perak. Currently, the management of the company does not have a system that can help them in managing their data and all the data are being managed manually. A user friendly system is needed and can be functioned in managed the company data such as create, retrieve, update and delete the data. The objectives of this project are to identify user requirement for KIMS, to design the KIMS based on the user requirements and to develop the KIMS by using Rapid Application Development (RAD). This system provide user to manage information systematically. This system also generate dashboard and report to improve the quality of management in the company. Data matching will be used to search specific data stored in the database. In addition, all data can be stored safely and can be retrieved quickly anywhere and anytime since this system is online system. This system will help the management to do managing order process more quickly with supplier email notification.
The methodology works best for projects where the scope is small or work can be broken down into manageable chunks. Furthermore, in order to keep the project within a short time frame, decisions must be made quickly, so it is imperative that there be very few client decision makers, preferably only one, and they must be clearly identified up front.
Identified problems were solved using KIMS especially to manage the data of stocks.
Future works are focusing in adding more interactive web design interfaces, applying Short Messages Services (SMS) notifications and customizable report to increase company efficiency and performance.
TABLE OF CONTENTS
CONTENT PAGE
SUPERVISOR APPROVAL ii STUDENT DECLARATION iii ACKNOWLEDGEMENT iv
ABSTRACT v TABLE OF CONTENTS vi
LIST OF FIGURES ix LIST OF TABLES xi LIST OF ABBREVIATIONS xii
CHAPTER 1: INTRODUCTION
1.1 Background 1 1.2 Problem Statement 6 1.3 Area of Interest 6 1.4 Research Questions 7
1.5 Objectives 7 1.6 Scopes 7 1.7 Significance 8 1.8 Summary of Research design 10
1.9 Summary 12
CHAPTER 2: LITERATURE REVIEW
2.1 Definitions 13 2.1.1 Inventory 13 2.1.2 Inventory management system 14
2.1.3 Web Based System 17 vi
2.1.4 System Development Life Cycle (SDLC) 17 2.1.5 Rapid Application Development (RAD) 19
2.1.6 User Interface (UI) Design 20 2.2 Tools/Technique/Technology of Inventory Management System 22
2.2.1 PHPMyAdmin 22 2.2.2 Yiiframework 23 2.2.3 PHP/Client-Server Application 23
2.2.1 Apache HTTP Server 24
2.2.5 WampServer 24 2.2.5 Notification 25 2.3 Reviewing Existing/Similar Web Based System/Application 27
2.3.1 Inflow Inventory 27 2.3.2 Cin7 Inventory 28 2.3.3 Skyware Inventory 29 2.3.4 Buble Inventory 30 2.3.5 Stockpile Inventory 31 2.4 Design Requirement 32
2.4.1 Functional Requirement 32 2.4.2 Non-Functional Requirement 32 2.5 Summary of Reviewing Existing/Similar Web Based System/Application 33
CHAPTER 3: METHODOLOGY
3.1 Project Approach 35 3.2 Research Plan/Framework Phases 37
3.2.1 Requirement Planning 38
3.2.2 User Design 40 3.2.3 Construction 41
