Irina Astrovskaya

1
Personal Information Management Software

• Irina Astrovskaya
• Daniel Bain
• Chris Gardner
• Kal Kolberg

2
Team organization
Irina Developer Technical Writer Daniel
Developer Technical Writer Chris Developer
Project Manager Kal Lead Developer
3
Introduction

• Too much info to keep track of by hand
• contact info
• Important tasks
• birthdays
• events (parties, appointments, etc.)
• Use electronic personal organizer
• small
• easy to use
• data is portable

4
Big problem

• Programs on electronic personal organizers
• too few features
• independent components
• proprietary

5
Our solution

• Personal information management (PIM) system
• cross-platform
• non-proprietary
• Familiar features
• add, edit, delete
• see events on calendar
• schedule and prioritize tasks
• simple, easy-to-use format

6
Specific features

• Add, change, view, delete, print and search for
  events, tasks and contacts
• View his schedule in different time range or by
  categories
• Set reminder or priority to the event
• Recur event
• See information of participator of event
• Sort tasks alphabetically, by priority, or by
  date
• Move task to calendar
• Update calendar with birthday when creating new
  contact

7
Limitations

• Network
• no internet/network
• standalone
• Security
• no password or encryption
• reliant on existing system
• good ? no interference
• bad ? system dependency

8
Design goals

• Readability
• post-production add-ons by outsiders
• open-source modification
• Portability
• different OS environments
• Usability
• easy for everyone
• Extensibility
• lacking full features due to time constraints
• easy to add future modules

9
Design goals (cont.)

• Delivery time
• no later than December 11, 2006
• Speed over space
• optimized for single user
• most modern computers have enough storage space

10
System design - then
11
System design - now
12
GUI interface

• GUI interface
• Portable Code
• Swing
• SWT
• Graphics
• Creative Commons
• Experience
• Needs Polishing

13
Control System

• Object management
• Modules are self-contained
• To access information request object from control
• List of available resources
• More reliable code

14
Generic class interface

• Main control unit maintains resource list
• Each module registers with control object
• Standardized interface between control and
  modules
• Messaging system
• Module features
• Version
• Callable objects
• Initialization

15
Classes

• 4 Basic classes for each module
• Discrete Objects
• Each class represents one event, task or contact
• Management Object
• Control loading
• Interface object
• Provides standard interface to GUI
• GUI object
• Graphics for module

16
Data storage

• Custom Btree file system
• System Specs No Relational Database
• Custom File system
• Requirement to prevent data loss
• Save after every change
• Performance Requirements
• Indexed system
• Coding complexity
• Centralized Code

17
HW SW specifics

• Java Base w/graphics interface
• Interactive system
• Swing
• Portable
• Self-executing Jar file
• Developed 64-bit Linux
• Tested 32-bit Linux 32-bit Microsoft windows
• Storage
• Configuration
• Platform dependant
• Azureus http//azureus.sourceforge.net/
• Data
• Standard Java
• Networking
• Not Required

18
Development tools

• Eclipse http//www.eclipse.org/
• Jigloo http//www.cloudgarden.com/jigloo/
• Automatic installation
• Commercial software
• Free for non-commercial use
• MySQL http//www.mysql.org/
• Itzam http//www.coyotegulch.com/products/itzam/
  index.html
• CVS http//www.nongnu.org/cvs/
• Bugzilla http//www.bugzilla.org/

19
Demo
20
Today tomorrow

• Where are we?
• 1st version complete
• What else is planned?
• modify for multiple users
• add more security
• integration with other software
• insert extra features
• enable networking/internet

21
TTFN!