1. Domain Model
MIS 430 Section 001
Matt DiDiano, Garrett Dutkiewicz, Tim May, Dan Simon, Phil Marucci

2. TABLE OF CONTENTS___________________________________________________
Grading Discrepancies ……………………………………………………………… 3
Use Case Diagram ………………………………………………………………….. 4
Use Case Briefs …………………………………………………………………….. 5
1. Manage User Accounts
2. Apply for Jobs
3. Search for Employees
4. Register User
5. Create Position
6. Send Employee information
7. Receive Verified Information
Use Cases (Fully Dressed) ………………………………………………………… 12
1. Manage User Accounts
2. Apply for Jobs
3. Send Employee Information

3. Use Case:Manage UserAccounts
Scope
Validity Document Vetting System
Brief
Allows the prospective employee to register within the Validity system and then create a user
profile to facilitate further use. The user provides his or her personal information, employment
history, education history, and resume information. The system processes the user information,
generates a user profile, and prompts the user for payment for use of the site. The customer can
pay with a debit card or a credit card.

4. Use Case:Manage UserAccounts
Scope
Validity Document Vetting System
Level
Summary
Primary Actor
Customer
Stakeholders and Interests
● Customer: Wants to create an account to be able to access system.
● Validity: Wants to receive user information.
Preconditions
Customer already has internet connection. Customer is already on website.
Success Guarantee
● Create and Update: User account exists in the system and contains most recent
information.
● Delete: User account is removed from the system
Trigger
First step in Main Success Scenario.
Main Success Scenario
1. User specifies account operation to be performed.
2. User performs account operation.
3. System indicates successfulcompletion of the operation.
Extensions
2a. User specifies Create operation.
1. User specifies account information
2. System validates data.
1a. Required information incorrect.
1. System prompts for correct information.
2. User specifies account information.
3. System returns to step 2a2
1b. User already exists.
1. System prompts for login information.
2. User specifies login information.
3. System returns to Main Success Scenario 3.
3. System creates user account.
2b. User specifies Update operation.
1. User specifies account to be updated.
2. User specifies updated account data.
3. System validates data.
1a. Required information incorrect.

5. 1. System prompts for correct information.
2. User specifies account information.
3. System returns to step 2b3.
4. System updates account data.
2c. User specifies Delete operation.
1. User specifies account to be deleted.
2. System prompts for confirmation.
3. System deletes account from system.
Supplemental Requirements
None identified
Technology and Data Variations List
None identified
Frequency of Occurrence
None identified
Open Issues
None identified

6. Use Case: Apply for Jobs
Scope
Validity Document Vetting System
Brief
Allows employee to search for employer profiles or open job positions and apply to open
positions. The user enters search criteria for job type, job title, location, or employer. The
system processes user input, queries the system database to find relevant employer
profiles and open positions, and displays these profiles and open positions for employees
to view and apply to if they choose.

7. Use Case:Apply for Jobs
Scope
Validity Document Vetting System
Level
User Goal
Primary Actor
Customer
Stakeholders and Interests
● Customer: Wants to search and apply for open positions
● Validity: Wants to provide a safe, reliable source to exchange employee
information
● Employer: Wants to fill an open position
Preconditions
Customer already has internet connection. Customer has already accessed and registered
to the site.
Success Guarantee
The user is able to search and apply to open positions that are displayed by the system based on
search criteria entered by the user.
Trigger
First step in Main Success Scenario.
Main Success Scenario
1. User selects job search function.
2. User fills in desired criteria for a position.
3. System displays jobs with descriptions matching user criteria.
4. User selects desired job.
5. System displays detailed job information.
6. User selects to apply for position.
7. System sends user profile to company.
8. Posting company receives employee information.
Extensions
*a. User cancels search.
1. System returns to initial state.
*b. System failure occurs during process.
1. System notifies user.
2. System returns to initial state.
4-6a. Open job position is no longer available
1. System notifies user.

8. 2. System updates the database.
3. System returns to main success scenario step 3.
2a. User does not fill in any search criteria.
1. System notifies user that at least one criteria must be entered.
2. System returns to initial state.
3a. Search criteria does not match any open positions.
1. System notifies user.
2. System returns to main success scenario step 2.
Supplemental Requirements
None identified
Technology and Data Variations List
None identified
Frequency of Occurrence
Continuous
Open Issues
None identified

9. Use Case: Search for Employees
Scope
Validity Document Vetting System
Brief
Allows employer to search to find possible employees. The employer enters search
criteria for desired employee skills, experience, or name. The system searches employee
database, analyzes the possible employee's information, and displays employees for
company to target.

10. Use Case: RegisterUser
Scope
Validity Document Vetting System
Brief
Allows employer or employee to register with the system and create a profile. The user
provides personal information and payment information. The system processes the
financial transaction, creates a user account, and updates user database. The customer
registers as either an employer on an employee and can pay with a debit or credit card.

11. Use Case: Create Position
Scope
Validity Document Vetting System
Brief
Allows employer to add an active opening to the system for prospective employees to
apply to. The employer provides position summary, and qualification requirements.
System displays position to possible employees.

12. Use Case: Verification of Employee Information
Scope
Validity Document Vetting System
Brief
Allows system to send employee information to a 3rd party source. System gathers and
sends information from user input database to 3rd party source to be verified. The 3rd
party system sends verification status of information to system. System receives verified
information from 3rd party and updates user profiles to show which information has been
verified. Employee information can be verified, partially verified, or unverified.

13. Use Case: Verification of Employee Information
Scope:
Validity Document Vetting system
Level:
User Goal
Primary Actor:
Employer
Stakeholders and Interests:
● Customer: Wants information to be validated.
● Validity: Wants to exchange employee information with 3rd party for validation.
● Employer: Wants prospective employee information to be validated.
● Third Party System: To validate the customer information for the employer.
Preconditions
Customer has filled out all necessary information required by the employer.
Success Guarantee
The Third Party System will validate the submitted employee information for the
employer.
Trigger
First step in Main Success Scenario
Main Success Scenario
1. Employee submits information for data verification.
2. System sends employee information to Third Party System.
3. System receives information from Third Party System.
4. System confirms Third Party System validation.
5. System send verified information packet to Employer.
6. System updates user profiles to show verified information.
Extensions
*a. User Cancels search.
1. System returns to initial state.
*b. System Failure occurs during process.
1. System notifies user.
2. System returns to initial state.
1a. Submission fails.
1. Notifies employee of failure.

14. 2. Return to Main Success Scenario 1.
2a. Send Fails.
1. Notifies employee of failure.
2. Return to Main Success Scenario 2.
3a. Employee Information is Invalid.
1. System notifies employee.
2. Return to Main Success Scenario 1.
3b. Third Party System fails to return information.
1. System notifies Third Party System of lack of return.
2. Return to Main Success Scenario 2.
Supplemental Requirements
None Identified
Technology and Data Variations List
None Identified
Frequency of Occurrence
Continuous
Open Issues
None