Closed labs are an important part of the 221/222/321 course sequence. They are supposed to complement the lecture/activity sessions by providing a structured, supervised environment in which students can actively learn by performing activities that, because of their scope and complexity, would not naturally fit in the normal class periods.
The success of the closed lab experience depends on several factors.
The goal in closed lab should NOT be to be done as quickly as possible, so that students can be on their way to more entertaining and enjoyable activities! The goal, of course, is to learn. And, hopefully, also having some fun. It is important to realize that closed labs represent a unique environment and opportunity to interact with your partner and with your instructor/grader, and to get quick, timely feedback. It may be the only opportunity the student has of getting feedback not just about the specific activity involved, but also about programming style, techniques, methodology, and other aspects of the software component engineering discipline.
All this having been said, let us state unequivocally: closed labs are essential to a productive and successful experience in 321. To get credit for a closed lab session all three of the following conditions must be met (no exceptions allowed!):
If any of the three conditions is not met, you will not get credit for the closed lab. However, in consideration of the fact that there may be exceptional circumstances beyond your control that prevent you from satisfying these requirements, the 1% for that closed lab is not completely lost. It will be added to the value of your final exam grade. The final exam in 321 is worth 30% of the total grade. So, for example, if a student gets credit for only 6 out of 8 closed labs, her/his final exam will be worth 32% of the total grade. Note that based on experience, it is safe to say that it is much easier to get 1% in closed lab than earning it on the final exam. So we strongly encourage you not to miss any point on closed labs.