Parkson Book Store Information Management System.
BORANG PENGESAHAN STATUS TESIS
JUDUL: PARKSON BOOK STORE INFORMATION MANAGEMENT SYSTEM
SESI PENGAJIAN: 200912010
Saya YU KAI LING
mengaku membenarkan tesis (PSMlSarjana/Doktor Falsafah) ini disimpan di
Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dengan syarat-syarat
kegunaan seperti berikut:
1. Tesis dan projek adalah hakrnilik Universiti Teknikal Malaysia Melaka.
2. Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dibenarkan
membuat salinan untuk tujuan pengajian sahaja.
3. Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dibenarkan
membuat salinan tesis ini sebagai bahan pertukaran antara institusi pengajian
tinggi.
4. * * Sila tandakan (/)
/
SULIT
(Mengandungi
maklumat
yang
berdarjah keselamatan atau kepentingan
Malaysia seperti yang termaktub di
dalam AKTA RAHSIA RASMI 1972)
TERHAD
(Mengandungi maklumat TERHAD
yang
telah
ditentukan
oleh
organisasilbadan di mana penyelidikan
dijalankan)
TIDAK TERHAD
I\
(TANDATANGAN PENULIS)
Alarnat tetap: Lot 4417 Jalan Taman
King Lee Green Wood Park ,98000
Miri Sarawak
Tarikh: ~ t \ b \ @ [ '
(TANDATAN~AN
PENYELIA)
~ n & g f & & & @ ~ ~
Pensyarah
Jabatan Kejunrteraan t w i n
FakuRi Teknobgi Maklumat Dan K m i k a s i
MeMa
8
CATATAN: * Tesis dimaksudkan sebagai Laporan Akhir Projek Sarjana Muda
(PSM)
* * Jika Tesis ini SULIT atau TERHAD, sila lampirkan surat
daripada pihak berkuasa.
PARKSON BOOK STORE INFORMATION MANAGEMRNT SYSTEM
YU KAI LING
This report is submitted in partial fulfillment of the requirements for the
Bachelor of Computer Science (Database)
FACULTY OF INFORMATION AND COMMUNICATION TECHNOLOGY
UNIVERSITI TEKNIKAL MALAYSIA MELAKA
2010
DECLARATION
I hereby declare that this project report entitled
PARKSON BOOK STORE INFORMATION MANAGEMENT SYSTEM
is written by me and is my own effort and that no part has been plagiarized
without citations
STUDENT
/%
(YU %I LING)
I
SUPERVISOR
Jabatan Kejurutsraan Periskn
Fakrrlti Teknologi MakiurnaPDan Komunikasi
Universiti T*knikal Maleysia Melaka
Date:
~
( ("Iob
DEDICATION
To my beloved parents who always encourage me
YU YOUNG PUNG
TING A1 MEE
ACKNOWLEDGEMENTS
First, I need thank my advisor Puan Kasturi Kanchyrnalay, for her continuous support in
this subject. Puan Kasturi Kanchmalay was always there to listen and to give advice. She
showed me different ways to approach a research problem and the need of persistent in
achieving my goals. I would like to point out her unusual effort and patient in guiding
me for this project. Thank you very much.
At the same time, I would like to thank my beloved parents, who have been giving
support and motivation throughout my project. So let me don't have too much stress to
do this project. Besides this I also have to thank the ftmk's lab willing borrow me
barcode scanner to implement my project so i can finish my system. Lastly, also thank to
peter yong guang da for the ideas and insightful comments for my project throughout the
entire semester.
ABSTRACT
From this report, we will know this system more focusing in the day to day
transaction and stock controlling. This system got the a lot of multipurpose function like
generate the report, mapping checking, stock reminder, purchase order and other. Apart
from this, we also can compare to other related system or article in literature review to
improve this system. On .the other hand, we also can know the how the problem is
happen and from this problem statement we can make a complete solution to improve
for this inventory system. Design is a chapter that we can let the user to see our system
interface in graphic user interface (GUI) with nice view. From this chapter we also know
the flow chat and system structure diagram for the running flow and algorithm for this
whole system. How to link the database table for each related table to generate every
function and other internal design as well. Finally, we can say that, this system will
bring the user a lot of function to make the daily task became easily, flexible and also
systematic.
ABSTRAK
Dari laporan ini, kita akan mengetahui sistem in. lebih fokus dalam hari ke hari
transaksi dan barangan pengendali. Sistem ini punya banyak fimgsi serbaguna seperti
menghasilkan laporan, pemetaan menyemak,barangan peringatan, tempahan pembelian
dan lain-1ain.Selain itu, kita juga boleh membandingkan sistem ini dengan sistem
berkaitan lain atau artikel dalam tinjauan literatur supaya boleh dapat idea untuk
memperbaiki sistem ini. Di sisi lain, kita akan dapat mengetahui masalah yang dihadap
dan kita akan membuat penyelesaian lengkap untuk meningkatkan sistem ini.Design
merupakan sebuah bab yang kita boleh membiarkan pengguna untuk melihat antara
muka sistem kami dalarn antara muka pengguna grafik (GUI) dengan tampilan yang
bagus. Dari bab ini, kami juga tahu aliran chat dan diagram sistem struktur untuk
keseluruhan sistem. Akhirnya, kita dapat mengatakan bahawa, sistem ini akan membawa
pengguna lebih banyak fungsi untuk membuat tugas sehari-hari menjadi mudah,
fleksibel dan juga sistematik.
TABLE OF CONTENTS
CHAPTER
CHAPTER I
SUBJECT
PAGE
DECLARATION
ii
DEDICATION
iii
ACKNOWLEDGEMENT
iv
ABSTRACT
v
ABSTRAK
vi
TABLE OF CONTENTS
vii
LIST OF TABLES
xiii
LIST OF FIGURES
xiv
LIST OF ABBRREVIATONS
xix
LIST OF APPENDICES
XX
INTRODUCTION
1.1
Project Background
1.2
Problem Statement
1.3
Objective
CHAPTER
CHAPTER I1
PAGE
SUaTECT
1.4
Scope
1.5
Project significance
1.6
Expected Output
1.7
Conclusion
LITERATURE REVIEW
AND PROJECT METHODOLOGY
2.1
Introduction
2.2
Facts and findings
2.2.1
Domain
2.2.1.1
Book Store
information
management
system definition
2.2.2
2.2.1.2
Barcode
2.2.1.3
Barcodescanner
Existing System
2.2.2.1
Case Study 1:
CDP BOOK
SYSTEMS
2.2.2.2
Case Study 2:
ABEBOOKS
HOMEBASE
SYSTEM
2.3
Project Methodology
CHAPTER
SUBJECT
2.4
CHAPTER 111
PAGE
2.3.1
Requirement Analysis
2.3.2
Design
2.3.3
Implementation
2.3.4
Verification
2.3.5
Maintenance
Project Requirement
2.4.1
Software Requirement
2.4.2
Hardware Requirement
2.5
Project Schedule and Milestone
2.6
Conclusion
ANALYSIS
3.1
Introduction
3.2
Problem analysis
3.3
3.2.1
Current system
3.2.2
Problem Statement
Requirement analysis
3.3.1
Data Requirement
3.3.2
Functional Requirement
3.3.3
Non-functional Requirement
3.3.4
Other Requirement
3.3.4.1 Software Requirement
3.3.4.2 Hardware Requirement
3.4 Conclusion
CHAPTER
SUBJECT
CHAPTER IV
DESIGN
PAGE
4.1
Introduction
4.2
High-Level Design
4.2.1
System Architecture
4.2.2
User Interface Design
4.2.2.1
Navigation
Design
4.2.3
4.2.2.2
Input design
4.2.2.3
Output Design
Conceptual and Logical
Design
4.3
4.4
CHAPTER V
4.2.3.2
Business Rule
4.2.3.3
Data Dictionary
4.2.3.4
Normalization
4.2.3.5
DBMS Selection
Detail Design
4.3.1
Software Design
4.3.2
Physical database design
Conclusion
DESIGN
5.1 Introduction
5.2 Development
Environment setup
5.3
Database Implementation
CHAPTER
SUBJECT
PAGE
5.4
94
Software Configuration
Management
5.4.1
Configuration
94
environment setup
Version Control Procedure
5.4.2
CHAPTER VI
5.5
Implementation Status
98
5.6
Conclusion
106
TESTING
6.1
Introduction
6.2
Test Plan
6.3
6.2.1
Test Organization
6.2.2
Test Environment
6.2.3
Test Schedule
Test Strategy
6.3.1
6.4
CHAPTER VII
97
Classes of tests
Test Design
6.4.1
Test Description
6.4.2
Test Data
6.5
Test Result and Analysis
6.6
Conclusion
PROJECT CONCLUSION
7.1
Observation on weakness and strengths
115
CHAPTER
SUaTECT
PAGE
7.2
Propositions for Improvement
116
7.3
Contribution
117
7.4
Conclusion
117
REFERENCES
BIBLIOGRAPHY
LIST OF TABLES
TABLE
TITLE
Comparison two case studies
Hardware Requirement
Output design for whole system
List of Procedure and control
Implementation Status for modules
Test Organization
Test Schedule
PAGE
LIST OF FIGURES
FIGURE
TITLE
Barcode
Barcode Scanner
Waterfall model
Current system's
context diagram
Current system's DFD
Current system's DFD Level 1
for manage point of sales
and print receipt
Current system's DFD levels 21
for recording sales item
and daily sales report
Current system's DFD levels 21
for manage reorder
Current system's DFD levels 1
for update product's quantity
PAGES
FIGURE
TITLE
PAGES
Parkson book store information
27
management system's
context diagram
PBSMS's Data flow diagram
Two-tier architecture view
Navigation Design
Email received by manager
The content for email
Download the new purchase
Order attachment
Purchase Order
Output for line graph
Output for bar graph
Output for carta pie graph
ERD Diagram
Create database
FIGURE
4.12
TITLE
Selecting the operation that
will be performed
Selecting the database template
Named the Database Name
Selecting the mode to be operated
Selecting the initialization parameters
Description for database Storage
Creation option
Progress of database creation
Entering the password
for user sys and system
Login Page for login the oracle database
Success login, this is main page
for oracle database.
Error Message
Command Prompt for backup
PAGES
65
xvii
FIGURE
TITLE
PAGES
4.26
Load the backup command
78
4.27
Locate the backup file at local d
79
4.28
Type Recover command at
80
command Prompt
Load Recover command
Client server diagram
LAN Area
Login Interface for restring
and sorting Data
Supplier interface for restring
and sorting Data
Top Popular sales product for Restring
and Sorting Data
Product quantity interface for
join tables
Mapping Product interface for
aggregate function
Point Of Sales Interface for
aggregate function
FIGURE
TITLE
PAGES
5.9
Sales report interface for
92
aggregate function
Category Interface for
Update, Insert Function
Server Explore
Choose Data Source
Add Connection
Success Messages for
test connection
Unsuccess Messages for
text connection
LIST OF ABBRREVIATONS
ERD
-
Entity relationship diagrams
DFD
-
Data flow diagram
PBSMS
-
Parkson book store management system
LAN
-
Local area network
WLAN
-
Wireless local area network
LIST OF ATTACHMENTS
ATTACHMENTS
PAGE
APPENDIX A
MILESTONE
APPENDIX B
BUSINESS PROCESSING'S
APPENDIX C
PARKSON BOOK STORE
MANAGEMENT INFORMATION
SYSTEM (PBSM) DFD LEVEL 1
APPENDIX D
INTERFACE DESIGN
APPENDIX E
INPUT DESIGN
APPENDIX F
DATA DICTIONARY
APPENDIX G
NORMALIZATION
APPENDIX H
TEXT DESCRIPTION
APPENDIX I
TEXT DATA
APPENDIX J
TEXT RESULT
APPENDIX K
USER MANUAL
CHAPTER 1
INTRODUCTION
1.1 Project Background
Nowadays, more than 50% of the book store or book shop well still using with
traditionab'manual system to operate their business. Because of this problem, make a
lot of inconvenience for the owner and user to operate all the process with a good
systematic management. On this final year project, with title "Parkson Book Store
Information Management System" look well simple, but it will resolve the entire
problem as well to achieve the user goal as good as possible. Besides this, this
system will provide management system, to control the level of store in term of no
over stock or out of store situation been appear. On the other hand, this system wills
also having a fast search, update and other function as well as for each information.
Finally, we can find that this system is implementing with new technology hardware
with barcode scanner and also report generator. These two functions are to make
time consumption to the user besides than preparing purchase order (PO), searching,
key-in the data of each item and other as well as user-friendly for every user.
1.2 Problem Statement:
i)
Time Constraints - Previous system need a lot time to get item's
information.
ii)
Human Failure - Manual Inventory record will easily get wrong record
of quantity and information that item remains in the store. Because they
calculate manually.
iii)
Insufficiency in Service - The difficulty to finding stock location is very
challenge. This is because too much product is kept in the store and the
space of the store is large enough.
iv)
Security Problem - Lacks of security measurable, the information is
easily define by unauthorized persons
1.3 Objective
i)
Barcode scanner will be implementing for scan the item's code to quickly
retrieve the item's information and reduce worker's load and time
management.
ii)
This system wills implement auto controIling the stock can precise
calculate quantity remain stock .it generate report about product quantity
can let the purchaser making decision for reorder items
iii)
This system will provide mapping and actual location for particular stock
in a store of the shop.
iv)
Security policy and limitation of privilege in diffaent level of authorizers
will be implementing to make the system more secure.
1.4 Scope
The Platform for this Parkson book store information management system is
using client server platform. The users for using this system are manager, cashier,
purchaser and adrnin .Below is described about the role of each user.
Manager
This system let the manager view the fmal report according to sales,
purchase and the other.
This system let manager can restore the database.
Cashier
This system let the cashier operate point-of-sale in the shop.
This system let the cashier finding the product's information for the
customer.
JUDUL: PARKSON BOOK STORE INFORMATION MANAGEMENT SYSTEM
SESI PENGAJIAN: 200912010
Saya YU KAI LING
mengaku membenarkan tesis (PSMlSarjana/Doktor Falsafah) ini disimpan di
Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dengan syarat-syarat
kegunaan seperti berikut:
1. Tesis dan projek adalah hakrnilik Universiti Teknikal Malaysia Melaka.
2. Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dibenarkan
membuat salinan untuk tujuan pengajian sahaja.
3. Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dibenarkan
membuat salinan tesis ini sebagai bahan pertukaran antara institusi pengajian
tinggi.
4. * * Sila tandakan (/)
/
SULIT
(Mengandungi
maklumat
yang
berdarjah keselamatan atau kepentingan
Malaysia seperti yang termaktub di
dalam AKTA RAHSIA RASMI 1972)
TERHAD
(Mengandungi maklumat TERHAD
yang
telah
ditentukan
oleh
organisasilbadan di mana penyelidikan
dijalankan)
TIDAK TERHAD
I\
(TANDATANGAN PENULIS)
Alarnat tetap: Lot 4417 Jalan Taman
King Lee Green Wood Park ,98000
Miri Sarawak
Tarikh: ~ t \ b \ @ [ '
(TANDATAN~AN
PENYELIA)
~ n & g f & & & @ ~ ~
Pensyarah
Jabatan Kejunrteraan t w i n
FakuRi Teknobgi Maklumat Dan K m i k a s i
MeMa
8
CATATAN: * Tesis dimaksudkan sebagai Laporan Akhir Projek Sarjana Muda
(PSM)
* * Jika Tesis ini SULIT atau TERHAD, sila lampirkan surat
daripada pihak berkuasa.
PARKSON BOOK STORE INFORMATION MANAGEMRNT SYSTEM
YU KAI LING
This report is submitted in partial fulfillment of the requirements for the
Bachelor of Computer Science (Database)
FACULTY OF INFORMATION AND COMMUNICATION TECHNOLOGY
UNIVERSITI TEKNIKAL MALAYSIA MELAKA
2010
DECLARATION
I hereby declare that this project report entitled
PARKSON BOOK STORE INFORMATION MANAGEMENT SYSTEM
is written by me and is my own effort and that no part has been plagiarized
without citations
STUDENT
/%
(YU %I LING)
I
SUPERVISOR
Jabatan Kejurutsraan Periskn
Fakrrlti Teknologi MakiurnaPDan Komunikasi
Universiti T*knikal Maleysia Melaka
Date:
~
( ("Iob
DEDICATION
To my beloved parents who always encourage me
YU YOUNG PUNG
TING A1 MEE
ACKNOWLEDGEMENTS
First, I need thank my advisor Puan Kasturi Kanchyrnalay, for her continuous support in
this subject. Puan Kasturi Kanchmalay was always there to listen and to give advice. She
showed me different ways to approach a research problem and the need of persistent in
achieving my goals. I would like to point out her unusual effort and patient in guiding
me for this project. Thank you very much.
At the same time, I would like to thank my beloved parents, who have been giving
support and motivation throughout my project. So let me don't have too much stress to
do this project. Besides this I also have to thank the ftmk's lab willing borrow me
barcode scanner to implement my project so i can finish my system. Lastly, also thank to
peter yong guang da for the ideas and insightful comments for my project throughout the
entire semester.
ABSTRACT
From this report, we will know this system more focusing in the day to day
transaction and stock controlling. This system got the a lot of multipurpose function like
generate the report, mapping checking, stock reminder, purchase order and other. Apart
from this, we also can compare to other related system or article in literature review to
improve this system. On .the other hand, we also can know the how the problem is
happen and from this problem statement we can make a complete solution to improve
for this inventory system. Design is a chapter that we can let the user to see our system
interface in graphic user interface (GUI) with nice view. From this chapter we also know
the flow chat and system structure diagram for the running flow and algorithm for this
whole system. How to link the database table for each related table to generate every
function and other internal design as well. Finally, we can say that, this system will
bring the user a lot of function to make the daily task became easily, flexible and also
systematic.
ABSTRAK
Dari laporan ini, kita akan mengetahui sistem in. lebih fokus dalam hari ke hari
transaksi dan barangan pengendali. Sistem ini punya banyak fimgsi serbaguna seperti
menghasilkan laporan, pemetaan menyemak,barangan peringatan, tempahan pembelian
dan lain-1ain.Selain itu, kita juga boleh membandingkan sistem ini dengan sistem
berkaitan lain atau artikel dalam tinjauan literatur supaya boleh dapat idea untuk
memperbaiki sistem ini. Di sisi lain, kita akan dapat mengetahui masalah yang dihadap
dan kita akan membuat penyelesaian lengkap untuk meningkatkan sistem ini.Design
merupakan sebuah bab yang kita boleh membiarkan pengguna untuk melihat antara
muka sistem kami dalarn antara muka pengguna grafik (GUI) dengan tampilan yang
bagus. Dari bab ini, kami juga tahu aliran chat dan diagram sistem struktur untuk
keseluruhan sistem. Akhirnya, kita dapat mengatakan bahawa, sistem ini akan membawa
pengguna lebih banyak fungsi untuk membuat tugas sehari-hari menjadi mudah,
fleksibel dan juga sistematik.
TABLE OF CONTENTS
CHAPTER
CHAPTER I
SUBJECT
PAGE
DECLARATION
ii
DEDICATION
iii
ACKNOWLEDGEMENT
iv
ABSTRACT
v
ABSTRAK
vi
TABLE OF CONTENTS
vii
LIST OF TABLES
xiii
LIST OF FIGURES
xiv
LIST OF ABBRREVIATONS
xix
LIST OF APPENDICES
XX
INTRODUCTION
1.1
Project Background
1.2
Problem Statement
1.3
Objective
CHAPTER
CHAPTER I1
PAGE
SUaTECT
1.4
Scope
1.5
Project significance
1.6
Expected Output
1.7
Conclusion
LITERATURE REVIEW
AND PROJECT METHODOLOGY
2.1
Introduction
2.2
Facts and findings
2.2.1
Domain
2.2.1.1
Book Store
information
management
system definition
2.2.2
2.2.1.2
Barcode
2.2.1.3
Barcodescanner
Existing System
2.2.2.1
Case Study 1:
CDP BOOK
SYSTEMS
2.2.2.2
Case Study 2:
ABEBOOKS
HOMEBASE
SYSTEM
2.3
Project Methodology
CHAPTER
SUBJECT
2.4
CHAPTER 111
PAGE
2.3.1
Requirement Analysis
2.3.2
Design
2.3.3
Implementation
2.3.4
Verification
2.3.5
Maintenance
Project Requirement
2.4.1
Software Requirement
2.4.2
Hardware Requirement
2.5
Project Schedule and Milestone
2.6
Conclusion
ANALYSIS
3.1
Introduction
3.2
Problem analysis
3.3
3.2.1
Current system
3.2.2
Problem Statement
Requirement analysis
3.3.1
Data Requirement
3.3.2
Functional Requirement
3.3.3
Non-functional Requirement
3.3.4
Other Requirement
3.3.4.1 Software Requirement
3.3.4.2 Hardware Requirement
3.4 Conclusion
CHAPTER
SUBJECT
CHAPTER IV
DESIGN
PAGE
4.1
Introduction
4.2
High-Level Design
4.2.1
System Architecture
4.2.2
User Interface Design
4.2.2.1
Navigation
Design
4.2.3
4.2.2.2
Input design
4.2.2.3
Output Design
Conceptual and Logical
Design
4.3
4.4
CHAPTER V
4.2.3.2
Business Rule
4.2.3.3
Data Dictionary
4.2.3.4
Normalization
4.2.3.5
DBMS Selection
Detail Design
4.3.1
Software Design
4.3.2
Physical database design
Conclusion
DESIGN
5.1 Introduction
5.2 Development
Environment setup
5.3
Database Implementation
CHAPTER
SUBJECT
PAGE
5.4
94
Software Configuration
Management
5.4.1
Configuration
94
environment setup
Version Control Procedure
5.4.2
CHAPTER VI
5.5
Implementation Status
98
5.6
Conclusion
106
TESTING
6.1
Introduction
6.2
Test Plan
6.3
6.2.1
Test Organization
6.2.2
Test Environment
6.2.3
Test Schedule
Test Strategy
6.3.1
6.4
CHAPTER VII
97
Classes of tests
Test Design
6.4.1
Test Description
6.4.2
Test Data
6.5
Test Result and Analysis
6.6
Conclusion
PROJECT CONCLUSION
7.1
Observation on weakness and strengths
115
CHAPTER
SUaTECT
PAGE
7.2
Propositions for Improvement
116
7.3
Contribution
117
7.4
Conclusion
117
REFERENCES
BIBLIOGRAPHY
LIST OF TABLES
TABLE
TITLE
Comparison two case studies
Hardware Requirement
Output design for whole system
List of Procedure and control
Implementation Status for modules
Test Organization
Test Schedule
PAGE
LIST OF FIGURES
FIGURE
TITLE
Barcode
Barcode Scanner
Waterfall model
Current system's
context diagram
Current system's DFD
Current system's DFD Level 1
for manage point of sales
and print receipt
Current system's DFD levels 21
for recording sales item
and daily sales report
Current system's DFD levels 21
for manage reorder
Current system's DFD levels 1
for update product's quantity
PAGES
FIGURE
TITLE
PAGES
Parkson book store information
27
management system's
context diagram
PBSMS's Data flow diagram
Two-tier architecture view
Navigation Design
Email received by manager
The content for email
Download the new purchase
Order attachment
Purchase Order
Output for line graph
Output for bar graph
Output for carta pie graph
ERD Diagram
Create database
FIGURE
4.12
TITLE
Selecting the operation that
will be performed
Selecting the database template
Named the Database Name
Selecting the mode to be operated
Selecting the initialization parameters
Description for database Storage
Creation option
Progress of database creation
Entering the password
for user sys and system
Login Page for login the oracle database
Success login, this is main page
for oracle database.
Error Message
Command Prompt for backup
PAGES
65
xvii
FIGURE
TITLE
PAGES
4.26
Load the backup command
78
4.27
Locate the backup file at local d
79
4.28
Type Recover command at
80
command Prompt
Load Recover command
Client server diagram
LAN Area
Login Interface for restring
and sorting Data
Supplier interface for restring
and sorting Data
Top Popular sales product for Restring
and Sorting Data
Product quantity interface for
join tables
Mapping Product interface for
aggregate function
Point Of Sales Interface for
aggregate function
FIGURE
TITLE
PAGES
5.9
Sales report interface for
92
aggregate function
Category Interface for
Update, Insert Function
Server Explore
Choose Data Source
Add Connection
Success Messages for
test connection
Unsuccess Messages for
text connection
LIST OF ABBRREVIATONS
ERD
-
Entity relationship diagrams
DFD
-
Data flow diagram
PBSMS
-
Parkson book store management system
LAN
-
Local area network
WLAN
-
Wireless local area network
LIST OF ATTACHMENTS
ATTACHMENTS
PAGE
APPENDIX A
MILESTONE
APPENDIX B
BUSINESS PROCESSING'S
APPENDIX C
PARKSON BOOK STORE
MANAGEMENT INFORMATION
SYSTEM (PBSM) DFD LEVEL 1
APPENDIX D
INTERFACE DESIGN
APPENDIX E
INPUT DESIGN
APPENDIX F
DATA DICTIONARY
APPENDIX G
NORMALIZATION
APPENDIX H
TEXT DESCRIPTION
APPENDIX I
TEXT DATA
APPENDIX J
TEXT RESULT
APPENDIX K
USER MANUAL
CHAPTER 1
INTRODUCTION
1.1 Project Background
Nowadays, more than 50% of the book store or book shop well still using with
traditionab'manual system to operate their business. Because of this problem, make a
lot of inconvenience for the owner and user to operate all the process with a good
systematic management. On this final year project, with title "Parkson Book Store
Information Management System" look well simple, but it will resolve the entire
problem as well to achieve the user goal as good as possible. Besides this, this
system will provide management system, to control the level of store in term of no
over stock or out of store situation been appear. On the other hand, this system wills
also having a fast search, update and other function as well as for each information.
Finally, we can find that this system is implementing with new technology hardware
with barcode scanner and also report generator. These two functions are to make
time consumption to the user besides than preparing purchase order (PO), searching,
key-in the data of each item and other as well as user-friendly for every user.
1.2 Problem Statement:
i)
Time Constraints - Previous system need a lot time to get item's
information.
ii)
Human Failure - Manual Inventory record will easily get wrong record
of quantity and information that item remains in the store. Because they
calculate manually.
iii)
Insufficiency in Service - The difficulty to finding stock location is very
challenge. This is because too much product is kept in the store and the
space of the store is large enough.
iv)
Security Problem - Lacks of security measurable, the information is
easily define by unauthorized persons
1.3 Objective
i)
Barcode scanner will be implementing for scan the item's code to quickly
retrieve the item's information and reduce worker's load and time
management.
ii)
This system wills implement auto controIling the stock can precise
calculate quantity remain stock .it generate report about product quantity
can let the purchaser making decision for reorder items
iii)
This system will provide mapping and actual location for particular stock
in a store of the shop.
iv)
Security policy and limitation of privilege in diffaent level of authorizers
will be implementing to make the system more secure.
1.4 Scope
The Platform for this Parkson book store information management system is
using client server platform. The users for using this system are manager, cashier,
purchaser and adrnin .Below is described about the role of each user.
Manager
This system let the manager view the fmal report according to sales,
purchase and the other.
This system let manager can restore the database.
Cashier
This system let the cashier operate point-of-sale in the shop.
This system let the cashier finding the product's information for the
customer.