1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/thesis/pieces/requirements.tex	Thu Nov 13 15:06:40 2008 +0100
     1.3 @@ -0,0 +1,38 @@
     1.4 +\chapter{Use cases}
     1.5 +
     1.6 +Here follow typical use cases for \masqmail. If other \MTA{}s are better suited for certain use cases, it will be mentioned. The use cases are prestage for defining the requirements.
     1.7 +
     1.8 +%FIXME: rewrite!
     1.9 +%       How do I write use cases??
    1.10 +%       Are use cases the right tool for what I need, at all??
    1.11 +
    1.12 +The user writes email with one of the common programs (e.g. \path{/bin/mail} or \name{mutt}). \masqmail\ must provide an interface, to that prepared mail can be handled over.
    1.13 +
    1.14 +\masqmail\ must deliver mail to its destination.
    1.15 +
    1.16 +Mail must be send with different settings, if someone uses more than one internet connection.
    1.17 +
    1.18 +If the machine is offline, no mail, destinated to the internet, must be send. It needs to be queued until an online connection gets established.
    1.19 +
    1.20 +If the computer goes online, all mail for outside destinations, should be send through the active route.
    1.21 +
    1.22 +Local mail should be send at once, independent of the online state.
    1.23 +
    1.24 +\masqmail\ may act as \NAME{SMTP} server. To receive email from other hosts.
    1.25 +
    1.26 +Mail for local users should be delivered by \masqmail\ itself or passed to \name{mail delivery agent}s.
    1.27 +
    1.28 +\masqmail\ needs to provide the same interface as \sendmail\ has, for being a drop-in replacement.
    1.29 +
    1.30 +
    1.31 +%TODO: add Schaeffter's ideas here
    1.32 +\chapter{Requirements}
    1.33 +
    1.34 +\section{Structure}
    1.35 +\section{Security}
    1.36 +\section{Usability}
    1.37 +\chapter{Security issues}
    1.38 +
    1.39 +%TODO: write about:
    1.40 +% #ifdefs in code
    1.41 +% the single setuid root binary