Capstone Post Mortem

Capstone Post Mortem Report

Table of Contents

Project Successfulness 2

The Process 2

The Team 3

The Tools 3

The Takeaway 4

Changes for Next Time 4

Project Successfulness

Successfulness can be defined in many ways. However, I feel that our project was successful in that we were able to meet the constantly changing requirements that were given to us. However, the true measure of success will be how happy the customer is with our system. So I can't truly say that the project is successful but it did fulfill all of the requirements so I feel that it is a successful system.

The Process

Honestly, I don't think that the process worked for us at all because I feel that there wasn't enough customer involvement in the analysis and design process. We did have to create documents and those documents were accepted by the customer, but that did not prevent the customer from changing the requirements. I feel that the customer should be more involved in the analysis and design process so that the team would not have to keep redesigning the system to meet the users changing needs. I feel that we wasted too much precious time refactoring our design when we could have been working on improving the system.

I feel that the customer should provide the development team with the SRS and SDS since the customer knows exactly how the system should work. This way, the development team can have time to read over the requirements, examine them, and then return to the customer letting him know what is and isn't feasible and provide suggestions for changes to make the system better. Then, both the customer and development team can produce a final SRS and SDS that meets all of the users requirements and clearly communicates the needs to the development team. Having the development team write the SRS and SDS did not work at all.

Overall I feel that the process could have been helpful if there had been more customer involvement throughout the process. Most of the time, I...