docs/diploma

changeset 405:a3d9a63defa7

find changesets by author, revision, files, or words in the commit message
trivial change
author meillo@marmaro.de
date Sun, 08 Feb 2009 23:18:15 +0100
parents f0fa40e30dfb
children 1d527ad76c97
files thesis/tex/4-MasqmailsFuture.tex
diffstat 1 files changed, 1 insertions(+), 1 deletions(-) [+]
line diff
     1.1 --- a/thesis/tex/4-MasqmailsFuture.tex	Sun Feb 08 23:15:35 2009 +0100
     1.2 +++ b/thesis/tex/4-MasqmailsFuture.tex	Sun Feb 08 23:18:15 2009 +0100
     1.3 @@ -796,7 +796,7 @@
     1.4  In the short-time view, the effort for improving the existing code is much smaller than the effort for a new design plus improvements. But to have similar quality properties at the end of the short-time frame, a version that is based on current code will probably require nearly as much effort as a new designed version will take. For all further development afterwards, the new design will scale well while the old code will require exponential more work.
     1.5  \index{existing code}
     1.6  
     1.7 -The Break Even is the point in time when a new design is better than improvements of the old code for the first time. From this point on, the new design will be the better solution.
     1.8 +Break Even is the point in time when a new design is better than improvements of the old code for the first time. From this point on, the new design will be the better solution.
     1.9  
    1.10  In the long-time view, a restructuring for modularity is necessary anyway to keep the maintaining effort bearable. The question is, when the restructuring should be done: Right at the start in a new design, or later as restructuring work.
    1.11