Final Presentation

Final Project Presentation

In .htm Format

resources/Milestone6/FinalPresentation.htm

In .ppt Format

resources/Milestone6/FinalPresentation.ppt

Videos in Presentation

Comments by Deb Hoffman

Comments by Michele Leaman

In Outline Format

Messiah College Gender Initiative DBMS
Dana Champion (GI Liaison, M6 Leader)
Dave Lanzer (The other guy)
Jason Long (ITS Liaison)

• Executive Summary

  • The DBMS provides a method for electronic event, contact, and resource management

  • Why do we need it?

    • Current paper system is inefficient and ineffective
    • Our system provides easy access for leaders on and off campus to the GI data.

  • Investment

    • Student planned, designed, and programmed
    • Tailored for a Messiah College organization

• Project Introduction

  • Problems

    • Word-of-mouth networking and meetings of the women's caucus
    • Data-entry
    • Time to organize
    • Access to information – everything is on paper…somewhere

  • Objectives

    • Get rid of the paper!!!!!
    • Interactive public-access calendar of events
    • Recall contacts and conversations
    • Easy referencing of GI library files
    • User-friendly application

• Project Overview

  • Possible solution candidates
  • Our solution
  • How we implemented
  • Results

• Application Demonstration

  • Currently located at //reg01/gender/
  • To be relocated by ITS

• Impact of Application

  • Projected impact of application

    • Accessibility of information
    • Streamline process for GI
  • Will our goals be met?

• Project Strengths

  • POC, Michéle Leaman
  • Programming language/platform – ITS
  • Scope of the project
  • Organization was flexible
  • Split up functional implementation tasks
  • Different backgrounds
  • Good friends

• Project Weaknesses

  • Unable to supervise migration and final deployment
  • Communicating ideas from different experiences
• Sponsor Organization Assessment

• Lessons Learned

  • Easier for us to advise in our specialized areas rather than have a rotating team leader
  • Iterative/rapid prototyping – most coding in M4 instead of M5 (no time in M5 anyway)
  • Customer involvement in decision making

  • DFDs/Normalization redundant

    • Note: Some documentation really helped

• There’s so much more we could do!

  • Editing deleted events
  • Time recognition
  • Cached pages
  • Required fields
  • Phone fields
  • HIGHLIGHT
  • Automated data transfer in DB
  • View previous info during submission
• Questions