Infineon Digital Library - Cataloging (IDLC).
BORANG PENGESAHAN STATUS TESIS*
JUDUL: _________
In_fi_•_n_eo_n__ｄ｟ｩ］ｾＭｴ｡ｬｌ｢ｲｹﾷｃｯｮ
SESI PENGAJIAN: 2011/ 20 12
Saya LEE KlAN SENG
mengaku membenarkan tesis Projek Sarjana Muda ini disimpan di Perpustakaan
Fakulti Teknologi Maklumat dan Komunikasi dengan syarat-syarat kegunaan seperti
berikut:
1. Tesis dan projek adalah hakmilik 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
ＨｔａｎｄｾﾷｐｅｙｌｉＩ＠
(TANDATANGAN PENULIS)
Alamat tetap: N G
(,,..,4..,
lJe'li?!.
17 ,
Ant#...
ｫｴＧ
ｳ ｾ ＢＧ Ｎ｟＠
1
＿ｊｴｓｏｾ＠
PｦＮ＿ ｵ ｾ＠ ｾＢ＠
1I
ＡＮｾＧｬｦ
(f
ｾｨ＠
ｾｍ＠
Nama Penyelia
Ｌ＠
ｐｾｲｱｫ＠
Tarikh:
CATATAN:
Tarikh:
* Tesis dimaksudkan sebagai Laporan Projek Sarjana Muda (PSM).
** Jika tesis ini SULIT atau atau TERHAD, sila lampirkan surat
daripada pihak berkuasa.
© Universiti Teknikal Malaysia Melaka
11
DECLARATION
I hereby declare that this project report entitled
Infineon Digital Library - Cataloging
(IDLC)
is written by me and is my own effort and that no part has been plagiarized
without citations.
STUDENT
Date:
(LEE ｋｉａｾＬ＠
Date: 00 ｾ＠
SUPERVISOR
(PUAN EMALIANA BINTI KASMURI)
© Universiti Teknikal Malaysia Melaka
ｾ＠
'l..
lll
DEDICATION
This thesis is dedicated to my beloved parents. Without your patience,
understanding and support, the completion of this thesis would not have been
possible.
To my
supervisor,
Puan Emaliana binti
Kasmuri,
your
recommendations and comments has truiy been my source of inspiration in
completing this project. Also, a special thank is given to UTeM library staffs
for kindly providing useful information during interview.
© Universiti Teknikal Malaysia Melaka
lV
ACKNOWLEDGEMENTS
First and foremost, I would like to give my special thank to my helpful
supervisor, Puan Emaliana binti Kasmuri for giving assistance to me in completing
this project. The supervision and support that he gave me truly help the progression
and smoothness of the project development.
Last but not least, I would like to thank to my beloved parents, family and
friends for giving me support, motivation and confidence to complete this project.
© Universiti Teknikal Malaysia Melaka
v
ABSTRACT
Infineon Digital Library - Cataloging is a system that is developed specially
for Infineon, a semi conductor manufacturing factory located at Batu Berendam,
Melaka, Malaysia. The company is currently looking for an online based system that
will be applied to manage its library. The main objective why Infineon is looking for
an online based library is to replace the manual process of managing its library.
Therefore, Infineon Digital Library - Cataloging is developed according to Infineon
requirement to overcome the problems faced by Infmeon.
This report consists of seven chapters describing the project development
process. Chapter I will briefly introduce the background, objective and scope of this
project. Chapter II will describe the facts and findings regarding this project and the
project methodology used. The requirements analysis of the project will be discussed
in Chapter III while chapter IV presents the design of the project including
architectural design, database design and user interface design. Chapter V focus on
the implementation phase such as software configuration management, version
control procedure and implementation status. Chapter VI shows how the testing is
prepared and conducted. Finally, chapter VII will conclude all the project
development processes and experiences.
© Universiti Teknikal Malaysia Melaka
Vl
ABSTRAK
Infineon Digital Library -
Cataloging merupakan satu system yang
dibangunkan khasnya untuk Infineon, sebuah kilang pembuatan semi konduktor yang
berlokasi di Batu Berendam, Melaka. Syarikat ini sedang mancari satu system yang
dapat beroperasi di rangkaian internet untuk menggantikan system yang sedia ada di
mana proses pengurusan terlalu bergantung manusia.
Laporan in merangkumi tujuh bab tentang proses pembangunan sistem ini.
Bab I memperkenalkan latar belakang, objektif dan skop projek ini. Bab II akan
menerang penemuan dan kajian untul projek ini dan methodologi yang digunakan.
Analisa keperluan bagi projek ini akan dibincang dalam bab III manakala bab IV
akan menunjukkan rekaan projek termasuklan rekaan seni bina, rekaan pangkalan
data dan rekaan antaramuka bagi pengguna. Bab V bertumpu pada fasa perlaksaan
seperti pengurusan konfigurasi perisian, prosedur pengawalan versi dan status
perlaksaan. Bab VI menunjuk bagaimana ujian disedia dan dijalan. Akhir sekali, bab
VII akan menyedia kesimpulan untuk seluruh proses pembangunan and pengalaman
projek ini.
© Universiti Teknikal Malaysia Melaka
Vll
TABLE OF CONTENTS
CHAPTER
SUBJECT
PAGE
DECLARATION
II
DEDICATION
Ill
ACKNOWLEDGEMENTS
IV
ABSTRACT
v
ABSTRAK
VI
TABLE OF CONTENTS
LIST OF TABLES
LIST OF FIGURES
LIST OF ABBREVIATIONS
CHAPTER I INTRODUCTION
VII
X
XII
XIII
14
1.1 PROJECT BACKGROUND
14
1.2 PROBLEM STATEMENTS
15
1.3 OBJECTIVE
15
1.4SCOPE
16
1.5 PROJECT SIGNIFICANCE
18
1.6 CONCLUSION
19
CHAPTER II LITERATURE REVIEW AND PROJECT METHODOLOGY
20
2.1 INTRODUCTION
20
2.2 FACT AND FINDING
21
2.3 PROJECT METHODOLOGY
22
2.4 PROJECT REQUIREMENT
24
2.4.1 SOFTWARE REQUIREMENT
24
2.4.2 HARDWARE REQUIREMENT
25
© Universiti Teknikal Malaysia Melaka
Vlll
2.4.3 OTHER REQUIREMENT
25
2.5 PROJECT SCHEDULE AND MILESTONES
25
2.6 CONCLUSION
27
CHAPTER III ANALYSIS
28
3.1 INTRODUCTION
28
3.2 PROBLEM ANALYSIS
29
3.2.1 ANALYSIS OF CURRENT SYSTEM
29
3.2.1 FLOW OF CURRENT SYSTEM
29
3.2.2 PROBLEM OF CURRENT SYSTEM
33
3.3 REQUIREMENT ANALYSIS
34
3.3.1 BUSINESS RULES
34
3.3.2 USE CASE DIAGRAM
36
3.3.4 SYSTEM REQUIREMENTS
56
3.4 CONCLUSION
57
CHAPTER IV DESIGN
58
4.1 INTRODUCTION
58
4.2 HIGH LEVEL DESIGN
58
4.2.1 SYSTEM ARCHITECTURE
59
4.2.2 USER INTERFACE DESIGN
60
4.2.3 DATABASE DESIGN
64
4.4. CONCLUSION
87
CHAPTERV IMPLEMENTATION
88
5.1 INTRODUCTION
88
5.2 SOFTWARE DEVELOPMENT ENVIRONMENT SETUP
88
5.2.1 HARDWARE ARCHITECTURE
89
5.2.2 SOFTWARE ARCHITECTURE
89
5.3 SOFTWARE CONFIGURATION MANAGEMENT
90
5.3.1 CONFIGURATION ENVIRONMENT SETUP
90
5.3.2 VERSION CONTROL PROCEDURE
91
5.4 IMPLEMENTATION STATUS
91
© Universiti Teknikal Malaysia Melaka
IX
5.5 CONCLUSION
CHAPTER VI TESTING
93
94
6.1 INTRODUCTION
94
6.2 TEST PLAN
94
6.2.1 TEST ORGANIZATION
95
6.2.2 TEST ENVIRONMENT
95
6.2.3 TEST SCHEDULE
96
6.3 TEST STRATEGIES
97
6.3.1 TEST CLASSES OF TESTS
98
6.4 TEST DESIGN
98
6.4.1 TEST DESCRIPTION
98
6.4.2 TEST DATA
109
6.5 TEST RESULT AND ANALYSIS
110
6.6 CONCLUSION
112
CHAPTER VII PROJECT CONCLUSION
113
7.1 OBSERVATION ON WEAKNESS AND STRENGTH
113
7.1.1 STRENGTH
113
7 .1.2 WEAKNESS
114
7.2 PROPOSITIONS FOR IMPROVEMENT
114
7.3 CONTRIBUTION
114
7.4 CONCLUSION
115
REFERENCES & BIBLIOGRAPHY
116
APPENDICES
117
© Universiti Teknikal Malaysia Melaka
X
LIST OF TABLES
TABLE
TITLE
Table 1: Strength and weakness
Table 2: Software requirement
Table 3: Hardware requirement
Table 4: Project schedule and milestone
Table 5: Software requirement
Table 6: Hardware requirement
Table 7: Network requirement
Table 8: Input design
Table 9: Data dictionary of User
Table 10: Data dictionary of Library Material
Table 11: Data dictionary of Loan
Table 12: Data dictionary of Acquisition
Table 13: Data dictionary of AcqDiscussion
Table 14: Data dictionary of Favourite Material
Table 15: Data dictionary of ViewedMaterial
Table 16: Data dictionary of QueueList
Table 17: Data dictionary of Announcement
Table 18: Description of Class LoginDB
Table 19: Description of Class UserDB
Table 20: Description of Class CatalogDB
Table 21: Description of Class BrowseMateriaiDB
Table 22: Description of Class ReportDB
Table 23: User
Table 24: LibraryMaterial
Table 25: Loan
Table 26: Acquisition
Table 27: AcqDiscussion
Table 28: QueueList
Table 29: FavouriteMaterial
Table 30: ViewedMaterial
Table 31: Announcement
Table 32: Versions of product
© Universiti Teknikal Malaysia Melaka
PAGE
21
24
25
25
56
56
57
61
66
67
68
69
70
70
71
71
72
74
75
76
79
83
84
84
85
85
86
86
86
87
87
91
XI
Table 33: Implementation status
Table 34: Role and responsibilities of test organization
Table 35: Hardware configuration
Table 36: Software configuration
Table 37: Test schedule
Table 38: Login module test description
Table 39: CatalogingMaterial module test description
Table 40: TraceMaterial test description
Table 41: MateriaiBrowsing test description
Table 42: Report module
Table 43: Test Results
© Universiti Teknikal Malaysia Melaka
92
95
96
96
96
99
99
103
104
106
110
Xll
LIST OF FIGURES
FIGURE
TITLE
Figure 1: Use case diagram of the current system
Figure 2: Activity diagram of acquisition and cataloging
Figure 3: Activity diagram of loaning library material
Figure 4: Activity diagram of returning library material
Figure 5: Overall use case diagram
Figure 6: Use case diagram- Cataloging
Figure 7: Sequence diagram of Login
Figure 8: Sequence diagram of Browse Library Material
Figure 9: Sequence diagram of Reservation of Library Material
Figure 10: Sequence diagram of Trace Library Material
Figure 11: Sequence diagram of Catalog Material
Figure 12: Sequence diagram of Publish Material
Figure 13: Sequence diagram of View Report
Figure 14: System architecture of IDLC
Figure 15: Navigation design of IDLC
Figure 16: Output design of login page
Figure 17: output design of Home page
Figure 18: Output design of Library Material Browsing
Figure 19: Entity Relationship Diagram of IDLC
Figure 20: Class User
Figure 21: Class LibraryMaterial
Figure 22: Class LoginDB
Figure 23: Class UserDB
Figure 24: Class CatalogDB
Figure 25: Class BrowseMateriaiDB
Figure 26: Class ReportDB
Figure 27: Diagram of hardware environment architecture
Figure 28: Diagram of software environment architecture
Figure 29: Diagram of the sequence of installing the software
© Universiti Teknikal Malaysia Melaka
PAGE
29
30
31
32
36
37
49
50
51
52
53
54
55
59
60
62
63
64
65
73
73
74
75
76
78
83
89
89
90
Xlll
LIST OF ABBREVIATIONS
IDLC
UTeM
Infineon Digital Library - Cataloging
Universiti Teknikal Malaysia Melaka
© Universiti Teknikal Malaysia Melaka
14
CHAPTER I
INTRODUCTION
1.1 Project Background
Library - a large collection of books. Providing the information resources
that are most often in printing materials like books, journals, encyclopaedia and etc,
library is a place where people visit to obtain information and knowledge.
However, as the technologies keep improving, the culture that people make
library as their primary source of information will face or is facing challenge. There
is trend that people would like to access to information through digital library.
Digital library is collection of information resources in digital formats but is not a
new idea since decade ago. There are already organizations and universities
involving in digital library practice.
This project that develops a digital library is actually based on the existing
target user, Infmeon in Melaka. The target user is currently looking for a digital
library to be developed in the company in order to enhance functionality of the
existing library and overcome some limitations. Therefore, this project will be
developed to meet the requirements.
© Universiti Teknikal Malaysia Melaka
15
1.2 Problem Statements
1. Difficult to manage the materials of library
As the materials of library keep increasing and this is no systematic management,
it is hard to keep track and organize the materials.
2. Availability of materials in Infineon is limited to staffs
When there is no systematic management to trace the materials of library, the
availability of the materials become limited to the users' requests.
3. Lack of report functionalities
This make library management cannot obtain useful information and statistic to
be utilized to provide better service to user.
1.3 Objective
1. Cataloging the materials of library
By cataloging, each material contains its own descriptive information. Thus, the
materials of library can be managed and organized systematically. Also, users
can search for the information resources more easily.
2. Create digital storage for materials in digital formats
With the digital storage, multiple users can easily access to the materials m
digital formats via internet. The materials become more available to users.
3. Derive trend analysis from statistics about library users
Trend analysis can help library provide better service to meet users' needs. By
figuring out what are the materials most likely required by users, library can
make related materials available to users.
© Universiti Teknikal Malaysia Melaka
16
1.4 Scope
1.
User
a.
Staffs
Role: The lnfineon staff can browse digital library materials through login
to the system. Also, they can trace the library material to check if the
requested materials are available and make a booking for them.
b.
Librarians
Role: Librarians are mainly responsible to manage the library materials in
a proper manner so that the materials are available to users. For examples,
librarians need to catalog the materials.
c.
Administrators
Role: Administrators are responsible to maintain library to run operation
efficiently according to policies, rules and regulations.
2.
Module I Function
a.
Browsing Library Materials
Functions:
Staffs can browse the library materials for reading and downloading as
references usage through the digital library.
b.
Trace Library Materials
Functions:
Staffs can trace the availability of the library materials requested. The
staff can then make booking or reservation to the materials.
© Universiti Teknikal Malaysia Melaka
17
c.
Cataloging
Functions:
Based on a defined catalog by lnfineon, register each materials with
metadata (descriptive information of the materials) in order to manage
the materials systematically.
d.
Generate Report
Functions:
Gather the information about users of the digital library such as annual
total access to certain kind of material using direct SQL approach. This
can lead to trend analysis.
3.
4.
Software
a.
Operating system - Windows 7 Ultimate.
b.
Programming Language - Microsoft .Net 4.0
c.
Development Tools I IDE- MicrosoftVisual Studio 2008.
d.
Database- Microsoft SQL Server 2008.
e.
Star UML tool
f.
Mircosoft office Word 2007
Hardware
a. Computer
- Processor: Intel(R) Core(TM)2 Duo CPU T6500 @ 2.1 OGHz
-RAM: 4GB
- Hard Disk: 250 GB
Monitor Specification
- Screen Size: 15" TFT
- Screen Resolution: 1366 x 768
b. Barcode scanner
c. Printer
© Universiti Teknikal Malaysia Melaka
18
1.5 Project Significance
This project, Digital Library is developed based on the existing target user,
Infineon in Melaka. Infineon is looking for a digital library system to be
implemented in their organization. Therefore, the system will be developed to meet
requirements of Infineon to achieve their objectives.
Once the system is developed completely and implemented, the system will
provide convenience to staffs to browse library materials without being present at
library in personal. The staff can just access to the digital library system via internet
easily and this is a kind of time saving. This is a great solution to make the materials
more available to the users.
As the traditional library is still being maintained, the system will help
librarian manage the materials more efficiently especially during loan and return
process. The availability of each material can be kept track and this is helpful when
the users request for certain materials.
Also, the system helps the administrator of library obtain the useful
information about the digital library more easily. There are many useful information
can be derived from the statistics generated such as the total number of users access
to materials of a certain category. With this information, it can be helpful to provide
materials that are suitable to the favourites of users.
The advantages of the digital system are not limited to all these have been
mentioned. The target user, Infmeon at Melaka, is believed to greatly benefit from
the system.
© Universiti Teknikal Malaysia Melaka
19
1.6 Conclusion
By going through the background of the target users, the current problems
that they are facing are being understood more clearly. Then, objectives are listed out
to direct the development of the project. Also, scope and the significance of the
project have been discussed.
The next activities to be developed will be the selection of methodology in
developing the system, identifying the project requirement, and the project milestone.
© Universiti Teknikal Malaysia Melaka
20
CHAPTER II
LITERATURE REVIEW AND PROJECT METHODOLOGY
2.1 Introduction
This chapter is about the literature review of digital library and the project
methodology to be applied.
Literature reviews are secondary sources that bring the reader up to date with
current literature on a topic and form the basis for the next goal. Literature review is
considered as a summary and synopsis of a particular area of research. "It is not a
collection of quotes and paraphrasing from other sources. A good literature review
should also have some evaluation of the quality and findings of the research."
(Martyn Shuttleworth, 2009)
Project Methodology is about the approach selected to develop the project or
system. All the stages and steps of managing the project development towards
completion will be described.
Also, this chapter will list out the hardware requirement and software
requirement and other requirement to develop the project.
Finally, project schedule or milestone will be generated in tabular form. The
activities and workflow together with timeline will be discussed. The project will be
developed by following the schedule planned.
© Universiti Teknikal Malaysia Melaka
21
2.2 Fact and Finding
2.2.1 Domain
The domain of this project is library and information science. This project is
specified to digital library and it concerns the management of both physical and
digital library of the target user. Domain knowledge of managing library is important
and needed to develop the system. All the workflow, process and procedure of how
standard library operates are as guideline and reference for this project. In this
project, target user has an existing physical library and it will be served as main
model when developing the digital library system.
2.2.2 Existing System
There is currently only a physical library system from target user. In fact,
there are existing digital library systems. Some of the systems are university-based
which limit the access from public.
For example, there are two existing channels, e-Resources offered by UTeM
to allow all UTeM students and staffs to access electronic resources provided. The
resources are provided from two main sources, subscribed from third parties and
original resource from UTeM.
Table 1: Strength and weakness
Strengths
Provides free access to information
resource from certain subscribed source
Provide multiple access to resource
simply via internet
Weakness
Access to few creditable source
provided, but access to content of
resource requires payment
Categories are not well defined, lead to
confusion
Resource belong to UTeM e.g. Thesis is
only available at physical library within
campus
There is some similarity between the existing system and to-be system.
However, the existing system can only be a reference and the to-be system has to be
tailored according the requirement of the target user.
© Universiti Teknikal Malaysia Melaka
22
2.2.3 Technique
The technique that was used to collect the information about how library
operate was interview. An interview was conducted with the librarians and
department officers at UTeM library. The information obtained was so useful to have
overview of the workflow of library.
2.3 Project Methodology
The chosen methodology is Object-Oriented Analysis and Design (OOAD)
which is industry-proven methodology for developing high-quality object-oriented
systems. This methodology involves three aspects: object-oriented analysis (OOA),
which analyze the functional requirement for a system, object-oriented design
(OOD), which translates a system architecture into programming constructs (such as
interfaces, classes, and method descriptions); and object-oriented programming
(OOP), which implements these programming constructs.
Object-oriented analysis and design methodology models a system as a group
of interacting objects. In other words, it is about object decomposition, breaking the
complex software system down into manageable objects. OOAD methodology helps
producing flexible, modifiable, easily maintainable object-oriented systems. Besides,
this methodology focuses on the concept of reusability which greatly saves cost
during implementation.
Rational Unified Process (RUP) is an iterative and incremental software
development process framework that applies OOAD approach. RUP has determined
four phases of a project life cycle that are inception phase, elaboration phase,
construction phase and transition phase. In iterative approach, each phase will go
through the activities of system development life cycle (requirements, analysis,
design, implementation, and testing). In incremental approach, the effort in each
phase will be incremented to next following phase and finally end with one huge
effort as a whole.
© Universiti Teknikal Malaysia Melaka
23
a) Iterative phase:
In requirement stage, the activities will be carried out to gather and
understand the requirement of the digital library system. The requirement
specifications have to be established at this stage via various appropriate
techniques such as interview with the relevant parties.
In analysis stage, the requirement gathered from previous stage will
be analyzed and refined. It is required to identify and clarify the functional
requirement, non-functional requirement and other requirement for the
system development.
In design stage, the functional requirement and non-functional
requirement will be finalized. Also, programming language, developing tools,
platform and other requirement will be determined. The architecture and
design of the system will be produced according to requirement for next
stage.
In implementation stage, the system will be implemented based on the
architecture and design has been produced from previous stage.
In testing stage, the main objective is to verify if the system developed
meet or fulfil the requirement as agreement of developers and client. The
testing will be conducted from various aspects via different methods to
confirm client satisfaction.
b) Incremental phase:
In inception phase, requirement stage activities are carried out to
collect requirement. Then analysis and design phase may start. The
implementation is limited due to lack of sufficient and finalized information.
In elaboration phase, the initial requirement will be refined. Analysis
and design become complete with the aid of Unified Modelling Language
© Universiti Teknikal Malaysia Melaka
24
(UML) model. Various diagrams generated through UML model such as use
diagram, sequence diagram, class diagram and so on will be used for the
development that take place soon. At this phase, prototype will be good idea
to verify the understanding established about requirement.
In construction phase, it is the period where the implementation of
system begins properly based on the requirement, specification and design
that have been decided. There will also be iteration of testing process taking
place to ensure the development follow requirement.
In transition phase, the system will be verified if it has fulfilled the
requirement as stated following the agreement of both developer and client. If
the system achieves the client satisfaction, then the system will be deployed
as the final deliverable to client.
2.4 Project Requirement
2.4.1 Software Requirement
Software Description
Specification
Operating System
Microsoft Windows 7
Programming Language
Microsoft .Net 4.0
Development Tools I IDE
Microsoft Visual Studio 2008
Database Management
Microsoft SQL Server 2008
Unified Modelling Tool
Star UML tool
Project Document Tool
Microsoft Office Word 2007
Table 2: Software requirement
© Universiti Teknikal Malaysia Melaka
JUDUL: _________
In_fi_•_n_eo_n__ｄ｟ｩ］ｾＭｴ｡ｬｌ｢ｲｹﾷｃｯｮ
SESI PENGAJIAN: 2011/ 20 12
Saya LEE KlAN SENG
mengaku membenarkan tesis Projek Sarjana Muda ini disimpan di Perpustakaan
Fakulti Teknologi Maklumat dan Komunikasi dengan syarat-syarat kegunaan seperti
berikut:
1. Tesis dan projek adalah hakmilik 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
ＨｔａｎｄｾﾷｐｅｙｌｉＩ＠
(TANDATANGAN PENULIS)
Alamat tetap: N G
(,,..,4..,
lJe'li?!.
17 ,
Ant#...
ｫｴＧ
ｳ ｾ ＢＧ Ｎ｟＠
1
＿ｊｴｓｏｾ＠
PｦＮ＿ ｵ ｾ＠ ｾＢ＠
1I
ＡＮｾＧｬｦ
(f
ｾｨ＠
ｾｍ＠
Nama Penyelia
Ｌ＠
ｐｾｲｱｫ＠
Tarikh:
CATATAN:
Tarikh:
* Tesis dimaksudkan sebagai Laporan Projek Sarjana Muda (PSM).
** Jika tesis ini SULIT atau atau TERHAD, sila lampirkan surat
daripada pihak berkuasa.
© Universiti Teknikal Malaysia Melaka
11
DECLARATION
I hereby declare that this project report entitled
Infineon Digital Library - Cataloging
(IDLC)
is written by me and is my own effort and that no part has been plagiarized
without citations.
STUDENT
Date:
(LEE ｋｉａｾＬ＠
Date: 00 ｾ＠
SUPERVISOR
(PUAN EMALIANA BINTI KASMURI)
© Universiti Teknikal Malaysia Melaka
ｾ＠
'l..
lll
DEDICATION
This thesis is dedicated to my beloved parents. Without your patience,
understanding and support, the completion of this thesis would not have been
possible.
To my
supervisor,
Puan Emaliana binti
Kasmuri,
your
recommendations and comments has truiy been my source of inspiration in
completing this project. Also, a special thank is given to UTeM library staffs
for kindly providing useful information during interview.
© Universiti Teknikal Malaysia Melaka
lV
ACKNOWLEDGEMENTS
First and foremost, I would like to give my special thank to my helpful
supervisor, Puan Emaliana binti Kasmuri for giving assistance to me in completing
this project. The supervision and support that he gave me truly help the progression
and smoothness of the project development.
Last but not least, I would like to thank to my beloved parents, family and
friends for giving me support, motivation and confidence to complete this project.
© Universiti Teknikal Malaysia Melaka
v
ABSTRACT
Infineon Digital Library - Cataloging is a system that is developed specially
for Infineon, a semi conductor manufacturing factory located at Batu Berendam,
Melaka, Malaysia. The company is currently looking for an online based system that
will be applied to manage its library. The main objective why Infineon is looking for
an online based library is to replace the manual process of managing its library.
Therefore, Infineon Digital Library - Cataloging is developed according to Infineon
requirement to overcome the problems faced by Infmeon.
This report consists of seven chapters describing the project development
process. Chapter I will briefly introduce the background, objective and scope of this
project. Chapter II will describe the facts and findings regarding this project and the
project methodology used. The requirements analysis of the project will be discussed
in Chapter III while chapter IV presents the design of the project including
architectural design, database design and user interface design. Chapter V focus on
the implementation phase such as software configuration management, version
control procedure and implementation status. Chapter VI shows how the testing is
prepared and conducted. Finally, chapter VII will conclude all the project
development processes and experiences.
© Universiti Teknikal Malaysia Melaka
Vl
ABSTRAK
Infineon Digital Library -
Cataloging merupakan satu system yang
dibangunkan khasnya untuk Infineon, sebuah kilang pembuatan semi konduktor yang
berlokasi di Batu Berendam, Melaka. Syarikat ini sedang mancari satu system yang
dapat beroperasi di rangkaian internet untuk menggantikan system yang sedia ada di
mana proses pengurusan terlalu bergantung manusia.
Laporan in merangkumi tujuh bab tentang proses pembangunan sistem ini.
Bab I memperkenalkan latar belakang, objektif dan skop projek ini. Bab II akan
menerang penemuan dan kajian untul projek ini dan methodologi yang digunakan.
Analisa keperluan bagi projek ini akan dibincang dalam bab III manakala bab IV
akan menunjukkan rekaan projek termasuklan rekaan seni bina, rekaan pangkalan
data dan rekaan antaramuka bagi pengguna. Bab V bertumpu pada fasa perlaksaan
seperti pengurusan konfigurasi perisian, prosedur pengawalan versi dan status
perlaksaan. Bab VI menunjuk bagaimana ujian disedia dan dijalan. Akhir sekali, bab
VII akan menyedia kesimpulan untuk seluruh proses pembangunan and pengalaman
projek ini.
© Universiti Teknikal Malaysia Melaka
Vll
TABLE OF CONTENTS
CHAPTER
SUBJECT
PAGE
DECLARATION
II
DEDICATION
Ill
ACKNOWLEDGEMENTS
IV
ABSTRACT
v
ABSTRAK
VI
TABLE OF CONTENTS
LIST OF TABLES
LIST OF FIGURES
LIST OF ABBREVIATIONS
CHAPTER I INTRODUCTION
VII
X
XII
XIII
14
1.1 PROJECT BACKGROUND
14
1.2 PROBLEM STATEMENTS
15
1.3 OBJECTIVE
15
1.4SCOPE
16
1.5 PROJECT SIGNIFICANCE
18
1.6 CONCLUSION
19
CHAPTER II LITERATURE REVIEW AND PROJECT METHODOLOGY
20
2.1 INTRODUCTION
20
2.2 FACT AND FINDING
21
2.3 PROJECT METHODOLOGY
22
2.4 PROJECT REQUIREMENT
24
2.4.1 SOFTWARE REQUIREMENT
24
2.4.2 HARDWARE REQUIREMENT
25
© Universiti Teknikal Malaysia Melaka
Vlll
2.4.3 OTHER REQUIREMENT
25
2.5 PROJECT SCHEDULE AND MILESTONES
25
2.6 CONCLUSION
27
CHAPTER III ANALYSIS
28
3.1 INTRODUCTION
28
3.2 PROBLEM ANALYSIS
29
3.2.1 ANALYSIS OF CURRENT SYSTEM
29
3.2.1 FLOW OF CURRENT SYSTEM
29
3.2.2 PROBLEM OF CURRENT SYSTEM
33
3.3 REQUIREMENT ANALYSIS
34
3.3.1 BUSINESS RULES
34
3.3.2 USE CASE DIAGRAM
36
3.3.4 SYSTEM REQUIREMENTS
56
3.4 CONCLUSION
57
CHAPTER IV DESIGN
58
4.1 INTRODUCTION
58
4.2 HIGH LEVEL DESIGN
58
4.2.1 SYSTEM ARCHITECTURE
59
4.2.2 USER INTERFACE DESIGN
60
4.2.3 DATABASE DESIGN
64
4.4. CONCLUSION
87
CHAPTERV IMPLEMENTATION
88
5.1 INTRODUCTION
88
5.2 SOFTWARE DEVELOPMENT ENVIRONMENT SETUP
88
5.2.1 HARDWARE ARCHITECTURE
89
5.2.2 SOFTWARE ARCHITECTURE
89
5.3 SOFTWARE CONFIGURATION MANAGEMENT
90
5.3.1 CONFIGURATION ENVIRONMENT SETUP
90
5.3.2 VERSION CONTROL PROCEDURE
91
5.4 IMPLEMENTATION STATUS
91
© Universiti Teknikal Malaysia Melaka
IX
5.5 CONCLUSION
CHAPTER VI TESTING
93
94
6.1 INTRODUCTION
94
6.2 TEST PLAN
94
6.2.1 TEST ORGANIZATION
95
6.2.2 TEST ENVIRONMENT
95
6.2.3 TEST SCHEDULE
96
6.3 TEST STRATEGIES
97
6.3.1 TEST CLASSES OF TESTS
98
6.4 TEST DESIGN
98
6.4.1 TEST DESCRIPTION
98
6.4.2 TEST DATA
109
6.5 TEST RESULT AND ANALYSIS
110
6.6 CONCLUSION
112
CHAPTER VII PROJECT CONCLUSION
113
7.1 OBSERVATION ON WEAKNESS AND STRENGTH
113
7.1.1 STRENGTH
113
7 .1.2 WEAKNESS
114
7.2 PROPOSITIONS FOR IMPROVEMENT
114
7.3 CONTRIBUTION
114
7.4 CONCLUSION
115
REFERENCES & BIBLIOGRAPHY
116
APPENDICES
117
© Universiti Teknikal Malaysia Melaka
X
LIST OF TABLES
TABLE
TITLE
Table 1: Strength and weakness
Table 2: Software requirement
Table 3: Hardware requirement
Table 4: Project schedule and milestone
Table 5: Software requirement
Table 6: Hardware requirement
Table 7: Network requirement
Table 8: Input design
Table 9: Data dictionary of User
Table 10: Data dictionary of Library Material
Table 11: Data dictionary of Loan
Table 12: Data dictionary of Acquisition
Table 13: Data dictionary of AcqDiscussion
Table 14: Data dictionary of Favourite Material
Table 15: Data dictionary of ViewedMaterial
Table 16: Data dictionary of QueueList
Table 17: Data dictionary of Announcement
Table 18: Description of Class LoginDB
Table 19: Description of Class UserDB
Table 20: Description of Class CatalogDB
Table 21: Description of Class BrowseMateriaiDB
Table 22: Description of Class ReportDB
Table 23: User
Table 24: LibraryMaterial
Table 25: Loan
Table 26: Acquisition
Table 27: AcqDiscussion
Table 28: QueueList
Table 29: FavouriteMaterial
Table 30: ViewedMaterial
Table 31: Announcement
Table 32: Versions of product
© Universiti Teknikal Malaysia Melaka
PAGE
21
24
25
25
56
56
57
61
66
67
68
69
70
70
71
71
72
74
75
76
79
83
84
84
85
85
86
86
86
87
87
91
XI
Table 33: Implementation status
Table 34: Role and responsibilities of test organization
Table 35: Hardware configuration
Table 36: Software configuration
Table 37: Test schedule
Table 38: Login module test description
Table 39: CatalogingMaterial module test description
Table 40: TraceMaterial test description
Table 41: MateriaiBrowsing test description
Table 42: Report module
Table 43: Test Results
© Universiti Teknikal Malaysia Melaka
92
95
96
96
96
99
99
103
104
106
110
Xll
LIST OF FIGURES
FIGURE
TITLE
Figure 1: Use case diagram of the current system
Figure 2: Activity diagram of acquisition and cataloging
Figure 3: Activity diagram of loaning library material
Figure 4: Activity diagram of returning library material
Figure 5: Overall use case diagram
Figure 6: Use case diagram- Cataloging
Figure 7: Sequence diagram of Login
Figure 8: Sequence diagram of Browse Library Material
Figure 9: Sequence diagram of Reservation of Library Material
Figure 10: Sequence diagram of Trace Library Material
Figure 11: Sequence diagram of Catalog Material
Figure 12: Sequence diagram of Publish Material
Figure 13: Sequence diagram of View Report
Figure 14: System architecture of IDLC
Figure 15: Navigation design of IDLC
Figure 16: Output design of login page
Figure 17: output design of Home page
Figure 18: Output design of Library Material Browsing
Figure 19: Entity Relationship Diagram of IDLC
Figure 20: Class User
Figure 21: Class LibraryMaterial
Figure 22: Class LoginDB
Figure 23: Class UserDB
Figure 24: Class CatalogDB
Figure 25: Class BrowseMateriaiDB
Figure 26: Class ReportDB
Figure 27: Diagram of hardware environment architecture
Figure 28: Diagram of software environment architecture
Figure 29: Diagram of the sequence of installing the software
© Universiti Teknikal Malaysia Melaka
PAGE
29
30
31
32
36
37
49
50
51
52
53
54
55
59
60
62
63
64
65
73
73
74
75
76
78
83
89
89
90
Xlll
LIST OF ABBREVIATIONS
IDLC
UTeM
Infineon Digital Library - Cataloging
Universiti Teknikal Malaysia Melaka
© Universiti Teknikal Malaysia Melaka
14
CHAPTER I
INTRODUCTION
1.1 Project Background
Library - a large collection of books. Providing the information resources
that are most often in printing materials like books, journals, encyclopaedia and etc,
library is a place where people visit to obtain information and knowledge.
However, as the technologies keep improving, the culture that people make
library as their primary source of information will face or is facing challenge. There
is trend that people would like to access to information through digital library.
Digital library is collection of information resources in digital formats but is not a
new idea since decade ago. There are already organizations and universities
involving in digital library practice.
This project that develops a digital library is actually based on the existing
target user, Infmeon in Melaka. The target user is currently looking for a digital
library to be developed in the company in order to enhance functionality of the
existing library and overcome some limitations. Therefore, this project will be
developed to meet the requirements.
© Universiti Teknikal Malaysia Melaka
15
1.2 Problem Statements
1. Difficult to manage the materials of library
As the materials of library keep increasing and this is no systematic management,
it is hard to keep track and organize the materials.
2. Availability of materials in Infineon is limited to staffs
When there is no systematic management to trace the materials of library, the
availability of the materials become limited to the users' requests.
3. Lack of report functionalities
This make library management cannot obtain useful information and statistic to
be utilized to provide better service to user.
1.3 Objective
1. Cataloging the materials of library
By cataloging, each material contains its own descriptive information. Thus, the
materials of library can be managed and organized systematically. Also, users
can search for the information resources more easily.
2. Create digital storage for materials in digital formats
With the digital storage, multiple users can easily access to the materials m
digital formats via internet. The materials become more available to users.
3. Derive trend analysis from statistics about library users
Trend analysis can help library provide better service to meet users' needs. By
figuring out what are the materials most likely required by users, library can
make related materials available to users.
© Universiti Teknikal Malaysia Melaka
16
1.4 Scope
1.
User
a.
Staffs
Role: The lnfineon staff can browse digital library materials through login
to the system. Also, they can trace the library material to check if the
requested materials are available and make a booking for them.
b.
Librarians
Role: Librarians are mainly responsible to manage the library materials in
a proper manner so that the materials are available to users. For examples,
librarians need to catalog the materials.
c.
Administrators
Role: Administrators are responsible to maintain library to run operation
efficiently according to policies, rules and regulations.
2.
Module I Function
a.
Browsing Library Materials
Functions:
Staffs can browse the library materials for reading and downloading as
references usage through the digital library.
b.
Trace Library Materials
Functions:
Staffs can trace the availability of the library materials requested. The
staff can then make booking or reservation to the materials.
© Universiti Teknikal Malaysia Melaka
17
c.
Cataloging
Functions:
Based on a defined catalog by lnfineon, register each materials with
metadata (descriptive information of the materials) in order to manage
the materials systematically.
d.
Generate Report
Functions:
Gather the information about users of the digital library such as annual
total access to certain kind of material using direct SQL approach. This
can lead to trend analysis.
3.
4.
Software
a.
Operating system - Windows 7 Ultimate.
b.
Programming Language - Microsoft .Net 4.0
c.
Development Tools I IDE- MicrosoftVisual Studio 2008.
d.
Database- Microsoft SQL Server 2008.
e.
Star UML tool
f.
Mircosoft office Word 2007
Hardware
a. Computer
- Processor: Intel(R) Core(TM)2 Duo CPU T6500 @ 2.1 OGHz
-RAM: 4GB
- Hard Disk: 250 GB
Monitor Specification
- Screen Size: 15" TFT
- Screen Resolution: 1366 x 768
b. Barcode scanner
c. Printer
© Universiti Teknikal Malaysia Melaka
18
1.5 Project Significance
This project, Digital Library is developed based on the existing target user,
Infineon in Melaka. Infineon is looking for a digital library system to be
implemented in their organization. Therefore, the system will be developed to meet
requirements of Infineon to achieve their objectives.
Once the system is developed completely and implemented, the system will
provide convenience to staffs to browse library materials without being present at
library in personal. The staff can just access to the digital library system via internet
easily and this is a kind of time saving. This is a great solution to make the materials
more available to the users.
As the traditional library is still being maintained, the system will help
librarian manage the materials more efficiently especially during loan and return
process. The availability of each material can be kept track and this is helpful when
the users request for certain materials.
Also, the system helps the administrator of library obtain the useful
information about the digital library more easily. There are many useful information
can be derived from the statistics generated such as the total number of users access
to materials of a certain category. With this information, it can be helpful to provide
materials that are suitable to the favourites of users.
The advantages of the digital system are not limited to all these have been
mentioned. The target user, Infmeon at Melaka, is believed to greatly benefit from
the system.
© Universiti Teknikal Malaysia Melaka
19
1.6 Conclusion
By going through the background of the target users, the current problems
that they are facing are being understood more clearly. Then, objectives are listed out
to direct the development of the project. Also, scope and the significance of the
project have been discussed.
The next activities to be developed will be the selection of methodology in
developing the system, identifying the project requirement, and the project milestone.
© Universiti Teknikal Malaysia Melaka
20
CHAPTER II
LITERATURE REVIEW AND PROJECT METHODOLOGY
2.1 Introduction
This chapter is about the literature review of digital library and the project
methodology to be applied.
Literature reviews are secondary sources that bring the reader up to date with
current literature on a topic and form the basis for the next goal. Literature review is
considered as a summary and synopsis of a particular area of research. "It is not a
collection of quotes and paraphrasing from other sources. A good literature review
should also have some evaluation of the quality and findings of the research."
(Martyn Shuttleworth, 2009)
Project Methodology is about the approach selected to develop the project or
system. All the stages and steps of managing the project development towards
completion will be described.
Also, this chapter will list out the hardware requirement and software
requirement and other requirement to develop the project.
Finally, project schedule or milestone will be generated in tabular form. The
activities and workflow together with timeline will be discussed. The project will be
developed by following the schedule planned.
© Universiti Teknikal Malaysia Melaka
21
2.2 Fact and Finding
2.2.1 Domain
The domain of this project is library and information science. This project is
specified to digital library and it concerns the management of both physical and
digital library of the target user. Domain knowledge of managing library is important
and needed to develop the system. All the workflow, process and procedure of how
standard library operates are as guideline and reference for this project. In this
project, target user has an existing physical library and it will be served as main
model when developing the digital library system.
2.2.2 Existing System
There is currently only a physical library system from target user. In fact,
there are existing digital library systems. Some of the systems are university-based
which limit the access from public.
For example, there are two existing channels, e-Resources offered by UTeM
to allow all UTeM students and staffs to access electronic resources provided. The
resources are provided from two main sources, subscribed from third parties and
original resource from UTeM.
Table 1: Strength and weakness
Strengths
Provides free access to information
resource from certain subscribed source
Provide multiple access to resource
simply via internet
Weakness
Access to few creditable source
provided, but access to content of
resource requires payment
Categories are not well defined, lead to
confusion
Resource belong to UTeM e.g. Thesis is
only available at physical library within
campus
There is some similarity between the existing system and to-be system.
However, the existing system can only be a reference and the to-be system has to be
tailored according the requirement of the target user.
© Universiti Teknikal Malaysia Melaka
22
2.2.3 Technique
The technique that was used to collect the information about how library
operate was interview. An interview was conducted with the librarians and
department officers at UTeM library. The information obtained was so useful to have
overview of the workflow of library.
2.3 Project Methodology
The chosen methodology is Object-Oriented Analysis and Design (OOAD)
which is industry-proven methodology for developing high-quality object-oriented
systems. This methodology involves three aspects: object-oriented analysis (OOA),
which analyze the functional requirement for a system, object-oriented design
(OOD), which translates a system architecture into programming constructs (such as
interfaces, classes, and method descriptions); and object-oriented programming
(OOP), which implements these programming constructs.
Object-oriented analysis and design methodology models a system as a group
of interacting objects. In other words, it is about object decomposition, breaking the
complex software system down into manageable objects. OOAD methodology helps
producing flexible, modifiable, easily maintainable object-oriented systems. Besides,
this methodology focuses on the concept of reusability which greatly saves cost
during implementation.
Rational Unified Process (RUP) is an iterative and incremental software
development process framework that applies OOAD approach. RUP has determined
four phases of a project life cycle that are inception phase, elaboration phase,
construction phase and transition phase. In iterative approach, each phase will go
through the activities of system development life cycle (requirements, analysis,
design, implementation, and testing). In incremental approach, the effort in each
phase will be incremented to next following phase and finally end with one huge
effort as a whole.
© Universiti Teknikal Malaysia Melaka
23
a) Iterative phase:
In requirement stage, the activities will be carried out to gather and
understand the requirement of the digital library system. The requirement
specifications have to be established at this stage via various appropriate
techniques such as interview with the relevant parties.
In analysis stage, the requirement gathered from previous stage will
be analyzed and refined. It is required to identify and clarify the functional
requirement, non-functional requirement and other requirement for the
system development.
In design stage, the functional requirement and non-functional
requirement will be finalized. Also, programming language, developing tools,
platform and other requirement will be determined. The architecture and
design of the system will be produced according to requirement for next
stage.
In implementation stage, the system will be implemented based on the
architecture and design has been produced from previous stage.
In testing stage, the main objective is to verify if the system developed
meet or fulfil the requirement as agreement of developers and client. The
testing will be conducted from various aspects via different methods to
confirm client satisfaction.
b) Incremental phase:
In inception phase, requirement stage activities are carried out to
collect requirement. Then analysis and design phase may start. The
implementation is limited due to lack of sufficient and finalized information.
In elaboration phase, the initial requirement will be refined. Analysis
and design become complete with the aid of Unified Modelling Language
© Universiti Teknikal Malaysia Melaka
24
(UML) model. Various diagrams generated through UML model such as use
diagram, sequence diagram, class diagram and so on will be used for the
development that take place soon. At this phase, prototype will be good idea
to verify the understanding established about requirement.
In construction phase, it is the period where the implementation of
system begins properly based on the requirement, specification and design
that have been decided. There will also be iteration of testing process taking
place to ensure the development follow requirement.
In transition phase, the system will be verified if it has fulfilled the
requirement as stated following the agreement of both developer and client. If
the system achieves the client satisfaction, then the system will be deployed
as the final deliverable to client.
2.4 Project Requirement
2.4.1 Software Requirement
Software Description
Specification
Operating System
Microsoft Windows 7
Programming Language
Microsoft .Net 4.0
Development Tools I IDE
Microsoft Visual Studio 2008
Database Management
Microsoft SQL Server 2008
Unified Modelling Tool
Star UML tool
Project Document Tool
Microsoft Office Word 2007
Table 2: Software requirement
© Universiti Teknikal Malaysia Melaka