1.1 --- a/thesis/tex/4-MasqmailsFuture.tex	Wed Jan 14 12:31:52 2009 +0100
     1.2 +++ b/thesis/tex/4-MasqmailsFuture.tex	Wed Jan 14 12:49:22 2009 +0100
     1.3 @@ -462,7 +462,9 @@
     1.4  However, a redesign and rewrite of software from scratch is hard. It takes time to design a new architecture, which then must prove it is secure and reliable. As well is much time and work needed to implement the design, test it, fix bugs, and so on. If flaws in the design appear during prototype implementation, it is necessary to start again. Thus the gain of a new design must overweight the effort needed.
     1.5  
     1.6  \person{Wheeler}'s program \name{sloccount} calculates following estimations for \masqmail's code base as of version 0.2.21 (excluding library code):
     1.7 -{\small
     1.8 +
     1.9 +\begin{quote}
    1.10 +{\footnotesize
    1.11  \begin{verbatim}
    1.12  Total Physical Source Lines of Code (SLOC)                = 9,041
    1.13  Development Effort Estimate, Person-Years (Person-Months) = 2.02 (24.22)
    1.14 @@ -475,6 +477,8 @@
    1.15  SLOCCount, Copyright (C) 2001-2004 David A. Wheeler
    1.16  \end{verbatim}
    1.17  }
    1.18 +\end{quote}
    1.19 +
    1.20  The development cost is not relevant for a \freesw\ project with volunteer developers, but the development time is. About 24 man-months are estimated. The current code base was written almost completely by \person{Oliver Kurth} within four years, in his spare time. This means he needed around twice as much time. Of course, he programmed as a volunteer developer, not as employee with eight work-hours per day.
    1.21  
    1.22  Given the assumptions that (1) an equal amount of code needs to be produced for a new \masqmail, (2) a third of existing code can be reused plus concepts and knowledge, and (3) development speed is like \person{Kurth}'s. Then it would take between two and three years to have a redesigned new \masqmail\ with the same features that \masqmail\ now has. Less time would be needed if a simpler architecture allows faster development, better testing, and less bugs.