Final Implementation Status

Final Implementation Status

• What we accomplished

  • 2.2.1.1 Homeowner Information - Partially implemented
  • 2.2.1.3 Adding Homeowners - Partially implemented
  • 2.2.2.1 General Homeowner Mortgage Information
  • 2.2.2.3 State Tax Information
  • 2.2.2.4 City Tax Information
  • 2.2.2.5 School Tax Information
  • 2.2.2.6 Yearly Tax Information
  • 2.2.2.7 Mortgage Payment Information
  • 2.2.2.8 Tax Payment Information
  • 2.2.2.10 Edit General Mortgage Information
  • 2.2.2.11 Add Tax Information - 95% implemented
  • 2.2.2.12 Edit Tax Information
  • 2.2.2.15 Add Payments - 95% implemented
  • 2.2.2.16 Edit Payments - 95% implemented
  • 2.2.4.5 Data integrity - 50% implemented
  • 2.2.5.1 Mortgage Invoices - 90% implemented
  • 2.3.2.1 Stand-alone
  • 2.3.2.2 Network Application

• Comparison between original functionality and delivered functionality

  The comparison is simple. We didn't get nearly as much done as we had hoped for back at the beginning of the Semester. It turns out that we bit off more than we could chew for just three months. We did not implement everything that we needed to implement to feel good about releasing HOME to Harrisburg Habitat. However, we did get enough done to do an Open Source release.

• Compare what we said we wanted to finish in Milestone 5 with what we did in Milestone 6

  We now have the basic Report Generation working. That in of itself is a major step forward from Milstone 5.

• What we believe held up our project

  • Other classes caused some significant problems because we could do more or less work depending on what was expected of us outside of this project.
  • Two of our members were learning the technology from scratch.
  • We had a fair number of feature changes throughout the project, even very late in the semester. These changes forced us to spend time redeveloping. However, these changes also refined what HOME will eventually be, and it was time well spent. Nonetheless, it contributed to our lack of progress.

• Things we would change for next time

  • Jon:

    • Less time on paperwork, more time coding

  • Tom:

    • I would personally do it in PHP if for no other reason then it has a shorter learning curve. This makes maintenance easier. I also believe that PHP can be set up in just as mantanable of a structure.
    • I also wish I could have been there at some of the meetings with Habitat, I've felt disconnected because I haven't.

  • Jim:

    • We just tried to do too much in three months. Our goals were lofty, and everyone worked very hard all semester to achieve those goals. It would have been better to have started implementation earlier, even though we didn't fully understand the requirements.
    • If we had done unit and regression tests from the start, we would be closer to a full release because less bugs would exist, and we would have had much more confidence in our app. I plan on adding Unit and regression tests after the semester to the project.

  • Denny:

    • One of the things that helped us later on in the project was that we began to define roles for ourselves within the project. Different members of the team worked on areas in which they had more knowledge. It might have been helpful to have more clearly defined roles from the beginning.
    • Communication was somewhat difficult with myself living off campus, but we managed fairly well. It took awhile to get things rolling it seemed. We worked better as a team as the project progressed.
    • There was a lot of documentation and planning done before any kind of implementation was done. While in some respects the planning was very helpful, it would have been nice to start implmentation sooner, especially given our short-term project life. Changes were made near the end of the project that caused us to change our original documentation anyway.

• What we want to do for the future of our project

  • Several of us will work on and maintain the project.
  • We will try to bring it up to production stage as we have time.