--- 02/assignment2.tex	2003/12/11 21:20:48	1.5
+++ 02/assignment2.tex	2003/12/12 13:47:14	1.6
@@ -154,7 +154,7 @@
         \subsubsection{Which of the two systems can be expected to require more
             effort to be built? Why?}
                 svar
-  \textbf{Measuring designs}
+  \\ \\ \textbf{Measuring designs}
   \subsection{Measure the class diagram presented in Design 1 using the CK metrics suite presented on the
     lecture.}
           svar
@@ -229,6 +229,52 @@
     metrics. Present the assumptions that you will use while
     creating the quality model. Provide an explanatory text
     for your model.}
-%huh? - jag kollar på denna... men vill du ha den så;)
-        max 8 sidor (totalt; inte på denna;)
+        Assumptions: We are using an iterative development
+        process, we are using function points to measure progress,
+        we are using a good configuration management tool, we are
+        identifying risks before starting a project, we are, but
+        not always using uml for our projects.
+
+        Since we are working on web-based applications we also
+        assumed that we are selling those to a customer. This made
+        us make a value based quality view. This made us decide
+        that usability, lernability, reusability, maintainability, reliability,
+        is the most important external attributes. The internal
+        attributes are not considered as important, other than to
+        help up the external. Customer satisfaction does supersede
+        this thou. The external attributes has the following
+        impact on customer satisfaction: \\
+        \begin{tabular}{|l|l|l|}
+            \hline
+            Attribute       & Importance    & Role \\ \hline
+            Usability       & High          &
+                Decides if the customer fells that he may use\\
+            & & the product or not. The more usable the product\\
+            & &  becomes, the higher value it gets (and thereby\\
+            & &  higher quality).   \\ \hline
+%hmmm, borde finnas nått bättre sätt...
+            Learnability    & High          &
+                The quicker the end-user can learn to use the \\
+            & & program, the quicker he feels the value of the\\
+            & & program and does need it. This makes the \\
+            & & customer feels a gain from buying our product \\ \hline
+            Reusability     & Medium        &
+                This is only important if using agreements like\\
+            & & ``avtal 90'' or similar that gives us the freedom\\
+            & & of the developed artifacts, and may use them in\\
+            & & projects to come. If the customer has no demands\\
+            & & on this, and will own the artifacts then it is \\
+            & & not taken into consideration.\\ \hline
+            Maintainability & Medium    &
+                This is only important if we are using the \\
+            & to low &
+                reusability from above. And only to support that\\
+            & & purpose. Otherwise this would not have been a \\
+            & & issue at all. \\ \hline
+            Reliability     & High      &
+                This is important since a reliable program is \\
+            & & seen as having a higher value. \\ \hline
+        \end{tabular} \\ \\
+        Internal attributes are only important in order to gain
+        the external attributes.
 \end{document}