Email and Calendar

Previous page : School eBooks

eReading devices are also a great way to process information such as email and electronic calendars. In general, an eReading device allows to increase our personal productivity by bringing information closer (our pocket or bag).

<todo> Add other productivity elements : collaboration...

<todo>A word about Collaboration Services and Lotus Notes.


Those components (email and calendar) are rather basic but they will play an important role in many good eReading scenarios. They can help to notify the user of events, send relevant information and even be the basis of a document distribution system.

Links :

Business Object : Agenda

The agenda of the eReader User.

Business Object : Mailbox

The mailbox of the eReader User.

Business Event

<todo> New Mail, New Meeting Request → Alerting Services

Business Process : Process emails

Just like the “Reading Documents” functionality has been promoted as a Business Process on the eReader Tier, processing emails might just like a functionality. Ii is here described as a process as it is more complex than just read a series of emails. Prioritization strategies are possible and actions can be executed during the email processing.

Business Process : Organize calendar

The process of making, reviewing and modifying a user's calendar.

Business Actor : Information Worker

The main actor here is an Information Worker who needs access to his email and calendar.

Business Role : eReader User

The eReader User is an information worker who uses an eReader for his email and Calendar.

Data Object

<todo> Data objects can be emails (ex:elm files) or calendar information (ex:ICS files)

Data Object : Email Archive

If emails are read on the eReader, an archive will maybe still reside on the Desktop. This will depend on the Storage Constraints Obstacle.

Application Service : WebCalendar

A web-based calendering service (ex: Google Calendar)

Application Service : WebMail

A web-based email service (ex: Gmail, Hotmail, Yahoo! Mail...)

Application Service : Mail System

The server side of a LAN-based Mail System (ex: Lotus Domino, MS Exchange...)

Application Function

<todo> List some important functions (add appointment, add meeting, send email, receive email...)

→ Will be further specified as other scenarios use calendar and email...

Application Interface

<todo>IMAP, POP, Google APIs...

Application Component : Email Client

On the Desktop tier, one will still find an email client. The collaboration between the email client and the other tiers is an important element here as multilying the number of places where emails and calendars can be modified could lead to synchronization problems.

Communication Path

Mobile Internet will become mainstream for eReaders, so Information Workers can access their emails and calendar anywhere.

Device

The tablets have an enormous advantage versus ePaper based devices for email and calendaring. They can use the webmail or their specific email clients (Google Mail on Android, Mail app on the iPad). Reading emails and calendar on ePaper devices is more complicated. There are several possibilities:

  • Running a custom optimized browser (like Midori on an iRex DR1000S or like this on the Kindle : http://delicious.com/appepaper/kindle+email )

    <todo>make a photo and publish the link - http://delicious.com/appepaper/Midori

  • Writing a custom app for downloading and displaying emails. It could for example be a Kindle App.

  • Transform your mailbox into a series of pdf or ePub documents and upload them to your eReader



Next page : Knowledge Bases
ċ
Fig027-PersonalProductivityByTier.png
(72k)
Jean-Francois Declercq,
Aug 9, 2011, 6:25 AM
Comments