1 / 15

Web-based Interactive Software Engineering (WISE) Columbian Park Zoo Volunteer Management

Web-based Interactive Software Engineering (WISE) Columbian Park Zoo Volunteer Management. 4.19.2012 Purdue University. Team Members. Columbian Park Zoo Volunteer Management. 2. Project Partner: Columbian Park Zoo. Columbian Park Zoo Volunteer Management.

chill
Télécharger la présentation

Web-based Interactive Software Engineering (WISE) Columbian Park Zoo Volunteer Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Web-based Interactive Software Engineering (WISE)Columbian Park Zoo Volunteer Management 4.19.2012 Purdue University

  2. Team Members Columbian Park Zoo Volunteer Management 2

  3. Project Partner: Columbian Park Zoo Columbian Park Zoo Volunteer Management • The Columbian Park Zoo is a publicly funded organization that serves the Greater Lafayette area The Columbian Park Zoo’s mission is to encourage the appreciation of the world’s wildlife, to enhance the preservation and conservation of biodiversity and to inspire educational discovery and exploration in a fun, family-oriented environment for all citizens of the Greater Lafayette Area.

  4. Update Columbian Park Zoo Volunteer Management • Week 7 -> Design Review • Week 8 -> Met with project partner, revised planned design • Week 9 -> Overview of final design, existing works • Week 10-13 -> Database design

  5. Project Identification: Intro The Zoo Volunteer Management system is looking to improve current performance in data collection and organization, while respecting certain systems Columbian Park Zoo Volunteer Management • Existing System Functions • New volunteer admittance: • Profile and background check • Event Scheduling • Done through the Zoo • Physical bulletin • Clock-In and Clock-Out • Hours, location and service performed • Data collection • Reports Suggested Deliverables Online volunteer submission form Create new event form (Initial) Revised: Load scheduling information weekly Kiosk interface for clock-in, clock-out Database-> data organization and form auto completion (Initial) Revised: forms done by hand 5

  6. Revisions per Project Partner Columbian Park Zoo Volunteer Management • Event schedule is fixed per week, month, and year. Our system should load this information instead of creating it. • Project Partner desires to perform certain tasks with physical documentation. • The Zoo has a limited budget, implementation and maintenance costs will be restricted. • The project should be completed by the end of the next fall semester

  7. Our Deliverables Columbian Park Zoo Volunteer Management Volunteer Registration: • Registration is submitted online (Current Form) • Application depends on background check and administrative approval • An orientation session is held Event Scheduling: • Loaded weekly from ZOO server • Availability checked against weekly schedule

  8. Our Deliverables cont. Columbian Park Zoo Volunteer Management Clock-in, Clock-out • One kiosk will handle the clock-in and clock-out of the volunteers Online System Design • System development and implementation with Linux-Apache-MySQL-PHP. • Cheaper deployment cost • Faster development • Existing work within WISE not applicable to ZOO project

  9. Brief Overview of Concepts

  10. Online System ? Administrative Page ? Database Kiosk System 10

  11. System Modules Columbian Park Zoo Volunteer Management

  12. Database Structure Entire system relies on implied relationships among a small set of data. Reduces hours of manual cross-referencing.

  13. Applications logs Usergroups n n actions contained in belongs to Schedule 1 n 1 Users 1 assigned to 1 Roles n 1 worked as 1 contained in 1 define works m n n Availability Groups 1 Shifts

  14. The Next Step… • Complete Design & UI and Core System Architecture • Prototype Modules, Revise and Develop. • Finalizations, and prepare for Initial Deployment (December 2012) • Add other features as needed.

  15. Questions and Suggestions • Consider the following core areas: • UI • Modular Ability • Database Structure • Deployment Process

More Related