cvs/02/assignment2.tex

%Assignment is conducted in pairs. Max. 8 pages.
\documentclass[12pt, a4paper]{article}
\usepackage[latin1]{inputenc}

\begin{document}
  \pagenumbering{roman}
  \thispagestyle{empty}
  \begin{centering}
    Assignment 1 - PAC003: Software Metrics, 5p\\
    Jonas Petersson \& Mathias Börjeson\\
    \emph{jopd01@student.bth.se \& tb00mbo@student.bth.se}\\
  \end{centering}
  \tableofcontents
  \newpage
  \pagenumbering{arabic}
  \section{Internal product attributes}
    \subsection{Explain how the three aspects of the software size (Length,
    Functionality and Complexity) are supplementing each other to describe
    the notion of software size.}
        %length        = is a physical size of the product
        %functionality = counts the functions supplied by the product
        %complexity    = measures the complexity od underlying problem, or a solution
%utan att ha en aning om hur notationen ser ut drar jag till med följande
        These three supplements each other adding references to
        each other. None of these is useful by itself, but by
        adding them up one can get a better perspective of the
        size of the software. The length itself don't tell
        anything of how large the completed software will be, but
        together with functions and complexity one can understand
        the size of the software. Once the size of the software is
        established one may come with effort estimations, and
        based on those make a budget for what resources the
        project will need. Given these three it is possible to get
        an idea of how productive a programmer is during a time
        unit. It will not be a perfect answer, but it will be
        something that could be used to measure deviations in work
        etc.
    \subsection{Give an example where code length measure can be useful and an
    example where source code length measure is not useful.}
        Code length is useful if it is not going to be used by
        itself. One example of this could be if we are interested
        in how much work is done in a week. Then we could look at
        loc, and also take into account the complexity and the functions provided
        (like loc * complexity / functions or something similar).
        Then loc could be useful.

        Code length is useless if it is used by itself. For
        example the statement I am a good programmer since I
        produce more then n loc per week useless.
    \subsection{Explain what are the main ideas behind Albrecht's Function Points.
    Discuss advantages and disadvantages of the measure. Motivate.}
        %denna var bra http://www.spr.com/products/function.htm
        The main idea behind FP's are to provide  language
        independent metric that can be used no matter what
        language are used. Albrech thought it was wrong that the
        only way to tell effort and cost per effort until he begun
        was in loc. A often used metric to tell productivity was
        cost/loc, and that don't tell anything since different
        languages require different number of loc's to solve the
        same problem. This cost could be lover if the language
        requires a lot of code, but the end cost could still get
        higher if the program takes longer time to complete.
        The main idea behind FP's is to give ways to
        tell cost and productivity in a way that is language
        independent. FP's does satisfy this idea. A easier
        language will get a lower cost/FP and a greater number of
        FP's/person\&month then a more complex language.

        The great advantage with this method is that it is (almost) truly
        language independent, while a disadvantage would be that
        if this is established in the beginning of a project and
        should be used to choose a appropriate language to use, if
        the language is unfamiliar, then these metrics can't be
        computed (like FP's/person\&month). Also this way of presenting
        the result does not take into account training and
        inexperience while showing the result. Also this should
        not be used to compare different projects or groups to se
        the difference between them since this does not take
        everything into account. Also one might be tempted to
        always use the language with the highest productivity,
        this is good in most cases, but sometimes there are other
        factors to sum in, like speed, security etc.
    \subsection{Describe structural measures presented by Fenton. (Control flow
    structure, Data flow structure, Data structure). Give an example
    where you explain how one could use the structural measures
    (specify which structural measure) to ensure the quality of the
    software product.}
        %http://sern.ucalgary.ca/~kliewerc/SENG/623/summaries.htm#sum02 var lite halvbra... det bästa jag kunde hitta dock, + F4...
        Control flow is a diagram with nodes, connected via the
        directed connections showing the possible routs the
        program (or actually the flow of data in the program) may
        take. This could be broken down to several diagrams if it
        gets to large and complex. This diagram can be used to
        decide how many test cases is needed to test the program
        completely.

        The data flow structure could be shown in a module-call
        graph. The module-call graph shows what modules calls what
        other modules, and thereby showing more the flow of
        information within the program. This may also be used to
        show coupling and cohesion in the program.

        The data structure can be measured both locally and
        globally. Locally it is interesting how much data
        structure each data item has, and globally it is the
        amount of data for the system. For the local data
        structures very little research has been done, but for the
        global there are more.
    \subsection{Draw the flow graph for the program, which
    based on the data provided by everyday measurements of the air
    temperature will calculate the maximum, minimum and the most
    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:}
        \subsubsection{Statement coverage}
            svar
        \subsubsection{Branch coverage}
            svar
        \subsubsection{Visit each loop}
            svar
    \subsection{Calculate the cyclomatic complexity of your program. What does
    this figure tell you?}
        svar
  \section{OO metrics}
  \textbf{Measuring the use cases}
    \subsection{Measure the use case specifications shown in Design 1 using the
    chosen use case metrics suite from the lecture}
        svar
    \subsection{Measure the use case specifications shown in Design 2 using the
    chosen use case metrics suite from the lecture}
        svar
    \subsection{Write a short section (up to ½ page) with answers to the following
    questions:}
        \subsubsection{Which of the two systems presented can be expected to be
             more complex and why?}
                svar
        \subsubsection{Which of the two systems can be expected to require more
            effort to be built? Why?}
                svar
  \textbf{Measuring designs}
  \subsection{Measure the class diagram presented in Design 1 using the CK metrics suite presented on the
    lecture.}
          svar
    \subsection{Measure the class diagram presented in Design 2 using
    the CK metrics suite presented on the lecture.}
          svar
    \subsection{Measure the code in the files .java from Design 1 with the CK metrics suite
    presented on the lecture.}
          svar
    \subsection{ Measure the code in the files .java
    from Design 2 with the CK metrics suite presented on the lecture.}
          svar
    \subsection{Write a short section (up to ½ page) with answers to the following
    questions:}
        \subsubsection{Which of the metrics could not be computed based on the class
        diagrams? Why?}
            svar
        \subsubsection{Which of the two systems is more complex? Why?}
            svar
        \subsubsection{Which method of gathering metrics - from UML designs or source
        code - is less time consuming?}
            svar
  \section{External product attributes}
    \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
    for your model.}
        max 8 sidor
\end{document}
1	jontas	1.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	jontas	1.2	size of the software. The length itself don't tell
28			anything of how large the completed software will be, but
29			together with functions and complexity one can understand
30			the size of the software. Once the size of the software is
31			established one may come with effort estimations, and
32			based on those make a budget for what resources the
33			project will need. Given these three it is possible to get
34			an idea of how productive a programmer is during a time
35			unit. It will not be a perfect answer, but it will be
36			something that could be used to measure deviations in work
37			etc.
38	jontas	1.1	\subsection{Give an example where code length measure can be useful and an
39			example where source code length measure is not useful.}
40	jontas	1.2	Code length is useful if it is not going to be used by
41			itself. One example of this could be if we are interested
42			in how much work is done in a week. Then we could look at
43			loc, and also take into account the complexity and the functions provided
44			(like loc * complexity / functions or something similar).
45			Then loc could be useful.
46
47			Code length is useless if it is used by itself. For
48			example the statement I am a good programmer since I
49			produce more then n loc per week useless.
50	jontas	1.1	\subsection{Explain what are the main ideas behind Albrecht's Function Points.
51			Discuss advantages and disadvantages of the measure. Motivate.}
52	jontas	1.3	%denna var bra http://www.spr.com/products/function.htm
53	jontas	1.2	The main idea behind FP's are to provide language
54			independent metric that can be used no matter what
55			language are used. Albrech thought it was wrong that the
56			only way to tell effort and cost per effort until he begun
57			was in loc. A often used metric to tell productivity was
58			cost/loc, and that don't tell anything since different
59			languages require different number of loc's to solve the
60			same problem. This cost could be lover if the language
61			requires a lot of code, but the end cost could still get
62			higher if the program takes longer time to complete.
63			The main idea behind FP's is to give ways to
64			tell cost and productivity in a way that is language
65			independent. FP's does satisfy this idea. A easier
66			language will get a lower cost/FP and a greater number of
67			FP's/person\&month then a more complex language.
68
69			The great advantage with this method is that it is (almost) truly
70			language independent, while a disadvantage would be that
71			if this is established in the beginning of a project and
72			should be used to choose a appropriate language to use, if
73			the language is unfamiliar, then these metrics can't be
74			computed (like FP's/person\&month). Also this way of presenting
75			the result does not take into account training and
76			inexperience while showing the result. Also this should
77			not be used to compare different projects or groups to se
78			the difference between them since this does not take
79			everything into account. Also one might be tempted to
80			always use the language with the highest productivity,
81			this is good in most cases, but sometimes there are other
82			factors to sum in, like speed, security etc.
83	jontas	1.1	\subsection{Describe structural measures presented by Fenton. (Control flow
84			structure, Data flow structure, Data structure). Give an example
85			where you explain how one could use the structural measures
86			(specify which structural measure) to ensure the quality of the
87			software product.}
88	jontas	1.4	%http://sern.ucalgary.ca/~kliewerc/SENG/623/summaries.htm#sum02 var lite halvbra... det bästa jag kunde hitta dock, + F4...
89			Control flow is a diagram with nodes, connected via the
90			directed connections showing the possible routs the
91			program (or actually the flow of data in the program) may
92			take. This could be broken down to several diagrams if it
93			gets to large and complex. This diagram can be used to
94			decide how many test cases is needed to test the program
95			completely.
96
97			The data flow structure could be shown in a module-call
98			graph. The module-call graph shows what modules calls what
99			other modules, and thereby showing more the flow of
100			information within the program. This may also be used to
101			show coupling and cohesion in the program.
102
103			The data structure can be measured both locally and
104			globally. Locally it is interesting how much data
105			structure each data item has, and globally it is the
106			amount of data for the system. For the local data
107			structures very little research has been done, but for the
108			global there are more.
109	jontas	1.1	\subsection{Draw the flow graph for the program, which
110			based on the data provided by everyday measurements of the air
111			temperature will calculate the maximum, minimum and the most
112			commonly occurred temperature (the temperature that occurs twice
113			or more) for a given month. Present program paths that has to be
114			executed in order to satisfy the following testing strategies:}
115			\subsubsection{Statement coverage}
116			svar
117			\subsubsection{Branch coverage}
118			svar
119			\subsubsection{Visit each loop}
120			svar
121			\subsection{Calculate the cyclomatic complexity of your program. What does
122			this figure tell you?}
123			svar
124			\section{OO metrics}
125			\textbf{Measuring the use cases}
126			\subsection{Measure the use case specifications shown in Design 1 using the
127			chosen use case metrics suite from the lecture}
128			svar
129			\subsection{Measure the use case specifications shown in Design 2 using the
130			chosen use case metrics suite from the lecture}
131			svar
132			\subsection{Write a short section (up to ½ page) with answers to the following
133			questions:}
134			\subsubsection{Which of the two systems presented can be expected to be
135			more complex and why?}
136			svar
137			\subsubsection{Which of the two systems can be expected to require more
138			effort to be built? Why?}
139			svar
140			\textbf{Measuring designs}
141			\subsection{Measure the class diagram presented in Design 1 using the CK metrics suite presented on the
142			lecture.}
143			svar
144			\subsection{Measure the class diagram presented in Design 2 using
145			the CK metrics suite presented on the lecture.}
146			svar
147			\subsection{Measure the code in the files .java from Design 1 with the CK metrics suite
148			presented on the lecture.}
149			svar
150			\subsection{ Measure the code in the files .java
151			from Design 2 with the CK metrics suite presented on the lecture.}
152			svar
153			\subsection{Write a short section (up to ½ page) with answers to the following
154			questions:}
155			\subsubsection{Which of the metrics could not be computed based on the class
156			diagrams? Why?}
157			svar
158			\subsubsection{Which of the two systems is more complex? Why?}
159			svar
160			\subsubsection{Which method of gathering metrics - from UML designs or source
161			code - is less time consuming?}
162			svar
163			\section{External product attributes}
164			\subsection{Describe how the external product attributes differ from the
165			internal ones. Describe the connection between external and
166			internal product attributes.}
167			svar
168			\subsection{Assume that you are
169			working at the company that mainly specializes on developing of
170			web-based applications. Your manager gives you an assignment to
171			develop a software quality model for the company. The model should
172			show external quality attributes, corresponding internal
173			attributes and metrics. Present the assumptions that you will use
174			while creating of the quality model. Provide an explanatory text
175			for your model.}
176			max 8 sidor
177			\end{document}