Mercurial > docs > diploma
changeset 405:a3d9a63defa7
trivial change
| author | meillo@marmaro.de |
|---|---|
| date | Sun, 08 Feb 2009 23:18:15 +0100 (2009-02-08) |
| parents | f0fa40e30dfb |
| children | 1d527ad76c97 |
| files | thesis/tex/4-MasqmailsFuture.tex |
| diffstat | 1 files changed, 1 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/thesis/tex/4-MasqmailsFuture.tex Sun Feb 08 23:15:35 2009 +0100 +++ b/thesis/tex/4-MasqmailsFuture.tex Sun Feb 08 23:18:15 2009 +0100 @@ -796,7 +796,7 @@ 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. \index{existing code} -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. +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. 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.