Name of the project : Personal Identity Management
Objective /Vision Stand-alone product that aggregates identity records of an
individual and creates a secure file that can be used by the individual and authorized people only. Something like a personal data vault. User of the system Owner and authorized persons. Functional Requirements 1. Security, encryption and paper-trail of usage. 2. Ability to store data with history 3. Ability to link data with applications with native inerfaces. 4. Ability to set rules for the kinds of applications that can access it. 5. Cookie manager interface: Interface it with applications and create multiple cookies with different user ids. 6. Generate Ghost ids for use with anonymous services. 7. Logging applications and IPs that have accessed data. 8. Function as a storage locker for passwords. 9. Complete control over access from external applications. Non-Functional Requirements i. Secure access of confidential data (user’s details). SSL can be used. ii. 24 X 7 availability iii. Better component design to get better performance at peak time Flexible service based architecture will be highly desirable for future extension Optional Features 1. Function as gateway to advice on “perfect” identity management. User Interface Priorities A. Professional look and feel B. Use of AJAX atleast with all registration forms C. Browser testing and support for IE, NN, Mozila, and Firefox. D. Use of Graphical tool like JASPER to show strategic data to admin E. Reports exportable in .XLS, .PDF or any other desirable format Reports Printed paper trail. Other Important Issues Good hashing and encryption techniques to protect information. Team Size 2 – 4 members Technologies to be used UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA Tools to be used • ROSE/RSA / WebSphere Modeler • Eclipse/ RAD / Lotus Forms Designer / Portlet Factory • WebSphere Portal/ WAS/ WAS CE / WPS • DB2 Express – ‘C’ or DB2 UDB • Tivoli CDP/TSM / Tivoli Directory Server Linux will be the preferred OS. Final deliverables must include A. Online or offline help to above said users, Application deployment executive and developer B. Application archive ( .war/.ear ) with source code C. Database backup and DDL Script D. Complete Source code Documents