ABSTRACT
Database is an organized collection of information, data, or citations stored in electronic format that can be searched for specific information or records by techniques specific to each database.
Database program is a program used to electronically collect data, process it and also store it for future use.
This database program implements the techniques of database normalization. Normalization is the process of efficiently organizing data in a database. There are two goals of the normalization process: eliminating redundant data (for example, storing the same data in more than one table) and ensuring data dependencies make sense (only storing related data in a table). Both of these are worthy goals as they reduce the amount of space a database consumes and ensure that data is logically stored.
The program more on a religious group.The sore purpose of this program is to enhance and facilitate the church approach to information collection and storage for future use.
ORGANIZATION OF WORK
This project work is primarily designed to give an insight to database application in a religious group.
Chapter one talks about introduction to database program, study of problem and objectives as well as definition of the scope.
Chapter two comprises the literature review. Chapter three gives the detailed information about the existing (old) system, while chapter four and five deals with the design and implantation of new system.
Chapter six document the project work, while chapter seven summaries, conclusion and suggestions were made.
TABLE OF CONTENTS
Title page i
Certification ii
Dedication iii
Acknowledgement iv
Abstract v
Table of contents vii
CHAPTER ONE
INTRODUCTION 1
1.1 Background of the study 1
1.2 State of the problem 2
1.3 Purpose of the study 3
1.4 Aims and objectives 3
1.5 Scope of study 5
1.6 Limitations of study 5
1.7 Assumptions 6
1.8 Definition of terms 7
CHAPTER TWO
LITERATURE REVIEW 8
CHAPTER THREE
- Description and analysis of existing system                           15
- Fact finding method used                                                       17
- Organization structure                                                  19
- Objectives of Existing system                                       21
- Input, Process and Output Analysis                             22
- Information Flow Diagrams                                         26
- Problems of the Existing System                                  27
- Justification of the New System                                             28
CHAPTER FOUR
- Design of the New System                                            30
- Input Specification and design                                               30
- Output specification and design                                             32
- File Design                                                                    34
- Procedure chart                                                             36
- System flow chart                                                                  38
- System requirements                                                    40    Â
CHAPTER FIVE
- Implementation                                                             42
- Program Design                                                            45
- Program Flowchart                                                       48
- Pseudo code                                                                           54
- Source Program: Test Run                                            59
CHAPTER SIX
Documentation 60
CHAPTER SEVEN
- Recommendation                                                          62
- Conclusion                                                                    64
Bibliography 65
1.0 CHAPTER ONE
INTRODUCTION
The role information technology have played in various field of human endeavors can not be over emphasized. As most section of humanity like banking industries, auto mobile industries etc have experience the influenced of information technology like wise the religious setting.
A computer database is a structured collection of records or data that is stored in a computer system. A database relies upon software to organize the storage of data. In other words, the software models the database structure in what are known as database models (or data models). The model in most common use today is the relational model. Other models such as the hierarchical model and the network model use a more explicit representation of relationships (see below for explanation of the various database models).
Database management systems are usually categorized according to the database model that they support. The data model tends to determine the query languages that are available to access the database. A great deal of the internal engineering of a DBMS, however, is independent of the data model, and is concerned with managing factors such as performance, concurrency, integrity, and recovery from hardware failures. In these areas there are large differences between products
Database normalization, sometimes referred to as canonical synthesis, is a technique for designing relational database tables to minimize duplication of information and, in so doing, to safeguard the database against certain types of logical or structural problems, namely data anomalies. For example, when multiple instances of a given piece of information occur in a table, the possibility exists that these instances will not be kept consistent when the data within the table is updated, leading to a loss of data integrity. A table that is sufficiently normalized is less vulnerable to problems of this kind, because its structure reflects the basic assumptions for when multiple instances of the same information should be represented by a single instance only.
Higher degrees of normalization typically involve more tables and create the need for a larger number of joins, which can reduce performance. Accordingly, more highly normalized tables are typically used in database applications involving many isolated transactions (e.g. an Automated teller machine), while less normalized tables tend to be used in database applications that need to map complex relationships between data entities and data attributes (e.g. a reporting application, or a full-text search application).
Database theory describes a table’s degree of normalization in terms of normal forms of successively higher degrees of strictness. A table in third normal form (3NF), for example, is consequently in second normal form (2NF) as well; but the reverse is not necessarily the case.
Although the normal forms are often defined informally in terms of the characteristics of tables, rigorous definitions of the normal forms are concerned with the characteristics of mathematical constructs known as relations. Whenever information is represented relationally, it is meaningful to consider the extent to which the representation is normalized.
Computer programmers have gone ahead to write a database program to assist in the storage of information in many organization including religious groups.
