Transcript View Post Mortem

Spring 2004
CS-EE 481
StatMonitor
Post Mortem Review
Wednesday, April 21
481s04-PM
University of Portland
School of Engineering
1
Spring 2004
CS-EE 481
What Worked Well
• Class Diagrams (Java Applet)
– Determined Model-View-Controller architecture
– Gave us an idea of classes and methods
• Sequence Diagrams (Website)
– Illustrated specific steps a user would follow to
accomplish a certain task
• Entity Relationship Diagrams (Database)
– Determined all necessary tables and attributes in the
database for StatMonitor
481s04-PM
University of Portland
School of Engineering
2
Spring 2004
CS-EE 481
What Went Wrong
• Server Issues
– Not properly prepared to handle issues that came up
throughout the project
• Applet Dependencies
– We needed certain programs installed on the computer
in order for the applet to function properly
• Versions of Software
– PHP not properly configured to connect to MySQL
Database
– Certain SQL queries were either not handled or less
efficient with the version we used
481s04-PM
University of Portland
School of Engineering
3
Spring 2004
CS-EE 481
Recommendations
• Determine team and the scope of the project
before school begins
• Determine programming languages and
learn basic functions of that language
• Software projects should be encouraged to
start coding in the Fall
481s04-PM
University of Portland
School of Engineering
4