echurchgive: development priorities and functional requirements

8/13/2019 eChurchGive: Development Priorities and Functional Requirements

1/8

eChurchGive: Development Priorities and Functional

Requirements

Well use this document to make sure the developers are spending their time on the features

that are most important to the stakeholders. These priorities are a work-in-progress, so if

anything is inaccurate or changes, please let us know!

Note: Instead of editing this page directly, please use comments. To comment on the whole

document, click on the Comments button near the top right of the screen. You can add a

comment to a particular part of the document by selecting a section of text, then going to the

Insert menu at the top of the page and choosing Comment. A little box will appear on the side of

the screen and the commented text will become highlighted. Commented text looks like this. You

can also see all comments (including resolved ones) by clicking on the Comments button at the

top right of the page.

Googles explanation of comments is here, and their tutorial for all of Google Docs is here.
https://support.google.com/docs/bin/answer.py?hl=en&answer=143206https://support.google.com/docs/bin/answer.py?hl=en&answer=143298&topic=21014&ctx=topic


2/8

Required (Primary) Features

These are the things the app mustbe able to do by June 8th. They will be implemented for the

iPhone, iPad, and will be available as an application that will function properly on any of the

popular desktop browsers. These features directly add value for the stakeholders. They are

ordered from most to least important.

1. Donations

2. Video streaming

3. Featured pastor page

4. Daily reading page

5. Why I Give


3/8

Infrastructure (Secondary) Features

These are things that are required to make primary features work, but do not directly add value

for the stakeholders. These are ordered from most to least important.

1. Login/registration (this will be a pop-up via a link on each page. It will also pop-up when

the user does something that they need to be logged in to do)

a. As a donor

b. As a church

2. Finance handling

a. Register debit/credit card (this will exist as a pop-up when the user adds or edits

a card in the MyGiving view or the preferences view)

b. MyGiving donation page

i. Choose/find a church list (this will be created as a separate view but will

not be accessible through the tabs. It will be accessible from the MyGiving

view and the preferences view)

1. From here you can get to a churchs profile view (name, location,

etc.)

ii. There will be a few cases here:

1. Registered user giving to a member church

2. Registered user giving to a non-member church

a. Pop-up to announce 4% transaction fee

b. Make sure the user realizes that they are still responsible

for their donation even if they give it to the wrong church

unintentionally

3. Non-registered user giving to a member church

4. Anonymous user giving to a member church

iii. Create a code snippet generator similar to,

https://www.paypal.com/us/cgi-bin/?cmd=_donate-intro-outside, that is

embeddable in a churchs website. It will lead to a page that allows the

donor to donate to a registered church even if the donor is not a member.

This will not incur the 4% fee.

c. Donation history

i. Donor

ii. Church

3. Preferences

a. Phone handset needs to remember certain preferences

b. Preferred church

c. Preferred card
http://www.google.com/url?q=https%3A%2F%2Fwww.paypal.com%2Fus%2Fcgi-bin%2F%3Fcmd%3D_donate-intro-outside&sa=D&sntz=1&usg=AFQjCNG5iCMjm3MaSBasfk-WsAZ0Av0Z1whttp://www.google.com/url?q=https%3A%2F%2Fwww.paypal.com%2Fus%2Fcgi-bin%2F%3Fcmd%3D_donate-intro-outside&sa=D&sntz=1&usg=AFQjCNG5iCMjm3MaSBasfk-WsAZ0Av0Z1whttp://www.google.com/url?q=https%3A%2F%2Fwww.paypal.com%2Fus%2Fcgi-bin%2F%3Fcmd%3D_donate-intro-outside&sa=D&sntz=1&usg=AFQjCNG5iCMjm3MaSBasfk-WsAZ0Av0Z1w


4/8

d. Preferred donation amount

e. Preferred donation scheduling

f. Auto-login


5/8

Desired (Tertiary) Features

These are things that well implement if we finish ahead of schedule, but that are not as

important as the primary features or their supporting secondary functionalities.

1. Transaction history

a. For churches to see the details of each individual donation that they receive

2. Offerings

a. Add a new cause

b. View causes

3. Social media integration for discussion, blogging, devotions, and prayer

a. Ability to promote

i. a church

ii. an offering

iii. a pastor

b. Twitter

i. Login

ii. The user can tweet or view tweets about a specific church or

eChurchGive in general

c. Facebook

i. Login

ii. Post to timeline

4. Advertising

a. Advertising space in certain views

b. Admin view to add new advertisements

5. Streaming pay-per-view (see ONeils comment 2:53 5/21)

6. Marketplace

a. For each church

i. Event tickets

ii. Bookstore

b. For eChurchGive

i. Bookstore

7. Church calendar

a. Scheduling ability for churches to make sure the application and its user know

when the streams will be available.

8. Digital Bible

9. Language options

a. Spanish

10. Drag and drop video files from desktop to web app to upload.


6/8


7/8

Required (Primary) Platforms

These are the operating systems, browsers, and devices that we mustsupport. Note:There will

not be much code that will be shared between different operating systems for the native apps it

will have to be rewritten almost entirely. Code used between browsers will be very similar but will

not share similarities with the code from the native apps.

1. iOS

a. iPhone

b. iPad

2. Browsers for mobile (order based on:

http://gs.statcounter.com/#mobile_browser-ww-monthly-201105-201205as of May 2012)

a. Opera

b. Android

c. iPhone
http://www.google.com/url?q=http%3A%2F%2Fgs.statcounter.com%2F%23mobile_browser-ww-monthly-201105-201205&sa=D&sntz=1&usg=AFQjCNFUFVBdMzXoMDUFImQPXBTmkwNjDw


8/8

Desired (Secondary) Platforms

These are the platforms that well support if we finish ahead of schedule.

1. Browsers for desktops, laptops, and tablets (order based on:

http://www.w3schools.com/browsers/browsers_stats.aspas of April 2012)

a. Chrome

b. Firefox

c. Internet Explorer

d. Safari

2. Android

a. Phones

b. Tablets

3. Windows

a. Phones

b. Tablets
http://www.google.com/url?q=http%3A%2F%2Fwww.w3schools.com%2Fbrowsers%2Fbrowsers_stats.asp&sa=D&sntz=1&usg=AFQjCNFs1yUXHrJ53XlEFja0nXS1Tetqbw

echurchgive: development priorities and functional requirements

Documents