Browse Space
This set of Use Cases describe the expected behavior of the MailReader application
.
 |
Not implemented |
|---|---|
 |
Work in progress |
| Implemented |
| Priority | Actor | Goal | Story or Brief |
|---|---|---|---|
| *.* |
Visitor | Read Mail | Visitors can Browse or Register. Subscribers can Login to a Profile and Subscribe to various mail servers (external to the system), Retrieve the mail for subscriptions, and Compose email messages. Data is retained between sessions. |
| 0.1 | Visitor | Welcome | Visitors can select tasks available to them from the default Welcome menu. |
| 0.2 | System | Retain | Profiles and subscriptions are stored for later retrieval. |
| 0.3 | Subscriber | Register | Subscribers can store login credentials and a primary email contact with the system. |
| 0.4 | Subscriber | Menu | Subscribers can select available tasks from a list, including edit Profile and Logout. |
| 0.5 | Subscriber | Logout | Subscribers can end an application session, retaining any changes. |
| 0.6 | Subscriber | Login | Subscribers can present their registration credentials to use an account again. |
| 0.7 | Visitor | Localize | Visitors can select a supported language and browse the site in that language. |
| 0.8 | Visitor | Profile | Subscribers can create and edit an account profile. |
| 0.9 | Subscriber | Subscribe | Subscribers can maintain a set of email subscriptions for an account. |
| 0.10 | Visitor | Browse | Visitors can browse the Welcome, Login, and Register pages (only) without presenting credentials. |
| 0.11 |
Subscriber | Theme | Subscribers can select an alternate theme (or "skin") for the application. |
| 0.12 |
Subscriber | Expired | Subscribers can reactivate an expired account. |
| 0.13 |
Subscriber | Retrieve | Subscribers can check email subscriptions for new messages. |
| 0.14 |
Subscriber | Compose | Subscribers can compose email messages and replies. |
See also
MailReader Object Model
JPA System Use Cases
| Priority | Actor | Goal | Story or Brief |
|---|---|---|---|
| 0.1 | Engineer | Starter | Setup new MyEclipse project for JPA with database. |
| 0.2 | Engineer | CRUD | Create, retrieve, update, and delete entity objects. |
Browse
(Struts University)
Classic Use Cases
(Struts University)
Compose
(Struts University)
CRUD
(Struts University)
dao
(Struts University)
Expired
(Struts University)
Localize
(Struts University)
Login
(Struts University)
Logout
(Struts University)
Menu
(Struts University)
Profile
(Struts University)
Read Mail
(Struts University)
Register
(Struts University)
Retain
(Struts University)
Retrieve
(Struts University)
Starter
(Struts University)
Starter (create)
(Struts University)
Subscribe
(Struts University)
TestData
(Struts University)
Theme
(Struts University)
Welcome
(Struts University)
Q: Will the use cases be based on existing implementation of MailReader? Because I am not sure that combining User Profile and Subscripiton List on one page is the best design/usability decision.
Q: Will MailReader Demo actually become a mail reader? Currently it only collects the email addresses.
Posted by >> Will the use cases be based on existing implementation of MailReader? Because I am not sure that combining User Profile and Subscripiton List on one page is the best design/usability decision.
A: Ideally, a Use Case should be implementation neutral. I made some changes this morning to eliminate the Welcome use case, which was not a proper case.
>> Will MailReader Demo actually become a mail reader? Currently it only collects the email addresses.
A: I don't plan on taking it that far myself, but it seemed reasonable for the Use Cases to extend out to at least a rudimentary production release. The cases that have not been implemented, and may never be implemented, are marked with the dim bulbs. The outermost use case (with the bright bulb) would then ever be a "work in progress".
Q: Should a person who has not logged in yet, be considered a mere "visitor", but not "subscriber"?
A: Yes.