CS170 Lab 4 (kos_start) -- Scoring Criteria

Here is the scoring criteria for lab 4, based on 8 questions, together amounting to 100 points. For questions 4-8 the score depended on whether the turned-in software was able to correctly execute automated tests.

1. [5] Where there warnings during compilation? We expect no warnings during compilation with default flags. It is a good idea to have no warnings even with -Wall flag.


2. [5] How readable is the code? Meaningful variable names and helpful comments improve readability. Logical, simple structuring helps, too.


3. [10] What was the quality of the code? Points will be docked for unused variables, illogical organization of code, for grossly inefficient use of memory, and for significant unnecessary code.


4. [5] Code test: Booting and halting. Piece of cake!


5. [15] Code test: Writing to console (1 byte and 260 bytes)


6. [25] Code test: Argument parsing: checking argc, argv, and envp


7. [30] Code test: Reading from console (1 byte and 261 bytes) and "cat"


8. [5] Code test: Checking if your KOS handles invalid input to system calls