Browse
Search
2009-086 IT - Tax - Property Information Management System Software Vendors, Project Managers, and Transitional Contract Assistance
OrangeCountyNC
>
Board of County Commissioners
>
Contracts and Agreements
>
General Contracts and Agreements
>
2000's
>
2009
>
2009-086 IT - Tax - Property Information Management System Software Vendors, Project Managers, and Transitional Contract Assistance
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/10/2012 12:14:13 PM
Creation date
3/10/2011 12:40:12 PM
Metadata
Fields
Template:
BOCC
Date
10/20/2009
Meeting Type
Regular Meeting
Document Type
Contract
Agenda Item
4q
Document Relationships
Agenda - 10-20-2009 - 4q
(Linked To)
Path:
\Board of County Commissioners\BOCC Agendas\2000's\2009\Agenda - 10-20-2009
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
132
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Orange County Information Technology <br />PIN APPLICATION USE CASES <br />This document lists the basic functionalities expected of the PIN Application. It <br />uses a streamlined version of Use Case methodologies. It should be noted these <br />are general functionalities which may be implemented in several different and <br />specific ways. E.g., Many of the system interfaces will be specific queries to the <br />PIN Application, as denoted in Use Case #2, below. In that sense, the use cases <br />below indicate general classes of functionality. <br />1. Query PIN uniqueness <br />Input: PIN coordinates (based on Centroid) from GIS Mapping process <br />Output: returns that PIN (if it already is in the PIN App) or a null (if it isn't already <br />in the PIN App <br />Note:. If PIN is returned (indicating that PIN is already in PIN App), GIS will <br />resubmit new PIN (with slight offset coordinates, to attempt to establish a new, <br />unique PIN). This cycle continues until the PIN App returns a null. <br />2. Basic PIN attribute query <br />Input: PIN and data field(s) query request from another system or report <br />generator. <br />Output: PIN App returns attribute data associated with PIN in delimited format <br />3. Preliminary PIN assignment <br />Input: PIN and parent PIN(s) from Public Notice Application <br />Output: PIN App creates a new record, using PIN as primary key, parent PIN as <br />attribute. PIN App sets PIN status to "Preassigned." <br />4. Populate Preliminary PIN attributes <br />Input: PIN Attributes from Public Notice Application <br />Output: Attributes assigned to PIN are input to PIN App for that PIN <br />Page 1 of 6 1119/2009 PIMS Project <br />
The URL can be used to link to this page
Your browser does not support the video tag.