1. General Information & Proc.c General Information & Proc.c Juan Luis Pardo González Javier Lara Valtueña

2. General Information & Proc.c General Information & Proc.c -General Information: General Metrics Graphs -Proc.c: Proc.c Metrics Graphs.

3. General Information: General Metrics Graphs This round graph shows the percentage of Source Code,Comments,Blank Lines,Inactive and PreProcessor of the whole written code. Half of the code is Source Code,fourth part of the code is Comment Code. There is almost one line of Comment Code per two lines of Source Code. It is a GOOD MARK.

4. General Information: General Metrics Graphs This graph shows the five most commented functions. All functions have more than one of Comment Ratio.They have more comment lines than source lines.

5. General Information: General Metrics Graphs Sched(): This function determines the scheduling policy. It is called whenever a process must be added to one of the scheduling queues to decide where to insert it. As a side-effect the process' priority may be updated. do_revive(): Revive a process that was waiting for something. Clock_handler: This executes on each clock tick (i.e., every time the timer chip generates an interrupt). It does a little bit of work so the clock task does not have to be called on every tick.

6. General Information: General Metrics Graphs This graph shows the five Largest functions. All of them have more than 200 lines of code. Tcp_frag2conn() is by far the largest function,with more than 700 lines of code, when ip_ioctl() which is the second only has roughly 400 lines.

7. General Information: General Metrics Graphs This graph shows the five Largest files. All of them have more than 1000 lines of code. Two groups can be distinguished: The first three files with more than 2500 lines of code,and the rest with less than 2000 lines of code.

8. General Information: General Metrics Graphs This graph shows the five more complex files according to average cyclomatic complexity. All of them have an average complexity greater than 21. According to LaquSo methodology these are high risk parts of the program because its average cyclomatic complexity is greater than 21.

9. General Information: General Metrics Graphs This graph shows the five more complex functions according to cyclomatic complexity. All of them have a complexity greater than 50. According to LaquSo methodology these are the untestable functions of the program,because they have a cyclomatic complexity greater than 50. It makes them very high risk functions.

10. Proc.c: Proc.c Metrics Graphs. CountLineBlank -- Number of blank lines. CountLineCodeDecl -- Number of lines containing declarative source code. CountLineCodeExe -- Number of lines containing executable source code. CountLineComment -- Number of lines containing comment. Note that proc.c like almost all the code has one comment line per executable or declarative line.

11. Proc.c: Proc.c Metrics Graphs. MaxNesting -- Maximum nesting level of control constructs (if, while, for, switch, etc.) in the function.

12. Proc.c: Proc.c Metrics Graphs. CountPath -- Number of unique paths though a body of code, not counting abnormal exits or gotos.

13. Proc.c: Proc.c Metrics Graphs.