1. USE CASE
DOCUMENTAION
Team: Honeydew

2. Version Author Other
1.0 Jiping Zhou
2.0 Jiping Zhou Added the whole use case and
revised the document

3. Contents
Contents......................................................................................................................................................3
1. Simple View.............................................................................................................................................7
Complete Use Case: Add Meeting to Honeydew.....................................................................................7
2. Detailed View...........................................................................................................................................9
1. Use Case: Trigger Honeydew...............................................................................................................9
2. Use Case: Confirm Meeting Information...........................................................................................11

4. Figure 1 Simple View of Use Case Diagram

5. Figure 2 Detailed Use Case Diagram

6. Figure 3 Detailed Use Case Diagram (Revised One)

7. 1. Simple View
Complete Use Case: Add Meeting to Honeydew
Scope: Honeydew Application
Level: User goal
Stakeholder and Interest:
• User:
 want to add the meeting information from an e-mail into his/her own Google calendar
through Honeydew;
 want to get as accurate meeting information as possible with the help of Honeydew,
which means little modification is required
• Honeydew:
 want to provide detail information about a meeting e-mail to the user;
 want to revise the information classifier model to require higher prediction accuracy in
the future;
 want to achieve better user experience from one iteration to another
Preconditions:
• The user has successfully installed Honeydew on Firefox.
• Honeydew server has started up successfully.
• An initial retrieval/classifier model has been trained on Honeydew.
Success Guarantee (Postconditions):
• A meeting event of an e-mail has been added to actor’s Google Calendar under “honeydew”
category.
Main Success Scenario (Basic Flow)
This use case starts when an actor wishes uses Honeydew System.
1. User browses to Google Email and reads an email in it.

8. 2. User clicks the “Honeydew” on the head of the email.
3. Honeydew reads the mail and predicates most possible meeting date, meeting time and
meeting location.
4. Honeydew opens another window in web browser and provides user with a meeting request
form having information got form step 3.
5. User confirms the information in the window and corrects all wrong information.
6. User chooses to add the meeting event into the Honeydew or cancel the meeting request.
7. Honeydew adds the meeting event of the e-mail to actor’s Google calendar under “honeydew”
category.
Alternative Workflow
• For step 6, the alternative workflow is:
Actor can choose to cancel adding the meeting event into the Google Calendar.
Special Requirements
• After user clicks on “Honeydew”, he/she will receive some help messages.
• If the event has been successfully added to the Google calendar, a “congratulation” message
will be popped up.
• If there is anything wrong in the input, a warning message should be provided to the user.
• The response time of “Honeydew” is less than 5 seconds.
Frequency of Occurrence: Depends on the user.
Open Issues:
1. How to distract user from waiting time?
2. How to make Honeydew available for various languages?
3. How to make Honeydew available for other browsers such as Internet Explorer?

9. 2. Detailed View
1. Use Case: Trigger Honeydew
Scope: Honeydew Application
Level: User goal
Stakeholder and Interest:
• User: want to get the meeting information (including meeting date, meeting time and meeting
location) through Honeydew
• Honeydew: want to provide detail information about a meeting to the user
Preconditions: The user has successfully installed Honeydew on Firefox and opened an email in Google.
Honeydew server has started up successfully.
Success Guarantee (Postconditions): Honeydew provides information about the meeting in the email in
a form.
Main Success Scenario (Basic Flow)
This use case starts when an actor wishes uses Honeydew System.
8. User opens an email in Google.
9. User clicks the “Honeydew” on the head of the email.
10. Honeydew reads the request meeting request and predicates most possible meeting date,
meeting time and meeting location.
11. Honeydew provides user with meeting information in a web form.
Alternative Workflow
• None.
Special Requirements
• After user clicks on “Honeydew”, he/she will receive some help messages.
• The response time of “Honeydew” is less than 5 seconds.
Frequency of Occurrence: Depends on the user.

10. Open Issues:
4. How to distract user from waiting time?
5. How to make Honeydew available for various languages?
6. How to make Honeydew available for other browsers such as Internet Explorer?

11. 2. Use Case: Confirm Meeting Information
Scope: Honeydew Application
Level: User goal
Stakeholder and Interest:
• User: Want to confirm whether Honeydew provides correct information. If it is not the case,
user will modify the information to improve Honeydew performance.
• Honeydew: Want to improve Honeydew learning model.
• Honeydew Research: Want to learn about how user expresses a meeting request.
Preconditions: Honeydew has provided meeting information from internal parsing model.
Success Guarantee (Postconditions): Honeydew improves its existing learning model.
Main Success Scenario (Basic Flow)
This use case starts when Honeydew has provides a draft version of meeting information to the user
through web servlet.
1. The Honeydew system provides meeting information of an email in a form through web
browser.
2. The actor checks provided information and correct them if something is wrong.
3. Honeydew improves the learning model according to user’s modification.
Alternative Workflow
• None.
Special Requirements
• None.
Frequency of Occurrence: Each session once.
Open Issues:
How to deal with if the actor wrongly inputs content?