Project Bid Proposal 1

Version 1.0

Date: Friday Jan 14, 2005

Product: eWallet - Project Description

Team Silent Mission

Jenny Greenwood, Shannon Whitaker, Brittney Brown, Zack Douglas

1.0 Project Preferences

2.0 Qualifications & Tradeoffs

2.1 Strengths and Qualifications

    We have a diverse team to specialize in each of the necessary areas for this 
     project.  The project is diverse and needs development in various sections.  We have 
     team members competent in Java, C++, Smart Cards and Web Development.  Some 
     documentation has already been done on this project but NO code has been written.

     We are all devoted to providing sufficient time to the project not only to obtain a 
     good grade in this class, but to produce a great piece of software. We feel we have 
     a unique opportunity to create something cool because all the hardware and cards 
     have already been agreed to be supplied to the team.  No other team will have access 
     to this equipment without some hard work getting it.

2.2 Trade-offs, Constraints, and Special Considerations

     Smart cards are a new technology and we would like to explore a practical use
     for them.  It is true most of our members due not have experience with them but all 
     have the desire to learn.  It is also true that our project is not going to be 
     applicable in real world applications at this time.  To actually work in the real 
     world all vendors would have to more generally accept smart cards -  which has not 
     happened yet.  

     Smart cards are also expensive and more expensive than mag stripe cards.  But the 
     theory of a one card wallet is a fantastic idea that we would like to implement today.
     The cards themselves only hold 32K of data so we will need to find ways to compress image
     files and store all the data as efficiently as possible.

3.0 Project Name - eWallet

3.1 Approach

    Our approach is to provide all of the items that go in a wallet the option of 
     going on one card including driver’s license, money, credit cards with additional 
     security not provided on regular wallets like fingerprint verification and pin access.  

     Each of these separate functions on the card will involve separate java applet designs.  
     Using applets will be necessary to transfer the information to the system.  We will also 
     implement the end-user applications that manipulate the card applets include a point of 
     sale console, drivers license enrollment console, credit card editing and stored cash 
     value interfaces.

     It seems to make the most sense to design each applet and cooresponding system together 
     and then move on to the next applet.

3.2 Implementation Considerations

    Java will provide many of the important components and libraries for interactions 
     with the smart card and card readers.  IBM wrote the smart card operating system and 
     provides the Java libraries necessary to communicate with it.  They also provide PCSC for 
     the card readers.  These IBM Java components and libraries are absolutely necessary for
     the project to be functional.