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

Diff of /02/assignment2.tex

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

revision 1.1 by jontas, Thu Dec 11 14:44:50 2003 UTC revision 1.4 by jontas, Thu Dec 11 18:49:54 2003 UTC
# Line 24  Line 24 
24          These three supplements each other adding references to          These three supplements each other adding references to
25          each other. None of these is useful by itself, but by          each other. None of these is useful by itself, but by
26          adding them up one can get a better perspective of the          adding them up one can get a better perspective of the
27          size of the software.          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      \subsection{Give an example where code length measure can be useful and an      \subsection{Give an example where code length measure can be useful and an
39      example where source code length measure is not useful.}      example where source code length measure is not useful.}
40          svar          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      \subsection{Explain what are the main ideas behind Albrecht's Function Points.      \subsection{Explain what are the main ideas behind Albrecht's Function Points.
51      Discuss advantages and disadvantages of the measure. Motivate.}      Discuss advantages and disadvantages of the measure. Motivate.}
52          svar          %denna var bra http://www.spr.com/products/function.htm
53            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      \subsection{Describe structural measures presented by Fenton. (Control flow      \subsection{Describe structural measures presented by Fenton. (Control flow
84      structure, Data flow structure, Data structure). Give an example      structure, Data flow structure, Data structure). Give an example
85      where you explain how one could use the structural measures      where you explain how one could use the structural measures
86      (specify which structural measure) to ensure the quality of the      (specify which structural measure) to ensure the quality of the
87      software product.}      software product.}
88          svar          %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      \subsection{Draw the flow graph for the program, which      \subsection{Draw the flow graph for the program, which
110      based on the data provided by everyday measurements of the air      based on the data provided by everyday measurements of the air
111      temperature will calculate the maximum, minimum and the most      temperature will calculate the maximum, minimum and the most
Legend:
Removed from v.1.1  
changed lines
  Added in v.1.4
root@recompile.se
 ViewVC Help
Powered by ViewVC 1.1.26