Civil Rights Management System Uses Cases V1.0

7/31/2019 Civil Rights Management System Uses Cases V1.0

1/39

Use Cases

For

Civil Rights Management

System

Payroll Web Application

1.0

Version 1.0

Prepared by the CPMS Team - September, 2005


2/39

Revision History

Name Date Reason For Changes Version

Keith Janes 6/29/2005 initial draft 1.0 draft 1Keith Janes 9/1/2005 revised draft 1.0 draft 2


3/39

Use Cases for Civil Rights Management System Page 1

The various user classes identified the following use cases and primary actors for the Civil Rights

Management System:

Primary Actor Use Cases

ContractorProject Engineer

Division Payroll

Compliance

Administrator

Central Office Payroll

Compliance

Administrator

Office Engineer

1. Add Contractor2. Enter Certified Payroll3. Upload Certified Payroll File4. Check Certified Payroll5. Submit Certified Payroll6. Approve Certified Payroll7. Add Job Craft8. Add Wage Decision9. Add Project Wage


4/39

1 / 1

Object-Oriented Model

Model: Certified Payroll Use Cases

Package:

Diagram: UseCaseDiagram_Main

Author: janesk Date: 9/1/2005

Version:

Contractor

Prime Contractor

Project Engineer

Division Compliance Administrator

CO Payroll Compliance Administrator

Register Contractor

Enter Certified Payroll

Upload Certified Payroll File Submit Certified Payroll

Office Engineer

Check Certified Payroll

Approve Certified Payroll


5/39


Use Case ID: 1

Use Case Name: Register Contractor

Actors: Contractor (Prime or Sub), Office Engineer

Description: A Contractor requests a CRMS User ID from ALDOT.

Preconditions: Contractor is a valid contractor or subcontractor in ALDOTs database.Postconditions:

Normal Flow: Register Contractor

1. Contractor accesses the CRMS web site and registers to get a new User ID.2. System verifies the contractor and stores the request.3. Office Engineer reviews the request and approves it.4. System sends the Request Approval back to the Contractor along with a new

User ID and initial Password.

Alternative Flows:

Exceptions: 2.0.E.1 If the contractor doesnt exist in the system, then the system displays an

error message to that effect.

2.0.E.2 If the Contractor has already been assigned a User ID, then the system

displays an error message to that effect.

3.0.E.1 If Office Engineer denies the request, a denial notification is sent back to

the Contractor.

Includes: None

Priority: High

Frequency of Use: As Required.

Business Rules:

Special Requirements:

Assumptions:

Notes and Issues:


6/39


Use Case ID: 2

Use Case Name: Enter Certified Payroll

Actors: Contractor (Prime or Sub)

Description: A Contractor accesses the Civil Rights Management System (CRMS) via the

Internet to enter a Certified Payroll.Preconditions: Contractor is logged into CRMS with an ID and password that uniquely

identifies them.

Postconditions:

Normal Flow: Enter Certified Payroll

1. User enters Certified Payroll data, including Federal Aid Project Number,Employee Social Security Numbers, the payroll date range, work hours,

wage rate, wages earned, and deductions.

2. User indicates that the Certified Payroll is completely entered.3. System prompts the user for Fringe Benefit exceptions, remarks, and

Statement of Compliance Signatory name and title.

4. System adds the Certified Payroll file to a list of payrolls ready to submit.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


7/39


Use Case ID: 3

Use Case Name: Upload Certified Payroll File



Internet to upload a Certified Payroll file.Preconditions: Contractor is logged into CRMS with an ID and password that uniquely

identifies them.

Postconditions:

Normal Flow: Upload Certified Payroll File

1. User selects the Certified Payroll file to be uploaded.2. User uploads the Certified Payroll file to ALDOT.3. System validates the Certified Payroll against the schema.4. System edits the Certified Payroll (see Use Case 5 Check Certified

Payroll).

5. System returns a validation report.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


8/39


Use Case ID: 4

Use Case Name: Submit Certified Payroll


Description: A Contractor accesses the Civil Rights Management System (CRMS) via theInternet to submit a Certified Payroll.

Preconditions: Contractor is logged into CRMS with an ID and password that uniquely

identifies them.

Postconditions:

Normal Flow: Submit Certified Payroll

1. User selects the Certified Payroll from list of available payrolls.2. User submits the Certified Payroll to ALDOT.3. System validates the Certified Payroll against the schema.4. System edits the Certified Payroll (see Use Case 5 Check Certified

Payroll).


Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


9/39


Use Case ID: 5

Use Case Name: Check Certified Payroll


Description: A Certified Payroll is Uploaded or Submitted to CRMS via the Internet. The

Certified Payroll is edited and stored, and a validation report is sent back to theContractor.


identifies them.

Postconditions:

Normal Flow: Check Certified Payroll

1. System verifies that the Employer is a valid ALDOT Contractor.2. System verifies that the Payroll is not a duplicate of a previously submitted

Payroll based on the Pay Period Dates, Contractor, and Project (Contract).

3. System verifies that the Project (Contract) is valid for the contractor.4. System verifies that the Job Crafts are valid for the Project (Contract).5. System verifies that the Hourly Rates meet or exceed the Prevailing Wage

Rate for the given Project and County.

6. System verifies calculations of total hours, total wages, and total deductionsagainst the net wages.

7. System stores the Certified Payroll data into the CRMS database.8. System returns a validation report.

Alternative Flows:

Exceptions: All exceptions are returned to the submitter with appropriate error messages in a

validation report.

Includes: None

Priority: High


Business Rules:Special Requirements:

Assumptions:

Notes and Issues:


10/39


Use Case ID: 6

Use Case Name: Approve Certified Payroll

Actors: Prime Contractor, Project Engineer, Division Payroll Compliance Administrator,

Central Office Payroll Compliance Administrator

Description: A user accesses the Civil Rights Management System (CRMS) via the Internet toapprove a Certified Payroll.

Preconditions: User is logged into CRMS with an ID and password that uniquely identifies

them.

Postconditions:

Normal Flow: Approve Certified Payroll

1. User selects the Certified Payroll from list of available pending CertifiedPayrolls.

2. User approves the Certified Payroll.3. Notification sent to the next up-stream approving authority for further

approval.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


11/39


Use Case ID: 8

Use Case Name: Add Wage Decision

Actors: Central Office Payroll Compliance Administrator

Description: Central Office Payroll Compliance Administrator accesses the Civil Rights

Management System (CRMS) to add a Wage Decision.Preconditions: User is logged into CRMS with an ID and password that uniquely identifies

them.

Postconditions:

Normal Flow: Add Wage Decision

1. User enters a new wage decision number, counties, date range, andprevailing wage rate.

2. System verifies the data and stores it into the Wage Decision table(s).

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


12/39


Use Case ID: 9

Use Case Name: Add Project Wage

Actors: Office Engineer

Description: Office Engineer accesses the Civil Rights Management System (CRMS) to add

or associate a Wage Decision to a project.Preconditions: User is logged into CRMS with an ID and password that uniquely identifies

them.

Project has been scheduled for letting to contractors.

Postconditions:

Normal Flow: Add Project Wage

1. For a given project, user enters the Wage Decision numbers associated withthe project.

2. System verifies the data and stores it into the Project Wage table.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


13/39

Use Cases

For


System

On The Job Training (OJT)Web Application

1.0

Version 1.0

Prepared by the CPMS Team September, 2005


14/39

Revision History


Keith Janes 8/31/2005 initial draft 1.0 draft 1


15/39



Management System:


Prime ContractorProject Engineer

Division

Human Resources

FHWA

1. Assign Project OJT Hours2. Enter OJT Plan3. Upload OJT Plan File4. Submit OJT Plan5. Check OJT Plan6. Approve OJT Plan7. Enter OJT Time Report8. Upload OJT Time Report File9. Submit OJT Time Report10.Check OJT Time Report11.Approve OJT Time Report12.Compile OJT Training Summary

Report13.Compile Enrollment Time Report14.Compile OJT Initial Enrollment

Report


16/39

1 / 1


Model: OJT Plan Use Cases

Package:

Diagram: UseCaseDiagram_1


Version:

Human Resources

Prime Contractor

Assign Project OJT Plan Hours

Upload OJT Plan File Submit OJT Plan

Check OJT Plan

Approve OJT Plan

Division

Enter OJT Plan


17/39


Use Case ID: 1

Use Case Name: Assign Project OJT Hours

Actors: Human Resources

Description: Human Resources assigns On the Job Training Hours to a project.

Preconditions: User is logged into CRMS with an ID and password that uniquely identifiesthem.

Project is in the initial planning stages, prior to being let to contractors.

Postconditions:

Normal Flow: Assign Project OJT Hours

1. For a given project, user enters the On the Job Training Hoursassociated with the project.

2. System verifies the data and stores it into the OJT Project Hours table.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


18/39


Use Case ID: 2

Use Case Name: Enter OJT Plan

Actors: Contractor (Prime)


Internet to enter an OJT Plan.Preconditions: Contractor is logged into CRMS with an ID and password that uniquely

identifies them.

Postconditions:

Normal Flow: Enter OJT Plan

1. User enters OJT data, including project ID, county, number of trainees, jobclassifications, and training hours for each classification.

2. User indicates that the OJT Plan is completely entered.3. System prompts the user for Signatory name and title.4. System adds the OJT Plan file to a list of plans ready to submit.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


19/39


Use Case ID: 3

Use Case Name: Upload OJT Plan File



Internet to upload an OJT Plan.Preconditions: Contractor is logged into CRMS with an ID and password that uniquely

identifies them.

Postconditions:

Normal Flow: Upload OJT Plan File

1. User selects the OJT Plan file to be uploaded.2. User uploads the OJT Plan file to ALDOT.3. System validates the OJT Plan against the schema.4. System edits the OJT Plan (see Use Case 5 Check OJT Plan).5. System returns a validation report.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


20/39


Use Case ID: 4

Use Case Name: Submit OJT Plan


Description: A Contractor accesses the Civil Rights Management System (CRMS) via theInternet to submit an OJT Plan.


identifies them.

Postconditions:

Normal Flow: Submit OJT Plan

1. User selects the OJT Plan from list of available plan files.2. User submits the OJT Plan to ALDOT.3. System validates the OJT Plan against the schema.4. System edits the OJT Plan (see Use Case 5 Check OJT Plan).5. System returns a validation report.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


21/39


Use Case ID: 5

Use Case Name: Check OJT Plan


Description: An OJT Plan is Uploaded or Submitted to CRMS via the Internet. The OJT Plan

is edited and stored, and a validation report is sent back to the Contractor.Preconditions: Contractor is logged into CRMS with an ID and password that uniquely

identifies them.

Postconditions:

Normal Flow: Check OJT Plan

1. System verifies that the Employer is a valid ALDOT Contractor.2. System verifies that the OJT Plan is not a duplicate of a previously

submitted OJT Plan based on the Submission Date, Contractor, and Project

(Contract).

3. System verifies that the Project (Contract) is valid for the contractor.4. System stores the OJT Plan data into the CRMS database.5. System returns a validation report.

Alternative Flows:


validation report.

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


22/39


Use Case ID: 6

Use Case Name: Approve OJT Plan

Actors: Prime Contractor, Division, Human Resources

Description: A user accesses the Civil Rights Management System (CRMS) via the Internet to

approve an OJT Plan.Preconditions: User is logged into CRMS with an ID and password that uniquely identifies

them.

Postconditions:

Normal Flow: Approve OJT Plan

1. User selects the OJT Plan from list of available pending OJT Plans.2. User approves the OJT Plan.3. Notification sent to the next up-stream approving authority for further

approval.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


23/39

1 / 1


Model: OJT Time Reporting Use Cases

Package:

Diagram: UseCaseDiagram_Main


Version:

Contractor

Project Engineer

Division

Upload OJT Time Report FileSubmit OJT Time Report

Human Resources

Check OJT Time Report

Approve OJT Time Report

Compile OJT Training Summary

Compile Enrollment Time Report

Compile OJT Initial Enrollment

FHWA

Enter OJT Time Report


24/39


Use Case ID: 7

Use Case Name: Enter OJT Time Report



Internet to enter an OJT Time Report.Preconditions: Contractor is logged into CRMS with an ID and password that uniquely

identifies them.

Postconditions:

Normal Flow: Enter OJT Time Report

1. Contractor enters OJT Time Reporting data, including project ID, countyreporting period, trainee, and trainees hours by training plan section and

subsection.

2. Contractor indicates that the OJT Time Report is completely entered.3. System prompts for Signatory name and title.4. System adds the OJT Time Report file to a list of report files ready to

submit.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


25/39


Use Case ID: 8

Use Case Name: Upload OJT Time Report File



Internet to upload an OJT Time Report file.Preconditions: Contractor is logged into CRMS with an ID and password that uniquely

identifies them.

Postconditions:

Normal Flow: Upload OJT Time Report File

1. User selects the OJT Time Report file to be uploaded.2. User uploads the OJT Time Report file to ALDOT.3. System validates the OJT Time Report against the schema.4. System edits the OJT Time Report (see Use Case 10 Check OJT Time

Report).


Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


26/39


Use Case ID: 9

Use Case Name: Submit OJT Time Report


Description: A Contractor accesses the Civil Rights Management System (CRMS) via theInternet to submit an OJT Time Report.


identifies them.

Postconditions:

Normal Flow: Submit OJT Time Report

1. User selects the OJT Time Report file from list of available time report files.2. User submits the OJT Time Report to ALDOT.3. System validates the OJT Time Report against the schema.4. System edits the OJT Time Report (see Use Case 10 Check OJT Time

Report).


Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


27/39


Use Case ID: 10

Use Case Name: Check OJT Time Report


Description: A OJT Time Report is Uploaded or Submitted to CRMS via the Internet. The

OJT Time Report is edited and stored, and a validation report is sent back to theContractor.


identifies them.

Postconditions:

Normal Flow: Check OJT Time Report

1. System verifies that the Employer is a valid ALDOT Contractor.2. System verifies that the OJT Time Report is not a duplicate of a previously

submitted OJT Time Report based on the Reporting Dates, Contractor, and

Project (Contract).

3. System verifies that the Project (Contract) is valid for the contractor.4. System verifies that the OJT Job Crafts are valid for the Project (Contract).

5. System verifies that the sections and subsections entered are valid for thegiven Project (Contract).

6. System stores the OJT Time Report data into the CRMS database.7. System returns a validation report.

Alternative Flows:


validation report.

Includes: None

Priority: High


Business Rules:

Special Requirements:Assumptions:

Notes and Issues:


28/39


Use Case ID: 11

Use Case Name: Approve OJT Time Report

Actors: Prime Contractor, Project Engineer, Division, Human Resources

Description: A user accesses the Civil Rights Management System (CRMS) via the Internet to

approve an OJT Time Report.Preconditions: User is logged into CRMS with an ID and password that uniquely identifies

them.

Postconditions:

Normal Flow: Approve OJT Time Report

1. User selects the OJT Time Report from list of available pending OJT TimeReports.

2. User approves the OJT Time Report.3. Notification sent to the next up-stream approving authority for further

approval.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


29/39


Use Case ID: 12

Use Case Name: Compile OJT Training Summary

Actors: Division, Human Resources

Description: Division compiles an OJT Training Summary Report and submits it to Human

Resources for review.Preconditions: User is logged into CRMS with an ID and password that uniquely identifies

them.

Postconditions:

Normal Flow: Compile OJT Training Summary

1. User selects the OJT Training Summary Report to be generated.2. System generates the OJT Training Summary Report.3. User reviews the report.4. User submits the report to Human Resources for review.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


30/39


Use Case ID: 13

Use Case Name: Compile Enrollment Time Report

Actors: Division, Human Resources

Description: Division compiles a Trainee Enrollment Time Report and submits it to Human

Resources for review.Preconditions: User is logged into CRMS with an ID and password that uniquely identifies

them.

Postconditions:

Normal Flow: Compile Enrollment Time Report

1. User selects the Trainee Enrollment Time Report to be generated.2. User reviews the report.3. User submits the report to Human Resources for review.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


31/39


Use Case ID: 14

Use Case Name: Compile OJT Initial Enrollment

Actors: Human Resources, FHWA

Description: Human Resources compiles an OJT Initial Enrollment Report and submits it toFHWA for review.


them.

Postconditions:

Normal Flow: Compile OJT Initial Enrollment

1. User selects the OJT Initial Enrollment Report to be generated.2. User reviews the report.3. User submits the report to Human Resources for review.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


32/39

Use Cases

For


System

Wage / EEO ReportingApplication

1.0

Version 1.0

Prepared by the CPMS Team September, 2005


33/39

Revision History


Keith Janes 9/1/2005 initial draft 1.0 draft 1


34/39



Management System:


Central Office PayrollCompliance

Administrator

Division EEO

Compliance

Administrator

Central Office EEO

Compliance

Administrator

Department of Labor

FHWA

1. Enter Wage Decision2. Add Job Craft3. Compile Wage Rate Survey4. Compile FHWA Form 1392


35/39

1 / 1


Model: Wage / EEO Reporting Use Cases

Package:

Diagram: UseCaseDiagram_1


Version:

Central Office Payroll Compliance Administrator Department of Labor

Add Job Craft

Compile Wage Rate Survey

Enter Wage Decision

Central Office EEO Compliance Administrator

Compile FHWA Form 1392Division EEO Compliance Administrator

FHWA


36/39


Use Case ID: 1

Use Case Name: Enter Wage Decision

Actors: Central Office Payroll Compliance Administrator, Department of Labor

Description: Central Office Payroll Compliance Administrator receives a Wage Decision from

the Department of Labor and enters it into the Civil Rights Management System(CRMS).


them.

Postconditions:

Normal Flow: Enter Wage Decision

1. Department of Labor publishes a new Wage Decision, including WageDecision Number, County(ies), Job Craft, Prevailing Hourly Wage Rates

and Prevailing Hourly Fringe Rates.

2. Central Office Payroll Compliance Administrator enters the new WageDecision Number.

3. System verifies that the Wage Decision Number doesnt already exist.

4. User enters the Job Craft.5. System verifies that the Job Craft exists in CRMS.6. User enters the Zone Number, County, Prevailing Hourly Wage Rate and

Prevailing Hourly Fringe Rate.

7. System adds the Wage Decision to the Wage Decision tables.

Alternative Flows: 3.0.E.1 If the Wage Decision Number already exists, then the system displays an

error message to that effect.

5.0.E.1 If the Job Craft Code does not exist, then the user is prompted to enter

the Job Craft (see Use Case 2 Add Job Craft below).

Exceptions:

Includes: None

Priority: HighFrequency of Use: As Required.

Business Rules:


Assumptions:

Notes and Issues:


37/39


Use Case ID: 2

Use Case Name: Add Job Craft

Actors: Central Office Payroll Compliance Administrator


Management System (CRMS) to add a Job Craft.Preconditions: User is logged into CRMS with an ID and password that uniquely identifies

them.

Postconditions:

Normal Flow: Add Job Craft

1. User enters a new job craft code and description.2. System verifies the data and stores it into the Job Craft table.

Alternative Flows:

Exceptions:

Includes: None

Priority: High

Frequency of Use: As Required.Business Rules:


Assumptions:

Notes and Issues:


38/39


Use Case ID: 3

Use Case Name: Compile Wage Rate Survey



Management System (CRMS) to compile a Wage Rate Survey Report to send tothe Department of Labor.


them.

Postconditions:

Normal Flow: Compile Wage Rate Survey

1. User selects a Zone or County for which a Wage Rate Survey Reportshould be generated.

2. System generates the Wage Rate Survey Report.3. User reviews the report.4. User submits the report to the Department of Labor.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:


39/39


Use Case ID: 4

Use Case Name: Compile FHWA Form 1392



Management System (CRMS) to compile a Form 1392 (Summary ofEmployment Data) Report to send to the Department of Labor.


them.

Postconditions:

Normal Flow: Compile FHWA Form 1392

1. User selects FHWA Form 1392 (Summary of Employment Data) Reportto be generated.

2. System generates the FHWA Form 1392 (Summary of EmploymentData) Report.

3. User reviews the report.4. User submits the report to FHWA.

Alternative Flows:

Exceptions:

Includes: None

Priority: High


Business Rules:


Assumptions:

Notes and Issues:

Civil Rights Management System Uses Cases V1.0

Documents

Transcript of Civil Rights Management System Uses Cases V1.0