Skip to main content
 
Constructing the New York State-Local Internet Gateway Prototype: A Technical View



Application Scope Statements, Role Designations, and Functional and Data Requirements

Dog Licensing Application

Scope Statement. This application represented a high volume transaction process involving the NYS Department of Agriculture and Markets and cities, towns, and villages throughout New York State. The Dog Licensing Application provided:
  • data as required in the existing DL1 Form,
  • input into a repository of new dogs and owner information, producing generic recording of licenses for non-purebred dogs,
  • renewal of licenses (excluding mailing renewal notices to owners), transfer of ownership, and local reporting functions.
Role Designations. Individuals given access to the Dog Licensing Application were responsible for processing dog licensing applications within their municipality. Within the Dog Licensing Application two roles were assigned:
  • Dog-Licensing Agents (DLA) could perform all the functions that are part of processing dog licenses. This includes new registrations, renewals, and transfers. In addition, this role had the capability to run reports and search for specific dog licenses.
  • Agriculture and Markets Staff were able to review state-wide data and produce reports. In addition they had access to an administrative function that allows this role to update information requirements about dog licensing.
Functional Requirements. The basic functional requirements included the ability of the application to:
  • Perform the functions listed in the Dog Licensing Application Scope Statement.
  • Provide all appropriate users access to the application via a standard web browser.
  • Run within the Prototype system.
  • Remain self-contained and not integrate with existing production systems.
More specifically, the major functional requirement of the application was to provide all Dog Licensing users with a database of new dog licenses, which allows them to input, edit and access data, so that there is a single repository of license data, the data exchange process is simplified, and that better quality data is online more quickly for all users. In addition, the application was designed to perform these five major business processes:
  • Research request for dog license application
  • Process initial dog license and renewals
  • Process transfer of dog ownership
  • Update information about the dog or owner
  • Process Queries and Reports
Data Requirements: Specific fields that capture data about a dog license was taken directly from the DL1 Form and data requirements were selected by the Prototype Team to support the functional requirements of the application. The selected data fields to support the dog licensing application are in shown in Table 6.

Table 6. Selected Data Fields for the Dog Licensing Application

Data Item(s)
 
Requirement
 
Owner Name and Address
 
Accommodate for multiple addresses (mailing and location addresses)
 
Owner E-mail
 
New data item outside of DL-1 form
 
Dog Address
 
Some dogs may be harbored in a location other than the owner’s
 
Dog Birth Date
 
There are different business rules for registration based on dog’s age
 
Dog Breed, Color, Mix Designation
 
For tracking, identification and reporting purposes
 
Dog Municipality
 
Where the dog itself resides. DLAs are responsible for the registrations within their municipality.
 
Dog Spayed, Neutered
 
There are different business rules for registration based on dog’s status
 
Dog Gender, Dangerous Designation, Identifying Marks
 
For tracking, identification and reporting purposes
 
Dog License Number
 
Exists for the life of the dog
 
TCV (Town, City, Village)
 
Track history of where dog has been registered, for the life of the dog

Municipality designation (location of licensing agent) which came from Ag. & Mkts data source
 
Look Up Tables
 
Colors, Breeds, Mixes, Registration Types, Vaccination Types extracted from DL1 form (list of standard category items for each data type)
 
Security Tables
 
Maintain role based security to grant/deny access to dog application specific functionality
 
Registration Date
 
The Start Date is calculated by looking at all of the transactions for this dog and taking the latest end date and adding one day

The End Date is calculated by adding two years to the Start Date

The Start Date and End Date are overrideable, but the Start Date must occur before the End Date
 
License Type
 
If birth month is supplied, dog birthday is rounded to the first of the month for purposes of subsequent calculations

If birth month is not supplied, birthday is rounded to first of year for purposes of subsequent calculations

If dog is female and spayed, default to "Female, spayed" type

If dog is female and unspayed, default to "Female, unsprayed (xxx)" type with the under/over four months calculated from birthday and current date. If birthday is not supplied, default to "Female, unsprayed (under 4 mos.)"

If dog is male and neutered, default to "Male, neutered" type

If dog is male and unneutered, default to "Male, unneutered (xxx)" type with the under/over four months calculated from birthday and current date. If birthday is not supplied, default to "Male, unneutered (under 4 mos.)"