About the Data Quality Design for the Sample Application

Item No.

Description

Requirement(s) Satisfied

DQD1

Reasonable measures should be taken to ensure duplicate records do not exist for Customers. The system will use a duplicate checking object for the Customers entity to identify potential duplicates that match on First and Last Names and absolute duplicates that match on First Name, Last Name, and phone number.

BPR3: Prevent Duplicate Customer Accounts

DQD2

Reasonable measures should be taken to ensure duplicate records do not exist for Vehicle Models. The system will use a duplicate checking object for the Vehicle Models entity to identify absolute duplicates for matching year, make, and model name, and partial duplicates for matching make and model name.

BPR6: Prevent Duplicate Models

DQD3

Basic field level validation will be used for the Customers and Associates entities to help ensure the format (data type integrity) for email addresses (xxxx@yyyy.zzz).

BPR4: Enforce Email Address Format; UIR2: User-Friendly Warnings When User Enters Incorrect Value

DQD4

Vehicle Model Year has a valid range of values. The Year Field in the Vehicle Models entity will include field level validation so that a value entered by a user is only valid if between (current year - 10 years) to (current year + 1 year). For example since the current year is 2007, only vehicles 1997 to 2008 may be entered.

BPR7: Prevent Older Model Vehicles from Entering Fleet

DQD5

Basic field level validation will be used on the VIN Field in the Vehicles entity. VINs only contain 17 alphanumeric characters and exclude I, O, and Q.

BPR10: Enforce VIN Number Accuracy; UIR2: User-Friendly Warnings When User Enters Incorrect Value

DQD6

If/when a vehicle is disposed, both the date and method must be recorded in the vehicle record. The system will use field level validation for the DisposalMethod and DisposalDate Fields in the Vehicles entity to ensure that both fields are set by the user. When a Vehicle is disposed, the Status should update automatically to reflect this new state as well.

BPR12: Track Vehicle Disposal; BPR11: Automatically Track Vehicle Status and Mileage; UIR2: User-Friendly Warnings When User Enters Incorrect Value

DQD7

The system will include a field validation script to automatically update a vehicle's status as needed without requiring manual intervention from a user.

UIR4: Prevent Users From Manually Setting Vehicle Status

DQD8

Only vehicles that are available for rent during the Customer's specified rental period (Rental Date to Expected Return Date) should be allowed to be selected for that Rental Agreement.

BPR13: Automatically Identify Available Vehicles

DQD9

Only a manager can modify the Release to Fleet selection option to approve a vehicle's servicing and return it to the rental pool. The system will not update a vehicle's status until after the Release to Fleet option has been selected by a manager. Field Level Security will be implemented for the Release to Fleet option box so that only managers can update this field.

BPR23: Service Ticket Approval; BRP24: Automatically Update Vehicle Status Once Servicing Approved