Your task is to create a thorough critique/review of this entire project, with emphasis on planning, requirements and design activities. You are to prepare your critique in HTML and place it in your project team's directory. Each team should provide a special directory called final under the team's main Web directory. In that directory, each student's critique should be named FirstnameLastname.html. In addition, a printed version of the critique should be handed in to the instructor/TA on the day of the exam.
What am I looking for in your critique? Well, part of the purpose of this exam is to see how you would approach reviewing another project and how you would structure your comments, so I am purposely going to be vague in telling you what to deliver. I will only point out to you that this is your final exam and should reveal the depth of knowledge that you have accumulated in software engineering this quarter. I want to read from you both what you consider the good features and the bad features of this project as documented. I want your criticisms to be expressed as constructively as possible, meaning it is not enough to point out an inadequacy. To be constructive means to provide advice for how to make something better.
How long should this be? It is hard to give a firm page minimum or maximum. I want to see that you have looked over the entire project (specifically, the planning, requirements, design and prototype aspects). However, you will be rewarded for being succinct, so do not try to overwhelm me with page after page of unstructured commentary. Given this overall advice, I think you should shoot for a critique that is in the neigborhood of 1000-1500 words.