Merge pull request #7 from GChristensson/doc/#1

doc/#1: Answered questions to the part about complexity

Author: GChristensson

README.md

@@ -76,12 +76,42 @@ for each project, along with reason(s) why you changed to a different one.
 ## Complexity
 
 1. What are your results for ten complex functions?
-   * Did all methods (tools vs. manual count) get the same result?
-   * Are the results clear?
-2. Are the functions just complex, or also long?
-3. What is the purpose of the functions?
-4. Are exceptions taken into account in the given measurements?
-5. Is the documentation clear w.r.t. all the possible outcomes?
+    * 1: _remove_repair (lines 212-283) (CCN: 31)
+    * 2: canny (lines 21-113) (CCN: 26)
+    * 3: points_to_polynomial (lines 1-103) (CCN: 21)
+    * 4: next_term (lines 21-107) (CCN: 20)
+    * 5: solution (lines 95-149) (CCN: 20)
+    * 6: bidirectional_dij (lines 20-107) (CCN: 20)
+    * 7: search (lines 12-74) (CCN: 20)
+    * 8: inverse_of_matrix (lines 8-155) (CCN: 20)
+    * 9: move (lines 155-210) (CCN: 19)
+    * 10: find_optimal_binary_search_tree (lines 68-134) (CCN: 19)
+
+**Q: Did all methods (tools vs. manual count) get the same result?**
+
+**A:** We chose to manually count 5 functions as follows:
+
+* Canny: Same results
+* Optimal binary search tree: Same results
+* Search: Not the same results. Lizard got 20 and we counted 21.
+* Inverse of matrix: Not the same results. Lizard got 20 while we got differing results. We eventually counted it manually together as a whole group but could still not get the same result as lizard.
+* Bidirectional dijkstra's: Same as with the case of the "Inverse of matrix" above.
+
+**Q: Are the functions just complex, or also long?**
+
+**A:** Some functions are "long" (around 100 lines) while some are shorter (around 50 lines). The functions did not seem too complex, in the sense of having nested loops, etc.
+
+**Q: What is the purpose of the functions?**
+
+**A:** The purpose of the functions are to implement different kinds of algorithms. The names of the functions are self-explanatory and thus explains the purpose of the functions well.
+
+**Q: Are exceptions taken into account in the given measurements?**
+
+**A:** We took exceptions into account when counting manually.
+
+**Q: Is the documentation clear w.r.t. all the possible outcomes?**
+
+**A:** Not quite. In most functions it is not documented why an error was raised, for example. Also, there is mostly no documentation to if-statements that explains why a certain path is taken or not.
 
 ## Refactoring