/[cvs]/02/assignment2.tex
ViewVC logotype

Diff of /02/assignment2.tex

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.5 by jontas, Thu Dec 11 21:20:48 2003 UTC revision 1.7 by jontas, Fri Dec 12 14:52:20 2003 UTC
# Line 142  Line 142 
142      %vi skall använda templaten, och bifoga denna...      %vi skall använda templaten, och bifoga denna...
143      \subsection{Measure the use case specifications shown in Design 1 using the      \subsection{Measure the use case specifications shown in Design 1 using the
144      chosen use case metrics suite from the lecture}      chosen use case metrics suite from the lecture}
145          svar          See appendix b.
146      \subsection{Measure the use case specifications shown in Design 2 using the      \subsection{Measure the use case specifications shown in Design 2 using the
147      chosen use case metrics suite from the lecture}      chosen use case metrics suite from the lecture}
148          svar          See appendix c.
149      \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
150      questions:}      questions:}
151          \subsubsection{Which of the two systems presented can be expected to be          \begin{itemize}
152               more complex and why?}              \item Which of the two systems presented can be expected to be
153                  svar              more complex and why?
154          \subsubsection{Which of the two systems can be expected to require more              \item Which of the two systems can be expected to require more
155              effort to be built? Why?}              effort to be built? Why?
156                  svar          \end{itemize}
157    \textbf{Measuring designs}              svar
158      \\ \\ \textbf{Measuring designs}
159    \subsection{Measure the class diagram presented in Design 1 using the CK metrics suite presented on the    \subsection{Measure the class diagram presented in Design 1 using the CK metrics suite presented on the
160      lecture.}      lecture.}
161            svar            See appendix b.
162      \subsection{Measure the class diagram presented in Design 2 using      \subsection{Measure the class diagram presented in Design 2 using
163      the CK metrics suite presented on the lecture.}      the CK metrics suite presented on the lecture.}
164            svar            See appendix c.
165      \subsection{Measure the code in the files .java from Design 1 with the CK metrics suite      \subsection{Measure the code in the files .java from Design 1 with the CK metrics suite
166      presented on the lecture.}      presented on the lecture.}
167            svar            See appendix b.
168      \subsection{ Measure the code in the files .java      \subsection{ Measure the code in the files .java
169      from Design 2 with the CK metrics suite presented on the lecture.}      from Design 2 with the CK metrics suite presented on the lecture.}
170            svar            See appendix c.
171      \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
172      questions:}      questions:}
173          \subsubsection{Which of the metrics could not be computed based on the class          \begin{itemize}
174          diagrams? Why?}              \item Which of the metrics could not be computed based on the class
175              svar              diagrams? Why?
176          \subsubsection{Which of the two systems is more complex? Why?}              \item Which of the two systems is more complex? Why?
177              svar          \end{itemize}
178            Svar
179          \subsubsection{Which method of gathering metrics - from UML designs or source          \subsubsection{Which method of gathering metrics - from UML designs or source
180          code - is less time consuming?}          code - is less time consuming?}
181              svar              svar
# Line 229  Line 231 
231      metrics. Present the assumptions that you will use while      metrics. Present the assumptions that you will use while
232      creating the quality model. Provide an explanatory text      creating the quality model. Provide an explanatory text
233      for your model.}      for your model.}
234  %huh? - jag kollar på denna... men vill du ha den så;)          Assumptions: We are using an iterative development
235          max 8 sidor (totalt; inte på denna;)          process, we are using function points to measure progress,
236            we are using a good configuration management tool, we are
237            identifying risks before starting a project, we are, but
238            not always using uml for our projects.
239    
240            Since we are working on web-based applications we also
241            assumed that we are selling those to a customer. This made
242            us make a value based quality view. This made us decide
243            that usability, lernability, reusability, maintainability, reliability,
244            is the most important external attributes. The internal
245            attributes are not considered as important, other than to
246            help up the external. Customer satisfaction does supersede
247            this thou. The external attributes has the following
248            impact on customer satisfaction: \\
249            \begin{tabular}{|l|l|l|}
250                \hline
251                Attribute       & Importance    & Role \\ \hline
252                Usability       & High          &
253                    Decides if the customer fells that he may use\\
254                & & the product or not. The more usable the product\\
255                & &  becomes, the higher value it gets (and thereby\\
256                & &  higher quality).   \\ \hline
257    %hmmm, borde finnas nått bättre sätt...
258                Learnability    & High          &
259                    The quicker the end-user can learn to use the \\
260                & & program, the quicker he feels the value of the\\
261                & & program and does need it. This makes the \\
262                & & customer feels a gain from buying our product \\ \hline
263                Reusability     & Medium        &
264                    This is only important if using agreements like\\
265                & & ``avtal 90'' or similar that gives us the freedom\\
266                & & of the developed artifacts, and may use them in\\
267                & & projects to come. If the customer has no demands\\
268                & & on this, and will own the artifacts then it is \\
269                & & not taken into consideration.\\ \hline
270                Maintainability & Medium    &
271                    This is only important if we are using the \\
272                & to low &
273                    reusability from above. And only to support that\\
274                & & purpose. Otherwise this would not have been a \\
275                & & issue at all. \\ \hline
276                Reliability     & High      &
277                    This is important since a reliable program is \\
278                & & seen as having a higher value. \\ \hline
279            \end{tabular} \\ \\
280            Internal attributes are only important in order to gain
281            the external attributes.
282  \end{document}  \end{document}
Legend:
Removed from v.1.5  
changed lines
  Added in v.1.7
root@recompile.se
 ViewVC Help
Powered by ViewVC 1.1.26