186 |
See appendix c. |
See appendix c. |
187 |
\subsection{Write a short section (up to ½ page) with answers to the following |
\subsection{Write a short section (up to ½ page) with answers to the following |
188 |
questions:} |
questions:} |
189 |
\begin{itemize} |
\subsubsection{Which of the metrics could not be computed based on the class diagrams? Why?} |
190 |
\item Which of the metrics could not be computed based on the class |
The LCOM (Lack of Cohesion in Methods) metric could |
191 |
diagrams? Why? |
not be computed from the class diagram because LCOM metrics |
192 |
\item Which of the two systems is more complex? Why? |
are gathered through counting the number of |
193 |
\end{itemize} |
method-pairs that have no attributes in common and |
194 |
denna bör nog du ge dig på |
then subtract the number of pairs that do have |
195 |
|
common attributes. This can not be seen when looking |
196 |
|
at the class diagram so you have to look at the |
197 |
|
code to compute it. It would probably be quite handy |
198 |
|
with a tool that computes this metric automatically |
199 |
|
since it is very time consuming to do by hand. |
200 |
|
\subsubsection{Which of the two systems is more complex? Why?} |
201 |
|
Since Design2 has a lower total LCOM value (140 vs |
202 |
|
93) it is therefore considered more complex. |
203 |
|
We draw this conclusion from the lecture and slides about CK metrics, a class |
204 |
|
with low cohesion is ''hard to comprehend, hard to |
205 |
|
reuse, hard to maintain and constantly effected by |
206 |
|
change´´ |
207 |
\subsubsection{Which method of gathering metrics - from UML designs or source |
\subsubsection{Which method of gathering metrics - from UML designs or source |
208 |
code - is less time consuming?} |
code - is less time consuming?} |
209 |
denna bör nog du ge dig på |
You get a much better overview of the system when |
210 |
|
looking at the UML design and it is much less |
211 |
|
time consuming than searching through source code after source code to |
212 |
|
find inheritance, number of children and so on. Some |
213 |
|
metrics require going through source code though, so you |
214 |
|
can not get everything from the UML designs, although it |
215 |
|
would have been handy if it was possible. |
216 |
\section{External product attributes} |
\section{External product attributes} |
217 |
\subsection{Describe how the external product attributes differ from the |
\subsection{Describe how the external product attributes differ from the |
218 |
internal ones. Describe the connection between external and |
internal ones. Describe the connection between external and |