1 / 16

Project Forward Leap

Project Forward Leap. Ryan Albright, Daniel Groff, Reed Horanburg, Jeffrey Lamos. Executive Summary. Project Forward Leap is a private, nonprofit enrichment program that helps middle school students from inner city and disadvantaged backgrounds grow both academically and personally.

darcie
Télécharger la présentation

Project Forward Leap

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. Project Forward Leap Ryan Albright, Daniel Groff, Reed Horanburg, Jeffrey Lamos

  2. Executive Summary • Project Forward Leap is a private, nonprofit enrichment program that helps middle school students from inner city and disadvantaged backgrounds grow both academically and personally.

  3. Introduction • The problem was that we had to construct a database that would replace the current paper and simple spreadsheet format system. In the near future Project Forward Leap intends to expand the program to more college campuses which would make the paper records and other simple approaches unmanageable. We also needed to provide the employees the ability to quickly generate reports to track student’s progress, to make documents available to potential donors, and to update their own records.

  4. Overview • Milestone 1 • Met with PFL and decided that to best accomplish their needs, 3 databases needed to be created. • Took all information presented to us from PFL and devised a project plan which contained all the deliverables as well as preparation required to complete the project.

  5. Overview • Milestone 2 • We first had to look at the system PFL was currently using and then designed a To-Be system that we would be creating. • We had to decide what type of project we were facing (Automation, Improvement, or Reengineering). • We developed a use case-based requirements doc

  6. Overview • Milestone 3 • We now focused on diagramming the whole project. • We created Behavioral Diagrams of the system showing how the different characters would interact with each other in the system. • Finally we decided that using Access would be the most convenient and best option for this database.

  7. Overview • Milestone 4.1 • This is where we actually started creating the database. • We focused on creating, editing, and deleting in each of the 3 databases. • We also continued to update our plan throughout to meet the needs of PFL and accomplish what we knew was possible.

  8. Overview • Milestone 4.2 • Here we expanded the functionality of the system that was created in the previous milestone. • We were able to add applicants in the student and HR databases.

  9. Overview • Milestone 4.3 • We created reports for each of the 3 databases. • Polished up functionality. • Debugged the system by running tests for each use case that we had created. • We created a manual of how to use the system. • We also came up with a transition plan of how we were going to deliver the system to PFL.

  10. Overview • Milestone 5 • We delivered the system to PFL. • This included delivering the manual and demonstrating how the system worked. • It was rewarding to get feedback of the system from PFL. • We then prepared for this final presentation.

  11. Demonstration • http://webstu.messiah.edu/~jl1219/bis412/milestone_5.htm

  12. Impact of Project • Our system originally was supposed to be accessible through the web for all sites. • We were unable to accomplish this. • The system that we delivered will meet basic needs for the main office but will not be able to be used in other locations without a copy of the database being taken to that site. • All the functionalities that they had hoped for have been met except for the remote access.

  13. Project Strengths/Weaknesses • Strengths • Meets needs of PFL • Easy to use • Huge improvement to previous paper system • Easily upgradeable/expandable • Weaknesses • Some minor bugs • Lack of enough time • Not remote accessible

  14. PFL’s Assessment • Meets the needs that were set forth in initial meetings • Very user friendly • More functional in tracking Students & generating reports than Powerschool • Tailored to specific needs of PFL • Helps to standardize methods between sites • Exceeded expectations; Huge improvement over old system (paper & pencil)

  15. Lessons Learned By working through this project we have learned the following lessons: • Get started early • Have a good plan from the start • Keep good communication with team and Sponsor

  16. Lessons Learned By working through this project we have learned the following lessons: • Collaboration Diagrams are easier than Sequence Diagrams • Make decisions based on what you know and the progress you have made. • Teamwork is essential

More Related