| 1 |
%Assignment is conducted in pairs. Max. 8 pages. |
| 2 |
\documentclass[12pt, a4paper]{article} |
| 3 |
\usepackage[latin1]{inputenc} |
| 4 |
|
| 5 |
\begin{document} |
| 6 |
\pagenumbering{roman} |
| 7 |
\thispagestyle{empty} |
| 8 |
\begin{centering} |
| 9 |
Assignment 1 - PAC003: Software Metrics, 5p\\ |
| 10 |
Jonas Petersson \& Mathias Börjeson\\ |
| 11 |
\emph{jopd01@student.bth.se \& tb00mbo@student.bth.se}\\ |
| 12 |
\end{centering} |
| 13 |
\tableofcontents |
| 14 |
\newpage |
| 15 |
\pagenumbering{arabic} |
| 16 |
\section{Internal product attributes} |
| 17 |
\subsection{Explain how the three aspects of the software size (Length, |
| 18 |
Functionality and Complexity) are supplementing each other to describe |
| 19 |
the notion of software size.} |
| 20 |
%length = is a physical size of the product |
| 21 |
%functionality = counts the functions supplied by the product |
| 22 |
%complexity = measures the complexity od underlying problem, or a solution |
| 23 |
%utan att ha en aning om hur notationen ser ut drar jag till med följande |
| 24 |
These three supplements each other adding references to |
| 25 |
each other. None of these is useful by itself, but by |
| 26 |
adding them up one can get a better perspective of the |
| 27 |
size of the software. |
| 28 |
\subsection{Give an example where code length measure can be useful and an |
| 29 |
example where source code length measure is not useful.} |
| 30 |
svar |
| 31 |
\subsection{Explain what are the main ideas behind Albrecht's Function Points. |
| 32 |
Discuss advantages and disadvantages of the measure. Motivate.} |
| 33 |
svar |
| 34 |
\subsection{Describe structural measures presented by Fenton. (Control flow |
| 35 |
structure, Data flow structure, Data structure). Give an example |
| 36 |
where you explain how one could use the structural measures |
| 37 |
(specify which structural measure) to ensure the quality of the |
| 38 |
software product.} |
| 39 |
svar |
| 40 |
\subsection{Draw the flow graph for the program, which |
| 41 |
based on the data provided by everyday measurements of the air |
| 42 |
temperature will calculate the maximum, minimum and the most |
| 43 |
commonly occurred temperature (the temperature that occurs twice |
| 44 |
or more) for a given month. Present program paths that has to be |
| 45 |
executed in order to satisfy the following testing strategies:} |
| 46 |
\subsubsection{Statement coverage} |
| 47 |
svar |
| 48 |
\subsubsection{Branch coverage} |
| 49 |
svar |
| 50 |
\subsubsection{Visit each loop} |
| 51 |
svar |
| 52 |
\subsection{Calculate the cyclomatic complexity of your program. What does |
| 53 |
this figure tell you?} |
| 54 |
svar |
| 55 |
\section{OO metrics} |
| 56 |
\textbf{Measuring the use cases} |
| 57 |
\subsection{Measure the use case specifications shown in Design 1 using the |
| 58 |
chosen use case metrics suite from the lecture} |
| 59 |
svar |
| 60 |
\subsection{Measure the use case specifications shown in Design 2 using the |
| 61 |
chosen use case metrics suite from the lecture} |
| 62 |
svar |
| 63 |
\subsection{Write a short section (up to ½ page) with answers to the following |
| 64 |
questions:} |
| 65 |
\subsubsection{Which of the two systems presented can be expected to be |
| 66 |
more complex and why?} |
| 67 |
svar |
| 68 |
\subsubsection{Which of the two systems can be expected to require more |
| 69 |
effort to be built? Why?} |
| 70 |
svar |
| 71 |
\textbf{Measuring designs} |
| 72 |
\subsection{Measure the class diagram presented in Design 1 using the CK metrics suite presented on the |
| 73 |
lecture.} |
| 74 |
svar |
| 75 |
\subsection{Measure the class diagram presented in Design 2 using |
| 76 |
the CK metrics suite presented on the lecture.} |
| 77 |
svar |
| 78 |
\subsection{Measure the code in the files .java from Design 1 with the CK metrics suite |
| 79 |
presented on the lecture.} |
| 80 |
svar |
| 81 |
\subsection{ Measure the code in the files .java |
| 82 |
from Design 2 with the CK metrics suite presented on the lecture.} |
| 83 |
svar |
| 84 |
\subsection{Write a short section (up to ½ page) with answers to the following |
| 85 |
questions:} |
| 86 |
\subsubsection{Which of the metrics could not be computed based on the class |
| 87 |
diagrams? Why?} |
| 88 |
svar |
| 89 |
\subsubsection{Which of the two systems is more complex? Why?} |
| 90 |
svar |
| 91 |
\subsubsection{Which method of gathering metrics - from UML designs or source |
| 92 |
code - is less time consuming?} |
| 93 |
svar |
| 94 |
\section{External product attributes} |
| 95 |
\subsection{Describe how the external product attributes differ from the |
| 96 |
internal ones. Describe the connection between external and |
| 97 |
internal product attributes.} |
| 98 |
svar |
| 99 |
\subsection{Assume that you are |
| 100 |
working at the company that mainly specializes on developing of |
| 101 |
web-based applications. Your manager gives you an assignment to |
| 102 |
develop a software quality model for the company. The model should |
| 103 |
show external quality attributes, corresponding internal |
| 104 |
attributes and metrics. Present the assumptions that you will use |
| 105 |
while creating of the quality model. Provide an explanatory text |
| 106 |
for your model.} |
| 107 |
max 8 sidor |
| 108 |
\end{document} |
Parent Directory
| 
Revision Log