The Development Of Prison Management System (PRMS).

(1)

BORANG PENGESAHAN STATUS TESIS·

JUDUL:

l1+e

ｄｾｖＢＬｖｊｐＯｬＱｅｎｩ＠ of ｰｬＴｬｾｏｎ＠ＯｨｾＢＶＩｅｉｙｬｴ］ｴｶｔ＠ $ '1\[SIl\ CPRMS)

SESI PENGAJIAN : l001 /20 0

'it

Saya ｎａｄｾｔｵｌ＠Ｍｉｆｆｾｈ＠ ST . ABu ｈｾｓａｎ＠

(HURUF BESAR)

mengaku membenarkan tesis (pSMlSarjana/Doktor Falsafah) ini disimpan di Perpustakan Fakulti Teknologi Maklumat dan Komunikasi dengan syarat-syarat kegunaan seperti berikut:

I. 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 MakJumat dan Komunikasi dibenarkan untuk membuat salinan tesis ini sebagai bahan pertukaran antara institusi pengajian tinggi.

4. ··Sila tandakan (I)

SULIT

TERHAD

TlDAK TERHAD

(TANDATANGAN PENULlS)

Alamat Tetap:

4lt>.

TAIllIl/J TIIINlllq

｜ｉｾＨｊｉ＠ I 010200 l<ep'ILA

I2AJf}S-'" e

DI'}\-\ ) Tarikh: 2'

7 '

I

ｯｾ＠

• I

(Mengandungi maklumat yang berdatjah keselamatan atau

kepentingan Malaysia seperti yang tennaktub di dalam AKT A RAHSIA RASMI 1972)

(Mengandungi makJumat TERHAD yang telah di tentukan oleh

organisasilbadan di mana penyelidikan dijalankan)

MISS ｎｾｐＭ ITIft5 I'\trJA &T·

mO ·

ｾｯｴｴｦｬｰＮＮＱ＠

(Nama Penyelia)

Tarikh:

ｊＮＧＯｾＯｏｧ＠

(2)

NADATUL 'IFFAH BINTI ABU HASAN

This report is submitted in partial fulfilment of the requirements for the Bachelor of Computer Science (Database Management)

FACULTY OF INFORMATION AND COMMUNICATION TECHNOLOGY UNIVERSITI TEKNTKAL MALAYSIA MELAKA

(3)

DECLARATION

I hereby declare that this project report entitled

THE DEVELOPMENT OF PRISON MANAGEMENT SYSTEM (PRMS)

is written by me and is my own effort and that no part has been plagiarized

without citations.

STUDENT

SUPERVISOR

(NADATUL ' IFFAH BT. ABU HASAN)

Date:

'1"

{" /

,

0

"6

(4)

DEDICATION

To my lovely family ; your caring, support and understanding are my greatest inspiration.

To my supervisor, Miss Nor Mas Aina Bt. Md. Bohari, for your guidance, suggestions

and ideas. Thank you for everything.

To my dear friends who always be there for me and share lots of great ideas. Thank you

(5)

III

ACKNOWLEDGEMENTS

First of all, I would like to thank to God because I managed to accomplish the first part

of my final year project. I dedicate my warmest thanks to my beloved family and friends

for their million supports and encouragement during this project. For them, any

expression of thanks is insufficient.

I would like to express my gratitude and appreciation to my supervisor, Miss Nor Mas

Aina hI. Md. Bohari who had guided me a lot during the development of the project.

Thank you for being there for me during my most trying moments and also for the

suggestions and brilliant ideas. Not to forget, a million thanks to my language

supervisor, Mdm. Nik Rahiia bt. Dato' Wan Ibrahim who always guide me to write a

good technical report for this project. Also thanks to my evaluator, Po . Rosleen Bt.

Abdul Samad.

A note of thanks is specially dedicated to Faculty of Information and Communication

Technology (FTMK), Universiti Teknikal Malaysia Melaka for providing this project as

part of our degree program. Apart from that, I would like to express my sincere gratitude

to all the lecturers of Universiti Teknikal Malaysia Melaka that always keep me from

falling apart.

Not forgetting also the staffs of the Penjara Alor Setar for their cooperation during my

visit to gather some information about the flow of the procedure in prisons and also the

(6)

ABSTRACT

(7)

v

ABSTRAK

(8)

CHAPTERD LITERATURE REVIEW AND PROJECT

METHODOLOGY

2.1 Introduction

2.2 Facts and Finding

2.2.1 Techniques

2.2.2 Existing System

2.2.3 Database Function

2.2.4 Summary of Facts and Finding

2.3 Project Methodology

2.3.1 Planning

2.3.2 Analysis

2.3.3 Design

2.3.4 Implementation

2.3.5 Testing

2.4 Project Requirements

2.4. 1 Software Requirements

2.4.2 Hardware Requirements

2.4.3 Others Requirements

2.5 Project Schedule and Milestones

2.6 Conclusion

CHAPTERm ANALYSIS

3.1 Introduction

3.2 Problem Analysis

3.2.1 Flow Chart of Current System

3.3 Requirement Analysis

3.3.1 Data Requirement

(10)

3.3.2 Functional Requirement 31

3.3.2. 1 Context Diagram of 31

to-be system

3.3.2.2 Decomposition Diagram 32

3.3.2.3 Data Flow Diagram 33

(OFD) to-be system

3.3.3 Non-functional Requirement 37

3.3.4 Other Requirements 38

3.3.4.1 Software Requirement 38

3.3.4.2 Hardware Requirement 39

3.3.4.3 Network Requirement 40

3.4 Conclusion 40

CHAPTER IV

DESIGN

42

4.1 Introduction 42

4.2 High-Level Design 42

4.2.1 System Architecture 43

4.2.2 User Interface Design 44

4.2.2. 1 Navigation Design 44

4.2.2.2 Input Design 4S

4.2.2.3 Output Design 6S

4.2.3 Conceptual and Logical 66

Database Design

4.2.3.1 Conceptual Design 67

4.2.3.2 Logical Database Design 69

4.3 Detailed Desi gn 73

4.3 . 1 Software Design 73

4.3.2 Physical database Design 73

4.3.2.1 Data Definition Language 74

(11)

IX

4.3.2.3 Database Contingency 75

4.4 Conclusion 76

CHAPTER V IMPLEMENTATION 78

5.1 Introduction 78

5.2 Software Development Environment 78

Setup

5.2.1 Software and Database 79

Environment Setup

5.2.2 Hardware Setup 80

5.3 Database Implementation 8 1

5.4 Software Configuration Management 83

5.4. 1 Configuration Environment 83

Setup

5.4.1.1 Oracle9i Database 83

5.4.1.2 Oracle9i Developer Suite 84

5.4.2 Version Control Procedure 90

5.5 Implementation Status 91

5.6 Conclusion 93

CHAPTER VI TESTING 94

6.1 Introduction ₉₄

6.2 Test Plan ₉₄

6.2. 1 Test Organization 95

6.2.2 Test Environment 95

6.2.3 Test Schedu le 96

6.3 Test Strategy ₉₇

6.3.1 Classes of Tests ₉₈

6.4 Test Design ₉₉

6.4. 1 Test Descriptions ₉₉

(12)

CHAPTERVll

6.5 Test Results and Analysis

6.6 Conclusion

PROJECT CONCLUSION

7.1

Observation on Weaknesses and Strengths

7.1.1

Weaknesses of the PRMS

7.1.2

Strengths of the PRMS

7.2

Proposition for Improvement

7.3

Contribution

7.4

Conclusion

REFERENCES

BffilLlOGRAPHY

APPENDICES

100

102

103

103

104

105

106

107

109

(13)

xi

LIST OF TABLES

TABLE TITLE PAGE

2.1

Comparison between PRMS and existing systems

19

2.2

Software Requirements

23

2.3

Hardware Requirements

23

2.4

Project Milestones

24

4.1

Input Types and Validation Rules for Login page

47

4.2

Input Types and Validation Rules for Prisoner Detail

49

4.3

Input Types and Validation Rules for Dependent Detail

51

4.4

Input Types and Validation Rules for Cell Detail

52

4.5

Input Types and Validation Rules for Prisonercase

53

4.6

Input Types and Validation Rules for Parole Detail

55

4.7

Input Types and Validation Rules for Dynamic Table

56

4.8

Input Types and Validation Rules for Display and

59

Export Report.

4.9

Input Types and Validation Rules for Grant and

62

Revoke System and Object Privileges.

4.10

Input Types and Validation Rules for Backup and Recovery 64

4.11

Prisoner-Dependent Table

71

4.12

Prisoner Table

71

4.13

Dependent Table 72

(14)

5.1 Software Requirement 79

5.2 Basic Hardware Specifications SI

5.3 PRMS Progress 92

5.4 Test Organizations 95

5.5 Hardware Specification for Test Environment 95

5.6 Software Specification for Test Environment 95

5.7 Test Schedule ofPRMS 96

5.S Test Results for Test Cases 100

B.I Data Requirements for DBA 114

B.2 Data Requirements for SA 114

B.3 Data Requirements for Prisoner 115

8.4 Data Requirements for Dependent 116

B.5 Data Requirements for Cell 117

B.6 Data Requirements for Cases 117

B.7 Data Requirements for Prisonercase liS

B.S Data Requirements for Parole Request liS

C.I Data Dictionary for Staff table 121

C.2 Data Dictionary for Prisoner table 122

C.3 Data Dictionary for Dependent table 123

C.4 Data Dictionary for Cell table 124

C.5 Data Dictionary for Cases table 125

C.6 Data Dictionary for Prisonercase table 125

C.6 Data Dictionary for Parole table 126

D.I Login Module 129

D.2 Registration Data Module 129

D.3 Table Creation 130

D.4 Producing Report 131

D.5 Backup Data 131

D.6 Recovery Data 132

D.7 Grant Privilege 132

(15)

xiii

F.I Test Cases for Login Module 138

F.2 Test Cases for Record Management (Prisoner Form) 138

F.3 Test Cases for Record Management (Dependent Form) 140

FA Test Cases for Record Management (Cell Form) 141

F.S Test Cases for Record Management (Prisonercase Form) 142

F.6 Test Cases for Record Management (parole Form) 143

F.7 Test Cases for Record Management (SA role for DELETE

Privilege) 144

F.8 Test Cases for the used of Trigger in the PRMS 144

G.I First Test Data for Login Module 146

G.2 Second Test Data for Login Module 146

G.3 Test Data for Record Management (prisoner Form) 147

GA

Test Data for Record Management (Dependent Form) 148

G.S Test Data for Record Management (Cell Form) 149

G.6 Test Data for Record Management (prisonercase Form) ISO

G.7 Test Data for Record Management (parole Form) lSI

G.8 Test Data for Record Management (SA role for DELETE

Privilege) IS2

(16)

LIST OF FIGURES

FIGURES TITLE PAGE

2.1 Home Page of Portal Rasmi Jabatan Penjara Malaysia I I

2.2 Home Page of Lock & Track Online System 12

2.3 Iterative Waterfall Model 22

3.1 The Flow Chart of current system 29

3.2 Context Diagram of to-be system 31

3.3 Decomposition Diagram 32

3.4 Data Flow Diagram (DFD) level 0 of to-be system 34

3.5 Data Flow Diagram (DFD) level I of to-be system 35

4.1 System Architecture of PRMS 43

4.2 Navigation Design of PRMS 45

4.3 Input Design for Login Page 46

4.4 Input Design for Prisoner page 48

4.5 Input Design for Dependent page 50

4.6 Input Design for Cell page ₅₂

4.7 Input Design for Prisonercase page 53

4.8 Input Design for Parole page 54

4.9 Input Design for Create dynamic table 56

4.10 Prison Management report page 57

4.11 Display and export report page ₅₈

(17)

xv

4.13 Grant System Privilege page 60

4.14 Grant Object Privilege page 60

4.15 Revoke Option page 61

4.16 Revoke System Privilege page 61

4.17 Revoke Object Privilege page 62

4.18 Backup Table page 63

4. 19 Recover Table page 64

4.20 Output Design for Sample Report 65

4.21 Output Design for Confirmation Message 66

4.22 Output Design for Error Message 66

4.23 Entity Relationship Diagram ofPRMS 68

5.1 Development Environment ofPRMS 79

5.2 Listener.ora file of PRISON database 83

5.3 Oracle Net Configuration Assistant: Welcome page 86

5.4 Add Net Service Name for Net Service Name 87

Configuration

5.5 Choose Database Version for Net Service Name 87

Configuration

5.6 Service Name for Net Service Name Configuration 88

5.7 Select Protocols for Net Service Name Configuration 88

5.8 TCP/IP Protocol for Net Service Name Configuration 89

5.9 Test for Net Service Name Configuration 89

5. 10 Net Service name for Net Service Name Configuration 90

5.11 Example of Oracle Developer Form Module 91

backup file in other location

J. I Login Page ofPRMS 154

J.2 Login Successful Message Box 154

J.3 Main Menu Page 155

J.4 Prisoner Detail Page 155

J.5 Dependent Detail Page 156

(18)

J.7

Prisoner Case Detail Page

157

J.8

Parole Request Page

157

J.9

Confirmation Message Box for Exit

158

1.1

Login Page

160

1.2

Login Successful Message Box

160

1.3 Main Menu Page

161

1.4

Table Creation Page

162

1.5

Create User with Privilege Page

162

1.6

Backup & Recovery Page

163

(19)

XVII

LIST OF ABBREVIATIONS

DBA Database Administration

DBMS Database Management System

DCL Database Control Language

DDL Data Definition Language

DFD Data Flow Diagram

ERD Entity Relationship Diagram

FK Foreign Key

GUI Graphic User Interface

HlTP Hyper Text Transfer Protocol

IC Identification Card

JAR Java Archive

JVM Java Virtual Machine

J2EE Java 2 Platform

LAN Local Area Network

OC4J Oracle9iAS Containers for J2EE

OLTP On-line Transaction Processing

PK Primary Key

PRMS Prison Management System

SA System Administration

SDLC Software Development Life Cycle

SSADM Structured System Analysis and Design

(20)

LIST OF ATTACHMENTS

ATTACHMENT TITLE PAGE

A Gantt Chart

110

B

Data Requirement

113

C Data Dictionary

120

D Software Speci fication

128

E Data Definition Language

132

F Test Cases

137

G Test Data

145

H User Manual for System Administration

153

User Manual for Database Administration

157

(21)

CHAPTER I

INTRODUCTION

Thi s chapter contains project background, problem statement, obj ective, scope,

project significance, expected output of the system and the conclusion of thi s chapter.

Proj ect background describes briefl y about the proj ect that will be deve loped. The

pro blem statements will state the problems that encountered in the ex isting system or

current system. For the objecti ve, it is about the aim for the development o f the to-be

system in order to so lve m·ost of the pro blem in the ex isting system while scope covers

the target users, fun ction and the technology o f the to-be system. Project s igni fi cance

will describe the bene fit and the important o f the to-be system for the user. Meanwhile,

expected output will describe the fin a l output of the to-be system. T he conclusion

summarizes this chapter and gives an introduction o f the next chapter.

1.1 Project Background

The proj ect that will be .. developed is Prison Management System (PRMS) for the

use of Pri sons Department Malaysia under the Ministry of Interna l Security in

effecti vely managing the prison data and also more to the database management. The

users for this system are Database Admini strator (DBA) and System Administrator

(22)

tables, grants or revoke a system or object privilege to user, stored procedure or

function , and generate report by using system interface. This system is also to make sure

that DBA can do all the transaction by using this user-friendly interface not only by

doing all that in the database.

SA will register the new prisoner and all the other detail into the system and

process all the information of the prisoner. After the regi stration, system administrator

will update the data and do all the given mod ules in thi s system.

The existing system is still using both computer and manual file system such as

interview requests by the relatives of the prisoner. To solve this problem, this project

will automate business process and plus, other modules will be added to the system like

adding the specific interface that required all the information about prisoner and their

relatives.

1.2 Probleni Statement

The following problems are identified to deve lop this system:

I. Limited usage of database trigger

The database triggers are not widely use in the current system. The usage of the

tri gger is limited to important data, for example, trigger wi ll be used to set a time

when DBA want to make a backup.

2. Limited usage of stored procedure

DBA has to open the database to run the stored procedure or function . It is hard

[image:22.611.58.521.72.767.2]

(23)

3

3. Not using dynamic table structure

Usually, to create table for example, user is not required to give their own

parameter li kes number o f columns and have to know the syntax.

4. System administrator is not allow to give system and object privilege

Currently, system administrator cannot give a system or obj ect privilege to other

user in the system and only DBA will do that.

5. Us ing wizard for Data Backup and Recovery

DBA usuall y does the backup and recovery fil e by using some certa in wizard.

DBA has to make sure that the wizard can help to backup all the data in the tabl e

or small amount of data in some table.

6. . Produce a static report

In ex isting system, when the user wants to see the report, user chooses the

reports that are listed in the interface only. All the parameter is set to generate the

summary 0 f the report.

1.3 Objective

The a ims of the

PRMS

development are:

1. To apply and widely use the database trigger.

2. TQ apply stored procedure or fun ction in the system by using the interface.

(24)

4. To allow the syste m admini strator to grant and revoke the syste m and object

priv ilege to othe r user.

5. To provide the data backup and recove ry functio n by using system interfaces.

6. To produce the dyna mic report.

1.4 _Scope

The scope will expla in the boundaries o f this project a nd in order to de velop a

syste m fo r users in Prisons Department Malaysia that e nable them to manage the

prisone r registration and reports. Del iverables o f the project w ill be a complete syste m

fo r users that will meet the objectives.

1.4.1 Target use r

The target users for this Pri son Ma nage ment Syste m (PRM S) a re Syste m

Admini strator (SA) and Database Administrator (DB A) o f Prisons Department

Malaysia.

1.4.2 Function

The modules that the PRMS will provide:

1. Insert/U pdateffieleteiSearch

User w ill insert a new prisoner, update the data, or delete the data o[ the prisoner