Email Use Case

Created by: [Your Name]

I. Actors

• User

• Email Server

• Network

II. Preconditions

• User has a registered email account.

• User has internet connectivity.

• User is logged into the email application.

III. Main Flow

1. User composes a new email.

   • User enters the recipient’s email address.

   • User writes the email subject.

   • User writes the email body.

   • User attaches files (optional).

2. User clicks the "Send" button.

3. Email is sent to the Email Server.

4. Email Server processes and forwards the email to the recipient’s email server.

5. Recipient’s email server stores the email.

6. Recipient accesses the email through their email application.

IV. Alternative Flows

• If user’s internet connectivity fails, the email will be stored in the Outbox, and the application will attempt to resend it when connectivity is restored.

• If the recipient’s email address is invalid, the Email Server will return an error message to the user, indicating that the email was not delivered.

• If the attachment exceeds size limits, the user will receive an error message and will be prompted to remove or reduce the file size.

V. Postconditions

• Email is successfully delivered to the recipient’s email server.

• The user receives a delivery confirmation (if requested).

• The email is stored in the user’s Sent folder.

VI. Exceptions

• Network failure during email sending may result in email not being sent.

• Server downtime might delay and queue the email for later sending.

VII. Notes

Important Points
Ensure that the recipient's email address is correct to avoid delivery failures.
Attachments should comply with the email server’s size and type restrictions.
Consider using encryption for sensitive information.

Use Case Templates @ Template.net