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 PasswordsMaintain a Secure DatabaseLet Users Share Information When Required

Individual ContributionsGeorge Bell – Project manager, assembles and combines the input of each team memberChris Doty – Project Description and Data RequirementsCarey Johnson – Information and Interface RequirementsLuke Kelly – Tools/Techniques and part of Introduction

All - Review and Approve SectionsTruly a Team Effort

Background Who is the Client?

General Use ProductAnyone 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 RememberInformation is Forgotten or LostInformation is Stored InsecurelyUsers May Have Shared LoginsUsers May Use Multiple Computers

Goals & Objectives

Store and Manage User PasswordsAllow for Sharing of PasswordsPortable – Can Be Used on Multiple ComputersSecure – Files EncryptedPolicies Stored – Rules Regarding PasswordsAllow Users to Synchronize Information

Scope

Primary Design Purpose is to Share Passwords between UsersBack-up Database to Prevent Loss of DataWill work for Single UserUtilizes 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 CasesSystem Scenarios (Level 1)

PassLock Use CasesAdministrator Scenarios (Level 2)

Administrators manage the PassLock system

Administrators assist PassLock users

PassLock Use CasesCommon 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 PassLockMake Personal Application ProfilesShare Application Profiles with Groups Create Portable Information

Feasibility AnalysisSolutions Considered

Password Manager XP –Commercial ApplicationAccess Manager – Commercial ApplicationRoboForm – Commercial ApplicationPassword Corral – Commercial ApplicationPassLock – Custom Solution

Weighted Feasibility Analysis

PassLock Project Timeline: Requirements

Next Milestone: Present Systems Design4/16/2008

ID Task Name Duration Start Finish Resource Names

1 1 CS451: Software Engineering I 76 days Mon 1/14/08 Wed 4/16/08 Lisa Rich

2 1.1 Scope Definition 9 days Mon 1/14/08 Fri 1/25/08

7 1.2 Problem Analysis 14 days Mon 1/21/08 Wed 2/6/08

8 1.2.1 Understanding the Problem Domain 7 days Mon 1/21/08 Sun 1/27/08 Luke Kelly

9 1.2.2 Analyze Problems and Opportunities 7 days Mon 1/21/08 Sun 1/27/08 Carey Johnson

10 1.2.3 Analyze Business Processes 7 days Mon 1/21/08 Sun 1/27/08 Chris Doty

11 1.2.4 Establish System Improvement Objectives 7 days Mon 1/21/08 Sun 1/27/08 George Bell

12 1.2.5 Update or Refine Project Plan 9 days Sun 1/27/08 Tue 2/5/08 4 Guys & A Computer

13 1.2.6 Communicate Recommendations 0 days Wed 2/6/08 Wed 2/6/08

14 1.2.6.1 Submit Statement of Work 0 days Wed 2/6/08 Wed 2/6/08 4 Guys & A Computer

15 1.3 Requirements Analysis 23 days Thu 2/7/08 Wed 3/5/08

16 1.3.1 Identify & Express System Requirements 6 days Thu 2/7/08 Fri 2/15/08 4 Guys & A Computer

17 1.3.2 Prioritize System Requirements 7 days Sun 2/17/08 Fri 2/22/08 4 Guys & A Computer

18 1.3.3 Update or Refine the Project Plan 5 days Sun 2/24/08 Wed 2/27/08 4 Guys & A Computer

19 1.3.4 Communicate Requirements Statement 0 days Wed 2/27/08 Wed 2/27/08

20 1.3.4.1 Walkthrough 1: Systems Analysis 0 days Wed 2/27/08 Wed 2/27/08 4 Guys & A Computer

21 1.3.5 Finalize Approved Project Plan 4 days Thu 2/28/08 Wed 3/5/08

22 1.4 Logical Design 21 days Thu 3/6/08 Fri 4/4/08 4 Guys & A Computer

26 1.5 Decision Analysis 10 days Mon 4/7/08 Wed 4/16/08 4 Guys & A Computer

27 1.5.1 Review Candidate Solutions 4 days Mon 4/7/08 Fri 4/11/08

32 1.5.2 Update the Project Plan 5 days Sun 4/13/08 Wed 4/16/08

33 1.5.3 Recommend System Solution 0 days Wed 4/16/08 Wed 4/16/08

34 1.5.3.1 Walkthrough 2: Systems Design 0 days Wed 4/16/08 Wed 4/16/08 4 Guys & A Computer

35 2 CS452: Software Engineering II 64 days Mon 6/2/08 Thu 8/28/08 Beth Allen

36 2.1 Physical Design 19 days Mon 6/2/08 Fri 6/27/08

38 2.2 Construction and Testing 24 days Mon 6/30/08 Fri 8/1/08

40 2.3 Delivery and Implementation 19 days Mon 8/4/08 Thu 8/28/08

Luke Kelly

Carey Johnson

Chris Doty

George Bell

4 Guys & A Computer

2/6

4 Guys & A Computer

4 Guys & A Computer

4 Guys & A Computer

2/27

4/16

January February March April May June July August September

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 EndThank You