West Shore Survey System Milestone 2 Team Members: Brad Coverdale: Liaison, Requirements gathering Chris Dries: Web Designer, Quality control Christina.

Slides:

Advertisements

Similar presentations

©2013 by Transforming Churches Network Opening Doors to Your Community Through Seasons of Discovery.

Advertisements

Presented by Group: 110: Byron Sinclair, Jacob Alexander, and Manmeet Singh.

 84% more likely to be a high vital church  48% more likely to be a high attendance church  54% more likely to be a high growth church  30% more likely.

First Baptist Church Dover 2012 Survey. About Our Members:

Prepared by: Aiza Obalan. As part of QASD’s initiative on ensuring quality and improving our service, ONLINE EEI survey was created to easily gather information.

Enlighten V2.2 Manual – Super Admin Level Access Healthcare Training Section 1 Jayex Technology Limited Enlighten V2.2 – Super Admin Aug.

Project Proposal.

A strategic initiative of the Pacific Northwest Conference of the Free Methodist Church aimed at helping pastors and ministry leaders live and lead from.

Best Practices in the Use of Managerial Simulation Games-Based Learning Jindra Peterková.

Start. Directions Multiple choose. About team roles: leader, time keeper, information gather, recorder, and reporter. Select the answer that sounds best.

Code Walkers Final Presentation Report Ethan Bowyer Andrew Doyle Chad Sloan Stephanie Shaver.

Kodak Kiosk Locator Team kiLO Shawn Ellis Tom Guzewich Lora Magliocco Amanda Merritt Nick Shaw.

: Database Project : Database Project Chris Allen Brian Johnson Sean McIntire Brad Spegel.

Project Access Hope BIS 412 Systems Analysis and Design Applications Spring 2004 Project Developers: Philip Kelly Joseph Shaughnessy Daniel Vickers Project.

8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.

West Shore Survey System Team Members: Brad Coverdale Chris Dries Christina Felts Josh Henry.

West Shore Survey System Bradley Coverdale: Liaison, Tester Christopher Dries: Web Designer, JSP Christina Felts: PowerPoint Presentation, MySQL Modeling.

Team Members: Brian Barnes Jason Featherman Matt DeWitt Chris Blanchard.

Virtual Cell Support Software: User Interface Worldwide Web Instructional Committee, North Dakota State University, Fargo, ND.

FSH Technologies Requirements Specification October 31, 2011.

Team Project IS 485, Professor Matt Thatcher. 2 Agenda l Review l Team project –project overview –team feedback –milestones l Questions?

HELP Ministries – Final Presentation Team: Dave Hess, Ria Ghose, Bobby Lusk.

Lesson 10: IT Project and Program Management. Lesson 10 Objectives  Identify resources for technical data  Identify project management fundamentals.

1 CMPT 275 Software Engineering Requirements Analysis Phase Overview of Requirements Analysis Activity System Context Diagrams.

Church Health Team Agenda Overview of Natural Church Development

Speech Recognition Calculator ECE L02 - Group 8 Alfredo Herrera John Holmes Josh Liang Alex Kee.

Collections Management Museums Record Level Security Brad Lickman KE Software.

Timecales Start Finish Milestones Can be shown using a Gantt chart or written as a list.

WordNet CMS Presented By: Konkani NLP team Goa University.

ICELW, New York, June PROJECT USABILITY : SCHMOOSABILITY …what does it matter?

CS499 Use Cases References From Alistair Cockburn Writing Effective Use Cases (Book) - Use Case.

PYLBO Put Your Life in Better Order. Team Milko - developer, R & D, web application Rusko - developer (DB), sales Chris - marketing, design, finances.

Project Progress Document Optimization 5 April 2007 Team members: Chris Catalano Chun-Yu Chang Chris Joson David Matthes.

ITS Communication Plan: Focus Group & Survey Findings Raechelle Clemmons November 25, 2008.

Allen Stauffer Rarihwenhawi LaFrance.  University students often lack time to keep track of grades and monitor progress  System would focus on providing.

Chapter 4: Decision Making with Control Structures and Statements JavaScript - Introductory.

What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.

Project 3 Cookie Cutters Kevin Huynh Sean Tsusaki Jordaniel Wolk.

IT 499 Bachelor Capstone Week 4. Adgenda Administrative Review UNIT three UNIT Four Project UNIT Five Preview Project Status Summary.

Chapter 12 Evaluating Products, Processes, and Resources.

Working faithfully? Findings from the October st Century Evangelicals report on work.

Design & Development Scott Battaglia Rutgers, the State University of New Jersey.

1 Project 5: New Venue. 2 New Venue Based on the posted New Venue scenario 077_Ticket_Booth_Scenarios.pdf.

Step 4 Presenter: Updated 6/21/2013. Training Overview Introduction Walk Through Step 4 Scheduled FET Trainings & Completion Dates for FET Step(s) Question(s)

HCI: JCU Workflow Re-Design 2010 SP2: CP3301/CP5607 Human Computer Interaction Angela McCarthy Glenn Molochino Laurence Tardiani.

Prepared by : Dinesh Bajracharya Nepal Information System Development.

Brief Overview of EP3 Church Planting Software Tools Developed by Mission Aviation Fellowship.

100 Category #1 Category #2 Category #3 Category #4 Category #

BY BRITTANY PITCHER & CHRIS SMITH WorkWORLD “Empowerment Through Decision Support Technology”

Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.

Preparatory Groundwork For facilitators of a community assessment Programme Identify subject area Decide on date, time and place Decide on tools Identify.

Web-based Front End for Kraken Jing Ai Jingfei Kong Yinghua Hu.

Archdiocesan Pastoral Planning Commission’s Proposal On Ways to Strengthen Our Parishes St. Isidore Parish Consultation.

CARIS Community and Residential Information System IISC Project # A18 Ministry of Children and Family Development 2005.

STREAMLINING STORM WATER PERMIT IMPLEMENTATION THROUGH USE OF AN INFORMATION MANAGEMENT SYSTEM April 8, 2004 Presented by John W. Hart 30 th Environmental.

Knowledge Engineering. Review- Expert System 3 Knowledge Engineering The process of building an expert system: 1.The knowledge engineer establishes a.

Matt Tempia Chris Thomas Thomas Taylor Jeffrey Tansey.

Audience Response Systems A brief look at Turning Point Technology’s Audience Response Product CE 5560-John Martin Capstone project

The Hard Work of Systems Analysis: “Team Leader Position Descriptions”

© 2013 Software AG. All rights reserved. ARIS Interactive Guide helps you to find buttons and functionality from ARIS 7.2 in ARIS 9. Start After starting.

DotNetNuke® Web Application Framework Michael Washington Socaldug.org – Buena Park, CA

Communicating Excellence: Correcting Ministry Performance A Fable About Correcting 1.

Cornerstone Free Will Baptist Church TECHNOLOGY STRATEGIC PLAN.

Bethel Church of the Assembly of God Cliff Traub – pastor from Church Split, 1991 – -Building project consumed his thoughts. Church members.

Interactive MIPS Datapath Tutorial

Growth For Small Church

Earth Educators’ Rendezvous Workshop Leader Webinar

Blue Group The Motion Our Position.

«Болашақтың есігін ашатын бес кілттің бірі – білім ошақтары».

Race Questions: Question 1

Presentation transcript:

West Shore Survey System Milestone 2 Team Members: Brad Coverdale: Liaison, Requirements gathering Chris Dries: Web Designer, Quality control Christina Felts: Team Leader, PowerPoint Presentation, Requirements gathering Josh Henry: Quality control

Milestone 2 Summary Met with John Nesbitt, the Associate Pastor of Ministry Support, to determine what West Shore Evangelical Free Church (WSEFC) expects from our project. Met with John Nesbitt, the Associate Pastor of Ministry Support, to determine what West Shore Evangelical Free Church (WSEFC) expects from our project. Determined requirements and split them into 3 Increments Determined requirements and split them into 3 Increments Completed Software Requirements Specification (SRS) Completed Software Requirements Specification (SRS)

Requirements Overview Question Types - Each survey is made up of questions. How these questions are answered determines the types of requirements needed for that particular survey as well as how to display results properly Question Analysis - Each survey needs to display a report of the results to the user containing understandable information within a certain context Tracking Results - It is important to know how the survey will track the results, either anonymously or by username, depending on the situation for the survey. There also needs to be a way to eliminate redundant data by allowing the end user to access each survey only once User Interface - How the survey interface will interact with the user to achieve desired results from switching to a paperless system.