Guidelines: Individual Project Critique

200 Points - Due in SAL 328 by 12 pm on Friday, May 5, 2000

Length: 8-12 pages (+/- a factor of 2) recommended, but not absolutely required. Don't use very small or large fonts
Main Question: If we were to do the project over again, how would we do it better, and how does that relate to the software engineering principles in the course?

The Individual Project Critique shall consist of the following two elements (more emphasis on element 1, i.e., how your team's process could have been better):

1. Process Improvement (2/3 of emphasis)

Candidate topics include but are not limited to: We would be particularly interested in feedback on the various tools, that is constructive in suggesting improvements rather than just identifying shortfalls; it should be balanced in identifying things that were helpful as well as obstacles; and it should be relatively high-level in focusing on strategic factors rather than individual bugs (turn in separate bug reports for that). We would also be interested in well-reasoned improvement suggestions to the MBASE guidelines.

As part of this, perform causal analysis/defect prevention for your product and the class process. Consider the overall process implemented by the student teams, professors, TA, library personnel, and any other stakeholders. Identify defects, for which root causes can be determined. Make recommendations to prevent those defects from re-occurring if the projects were done over. For actions identified, assign actionees as though the tasks will be followed through to completion. Assignees could be any of the previously named process stakeholders.

2. Product Improvement (1/3 of emphasis)

Describe possible improvements in the various components of your product: i.e., if you had to design the system again, how would you do it better, knowing what you know now.

Suggested Readings