Mercurial > docs > diploma

comparison thesis/pieces/requirements.tex @ 86:24068a091af7

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
backuped and removed requirements part; moved part 2 back
author meillo@marmaro.de
date Thu, 13 Nov 2008 15:06:40 +0100
parents
children
comparison
equal deleted inserted replaced
85:a6aa37e12dff 86:24068a091af7
1 \chapter{Use cases}
2
3 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.
4
5 %FIXME: rewrite!
6 % How do I write use cases??
7 % Are use cases the right tool for what I need, at all??
8
9 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.
10
11 \masqmail\ must deliver mail to its destination.
12
13 Mail must be send with different settings, if someone uses more than one internet connection.
14
15 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.
16
17 If the computer goes online, all mail for outside destinations, should be send through the active route.
18
19 Local mail should be send at once, independent of the online state.
20
21 \masqmail\ may act as \NAME{SMTP} server. To receive email from other hosts.
22
23 Mail for local users should be delivered by \masqmail\ itself or passed to \name{mail delivery agent}s.
24
25 \masqmail\ needs to provide the same interface as \sendmail\ has, for being a drop-in replacement.
26
27
28 %TODO: add Schaeffter's ideas here
29 \chapter{Requirements}
30
31 \section{Structure}
32 \section{Security}
33 \section{Usability}
34 \chapter{Security issues}
35
36 %TODO: write about:
37 % #ifdefs in code
38 % the single setuid root binary