Project: PassLock

The Team George Bell Chris Doty Carey Johnson Luke Kelly

PassLock Overview Make it Easier for Users to Control and Maintain Login Information and Passwords Maintain a Secure Database Let Users Share Information When Required

Individual Contributions George Bell – Project manager, assembles and combines the input of each team member Chris Doty – Project Description and Data Requirements Carey Johnson – Information and Interface Requirements Luke Kelly – Tools/Techniques and part of Introduction All - Review and Approve Sections Truly a Team Effort

Background Who is the Client? General Use Product Anyone Who Has Login Information and Needs a Better System to Maintain and Control Their Login Information

Problem Statement Computer Users Have Multiple Login/Password Combinations to Remember Information is Forgotten or Lost Information is Stored Insecurely Users May Have Shared Logins Users May Use Multiple Computers

Goals & Objectives Store and Manage User Passwords Allow for Sharing of Passwords Portable – Can Be Used on Multiple Computers Secure – Files Encrypted Policies Stored – Rules Regarding Passwords Allow Users to Synchronize Information

Scope Primary Design Purpose is to Share Passwords between Users Back-up Database to Prevent Loss of Data Will work for Single User Utilizes a Database

Constraints The scope of PassLock is limited by the following: Users must be able to share passwords Utilize a Database Use VB.Net as programming language

Functional Requirements Securely Input/Store Multiple Login Credentials Multiple Users Can Share/Synchronize Passwords Group Passwords By Access Rights Can Be Run From A USB Drive Copy Usernames or Passwords To Clipboard Top 5 Functional Requirements:

Store And Enforce Password Policies Generate Random Numbers Search For Passwords Hide Passwords From Others Multiple Database On Same Machine Functional Requirements Continued: Functional Requirements

Clickable Hyperlinks Screen Has Timeout Log All Data Changes Backup Password Database Preview/Print Password List Functional Requirements Continued: Functional Requirements

Easy To Use Interface Simple To Synchronize Non-Functional Requirements

Database ERD

User Interface Class Data Flow DataSet Classes Database Providers Encryption Providers Business Entities DataSet Adapters Session Management

Class Data Table

Class Diagram – Business Entities

Business Entity Table

Administrators control the system All users control their own accounts PassLock Use Cases System Scenarios (Level 1)

PassLock Use Cases Administrator Scenarios (Level 2) Administrators manage the PassLock system Administrators assist PassLock users

PassLock Use Cases Common Scenarios (Level 2) All users maintain their own Login Account All users maintain their own Application Profiles

PassLock Event-driven Process Chain (EPC Diagram) Accounts Shared Groups Group Profiles Personal Profiles External / Temporal System Management

PassLock Activity Diagram Securely Login to PassLock Make Personal Application Profiles Share Application Profiles with Groups Create Portable Information

Feasibility Analysis Solutions Considered Password Manager XP –Commercial Application Access Manager – Commercial Application RoboForm – Commercial Application Password Corral – Commercial Application PassLock – Custom Solution

Weighted Feasibility Analysis

PassLock Project Timeline: Requirements Next Milestone: Present Systems Design 4/16/2008 Milestone: Present Requirements 2/27/2008

PassLock Project: System Requirements PassLock Project (CS451 Phase) 67% PassLock Project (CS452 Phase) 0%

PassLock Questions & Answers Thank You

The End Thank You