Design and Implementation of an Automated Register Management System a Case Study: Nabilatuk Ca Tholic Parish, Nakapiripirit District

ABSTRACT Catholic Parishes manage a range of data and information books. Most important, are registers where records about the sacramental information are kept as a demand by Mother Church. Much of the registration and register management duties are meant to be carried by the Parish Priest, but due to the work overload and the nature of the traditional book-keeping system, the Parish Priest employs, and is most often assisted by, the seminarians and catechists. The inconsistencies of the current system have rendered the registration process unproductive, thus raising the need for the designing and implementation of the computerized system. The purpose of this project was to design and implement an automated register management system for Nabilatuk Catholic Parish. It involved looking at the concepts and information already made available on: Database Management Systems, Information Systems; information management system, system development approaches, unified modeling language, and the recent developments relating to the proposed system. The importance of this was to relate the proposed system to what other researchers have written about similar systems so as to inform the research and system development process. The system developed has made a starting point where other researchers can obtain insight necessary to make a more robust system. This report presents the architectural, logical and physical designs of the system, implementation and recommendations for further improvement of the new system.

TABLE OF CONTENTS

DECLARATION

APPROVAL

DEDICATION

ACKNOWLEDGEMENTS iv

TABLE OF CONTENTS v

LIST OF ABREVIATIONS ix

ABSTRACT

CHAPTER ONE 1

INTRODUCTION

1.0 Introduction i

1.1 Background information to the project problem I

1.2 Problem statement 2

1.3 Purpose of the study 3

1.4.2 Specific Objectives 3

1.5 Justification 3

1.6 Conceptual Framework 4

1.6.1 Description of the context diagram 4

CHAPTER TWO 5

LITERATURE REVIEW 5

2.0 Introduction

2.1 Register system of the Roman Catholic Church 5

2.2 Information Systems 6

2.3 Management Information Systems 7

2.4 Database Management Systems 8

V

2.5 System development approaches 8

2.5.1 Prototyping 8

2.5.2 Water fall model 9

2.5.3 Incremental Model 9

2.5.4 Spiral Model 10

2.5.5 Rapid Applications Development (RAD) 10

2.6 System Development Tools 11

2.6.1 Unified Modeling Language (UML) 11

2.6.2 Visual Basic (VB) 11

CHAPTER THREE 12

METHODOLOGY 12

3.0 Introduction 12

3.1 Requirements definition 13

3.1.1 Reading documents about the existing system 13

3.1.2 Interviewing relevant authorities 13

3.2 Data analysis 13

3.3 Design tools 13

3.4 Implementation 14

3.5 Testing and Validation 14

CHAPTER FOUR 15

SYSTEM DESIGN 15

4.0 Introduction 15

4.1 Entity Relationship Diagram of the new system 15

4.2 Class Diagram 16

4.3 Data Flow Diagrams 18

vi

4.3.1 Data Flow Diagram for registering new user 18

4.3.2 Data Flow Diagram for Logging into the system 19

.3.3Data Flow Diagram for Searching details 20

4.4 Database Design 20

4.4.1 Table Structures 20

4.4.2 Data Input Design 21

4.4.3 Data Output Design 22

4.5 Conclusion 22

CHAPTER FIVE 23

SYSTEM IMPLEMENTATION 23

5.0 Introduction 23

5.1 Program Testing 23

5.2 User Training and Documentation 23

5.3 System implementation 24

5.4 Structural overview ofthe new system 24

5.5 User interface 24

5.5.1 Login Form 25

5.5.3 User Registration Form 27

5.5.4 Sacraments of Christian Initiation Form 28

5.5.5 Deaths and Burials Form 29

5.6 User Training and Documentation 29

5.7 Adapting the system to new requirements 30

5.8 Maintenance 30

5.9 Conclusion 30

CHAPTER SIX 31

vii

RECOMMENDATIONS AND CONCLUSION .31

6.0 Introduction 31

6.1 Recommendations 31

6.2 Areas for Further Work 31

6.3 Conclusion 32

REFERENCE 33

Appendix A 35

GLOSSARY 35

Appendix B 37

Work plan 37

Appendix C 39

BUDGET 39

AppendixD 40

INTERVIEW GUIDE 40

AppendixE 41

Sample Codes used to create the Application interface 41