10 points for each of the items I, II, III, IV and V. Total is out of 7 points (total / 50 * 7)

MedicAid:
I. Use case Diagram 8
 a. Distinction between department receptionist and the main receptionist is not clear.
 b. Does a doctor realistically update his/her schedule. Chances are a nurse or a receptionist
	will do that.
II. Flow of Events 6
 a. Sequence of steps are not clear. For instance in "schedule patient appoinment," you are
	talking about cancelling an appointment, but the sequence does not mention any thing
	about that. Also, you are affecting doctor's scheudule but you did not update or even
	fetch any inforamtion pertient to the patient. In the same use case, alternate path
	says "In step 3, can log out." Not necessarily an alternate path. Also, does the user
	have to login each time? Can't they be already logged in?
III. Description of functionality 8 
 a. Could present some addition details of consideration instead of a 
    laundry list of functionalities. For instance about special conditions
    or exceptions that needs to be considered. Issues of concurrencies, etc.
IV. Discussions/presentation of interfaces 7
 a. The UI's are better expressed with their use cases or need further
	description when presented separately.
V. Report overall 10

Note: I think you have too many use cases to be able to complete in given time.
 Would be better to reduce the scope a bit to make this more realistic. I suggest
 droppin the usecases related to the following actors: Lab Technician, Pharmacist.
Total 5.46

Student Testing System:
I. Use case Diagram 9
 a. Should the "View previous exams questions" be "View details of previous exam taken."
	Not sure what this means from the diagram (had to read the flow of events to find 
	the details) and could not find the short description.
II. Flow of Events 7
 a. The alternate paths are not clear. For instance in "Take a test" use case, 
	alternate path 1 says In step 5, change status to taken. But step 7 does just that as well?
    Also, the next alternate path talks about submitting automatically. What does that mean?
    The one following it says give a A for missing a test!
III. Description of functionality 10
IV. Discussions/presentation of interfaces 10
V. Report overall 10
Total 6.44

SyndiSnag:
I. Use case Diagram  8 
 a. The uses relationship is a bit shaky. Is the depending use case literally going to follow all
	sequence of events that the user will follow?
 b. An actor is external to the system. Calling the Scanning Timer as an actor is not clear cut.
	These are better handled as additional functionality descriptions rather than use cases.
II. Flow of Events 7
 a. Alternate paths may have to indicate error messages to the user rather than repeat a step.
 b. Is it allowed to have duplicate names for categories within a category?
 c. Alternate path for renaming category is redirecting to another use case. Not appropriate.
III. Description of functionality 10
IV. Discussions/presentation of interfaces 9 
 a. A brief description of each use case would help. 
V. Report overall 10
Total 6.16

Bug-base:
I. Use case Diagram 8
 a. Is there a relationship between the administrator and user actors?
	Does one inherit from another? The administrator is required to be
	logged in before operations can be performed.
II. Flow of Events 8
 a. Is the user allowed to login concurrently?
 b. In change password, any other action like storing the password needs to be mentioned.
    The last step of validating the password does not complete the use case.
III. Description of functionality 10
IV. Discussions/presentation of interfaces 10
V. Report overall 10
Total 6.44

Wheels.com:
I. Use case Diagram 9
 a. The order use case may be renamed to some thing more meaningful as a verb form like
	create Order for example.
 b. Some use cases either have typos in them or are not really verb form. It helps for 
	the name to convey the intent as much as possible.
II. Flow of Events 10
 a. Well written
III. Description of functionality 8 
 a. Could present some addition details of consideration instead of a 
    laundry list of functionalities. For instance about special conditions
    or exceptions that needs to be considered. Issues of concurrencies, etc.
IV. Discussions/presentation of interfaces 10
 a. The interface descriptions and brief description of use cases is good.
V. Report overall 10
 a. Good report
Total 6.58