BB2

Certificate
St. Andrews College of Arts, Science & Commerce

St. Dominic Road, Bandra (W)
Mumbai-400 050.
This is to certify that the Project Report

on
LIFE IN JESUS MINISTRIES

Prepared by the following students of
Bachelor of Science (Information Technology)
(Semester 6)
EZEKIEL JOHN PAUL SEAT NO:- 4023682

Submitted as partial fulfillment for the award of the
B.Sc. (IT) degree from the University of Mumbai
During the Academic year 2016-17.
___________________ ________________
Internal Examiner External Examiner
_____________________ _______________
Co-ordinator, B.Sc. (IT) Principal
1
2
Internal Guide Signature Sheet:
Project Title: LIFE IN JESUS MINISTRIES
Team Members: Ezekiel John Paul Seat No:

4023682
Software Used:
WordPress.
Xampp.
___________________
Internal Guide
St. Andrews College, Bandra(W) / TYBScIT(2016-17)

3
ACKNOWLEDGMENT
This is a sincere effort from us to express my heartfelt

gratitude in creating the software LIFE IN JESUS MINISTRIES as
my BSc. IT Project.
I am thankful to our Principal Dr. Marie Fernandes for giving

support throughout the tenure of the course.
I am sincerely thankful to the Coordinators of B.Sc.- I.T Prof. A.N.S
Sarvani, Prof. Neeraj Shukla, Prof. Jenecia Menezes for their active
involvement, valuable suggestions and constant support during the
preparation of the project. Without their diligent and hard work it
would have not been possible for us to complete the project in
record time.
I also owe a debt of gratitude to all those who helped us in the
development of this book.
I am grateful to all the teaching and non-teaching staff, those

who directly and indirectly helped me to make this report a
successful one. I am also thankful to friends and family for helping
me out in making this project a big success.
This project imparted a great deal of practical experience, which

will be helpful to me in the near future.
----------------------------------------
Name: EZEKIEL JOHN PAUL
Seat no: 4023682

4
DECLARATION
I, Mr. EZEKIEL JOHN PAUL of St. Andrews College T.Y.BSc.I.T.

hereby declare that I have completed this project, LIFE IN JESUS
MINISTRIES site for a Pastor during the academic year 2016-
2017
This project work is done by me and is not a copy of any other

work. This information submitted herein is true to the best of my
knowledge.
---------------------------------------
Name: EZEKIEL JOHN PAUL
Seat no: 4023682

5
INDEX
Sr.
No. Contents Page No
1 Introduction 7
1.1 Need 8
2 SRS 10
2.1 Synopsis 10
2.2 Features 11
2.3 Software Specification 12
2.3.1 Front End 12

2.3.2 Back End
15
3 Software Development Life Cycle 22
3.1 Overview 23
3.2 System Development Phases 23
3.3 Phases in SDLC 24
4 Iterative Model 27
4.1 Iterative Model Design 28
4.2 Iterative Model Application 30

6
5 Diagrams 32
5.1 DFD 32
5.2 E-R Diagram 39
5.3 Use Case Diagram 41
5.4 State Chart Diagram 44
5.5 Activity Diagram 46
5.6 Gantt Chart 49
5.7 WBS 51
5.8 Data Dictionary 54
6 Testing 57
6.1 Testing Methods 58
6.2 Levels of Testing 59
7 Screenshots 65
8 Maintenance and Security 77
9 Future Enhancement 79
10 Conclusion 81
11 References 83

7
1. INTRODUCTION
Managing the activities of church poses a number of challenges. Handling all
the social networking sites to reach many people is not that easy as it requires
to promote the ministry from different social networking sites. As there are
many people who still dont know to use the mobiles which will help them to
communicate using social networking sites. Many of the people doesnt know
to access internet either, theyll just watch or use the specific site they are told
to use. Hence this site will help the church to promote their church activities
and many more to those people who dont know to use social networking sites
as they can just switch to this site and can be informed about all the activities
happening in the church. Rather than promoting the church activities using
different social networking sites the pastor can promote it from this one site to
all. People can even contact pastor for help and for prayer requests. People
can listen to the songs in 3 different languages and can watch videos/sermons
of pastor 24/7 using internet. They can also watch the live telecast of the
church service every Sunday if they cannot make it to the church for any
reason. They can watch it live at home. While the live video being telecasted if
they want to read the bible they dont need to go get their bible and read.
Theres a section for bible in the website where you can read bibles of more
than 50 versions and in different languages and the first page when someone
visits the site they will get to read the Verse of the day from bible which is
generated on daily basis. So this site will help people to stay connected with
church activities and God and even pastor can communicate with everyone not
just the church members to preach the gods word to the unreached souls.

8
1.1 Need
Currently pastor uses different social networking sites like WhatsApp,
Facebook, Twitter, Instagram and Blogspot to communicate with church
members by sending spiritual quotes, revelations, etc. But it is not possible
to reach everyone using these social networking sites. So the site Life In Jesus
Ministries will help pastor to reach everyone not only church members but
everyone. This will help to increase the communication between pastor and
people.

9
SRS

10
2. SOFTWARE REQUIREMENT SPECIFICATION
2.1. SYNOPSIS
LIFE IN JESUS MINISTRIES is a website that helps pastor to preach

gospel to the world by adding audios, videos, bibles. He can also
use this application to telecast the live Sunday service of the church
as it is linked with Facebook Live and since many people doesnt use
Facebook they cannot watch it if they miss the church for some
reason. So using this application they can watch the live telecast of
the Sunday service if they are unable to attend the church.
PHP is a server-side scripting language designed primarily for
web development but also used as a general-purpose programming
language. Originally created by Rasmus Lerdorf in 1994, the PHP
reference implementation is now produced by The PHP
Development Team. PHP originally stood for Personal Home Page,
but it now stands for the recursive acronym PHP: Hypertext
Preprocessor.
PHP code may be embedded into HTML or HTML5 markup, or it
can be used in combination with various web template systems, web
content management systems and web frameworks. PHP code is
usually processed by a PHP interpreter implemented as a module in
the web server or as a Common Gateway Interface (CGI)
executable. The web server software combines the results of the
interpreted and executed PHP code, which may be any type of data,
including images, with the generated web page. PHP code may also
be executed with a command-line interface (CLI) and can be used to
implement standalone graphical applications.
The goal of this project is to help people from switching into
multiple social networking sites to get in touch with pastor and
church activities.

11
2.2. FEATURES
Add Videos
Add Audios
Add Images
Link to Facebook Page
Link to YouTube Channel
Link to Twitter Handle
Link to Blogspot
Link to Facebook Live Video
Link to Read Bibles
Delete a Video
Delete an Audio
Delete an Image

12
2.3. SOFTWARE SPECIFICATION
2.3.1. FRONT END:-
WORDPRESS:-
WordPress is a free and open-source content management system (CMS)

based on PHP and MySQL. WordPress is installed on a web server that is
either part of an Internet hosting service or a network host in its own right.
The first case may be a service like WordPress.com, for example, and the
second case could be a computer running the software package
WordPress.org. A local computer may be used for single-user testing and
learning purposes. Features include a plugin architecture and a template
system. WordPress was used by more than 27.5% of the top 10 million
websites as of February 2017. WordPress is reportedly the most popular
website management or blogging system in use on the Web, supporting more
than 60 million websites.
WordPress was released on May 27, 2003, by its founders, Matt Mullenweg
and Mike Little,[10] as a fork of b2/cafelog. WordPress is released under the
GPLv2 (or later) license from the Free Software Foundation.
WordPress has a web template system using a template processor. Its
architecture is a front controller, routing all requests for non-static URIs to a
single PHP file which parses the URI and identifies the target page. This
allows support for more human-readable permalinks. Once downloaded,
WordPress installation files have a size of about 20 MB.

13
Themes:-
WordPress users may install and switch between different themes. Themes
allow users to change the look and functionality of a WordPress website
without altering the core code or site content. Every WordPress website
requires at least one theme to be present and every theme should be
designed using WordPress standards with structured PHP, valid HTML
(HyperText Markup Language), and Cascading Style Sheets (CSS). Themes
may be directly installed using the WordPress "Appearance" administration
tool in the dashboard, or theme folders may be copied directly into the
themes directory, for example via FTP. The PHP, HTML and CSS found in
themes can be directly modified to alter theme behavior, or a theme can be a
"child" theme which inherits settings from another theme and selectively
overrides features. WordPress themes are generally classified into two
categories: free and premium. Many free themes are listed in the WordPress
theme directory, and premium themes are available for purchase from
marketplaces and individual WordPress developers. WordPress users may
also create and develop their own custom themes. The free theme
Underscores created by the WordPress developers has become a popular
basis for new themes.
Plugins:-
WordPress' plugin architecture allows users to extend the features and
functionality of a website or blog. WordPress has over 49,394 plugins
available, each of which offers custom functions and features enabling users
to tailor their sites to their specific needs. These customizations range from
search engine optimization, to client portals used to display private
information to logged in users, to content management systems, to content
displaying features, such as the addition of widgets and navigation bars. Not
all available plugins are always abreast with the upgrades and as a result
they may not function properly or may not function at all.
Mobiles:-
Native applications exist for WebOS, Android, iOS (iPhone, iPod Touch, iPad),
Windows Phone, and BlackBerry. These applications, designed by Automatic,
allow a limited set of options, which include adding new blog posts and
pages, commenting, moderating comments, replying to comments in addition
to the ability to view the stats.

14
Other features:-
WordPress also features integrated link management; a search engine
friendly, clean permalink structure; the ability to assign multiple categories to
posts; and support for tagging of posts. Automatic filters are also included,
providing standardized formatting and styling of text in posts (for example,
converting regular quotes to smart quotes). WordPress also supports the
Trackback and Pingback standards for displaying links to other sites that
have themselves linked to a post or an article. WordPress posts can be edited
in HTML, using the visual editor, or using one of a number of plugins that
allow for a variety of customized editing features.
Multi-user and multi-blogging:-

Prior to version 3, WordPress supported one blog per installation, although
multiple concurrent copies may be run from different directories if configured
to use separate database tables. WordPress Multisites (previously referred to
as WordPress Multi-User, WordPress MU, or WPMU) was a fork of WordPress
created to allow multiple blogs to exist within one installation but is able to be
administered by a centralized maintainer. WordPress MU makes it possible
for those with websites to host their own blogging communities, as well as
control and moderate all the blogs from a single dashboard. WordPress MS
adds eight new data tables for each blog.
As of the release of WordPress 3, WordPress MU has merged with
WordPress.

15
2.3.2. BACK END:-
SQL SERVER (MYSQL):-
Database:-
A database is a separate application that stores a collection of data. Each
database has one or more distinct APIs for creating, accessing, managing,
searching and replicating the data it holds Other kinds of data stores can be
used, such as files on the file system or large hash tables in memory but data
fetching and writing would not be so fast and easy with those types of systems
So nowadays, we use relational database management systems (RDBMS) to
store and manage huge volume of data. This is called relational database
because all the data is stored into different tables and relations are established
using primary keys or other keys known as foreign keys
Relational Data Base Management System (RDBMS):-

Enables you to implement a database with tables, columns and indexes.
Guarantees the Referential Integrity between rows of various tables.
Updates the indexes automatically.
Interprets an SQL query and combines information from various tables.
RDBMS Terminology:-
Database: A database is a collection of tables, with related data
Table: A table is a matrix with data. A table in a database looks like a simple
spreadsheet
Column: One column (data element) contains data of one and the same kind,
for example the column postcode
Row: A row (= tuple, entry or record) is a group of related data, for example the
data of one subscription
Redundancy: Storing data twice, redundantly to make the system faster
Primary Key: A primary key is unique. A key value cannot occur twice in one
table. With a key, you can find at most one row.

16
Foreign Key: A foreign key is the linking pin between two tables.
Compound Key: A compound key (composite key) is a key that consists of
multiple columns, because one column is not sufficiently unique.
Index: An index in a database resembles an index at the back of a book.
Referential Integrity: Referential Integrity makes sure that a foreign key value
always points to an existing row.

17
PhpMyAdmin:-
phpMyAdmin is a free and open source tool written in PHP intended to handle
the administration of MySQL or MariaDB with the use of a web browser. It can
perform various tasks such as creating, modifying or deleting databases,
tables, fields or rows; executing SQL statements; or managing users and
permissions.
Features Of phpMyAdmin:
1. Web interface.
2. MySQL and MariaDB database management.
3. Import data from CSV and SQL.
4. Export data to various formats: CSV, SQL, XML, PDF (via the TCPDF
library), ISO/IEC 26300 - OpenDocument Text and Spreadsheet, Word, Excel,
LaTeX and others.
5. Administering multiple servers.
6. Creating PDF graphics of the database layout.
7. Creating complex queries using Query-by-Example (QBE).
8. Searching globally in a database or a subset of it
9. Transforming stored data into any format using a set of predefined
functions, like displaying BLOB-data as image or download-link
10.Live charts to monitor MySQL server activity like connections, processes,
CPU/Memory usage, etc.

18
MARIADB:-
MariaDB is a community-developed fork of the MySQL relational database

management system intended to remain free under the GNU GPL.
Development is led by some of the original developers of MySQL, who forked
it due to concerns over its acquisition by Oracle Corporation. Contributors are
required to share their copyright with the MariaDB Foundation.
MariaDB intends to maintain high compatibility with MySQL, ensuring a "drop-
in" replacement capability with library binary equivalency and exact matching
with MySQL APIs and commands.[6] It includes the XtraDB storage engine for
replacing InnoDB. as well as a new storage engine, Aria, that intends to be both
a transactional and non-transactional engine perhaps even included in future
versions of MySQL.

19
XAMPP CONTROL:-
XAMPP is a free and open source cross-platform web server solution stack
package developed by Apache Friends, consisting mainly of the Apache HTTP
Server, MariaDB database, and interpreters for scripts written in the PHP and
Perl programming languages. XAMPP stands for Cross-Platform (X), Apache
(A), MariaDB (M), PHP (P) and Perl (P).
It is a simple, lightweight Apache distribution that makes it extremely easy for
developers to create a local web server for testing and deployment purposes.
Everything needed to set up a web server server application (Apache),
database (MariaDB), and scripting language (PHP) is included in an
extractable file. XAMPP is also cross-platform, which means it works equally
well on Linux, Mac and Windows.
Since most actual web server deployments use the same components as
XAMPP, it makes transitioning from a local test server to a live server extremely
easy as well.
Features Of XAMPP:
1. XAMPP is regularly updated to the latest releases of Apache, MariaDB, PHP
and Perl. It also comes with a number of other modules including OpenSSL,
phpMyAdmin, MediaWiki, Joomla, WordPress and more.
2. Self-contained, multiple instances of XAMPP can exist on a single computer,
and any given instance can be copied from one computer to another.
3. XAMPP is offered in both a full and a standard version (Smaller version).

20
Software Used:
Documentation: Microsoft Office Word 2016.

Charts and Diagram: Microsoft Office Word 2016, Star UML,
EDraw Max.
Software requirements:
Windows Operating System: Windows 7 and Above.

Web browser e.g. Mozilla Firefox, Opera, Internet Explorer, MySQL
Server 2008, PhpMyAdmin(Localhost).
XAMPP Control(Apache & MySQL Port).
WordPress 4.7 & above
Hardware requirements:
Intel Pentium Dual (minimum)

Processor.
Minimum of 512MB RAM (Recommended)
50GB Hard disk for storage.
Processor-Dual Core and Later.

21
SDLC

22
3. Software Development Life Cycle

23
3.1 Overview
Software Development Life Cycle (SDLC) is a process used by the software

industry to design, develop and test high quality softwares. The SDLC aims to
produce a high-quality software that meets or exceeds customer expectations,
reaches completion within times and cost estimates. SDLC is the acronym of
Software Development Life Cycle.
It is also called as Software Development Process.
SDLC is a framework defining tasks performed at each step in the software
development process.
ISO/IEC 12207 is an international standard for software life-cycle processes.
It aims to be the standard that defines all the tasks required for developing and
maintaining software.
SDLC is a process followed for a software project, within a software
organization. It consists of a detailed plan describing how to develop, maintain,
replace and alter or enhance specific software. The life cycle defines a
methodology for improving the quality of software and the overall development
process.
3.2 System Development Phases
Systems Development Life Cycle (SDLC) adheres to important phases that

are essential for developers, such as planning, analysis, design, and
implementation and are explained in the section below. There are several
Systems Development Life Cycle Models in existence. The oldest model, that
was originally regarded as "the Systems Development Life Cycle" is the
waterfall model: a sequence of stages in which the output of each stage
becomes the input for the next. These stages generally follow the same basic
steps but many different waterfall methodologies give the steps different
names and the number of steps seems to vary between 4 and 6. There is no
definitively correct Systems Development Life Cycle model, but the steps can
be characterized and divided in several steps

24
3.3 Phases in SDLC
There are 6 phases in the development of any software. They are as follows:
Phase 1- Planning
Planning is the first phase of software development. In this phase the client
gives the details and concepts of his/her software and we plan the requirement
of resources, time & budget of the proposed development.
Phase 2 - Requirements Analysis

The requirements analysis phase is concerned with capturing the
requirements of the package. The requirements review is a meeting with the
aim of discussing these requirements. The final output of this phase is a formal
requirements document (Software Requirement Specification), which aims to
freeze the requirements at this point and will serve as input to the design
phase.
Phase 3 - Design
SRS is the reference for product architects to come out with the best
architecture for the product to be developed. Based on the requirements
specified in SRS, usually more than one design approach for the product
architecture is proposed and documented in a DDS - Design Document
Specification. This DDS is reviewed by all the important stakeholders and
based on various parameters as risk assessment, product robustness, design
modularity, budget and time constraints, the best design approach is selected
for the product. A design approach clearly defines all the architectural
modules of the product along with its communication and data flow
representation with the external and third party modules (if any). The internal
design of all the modules of the proposed architecture should be clearly
defined with the minutest of the details in DDS.
Phase 4 - Implementation
The implementation phase involves the actual coding/programming of the
software. The output of this phase is typically the library, executables and User
Manuals and additional software documentation.

25
Phase 5 - Testing and Integration

This stage is usually a subset of all the stages as in the modern SDLC models,
the testing activities are mostly involved in all the stages of SDLC. However,
this stage refers to the testing only stage of the product where product defects
are reported, tracked, fixed and retested, until the product reaches the quality
standards defined in the SRS. Integration refers to the practice of combining
individually tested software components into an integrated whole. Software is
integrated when components are combined into subsystems or when
subsystems are combined into products.
Phase 6 Maintenance
Once the product is tested and ready to be deployed it is released formally in
the appropriate market. Then based on the feedback, the product may be
released as it is or with suggested enhancements in the targeting market
segment. After the product is released in the market, its maintenance is done
for the existing customer base.

26
ITERATIVE MODEL

27
4. ITERATIVE MODEL
In Iterative model, iterative process starts with a simple
implementation of a small set of the software requirements and
iteratively enhances the evolving versions until the complete system is
implemented and ready to be deployed.
An iterative life cycle model does not attempt to start with a full
specification of requirements. Instead, development begins by
specifying and implementing just part of the software, which is then
reviewed in order to identify further requirements. This process is then
repeated, producing a new version of the software at the end of each
iteration of the model.

28
4.1 Iterative Model Design
At each iteration, design modifications are made and new

functional capabilities are added. The basic idea behind this method is
to develop a system through repeated cycles (iterative) and in smaller
portions at a time (incremental).
Following is the pictorial representation of Iterative and Incremental

model:

29
Iterative and Incremental development is a combination of both

iterative design or iterative method and incremental build model
for development. "During software development, more than one
iteration of the software development cycle may be in progress at
the same time." and "This process may be described as an
"evolutionary acquisition" or "incremental build" approach."
In incremental model the whole requirement is divided into

various builds. During each iteration, the development module
goes through the requirements, design, implementation and
testing phases. Each subsequent release of the module adds
function to the previous release. The process continues till the
complete system is ready as per the requirement.
The key to successful use of an iterative software development

lifecycle is rigorous validation of requirements, and verification & testing
of each version of the software against those requirements within each
cycle of the model. As the software evolves through successive cycles,
tests have to be repeated and extended to verify each version of the
software.

30
4.2 Iterative Model Application

Like other SDLC models, Iterative and incremental development has
some specific applications in the software industry. This model is most often
used in the following scenarios:
Requirements of the complete system are clearly defined and
understood.
Major requirements must be defined; however, some
functionalities or requested enhancements may evolve with time.
There is a time to the market constraint.
A new technology is being used and is being learnt by the
development team while working on the project.
Resources with needed skill set are not available and are planned
to be used on contract basis for specific iterations.
There are some high risk features and goals which may change in
the future.
Iterative Model Pros and Cons:
The advantage of this model is that there is a working model of the

system at a very early stage of development which makes it easier to find
functional or design flaws. Finding issues at an early stage of
development enables to take corrective measures in a limited budget.
The disadvantage with this SDLC model is that it is applicable only to large and
bulky software development projects. This is because it is hard to break a small
software system into further small serviceable increments/modules.

31
DIAGRAMS

32
5. DIAGRAMS
5.1 DATA FLOW DIAGRAM:
A data flow diagram (DFD) maps out the flow of information for any
process or system. It uses defined symbols like rectangles, circles and
arrows, plus short text labels, to show data inputs, outputs, storage
points and the routes between each destination. Data flowcharts can
range from simple, even hand-drawn process overviews, to in-depth,
multilevel DFDs that dig progressively deeper into how the data is
handled. They can be used to analyze an existing system or model a new
one. Like all the best diagrams and charts, a DFD can often visually say
things that would be hard to explain in words, and they work for both
technical and nontechnical audiences, from developer to CEO. Thats
why DFDs remain so popular after all these years. While they work well
for data flow software and systems, they are less applicable nowadays
to visualizing interactive, real-time or database oriented software or
systems.
Symbols and Notations Used in DFDs:
External entity: an outside system that sends or receives data,

communicating with the system being diagrammed. They are the
sources and destinations of information entering or leaving the
system. They might be an outside organization or person, a
computer system or a business system. They are also known as
terminators, sources and sinks or actors. They are typically drawn
on the edges of the diagram.

33
Process: any process that changes the data, producing an output.

It might perform computations, or sort data based on logic, or
direct the data flow based on business rules. A short label is used
to describe the process, such as Submit payment.
Data store: files or repositories that hold information for later use,
such as a database table or a membership form. Each data store
receives a simple label, such as Orders.
Data flow: the route that data takes between the external entities,
processes and data stores. It portrays the interface between the
other components and is shown with arrows, typically labeled with
a short data name, like Billing details.

34
0-LEVEL DFD:

35
1-LEVEL DFD:

36
2-LEVEL DFD:
2.1-LEVEL DFD:

37
2.2-LEVEL DFD:

38
2.3-LEVEL DFD:

39
5.2 Entity Relationship Diagram (ER diagram)
An entity-relationship model is a systematic way of describing and

defining a business process. The process is modeled as components
(entities) that are linked with each other by relationships that express the
dependencies and requirements between them, such as: one building
may be divided into zero or more apartments, but one apartment can only
be located in one building. Entities may have various properties
(attributes) that characterize them. Diagrams created to represent these
entities, attributes, and relationships graphically are called entity
relationship diagrams.
An ER model is typically implemented as a database. In the case of a
relational database, which stores data in tables, which represent the
entities? Some data fields in these tables point to indexes in other tables;
such pointers represent the relationships.
The three schema approach to software engineering uses three levels of
ER models that may be developed.
Benefits of ER diagrams:
ER diagrams constitute a very useful framework for creating and

manipulating databases. First, ER diagrams are easy to understand and
do not require a person to undergo extensive training to be able to work
with it efficiently and accurately. This means that designers can use ER
diagrams to easily communicate with developers, customers, and end
users, regardless of their IT proficiency. Second, ER diagrams are readily
translatable into relational tables which can be used to quickly build
databases. In addition, ER diagrams can directly be used by database
developers as the blueprint for implementing data in specific software
applications. Lastly, ER diagrams may be applied in other contexts such
as describing the different relationships and operations within an
organization.
An entity-relationship model is a systematic way of describing and
defining a business process. The process is modeled as components
(entities) that are linked with each other by relationships that express
the dependencies and requirements between them, such as: one
building may be divided into zero or more apartments, but one apartment
can only be located in one building. Entities may have various properties
(attributes) that characterize them. Diagrams created to represent
these entities, attributes, and relationships graphically are called entity
relationship diagrams.

40
An ER model is typically implemented as a database. In the case

of a relational database, which stores data in tables, which represent the
entities? Some data fields in these tables point to indexes in other tables;
such pointers represent the relationships.
The three schema approach to software engineering uses three levels
of ER models that may be developed.

41
5.3 Use Case Diagram:

A use case diagram at its simplest is a representation of a user's
interaction with the system and depicting the specifications of a use
case. A use case diagram can portray the different types of users of a
system and the various ways that they interact with the system. This type
of diagram is typically used in conjunction with the textual use case and
will often be accompanied by other types of diagrams as well.
Use Case Diagram objects
Use case diagrams consist of 4 objects:
Actor
Use case
System
The objects are further explained below.
Actor
Actor in a use case diagram is any entity that performs a role in one given
system. This could be a person, organization or an external system and
usually drawn like skeleton shown below.

42
Use Case
A use case represents a function or an action within the system. Its
drawn as an oval and named with the function.
System
System is used to define the scope of the use case and drawn as a
rectangle. This an optional element but useful when your visualizing
large systems. For example you can create all the use cases and then
use the system object to define the scope covered by your project. Or
you can even use it to show the different areas covered in different
releases.
Extend Relationship Between Two Use Cases
Many people confuse the extend relationship in use cases. As the name
implies it extends the base use case and adds more functionality to the
system. Symbol: <<extend>>.

43
Include Relationship Between Two Use Cases
Include relationship show that the behavior of the included use case is
part of the including (base) use case. The main reason for this is to
reuse the common actions across multiple use cases. In some
situations this is done to simplify complex behaviors. Symbol:
<<include>>

44
5.4 State Chart Diagram

State diagrams are used for classes where it is necessary to
understand the behavior of the object through the entire system. Not all
classes will require state diagram and state diagrams are not useful for
describing the collaboration of all object in a use case.
State diagrams are used to describe the behavior of a system, state
diagrams can describe the possible states of an object as event occurs.
Each diagram usually represents objects of a single class and tracks the
different states of its objects through the system.
It describes different states of a component in a system. The
states are specific to a component/object of a system. They define
different state of object during its lifetime. And these states are changed
by events.
State Transitions:
Entry action An action that is executed when a state is entered.

Exit action An action that is executed when a state is exited.
External Transition A response to an event that causes a change
of state.
Internal Transition A response to an event that causes the execution of

an action but does not cause a change of state.

45

46
5.5 Activity Diagram

Activity diagram is another important diagram in UML to describe
dynamic aspects of the system.
Activity diagram is basically a flow chart to represent the flow

from one activity to another activity. The activity can be described
as an operation of the system.
So the control flow is drawn from one operation to another. This

flow can be sequential, branched or concurrent. Activity
diagrams deals with all type of flow control by using different
elements like fork, join etc.
Purpose:
The basic purposes of activity diagrams are similar to other four
diagrams. It captures the dynamic behavior of the system. Other four
diagrams are used to show the message flow from one object to another
but activity diagram is used to show message flow from one activity to
another.
Activity is a particular operation of the system. Activity diagrams

are not only used for visualizing dynamic nature of a system but they are
also used to construct the executable system by using forward and
reverse engineering techniques. The only missing thing in activity
diagram is the message part.
It does not show any message flow from one activity to another.
Activity diagram is some time considered as the flow chart. Although the
diagrams looks like a flow chart but it is not. It shows different flow like
parallel, branched, concurrent and single.

47
Admin Module:

48
User Module:

49
5.6 GANTT CHART

Gantt charts illustrate the start and finish dates of the terminal
elements and summary elements of a project. Terminal elements and
summary elements comprise the work breakdown structure of the
project. Modern Gantt charts also show the dependency (i.e.
precedence network) relationships between activities. Gantt charts can
be used to show current schedule status using percent-complete
shadings and a vertical "TODAY" line as shown here.
Gantt chart is a project management tool used to schedule,
organize and coordinate tasks within a project. The Gantt chart is named
After Charles Gantt, and did not an acronym. It is a schedule (time
ordered Listing) of planned events.
1. Gantt chart is useful tools for planning and scheduling project
2. It allows you to assess how long a project should take.
3. It lay out the order in which tasks need to be carried out.
4. It helps manage the dependencies between tasks.
5. It determines the resources needed.
6. It is useful tools when a project is under way.
7. It monitors progress. You can immediately see what should have

been achieved at a point in time.
8. It allows you to see how remedial action may bring the project back
on course.
9. It is useful way to present the general flow of the projects Tasks.

Such charts are particularly useful for coordinating multiple
Activities.

50
10. It also provides a useful way to track project Progress against the
plan and schedule.

51
5.7 Work Breakdown Structure
A Work Breakdown Structure (WBS) is a key project deliverable

that organizes the team's work into manageable sections. The work
breakdown structure visually defines the scope into manageable chunks
that a project team can understand, as each level of the work breakdown
structure provides further definition and detail. An easy way to think
about a work breakdown structure is as an outline or map of the specific
project. The project team creates the project work breakdown structure
by identifying the major functional deliverables and subdividing those
deliverables into smaller systems and sub-deliverables. These
subdeliverables are further decomposed until a single person can be
assigned. The work breakdown structure has a number of benefits in
addition to defining and organizing the project work. A project budget
can be allocated to the top levels of the work breakdown structure, and
department budgets can be quickly calculated based on the each
project's work breakdown structure. By allocating time and cost
estimates to specific sections of the work breakdown structure, a
project schedule and budget can be quickly developed. As the project
executes, specific sections of the work breakdown structure can be
tracked to identify project cost performance and identify issues and
problem areas in the project organization.
Project work breakdown structures can also be used to identify
potential risks in a given project. If a work breakdown structure has a
branch that is not well defined then it represents a scope definition risk.
These risks should be tracked in a project log and reviewed as the
project executes. By integrating the work breakdown structure with an
organizational breakdown structure, the project manager can also
identify communication points and formulate a communication plan
across the project organization.

52
When a project is falling behind, referring the work breakdown

structure will quickly identify the major deliverables impacted by a failing
work package or late sub- deliverable. The work breakdown structure
can also be color coded to represent sub- deliverable status. Assigning
colors of red for late, yellow for at risk, green for on-target, and blue for
completed deliverables is an effective way to produce a heat-map of
project progress and draw management's attention to key areas of the
work breakdown structure.
Creating a Work Breakdown Structure is a team effort and is the
culmination of multiple inputs and perspectives for the given project.
One effective technique is to organize a brainstorming session with the
various departments that will be involved with the project. Project teams
can use low-technology tools like a white board, note cards, or sticky
note pads to identify major deliverables, sub-deliverables, and specific
work packages. These cards can be taped to a wall and reorganized as
the team discusses the major deliverables and work packages involved
in the project.

53

54
5.8 Data Dictionary
Admin table:
Column Type Contraints Comments
ID int(5) Primary Key Unique no generated

when admin adds a
user
user_login varchar(60) Not Null Username of the user
user_pass varchar(255) Not Null Password of the user
user_nicename varchar(50) Not Null Nickname of the user
user_email varchar(100) Not Null Email id of the user
user_url varchar(100) Not Null Url assigned to the
user
user_registered datetime Not Null The time when user
registered
user_activation_key varchar(100) Not Null Activation key of the
user
user_status int(11) Not Null Status of the user
display_name varchar(250) Display name of the
user
Audio table:
Column Type Constraints Comments
audio_id int(5) Primary key Unique no generated

when admin adds an
audio
audio_name varchar(20) Not Null Necessary for the
identity of audio
Audio longblob Not Null Format of audio

55
Video table:
video_id int(5) Primary key Unique no generated

when admin adds an
video
video_name varchar(20) Not Null Necessary for the
identity of video
video longblob Not Null Format of video
Image table:
image_id int(5) Primary key Unique no generated

when admin adds an
image
image_name varchar(20) Not Null Necessary for the
identity of image
image longblob Not Null Format of image

56
TESTING

57
6. Testing
Software testing is a critical element of software quality assurance and

represents the ultimate review of specification, design and coding. In
fact, testing is the one step in the software engineering process that
could be viewed as destructive rather than constructive.
A strategy for software testing integrates software test case design
methods into a wellplanned series of steps that result in the successful
construction of software.
Testing is the set of activities that can be planned in advance and
conducted systematically.
The underlying motivation of program testing is to affirm software

quality with methods that can economically and effectively apply to both
strategic to both large and small-scale systems.

58
6.1 TESTING METHODS:
WHITE BOX TESTING:
White box testing is when the tester has access to the internal data structures
and algorithms including the code that implement these.
White-box testing (also known as clear box testing, glass box testing,
transparent box testing, and structural testing) is a method of testing software
that tests internal structures or workings of an application, as opposed to its
functionality (i.e. black-box testing). White-box testing can be applied at the
unit, integration and system levels of the software testing process.
BLACK-BOX TESTING:
Black-box testing treats the software as a "black box", examining functionality
without any knowledge of internal implementation. The testers are only aware
of what the software is supposed to do, not how it does it. Black-box testing
methods include: equivalence partitioning, boundary value analysis, all-pairs
testing, state transition tables, decision table testing, fuzz testing, model-
based testing, use case testing, exploratory testing and specification-based
testing.
One advantage of the black box technique is that no programming knowledge

is required. Whatever biases the programmers may have had, the tester likely
has a different set and may emphasize different areas of functionality.

59
6.2 LEVELS OF TESTING:

There are different levels during the process of testing. In this
chapter, a brief description is provided about these levels.
Levels of testing include different methodologies that can be used while

conducting software testing. The main levels of software testing are:
Functional Testing
This is a type of black-box testing that is based on the specifications of the

software that is to be tested. The application is tested by providing input and
then the results are examined that need to conform to the functionality it was
intended for. Functional testing of a software is conducted on a complete,
integrated system to evaluate the system's compliance with its specified
requirements.
Unit Testing:
This type of testing is performed by developers before the setup is handed

over to the testing team to formally execute the test cases. Unit testing is
performed by the respective developers on the individual units of source code
assigned areas. The developers use test data that is different from the test
data of the quality assurance team.

60
Integration Testing:
Integration testing is defined as the testing of combined parts of an application

to determine if they function correctly. Integration testing can be done in two
ways:
Bottom-up integration testing:
This testing begins with unit testing, followed by tests of progressively higher-
level combinations of units called modules or builds.
Top-down integration testing:
In this testing, the highest-level modules are tested first and progressively,
lower-level modules are tested thereafter.
System Testing:
System testing tests the system as a whole. Once all the components are
integrated, the application as a whole is tested rigorously to see that it meets
the specified Quality Standards. This type of testing is performed by a
specialized testing team. System testing is the first step in the Software
Development Life Cycle, where the application is tested as a whole.
The application is tested thoroughly to verify that it meets the functional and
technical specifications. The application is tested in an environment that is
very close to the production environment where the application will be
deployed. System testing enables us to test, verify, and validate both the
business requirements as well as the application architecture.

61
Regression Testing:
Whenever a change in a software application is made, it is quite possible that

other areas within the application have been affected by this change.
Regression testing is performed to verify that a fixed bug hasn't resulted in
another functionality or business rule violation.
The intent of regression testing is to ensure that a change, such as a bug fix
should not result in another fault being uncovered in the application. Minimize
the gaps in testing when an application with changes made has to be tested.
Testing the new changes to verify that the changes made did not affect any
other area of the application.
Acceptance Testing:
This is arguably the most important type of testing, as it is conducted by the

Quality Assurance Team who will gauge whether the application meets the
intended specifications and satisfies the clients requirement. The QA team
will have a set of pre-written scenarios and test cases that will be used to test
the application.
More ideas will be shared about the application and more tests can be
performed on it to gauge its accuracy and the reasons why the project was
initiated. Acceptance tests are not only intended to point out simple spelling
mistakes, cosmetic errors, or interface gaps, but also to point out any bugs in
the application that will result in system crashes or major errors in the
application. By performing acceptance tests on an application, the testing
team will deduce how the application will perform in production.

62
Alpha Testing:
This test is the first stage of testing and will be performed amongst the
teams. Unit testing, integration testing and system testing when combined
together is known as alpha testing.
Beta Testing:
This test is performed after alpha testing has been successfully performed. In
beta testing, a sample of the intended audience tests the application. Beta
testing is also known as pre-release testing.
Non-Functional Testing:
Non-functional testing involves testing a software from the requirements

which are non-functional in nature but important such as performance,
security, user interface, etc.
Performance Testing:
It is mostly used to identify any bottlenecks or performance issues rather than

finding bugs in a software. Performance testing can be either qualitative or
quantitative and can be divided into different sub-types such as Load testing
and Stress testing.

63
Usability Testing:
Usability testing is a black-box technique and is used to identify any error(s)

and improvements in the software by observing the users through their usage
and operation.
Security Testing:
Security testing involves testing a software in order to identify any flaws and
gaps from security and vulnerability point of view.
Portability Testing:
Portability testing includes testing a software with the aim to ensure its
reusability and that it can be moved from another software as well. Portability
testing can be considered as one of the sub-parts of system testing, as this
testing type includes overall testing of a software with respect to its usage over
different environments. Computer hardware, operating systems, and
browsers are the major focus of portability testing.

64
7.SCREENSHOTS

65
1. Home Page

66
2. About Us

67

68
3. Live

69
4. Audios
5. Videos

70

71
6. Bibles

72
7. Contact Us

73
8. Social Media Pages

8.1. Facebook
8.2. Twitter

74
8.3. YouTube
8.4. Instagram

75
8.4. Blogspot

76
MAINTENANCE &
SECURITY

77
8. MAINTENANCE & SECURITY
MAINTENANCE:
Since the system has very critical data and other personal details, taking
back-up is very much essential. Archiving the unwanted records to save
memory and reduce load over database in order to increase the database
processing time and database efficiency. Finally as far the maintenance is
concerned proper updates has to be done time to time.
Security:
The application is provided with the authentication feature so that only

the administrator can access the application. Without entering proper
user name and password user cannot make any changes in the
application. They can only view the contents and browse through the
contents but cannot add/remove contents in the application.

78
FUTURE
ENHANCEMENT

79
9. FUTURE ENHANCEMENT
It is not possible to build a system that incorporates all the

requirements of the user. User requirements keep changing as the system is
being used. Some of the future enhancements that can be done to this system
are:
As the technology emerges, it is possible to upgrade the system

and can be adaptable to desired environment.
Based on the future security issues, security can be improved
using emerging technologies.
And in future maybe we develop an android app for our church so
that the people can access the application anywhere and can
experience gods love.
In short, according to the future need, the development of the

system will be done more over users access to the application that
they may be able to upload any video or audio or they can download
any media from the application, the database & the security levels in
the systems.

80
CONCLUSION

81
9. CONCLUSION
The project LIFE IN JESUS MINISTRIES is used for computerizing

the activities of the church. The application takes care of some
requirements of the church. It helps reduce the use of more social .
networking sites to reach people and spread the word of God.
It provides the Bible Quote Of The Day as soon as the user opens
the homepage and it changes on daily basis. The application is also
linked to other social media pages of the church so that people can
connect and communicate with pastor as all the social media pages
are handled by pastor itself.

82
REFERENCES

83
10. REFERENCES
1. https://www.wordpress.org
2. https://www.github.com/wordpress
3. https://www.youtube.com
4. https://bitnami.com
5. https://www.w3schools.com
6. https://www.edrawsoft.com

BB2

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BB2

Hochgeladen von

Copyright:

Verfügbare Formate

Certificate

St. Andrews College of Arts, Science & Commerce

This is to certify that the Project Report

LIFE IN JESUS MINISTRIES

EZEKIEL JOHN PAUL SEAT NO:- 4023682

Internal Guide Signature Sheet:

Project Title: LIFE IN JESUS MINISTRIES

Team Members: Ezekiel John Paul Seat No:

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

This is a sincere effort from us to express my heartfelt

I am thankful to our Principal Dr. Marie Fernandes for giving

I am grateful to all the teaching and non-teaching staff, those

This project imparted a great deal of practical experience, which

Name: EZEKIEL JOHN PAUL

Seat no: 4023682

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

I, Mr. EZEKIEL JOHN PAUL of St. Andrews College T.Y.BSc.I.T.

This project work is done by me and is not a copy of any other

Name: EZEKIEL JOHN PAUL

Seat no: 4023682

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

2.3 Software Specification 12

2.3.1 Front End 12

3 Software Development Life Cycle 22

3.2 System Development Phases 23

3.3 Phases in SDLC 24

4.1 Iterative Model Design 28

4.2 Iterative Model Application 30

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

5.2 E-R Diagram 39

5.3 Use Case Diagram 41

5.4 State Chart Diagram 44

5.5 Activity Diagram 46

5.6 Gantt Chart 49

5.8 Data Dictionary 54

6.1 Testing Methods 58

6.2 Levels of Testing 59

8 Maintenance and Security 77

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

2. SOFTWARE REQUIREMENT SPECIFICATION

LIFE IN JESUS MINISTRIES is a website that helps pastor to preach

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

2.3. SOFTWARE SPECIFICATION

2.3.1. FRONT END:-

WordPress is a free and open-source content management system (CMS)

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

Multi-user and multi-blogging:-

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

2.3.2. BACK END:-

SQL SERVER (MYSQL):-

Relational Data Base Management System (RDBMS):-

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

MariaDB is a community-developed fork of the MySQL relational database

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

St. Andrews College, Bandra(W) / TYBScIT(2016-17)

Documentation: Microsoft Office Word 2016.

Windows Operating System: Windows 7 and Above.