--- 02/assignment2.tex	2003/12/11 18:49:54	1.4
+++ 02/assignment2.tex	2003/12/11 21:20:48	1.5
@@ -112,17 +112,34 @@
     commonly occurred temperature (the temperature that occurs twice
     or more) for a given month. Present program paths that has to be
     executed in order to satisfy the following testing strategies:}
+        See appendix a for the diagram.
         \subsubsection{Statement coverage}
-            svar
+            a-b-c-d-e-f-g-h-i-j-k-l-m-n
         \subsubsection{Branch coverage}
-            svar
+            a-b-c-d-e-f-g-h-i-j-k-l-m-n \\
+            a-b-c-b-c-d-e-g-i-j-k-m-n \\
+            a-b-c-d-e-f-g-h-i-j-k-l-m-k-m-n \\
         \subsubsection{Visit each loop}
-            svar
+%osäker på om detta är rätt...jag har bara antagit att man skall göra ett test så att man kör alla looparna
+            a-b-c-b-c-d-e-f-g-e-f-g-h-i-g-h-i-j-k-l-m-k-m-n
     \subsection{Calculate the cyclomatic complexity of your program. What does
     this figure tell you?}
-        svar
+        %Cyclomatic complexity (CC) = E - N + p
+        %where E = the number of edges of the graph
+        %N = the number of nodes of the graph
+        %p = the number of connected components
+        %http://www.sei.cmu.edu/str/descriptions/cyclomatic.html
+        Hopefully you mean McCabe's cyclomatic complexity\\
+        % e = no of arcs | n = no of nodes
+        e-n+2 | 18 - 14 + 2 = 18 - 16 = 2 \\ %men vad säger nu detta
+        This tells us the number of tests we have to do to cover
+        each path in the program. It could also be used to give a
+        estimation of how complex the final software will be. If
+        higher then 20 it should be seen as a high risk project,
+        and if higher then 50 as a very high risk project.  %nuffrorna kommer från http://www.sei.cmu.edu/str/descriptions/cyclomatic.html
   \section{OO metrics}
   \textbf{Measuring the use cases}
+    %vi skall använda templaten, och bifoga denna...
     \subsection{Measure the use case specifications shown in Design 1 using the
     chosen use case metrics suite from the lecture}
         svar
@@ -164,14 +181,54 @@
     \subsection{Describe how the external product attributes differ from the
     internal ones. Describe the connection between external and
     internal product attributes.}
-          svar
-    \subsection{Assume that you are
-    working at the company that mainly specializes on developing of
-    web-based applications. Your manager gives you an assignment to
-    develop a software quality model for the company. The model should
-    show external quality attributes, corresponding internal
-    attributes and metrics. Present the assumptions that you will use
-    while creating of the quality model. Provide an explanatory text
+          The internal attributes can be measured from within the
+          system (like loc etc) while for the external attributes
+          one must look at the finished product to se the external
+          attributes. Also in general internal attributes are
+          considered easier to measure (and then predict) then the
+          external attributes.
+
+          This is partly since the internal attributes can be
+          measured more ``directly'' then the external. For
+          instance loc is easy to count while usability is a lot
+          harder to measure. For the internal attributes one can
+          expect to be able to get absolute values while on the
+          external attributes one can expect them to be less
+          accurate.
+
+          However several of the internal attributes (if not all)
+          does affect the external attributes in a way that can
+          (in most cases) be predicted. One can for instance say
+          that in a specific solution if the loc is increased
+          (both with comments) then one could expect to get a
+          higher maintainability. Also most of the external
+          attributes can be affected via the internal if the
+          developers keep the external attributes in mind.
+
+          In most cases (if not always) the customer of the product
+          is more interested in the external attributes. Does this
+          mean that the external attributes are of ``greater''
+          value to the team developing the product?
+
+          Not always but in many cases. Also one should keep in
+          mind that just because the external attributes are more
+          important that the internal could be forgotten.
+    %\subsection{Assume that you are working at the company that
+    %mainly specializes on developing of web-based applications.
+    %Your manager gives you an assignment to develop a software
+    %quality model for the company. The model should show external
+    %quality attributes, corresponding internal attributes and
+    %metrics. Present the assumptions that you will use while
+    %creating of the quality model. Provide an explanatory text
+    %for your model.} %Jag tyckte inte om att läsa den texten;)
+    \subsection{Assume that you are working at a company that
+    mainly specializes in development of web-based applications.
+    Your manager gives you an assignment to develop a software
+    quality model for the company. The model should show external
+    quality attributes, corresponding internal attributes and
+    metrics. Present the assumptions that you will use while
+    creating the quality model. Provide an explanatory text
     for your model.}
-        max 8 sidor
+%huh? - jag kollar på denna... men vill du ha den så;)
+        max 8 sidor (totalt; inte på denna;)
 \end{document}
