DEDAN KIMATHI UNIVERSITY OF TECHNOLOGY

PROJECT REPORT FOR DEGREE IN

BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

SAMUEL NJARA BOTO

(C025-0711/2011)

JESUS SUMMATE APLICATION (JSA)

SUPERVISOR MR.KAGIRI

Project submitted in Partial Fulfillment of the Requirements for the award of

Bachelor of Science degree in Information Technology at Dedan Kimathi University

of Technology.

November 2015

Declaration

I declare that this project report documentation is my own, unaided work. It has not been

submitted previously for any degree or diploma examination in any other university. 

STUDENT’S NAME : SAMUEL NJARA BOTO

SIGNATURE …………………………………………..

DATE ……….…………………………………..

SUPERVISOR’S NAME : MR KAGIRI

SIGNATURE …………………………………………….

DATE ……….………………………………

Acknowledgement

First and foremost special thanks to the Almighty Lord for the much I have achieved, and

thanks to everyone who is assisting me for this the project; especially Mr. Kagiri, my

project supervisor for the assistance in the research and consultations. I heartily

acknowledge my dear parents for the financial support they are offering on my project

budget. I pass my esteemed gratitude to the school and the entire student and lecturers of

Dedan Kimathi University of Technology who are laboring endless to the project

proposal.

Abstract

Over the last 5 years, the African continent and the world at large have witnessed

sprouting of mega churches with up to 2000 or more worshippers per weekly service.

These churches are led by visionary and charismatic leaders who are able to make

disciples. The role of the modern church in the life of the 21st-century believer is critical

because it fills a void only the church can. If a car needs fixing, it is brought to the

mechanic shop. If someone is sick, the health center or hospital is the best place to seek

medical attention. Church is where people should go if they are in need of a "spiritual

fix." The church is really a hospital for sinners and not an exclusive club for saints. So

why would someone want to attend church? Regardless of what is said about churches,

people expect that their life problems can be addressed in some fashion or form. With all

the weight and pressures of their world weighing down on their minds, people expect the

church to provide Bible-based answers that no other institution can provide. With the

growing number of church members, seamless communication becomes even more

important because with more people to carry along, more attention needs to be paid to the

communication process and strategy. Yet, communication is one of the major challenges

in the church today. This challenge leads to an emotional disconnect between church

management and their members (Adobe.com, 2015).

This application is developed in response to the rising challenge of emotional disconnect

between church management and members. The aim of the application will be to provide

an interactive and user friendly mobile platform, through which, Christians can better

connect with each other and increase the presence of the church in the community. The

app extends the hand of fellowship beyond the church auditorium and into the everyday

lives of members. Churches can send daily devotionals to members to enable them grow

in their walk and relationship with God. The system will be developed in several modules

which will be implemented as Android classes, each performing a specific task and the

end product will be an integrated system that uses a mobile application as a point of

interaction between a user and the system. The project will be developed using the

waterfall software development methodology (Adobe.com, 2015).

Table of Contents

Declaration.....................................................................................................................................2

Acknowledgement..........................................................................................................................3

Abstract..........................................................................................................................................4

List of Terms and Abbreviations....................................................................................................7

List of Tables..................................................................................................................................8

List of Figures................................................................................................................................9

CHAPTER ONE: INTRODUCTION...................................................................................................10

1.1 BACKGROUND.....................................................................................................................10

1.2 PROBLEM STATEMENT..................................................................................111.3 Objectives...........................................................................................................121.4 JUSTIFICATION AND SIGNIFICANCE OF THE STUDY.............................131.5 GENERAL SCOPE AND APPLICATION OF THE PROJECT........................131.6 ASSUMPTIONS..................................................................................................13

CHAPTER 2: LITERATURE REVIEW......................................................................................15

2.0 INTRODUCTION...................................................................................................................15

2.1 GRAYMERE CHURCH OF CHRIST..........................................................................................15

2.2 LIFE WITHOUT LIMBS MINISTRY.........................................................................................15

2.3 ROSEWOOD ACADEMY CARROLLTON.................................................................................16

2.4 YOUTH MINISTRY RESOURCES............................................................................................16

CHAPTER 3: METHODOLOGY........................................................................................................17

3.1 Fact finding methodology...................................................................................................17

3.1.1 Questionnaires..................................................................................................173.1.2 Interview...........................................................................................................173.1.2 Observation.......................................................................................................173.1.3 Focus Groups....................................................................................................18

3.2 Development Process.........................................................................................................19

3.3 Data Analysis Methods and Techniques............................................................................21

4.2: SYSTEM ANALYSIS........................................................................................24CHARPTER 4: ANALYSIS AND DESIGN................................................................................29

CHAPTER 4: TESTING AND RESULTS.............................................................................................29

4.0 Introduction........................................................................................................................29

4.1 Data Validation and Reliability Test....................................................................................30

4.1.1 Input validation.................................................................................................304.1.2 Constraint validation.........................................................................................30

4.2 Requirements Analysis and Test Cases...............................................................................30

4.2.1 Functional Requirements..................................................................................304.2.2 Non-Functional Requirements.....................................................................33

CHAPTER FIVE: IMPLEMENTATION AND DEPLOYMENT................................................................34

CHAPTER SIX: CONCLUSIONS AND RECOMMENDATIONS............................................................42

6.1 Limitations..........................................................................................................................42

6.2 Recommendations..............................................................................................................43

6.3 Conclusion..........................................................................................................................44

6.0 References............................................................................................................45

List of Terms and Abbreviations

i) DFD: Data Flow Diagramii) OS: Operating Systemiii) App: Applicationiv) GPS: Global Positioning Systemv) JSA: Jesus summate Application

List of TablesTABLE 1: USER ACCOUNT REGISTRATION DETAILS...................................................................................................28TABLE 2:USER LOGIN DETAILS............................................................................................................................28TABLE 3:ADMINISTRATOR LOG IN DETAILS.............................................................................................................28

List of FiguresFIGURE 1:FIGURE 1: CHURCH SYSTEM DEVELOPMENT STAGES TO BE ADOPTED..........................................17FIGURE 2:TABLE 2: DATA ANALYSIS TABLE SHOWING DIFFERENT OPERATING SYSTEMS USED...........................................21FIGURE 3:FIGURE3: PIE CHART SHOWING DIFFERENT OPERATING SYSTEMS USED...........................................................21FIGURE 4:TABLE 3: TABLE SHOWING AGE SUPPORT OR REJECTION OF DEVELOPMENT OF THE SYSTEM...............................21FIGURE 5:FUGURE 4: HISTO-GRAPH SHOWING AGE SUPPORT OR REJECTION OF DEVELOPMENT OF THE SYSTEM..................22FIGURE 6:CONTEXT DIAGRAM......................................................................................................................23FIGURE 7:ADMINISTRATOR LEVEL ONE DIAGRAM.....................................................................................................24FIGURE 8:USER LEVEL ONE DIAGRAM....................................................................................................................24FIGURE 9: USE CASE DIAGRAM............................................................................................................................25FIGURE 10:USE CASE....................................................................................................................................26FIGURE 11:DATA FLOW DIAGRAM................................................................................................................26FIGURE 12:CLASS DIAGRAM.........................................................................................................................27FIGURE 13: ADMIN LOGIN CREDENTIALS......................................................................................................34FIGURE 14:THE MESSAGE DISPLAYED WHEN THE CREDENTIALS ENTERED ARE WRONG...............................34FIGURE 15:ADMIN VIEW OF THE HOMEPAGE................................................................................................35FIGURE 16:FORM TO INSERT NEW PROGRAM DETAILS..................................................................................36FIGURE 17:LIST OF THE AVAILABLE MOTORCYCLES.....................................................................................37FIGURE 18:DETAILS TO BE EDITED...............................................................................................................38FIGURE 19:CLIENT MAIN HOMEPAGE...........................................................................................................38FIGURE 20:THE USER PROGRAM VIEW..........................................................................................................39FIGURE 21:USER VIEWING OF ANNOUNCEMENTS..........................................................................................40

CHAPTER ONE: INTRODUCTION

The use of computer today is in peak point and each and every field uses computer

system for the fast processing and security of the data. Church ministry is one of the

fields where computers have made tasks easier, more efficient and organized. A church

system is used to keep all the church statistics so that, future plans can be drawn from the

information gathered after many years. It is also used to send information to Christians

regarding their spiritual growth and encouragement.

Recent technological developments have produced a range of sophisticated and readily

available digital systems implementing vast and very advanced levels of technologies to

the level of Global Positioning System (GPS). Yet despite this remarkable surge in

technology, church leaders have underutilized the power of computers to help them

increase their relevance in the community.

Although having a clean, up-to-date website should be a must for churches, users spend

86% of their mobile time on apps. As a result, failing to research and consider a church

mobile app ignores a huge segment of members and guests who rely on their mobile

devices rather than their computers. This project proposal aims at assisting churches to

dive deeper and engage more fully with their community by use of mobile application

system.

1.1 BACKGROUNDIn the recent past, there has been an unprecedented growth of smart phones in Kenya. A

recent report by Human IPO (2014) has said that Kenya has 67% smart phone

penetration. The report is based on figures released by Kenya’s leading mobile operator

Safaricom. 100,000 smart phones are sold each month in Kenya, making it a leading

market for smart phones in Sub-Saharan Africa. This can be attributed to the

infrastructure setup, cheap internet costs and low cost of entry level smart phones. We

have seen prices go as low as $50 for smart phones in the region. This of course reflects

on the mobile carrier revenues that see increased growth of data consumption in the

country .

Smart phone are powered by applications. The ultimate goal of these applications is to

improve personal, religious and business communication among people (Dye, 2010).

There has been rapid increase in mobile application development to run these phones

from Kenyan innovators. A good example is the m-pesa mobile money transfer service.

The overall objective of this research is to develop a religious application system to help

people better connect with Jesus through enhancing communication between the church

stakeholders.

1.2 PROBLEM STATEMENTJesus Summate Center is a fast-growing church in murang’a town .Over the last 3

years, since Reverend John Muriithi assumed leadership of the congregation, the church

has seen more than double of its size. It now has approximately 1000 registered

households. Since the church was rather small in the past, most of its records and

communication strategy uses paper works. However, the church secretary miss Jane

Ndirangu has suggested to the Reverend Miriithi that a computerized system might help

the church better meet its information needs, manage its activities and economies on

expenditures. From a business point of view, one thing that the church must be concerned

with is registration of new members. The church has been looking for ways to win new

disciples to the church. There has been a capital improvement campaign for purchasing a

nearby property to build additional parking to accommodate the church growing

membership. The cost of acquiring the property and paving it goes to about 3.4 million

Kenya shillings. The church obtained a loan to finance the project and it makes regular

payments on this loan from member’s regular contributions. Members were issued with

pledge forms to state how their commitments on how much money they would contribute

within the next three years. The church being a non-profit organization that relies on the

member’s contribution, it has been looking for ways to cut down its cost of operation so

as to channel more resources to the improvement campaign.

Furthermore, with the growing number of church members, seamless communication

becomes even more important because with more people to carry along, more attention

needs to be paid to the communication process and strategy.

Yet, communication is one of the major challenges in the church today. This challenge

leads to an emotional disconnect between church management and their members. In an

attempt to make sure that everyone reads from the same page, the management decided to

establish a church website which it broadcasts its activities, however, this has not solved

the church problems for the last 8 months. Even with rapid growth of mobile application

development and use, the church has not yet taped the power of mobile technology to

reach and touch more lives.

Developing a mobile application system for the church will help the church to grow and

make its presence felt in the community since; its followers are a part of a world that does

everything mobile. While there is much to be cautious of in technology today, there is

also much to grasp and take advantage of for eternal purposes. Creating an app for this

ministry can help equip this generation with the tools they need to stay grounded in a

quickly changing world. It can also help the church to cut down its costs thus channeling

those resources elsewhere.

1.3 Objectives1.3.1General objectives

Enhance the growth of the church through effective and efficient communication of

church leaders and their members.

1.3.2 Specific objectives

1. To develop a system that promotes church activities such as ceremonies, funerals,

weddings and baptism.

2. To develop a system that will allow church to receive donation

3. To develop a system that reduces cost on paper flyers and leaflets

4. To reduce on cost of publishing and printing .(design of posters)

5. To enhance up to-date communication of church activities/ announcements.

1.4 JUSTIFICATION AND SIGNIFICANCE OF THE STUDYJesus summate church invest its money in design and printing of program fliers and then reclaim the money back through members offerings and contributions. Since a church is not a profit making business, there is need to reduce spending so that more resources can be channeled in other ministerial objectives. The project will help the church to cut down cost of printing and publishing program fliers and enable the members to be up to date with church events and activities through better communication strategy.

1.5 GENERAL SCOPE AND APPLICATION OF THE PROJECTGenerally, the Jesus summate mobile application is intended for church members of Jesus

summate center in Murang’a county at Murang’a town. It is therefore exclusive for

religious use and growth of Christianity. Followers need to have the ability to operate

smart phones and not necessarily literate. Members need to create an account so that they

can be allowed to use the application. The application is to be downloaded from Google

play. The application is intended to promote the growth of the church and increase its

presence in the community. It is also an instrument to make pastors make more disciples

by reaching out for new prospects using social media. By enhancing communication and

interactiveness, the existing emotional disconnect will be solved and church will stay as

one body of Christ.

1.6 ASSUMPTIONS1. The users of the system are assumed to be computer literate.

2. The users of the system have access to the internet at all times and therefore have

access to the system whenever required.

3. The users of the system are able to easily utilize the android phones or have the

awareness of the android operations.

CHAPTER 2: LITERATURE REVIEW

2.0 INTRODUCTIONIn the course of my research I chose the following materials to enable me build up on my

idea and help me relate my work to what the others in the field of mobile development

have done. Among the key areas I greatly focused on are:

2.1 GRAYMERE CHURCH OF CHRISTThe Graymere church of Christ began in 1956 in Columbia, work was begun to convert a

restaurant building into a suitable meeting place for worship. The first services were held

the first Sunday of April, 1956. Thus, the Graymere congregation had her beginning.

. Whether you're a member or a visitor, there are features to help keep you engaged with

God and the church body, Mypocketchurch (2015).Some of these features include online

bible, mailing list and push notification. On its limitation is that, it lacks social media

interaction.

This application seeks to overcome this problem by providing access to social media

platforms where Christians can socialize with others for spiritual growth.

2.2 LIFE WITHOUT LIMBS MINISTRY

With a goal of making the word of God and the power of prayer available anywhere and

anytime, the Life without Limbs ministry has launched a free, innovative mobile

application with the following features, online bible, Photo and Image Galleries and

Videos, and finally events. The application support only face book as their social media.

This can be a barrier to reach more people and make more disciples (Play.google.com,

2015).

This application is based on the fact that, for you to make more disciples, you need to

reach out for them. It therefore uses multiple social media API’s and blogs to reach for

the lost.

2.3 ROSEWOOD ACADEMY CARROLLTON

Rosewood Academy in Carrollton provides a unique balance of both traditional and

Montessori methods to effectively cultivate your child's growth and success! Programs

available for infants through pre-kindergarten, after school and summer camps. Voted

‘Best Summer Camp in Carrollton' last year!

The new Rosewood Academy Carrollton app allows you to browse through the photo

gallery, view our latest videos, fill out forms, book tours, GPS locator for visitors directly

from your phone. It's just one more way that Rosewood keeps you connected! For you to

get to know the staff and mission of the academy, you are directed to their website which

can be an inconvenient to most people (Rosewood, 2009).

This application seeks to communicate about the staff, mission and vision of the church

so that, everybody can read from the same page. Furthermore, this app is not an academy

application but a religious application that will implement all the functionalities of the

Rosewood Academy Carrollton app.

2.4 YOUTH MINISTRY RESOURCES

This application provides youth resources to help young people to become more

grounded in this fast changing world. It provides young youth pastors and volunteers with

great ministry resources and ability to share what you learn with others through social

media or blogs. It has very high rating as a resourceful mobile application; however, it is

build for the youth only. This app intends to incorporate all the church groups such as

children, youth, parents and leaders so as to provide information to everyone need.

(Glomere.com, 2010)

CHAPTER 3: METHODOLOGY

3.1 Fact finding methodology

The tools and techniques of data collection to be used include:

3.1.1 Questionnaires A questionnaire is a research instrument consisting of a series of questions and other

prompts for the purpose of gathering information from respondents. Questionnaires was

given to 50 church members on a normal Sunday service to know whether they

recommend a church android app.

3.1.2 Interview An interview is a conversation between two or more people (the interview and the

interviewee) where questions are asked by the interviewer to obtain information from the

interviewee.

Reasons interview was used

Can motivate the responder to respond freely.

More feedback can be probed.

Can adapt questions for each individual.

The Local Church Committee (LCC) were interviewed about the challenges that the

church faces with current system of paper work. Despite spending too much on printing,

the fliers not everybody gets them. Sometimes they are over produced leading to wastage.

They agreed that developing a mobile app would double solve the existing problem.

3.1.2 Observation.Observation is either an activity of a living thing (human) consisting of receiving

knowledge of the outside world through the senses, or the recording of data using

scientific instruments. Techniques where the system Analyst either participates in or

watches a perform activities to learn about the system.

Reasons why observation was used:

Reliable data

Relatively inexpensive

Allows work measurement

Practical experience

Several visits to the church Sunday service were conducted to get a detailed

understanding of the normal routing on the church. Their practice and procedures is an

important part in solving the church real problem.

3.1.3 Focus GroupsThis particular data collection technique entailed engaging the church youth members group who were between (15-28). There was a detailed discussion with the major participants that helped in defining the problems that the church faces. Due to the fact that focus group is either discussion-oriented, problem solving or decision-oriented, similarly the approach taken used the same dimensions and this greatly helped gather a lot of information as the open interaction at the same level was greatly enhanced.

3.2 Development ProcessDuring the course of developing my system, I intend to use the waterfall-like System

development model.

Figure 1:Figure 1: Church system development stages to be adopted.

The sequential phases during the development of the church system will be as follows;

3.2.1 Assess the needs of the JS systemThis will be the first phase of the JS system and it will entail determining the necessary

information that will be required for the system to be fully operational as well as function

in the expected manner. I will formulate research questions that will be targeted to the

respective respondents. I will then list the information collected without any set

chronology as this will be done in the analysis stage of the development.

The requirements that I earlier captured previously will then be subjected to thorough

scrutiny to determine the level of essence of it as well as eliminate the unwanted

requirements.

Church system development methodology

3.2.2 Determine the flow of information in the JS systemWith the requirements having already been captured and analyzed, the design of the

information flow will be done here. It is in this phase that the flow charts, dataflow

diagrams and entity relationship diagrams will be drawn to show flow of information and

the activity diagrams will be developed to show the connection that will exist between

one information and another. Upon the development of the above, the database together

with its relationships will then be designed depending on the connection between the

various foreign keys.

Interface design will then follow which will form the front-end of the system that will

interact with the users through prompting them to enter the required information prior to

the performance of the intended operation. During the development of the interfaces,

logic will hold owing to the fact that the interfaces will be expected to communicate with

each other.

3.2.3 Perform the coding of the system functionalityAfter the design of the interfaces as well as the indication of the information flow through

the Sequence diagrams and the flowcharts algorithms, the next step will be to develop

code that will see the hidden functionality of the system to realize the already set

objectives. The code that will be developed will highly depend on the information flow

and therefore the flowcharts developed earlier will now apply here. A proper execution of

the previous stages will ensure an easier realization of this phase in the course of my

development. Upon completion of the coding, the various components of the system will

then be integrated in to one system in order to function collectively as a single

component.

3.2.4 Test the JS system test and verificationThe testing phase will come next to determine if the earlier intended objective will have

been realized by then. Testing will be done based on whether completeness will have

been realized or functional testing that will determine whether the software will do what

it is expected correctly and in the right way. User testing will then be carried out to

ascertain that the users will be contented with what will have been achieved then. This is

so much important as it will see criticism at this stage which in return will help realize

high level of acceptance.

3.2.5 Deploy the JS system and maintaining itOnes the system has undergone testing and passed all the validations and verifications,

then the system will be termed to be acceptable and therefore it will be handed over to the

owners for maintenance and operation as well. There are some issues in the client

environment that arise after the system has been developed. To fix those issues patches

will be released and as well to enhance the product better versions will be released all in a

bid to improve the client environment.

3.3 Data Analysis Methods and TechniquesUpon the completion of the data collection process, I subjected the data to thorough

scrutiny to determine the applicability and the suitability of the data from the various

respondents in the methods listed above. I placed the data in a tabular representation in

the form shown below.

3.3.1 The data analysis tables

FINDINGS FROM QUESTIONAIRE

No of respondents

With phones

Without phones

PercentageWith phones

PercentageWithout phones

Male 20 19 138 2

Female 30 26 452 8

Total50 45 5

TotalPercentage

100 90% 10%

Table 1: Data Analysis table showing gender and phone usage

Bar ChartA bar chart to represent the data obtained from the above table and represented as percentages.

15-20 20-300

2

4

6

8

10

12

14

Chart Title

Support the system Not support the system

Figure 3: Bar chart showing gender and phone usageType of operating system

Android Blackberry IPhone Windows Down phones

No. of users 30 2 3 5 10Percentage Total 60 4 6 10 20

Figure 2:Table 2: Data Analysis table showing different operating systems used3.3.3 Pie ChartsA pie chart to represent the above data from the table. The diagram below represents phone statistics for members in the church.

15-20

20-30

30-40

40-50

Above 50

Support the system

Figure 3:Figure3: pie chart showing different operating systems used

FINDINGS FROM THE QUESTIONNAIREAge

15-20 20-30 30-40 40-50 Above 50

Support the system

7 12 9 8 5

Not support the system 1 0 2 2 4

Figure 4:Table 3: table showing age support or rejection of development of the system

15-20 20-30 30-40 40-50 Above 500

2

4

6

8

10

12

14

0

0.5

1

1.5

2

2.5

3

3.5

4

4.5

Respondents data

Support the system Not support the system

Figure 5:Fugure 4: histo-graph showing age support or rejection of development of the system

3.4: SYSTEM ANALYSIS3.4.1 CONTEXT DATAFLOW DIAGRAM

Figure 6:Context diagram

The figure above shows the flow of information in the JS system which entail three users

of the system and these are, (Analyzing Information Systems Research, Morgan, S,

2009): The Client User, the Admin User and the guest user. The main distinction amongst

the three users is the privileges accorded for each of the users. The tasks that can be

performed by the member, admin and the guest are totally different with the least

privileges being those of the guest user who must login into the system which would

mean that he or she will see transformation to the level of a member to be able to execute

the tasks that he or she might want to perform.

3.4.2 Administrator level one diagram

Figure 7:administrator level one diagram

3.4.3 USER LEVEL ONE DIAGRAM

Figure 8:user level one diagram

3.4.4 USE CASE DIAGRAM

Figure 9: use case diagram

Figure 10:use case

3.4.3 Data Flow Diagram

Figure 11:data flow diagram

3.4.4 CLASS DIAGRAM

Figure 12:class diagram

CHAPTER 4: TESTING AND RESULTS

4.0 Introduction With the data having been collected and properly analyzed as well as the system having

been designed, the next stage that followed was testing the data collected with the system.

The data that was to be stored in the system is shown in the following tables:

Field Name Data Type DescriptionUser_Name Varchar User registers his/her namePassword varchar Password of the userConfirm_Password Varchar User Confirm passwordTable 1: User Account registration details

Field Name Data Type DescriptionUser_Name Varchar User inputs the namePassword varchar User enters the passwordTable 2:User logIn Details

Field Name Data Type DescriptionUser_Name Varchar Admin inputs the namePassword Varchar Admin enters the passwordTable 3:Administrator log in Details

These therefore formed the requirements of the Jesus Summate System and were broadly classified in to the functional requirements and the Non-functional requirements.

4.1 Data Validation and Reliability Test

4.1.1 Input validationDue to the fact that the users will be expected to provide some input to the system, the

input data was expected to be validated. This data would be validated based on whether:

they provided the semantic meaning to the interfaces or enabled the expected behavior

based on the input. I simply changed the inputs from the expected ones to see whether the

system noted it and how it behaved with the wrong inputs.

4.1.2 Constraint validationThere are set conditions that are used within the system and which must be abided by.

These were based on the fact that though certain input was required, a given size was set

for that input. For instance, though integer is what is required, maybe the size of that

integer is 12 characters. To perform constraint validation for this case I provide an integer

that exceeded the 12 characters expected. Once the two validations had been passed by

my system, then I was confident that my system was valid and reliable in that case,

failure to which the system would neither be valid nor reliable. (Data Warehouse Toolkit,

Kimball, R, 1996).

4.2 Requirements Analysis and Test Cases

4.2.1 Functional Requirements 4.2.1.1 User Login

Description of Feature

This feature is used by the User (Client/Admin) to login in to the system. They are

required to key in the username and the password before they are granted permission

to enter the system. The username and the password will be verified and the invalid

username and password are not allowed to enter the system.

Stimulus/Response Sequences

Stimulus : User runs the system.

Response : System request for the username and the password.

Stimulus : User enters the username and the password at the textbox provided.

Response : System verifies the username and the password with the data inside the

database. If the username and the password do not match, some message will pop up

to notify the user that the information supplied was invalid. If valid, user successfully

login to the JS System.

Functional Requirements

-Username is provided when they register with the system.

-The system must only allow the user with valid username and password to enter the

system.

-The system must be able to perform authorization process which decides what the

user’s level can access to.

-The user must be able to logout after they are finished using the system.

4.2.1.2 Register a new discipleDescription of Feature

This feature will be used by the administrator to register a new member to the system so

that it can be availed to the users or the clients for the purchase process.

Stimulus/Response Sequences

Stimulus : The admin presses Add New disciple.

Response : System prompts add new disciple form.

Stimulus : User enters the member details in the form provided.

Response : System ensures that the information supplied by the user (Admin) is of

the correct form through the input type of the android textboxes. After the user

presses the submit button a message will be provided informing the user that the

information has successfully been entered in to the database.

Functional Requirements

-System must be able to verify the information.

-System must enter the correct information on the textboxes.

-Repeated information must be prevented from the system database.

4.2.1.3 View church activitiesDescription of Feature

This feature allows the user to view information about the church on a particular day.

Stimulus/Response Sequences

Stimulus: User selects the record from the list of the available menus.

Response: System searches the record from the database and displays the entire details to

the user.

Stimulus: The user selects a particular menu.

Response: If the user selects a menu, the system proceeds to display the details of that

menu.

Functional Requirements

-System must be able to show out the correct information about the church on that date.

-System must show the information correctly with the correct model.

4.2.1.3 Edit church InformationDescription of Feature

This feature will allow the admin user to edit the records of the church in the database.

Stimulus/Response Sequences

Stimulus: Admin selects the menu from the records to view the details to be edited.

Response: The System responds by displaying the entire details of that particular menu.

Stimulus: The Admin then selects the edit button;

Response: The system displays the records in an editable format to the admin user.

Stimulus: The User then edits the records as required based on his or her specification.

Response: The system displays the records as they appear prior to the update of the

database.

Stimulus: The user presses the update button.

Response: The System informs the user of the update success to the user.

Functional Requirements

-System must be able to fetch the correct details from the database and display them to

the user.

-System must inform the user of the update success once the record has successfully

updated.

-System must reflect the edited form of the information in the database on the interface.

4.2.2 Non-Functional Requirements4.2.2.1 Usability: The system should be easy to use providing the user with expected

results. The most relevant information is displayed.

4.1.2.1 Availability and Accessibility: The application should be up and running when

needed. It should have easily identifiable icon with a clear label.

4.1.2.2 Security requirements: This system must be highly secured in the login part.

This is because some of the privileges are only allowed for the admin level. The

other non-specialized tasks are allowed for the other users in the client and the

guest modules.

4.1.2.3 Extensibility: The system should be easy to extend to include the features that

will unfold in the future.

4.1.2.4 Portability: The app is usable to almost all android phones and screens.

4.1.2.5 Implementation requirements: In implementing the system, it uses java

(android) as the main programming language and tools. Besides that, the SQLite

language will be used to maintain the information in the database.

4.1.2.6 Reliability requirements: The system must perform accurately towards the

administrator request. For example, when the administrator saves the edited

details of the church, after he reviews the details later, they must be changed

according to the latest details that was updated. Moreover, the client is not

allowed to view the details that the administrator has. Besides that, the login form

will have validity check to ensure that only the authorized users gain access to the

system.

CHAPTER FIVE: IMPLEMENTATION AND DEPLOYMENT5.0 Implementation5.0.1 IntroductionIn this part and with the requirements quite clear, I embarked on the implementation of

the findings so far. It is in this stage that I developed the programs that will help meet the

expectations of the system. Moreover I developed the interfaces that will interact with the

various users of the system.

5.0.2 User Interfaces

The Jesus summate System is used by both the Administrator and the user as well and so

it was designed simply without so much use of colors. The interface is user friendly and

easy to use. This can be proving when the user knows what the button’s function is when

he or she looks at the button. This is due to the fact that the button’s text is clear and easy

to understand. For example when the user wants to log into the system, he or she uses

“Log In” as button’s text and not anything else.

Jesus summit Application4.3.4.1 Login Page.

This is the login page for the admin and is therefore designed without so much

colorful interface because it is used by the administrator which can be considered as

the backend. It simply requires the username textbox and the password textbox for the

admin user.

Figure 13: Admin login credentials

If the Login Credentials are wrong, then the following interface is displayed to the Admin

requesting him or her to supply correct credentials or register if the account does not

exist.

Figure 14:The message displayed when the credentials entered are wrong.

4.3.4.2 Main Admin Homepage

Figure 15:Admin view of the homepage

This is the main page for the administrator side of the Jesus summate System and it is in

this screen that the administrator can choose to add a new program or announcement to

be view by the user when they visit the system, view the available programs and

announcements that are currently being displayed to the user.

4.3.4.3 Insertion of a new church program

Figure 16:Form to insert new program details

This is the screen that is used by the administrator to add details of a new program that

will be available for the user users to view them and make an informed decision on

whether the specifications indicated meet their preference or not.

4.3.4.4 program update

Figure 17:List of the available motorcycles

The figure above shows a list of the available programs that is displayed to both the

administrator and the client as well. For the admin the list is only displayed for purposes

of modification in the form of editing or the removal of its contents. For the user this is

meant to enable them to see the available programs.

4.3.4.6 User Details

Figure 18:details to be edited

4.3.4.7 Client main Homepage

Figure 19:Client Main homepage

The figure above shows the main homepage that is viewed by the user and this has

several modules such as view of the available programs, songs and announcements.

4.3.4.8 Client viewing service programs

Figure 20:the user program view

The figure above shows the screen that is used by the user to see all deals of the church

program.

4.3.4.9 User viewing of announcements

Figure 21:user viewing of announcements.

The figure above indicates a screen that will be used by the user to view all the

announcements that are taking place in the church.

CHAPTER SIX: CONCLUSIONS AND RECOMMENDATIONS

6.1 LimitationsThe development of the Jesus Summate System that is capable of operating in a mobile

that uses android platform has not been as easy as it may appear as severally I’ve had to

face a number of challenges and these are listed below:

6.1.1 Information SourceInformation required to develop the application was not readily available on the Internet

and if it did, this was not direct despite the high internet connection. This did not only

apply for the source codes only but also did apply for the Literature review still. The

codes available on the internet required a bit of customization and thorough editing in

order to realize the required functionality. This was not easy as for the information such

as the codes to be edited they required to first be understood before procession to edit the

contents from their current form.

6.1.2 Unavailability and Uncooperative RespondentsMost of the requirements that my system were meant to use required greatly the

involvement of major participants of this church and therefore I had to visit some

members in their homes to try and gain the insight of the requirements. The challenge

behind this was that due to the fact that the church members are always busy with their

businesses and work schedules, it was hard getting one respondents from the group who

could set aside time and respond to the questions that I required to get answers for.

Similarly literacy and language barrier proved to be a major challenge as the respondents

had low literacy levels and in most cases relied on their mother tongue for the

communication which further required and intermediate translator.

6.1.3 Financial Incapacitation

Financial incapacitation has also continued to be a major challenge as the amount

required to regularly print the documents such as the questionnaires and the interview

questions was large. Similarly, travelling to meet the respondents of the questionnaires

and the interview still proved to be a major challenge.

6.1.4 Learning and implementing a new language

Considering that android is a new version of the Java programming language and despite

the fact that it holds a large number of similarities to those of Java, implementing and

learning it has not been easy though after regular interaction with the language it has

enabled me gain a greater insight on what it entails. Moreover, the implementation of the

unique part of my system has not been easy as it has had to involve proper understanding

of the language as well as the twist of the existing android source codes.

6.2 RecommendationsTo reverse the above problems and realize improvements in succeeding developments, I

would like to make the following recommendations.

6.2.1 Reduction in strictness of the Time deadlines

Owing to the fact that some of these issues cover some very new concepts, I would

recommend that the students be allowed to begin the project development at a quite early

time to build up on their Ideas and to complete early and meet the set deadlines by the

requirements.

6.2.2 Provision of project finances to the students

Due to the fact that some of the students are unable to meet the threshold required for

data and requirements capture, I would recommend that some special finances be

provided to act as the support for the students who face difficulties in the development

and research process.

6.2.3 Provision of a bias for the uncooperative respondents

The researchers in the future should be allowed to sample or select respondents even

from outside the group being studied to compensate for the respondents who are

uncooperative and unwilling to give the required information.

6.2.4 Compelling some institutions to pave way for the students to develop

Some institutions have been a major obstacle in the development of the projects and the

higher level institutions should compel them to release as well as loosen the restrictions

they have over their intellectual property such API (Application Programming Interface).

6.3 ConclusionIn conclusion I would like to say that taking this project all through has been a wonderful

experience for me and for the practical knowledge that I acquired, this would not have

materialized. This is a very important part of my cause and has helped me familiarize

with the market expectations of the course at large.

Church Intimation App is a necessity for mega churches. It helps every church believer to

feel part of the large community. Furthermore, it makes the presence of the church to be

felt more in the society. This increases the overall efficiency and performance of the

institution as we work towards achieving vision 2030.

References

Adobe.com,. (2015). Mobile app development | Adobe Developer Connection. Retrieved

15 June 2015, from http://www.adobe.com/devnet/devices/mobile-apps.html

Dye, E. (2010). The Big List of 20+ Bible Apps for Mobile Devices - ChurchMag.

ChurchMag. Retrieved 15 June 2015, from http://churchm.ag/the-big-list-of-20-bible-

apps-for-mobile-devices/

Mypocketchurch.com,. (2015). My Pocket Church App Features. Retrieved 15 June

2015, from http://www.mypocketchurch.com/app-features

Play.google.com,. (2015). Retrieved 15 June 2015, from

https://play.google.com/store/apps/details?

id=com.youthministrytoolbox.youthministryresources

Play.google.com,. (2015). Retrieved 15 June 2015, from

https://play.google.com/store/apps/details?id=com.app_rose129.layout