AreaCode | A 3 – character alphanumeric field holding the client’s area code. | Barcode | A 20-character alphanumeric barcode ID that is either pre-printed on each component package or added via a label at Coastline Consulting. | City | A 20-character alphanumeric field holding the name of the client’s city. | ClientID | A system-generated large integer numeric value unique to each client. | CloseDate | A date field holding the date a service request was resolved. | Config | A system-generated large integer numeric value unique to each software configuration record. | ContactFirst | A 20-character alphanumeric field consisting of the first name of the client contact person. | ContactLast | A 30-character alphanumeric field consisting of last name of the client contact person. | DateInstalled | Date field consisting of the date a component was installed into a piece of equipment. | DateRemoved | Date field consisting of the date a component was removed from a piece of equipment. | Descrip | A 30-character description of the inventory. | Description | A 30-character description of the problem. | Details | A large alphanumeric field describing the work done on a work record. | Email | A 70-character alphanumeric field consisting of the client contact’s e-mail address. | Equipment | A 20-character alphanumeric description of the piece of equipment, if any, for a software configuration record. | EqName | A 15-character alphanumeric field holding the identifying name for the piece of equipment | EquipNo | A system-generated numeric value unique to each piece of equipment. | EQT | A 10-character alphanumeric field identifying the equipment as PC, Printer, Scanner, etc. | Finish | A time field holding the time a technician finished work on a request. | InDate | A date field consisting of the date the piece of equipment was placed in service. | InfoName | A 20-character alphanumeric description of the information stored in a software configuration record. | InfoDescrip | A 50-character alphanumeric information value stored in a software configuration record. |
Data Dictionary

ModelNum | A 10-character alphanumeric identifier of the model number of the component. | Name | A 50-character alphanumeric field holding the client’s company name. | PartType | A 10-character alphanumeric classification of the type of component. | PrtNo | A system generated 20-character alphanumeric identifier of the part number that is unique to the part. | PurchDate | A date field representing the date a component was purchased. | Quantity | A numeric field specifying the quantity of items installed as a Part. This is always a whole number. An inspection of past forms shows no quantity exceeding 50. | Requestor | A 50-character alphanumeric field holding the first and last name of the person reporting a service request. | ReqNo | A system-generated large integer numeric value unique to each service request. | RptDate | A date field holding the date a service request was reported. | Start | A time field holding the time a technician began work on a request. | State | A 2-character abbreviation for the client’s state. | Street | A 30-character alphanumeric field holding the client’s street or box address. | TechInitials | A 3-character alphanumeric field consisting of the initials of the technician performing work. | Telephone | A 7-character alphanumeric field consisting of the telephone number of the client. | Vendor | A 30-character field holding the name of the vendor from whom a component was purchased. | Warranty | A 30-character alphanumeric field for warranty information. | WorkDate | A date field consisting of the date a technician did work on a request. | WorkNo | A system-generated large integer numeric value unique to each work record. | Zip | A 10-character alphanumeric postal code of a client. |
Data Dictionary

The Data Dictionary and Relationship Flow above are based on Milestone 3 & 4 with information from Milestone 5 for the descriptions and type of data.

Set up is based on the front end, client limited view, management - tech and bkkpr full view, with back end operations solely for tech and bkkpr

Event Diagrams take each use case from Milestone 3 & 4 to flow. 14 Use cases, 14 event diagrams.