North Carolina's journey to an integrated juvenile abuse, neglect and dependency court management information system - Page 52 |
Previous | 52 of 197 | Next |
|
small (250x250 max)
medium (500x500 max)
Large
Extra Large
large ( > 500x500)
Full Resolution
All (PDF)
|
This page
All
|
1. Evaluate current Adult MIS Reports 2. Evaluate Youth MIS and incorporate elements into existing and new reports 3. Meet with FTC User Group to receive feedback on revising, editing, deleting or adding any necessary components for the reports 4. Edit Adult MIS reports used in the current system to include additional FTC information 5. Create reports that are to be used solely by users logged into the FTC / family database Phase V 1. Security Grid / Security Matrix ( user privileges rest within database / provides environment where Drug Treatment Court Services can add and edit user IDs and easily determine if the ID is “ active” or “ revoked”) 2. Test Plan 3. Alpha testing 4. Program and testing for Database Conversion a. F. I. R. S. T. data migration from MS Access to Microsoft SQL Server b. Mecklenburg and Durham family data migration ( Microsoft SQL Server to Microsoft SQL Server) 5. Historical non- rewritable weekly back- ups to CD in place 6. Daily ( rewritable) data back- ups 7. Beta testing in Mecklenburg and Durham 8. Report of Test Results 9. Correction of bugs reported in the Beta test 10. Training and user manual Phase VI 1. Provide two, 2- day trainings and two, 1- day trainings and ensure scheduling is done one month prior to the meeting 2. Data Export functionality and provide software for up to 4 Personal Computers that have data export functionality 3. Contractor maintains responsibility for receiving, recording, correcting, and relaying bugs reported and bugs fixed in a timely manner, with the ability to view and prioritize all bugs reported 4. Support for bug fixes should last for at least one year. Three months after completion of the four trainings every bug reported, whether past or present, must be fixed by the contractor within one month Phase VII 1. Provide the ability for the DTC Office to create an infinite number of user groups and assign which sections can be viewed and edited as a member of that user group 51
Object Description
Description
Title | North Carolina's journey to an integrated juvenile abuse, neglect and dependency court management information system - Page 52 |
Pres Local File Path-M | \Preservation_content\StatePubs\pubs_borndigital\images_master\ |
Full Text | 1. Evaluate current Adult MIS Reports 2. Evaluate Youth MIS and incorporate elements into existing and new reports 3. Meet with FTC User Group to receive feedback on revising, editing, deleting or adding any necessary components for the reports 4. Edit Adult MIS reports used in the current system to include additional FTC information 5. Create reports that are to be used solely by users logged into the FTC / family database Phase V 1. Security Grid / Security Matrix ( user privileges rest within database / provides environment where Drug Treatment Court Services can add and edit user IDs and easily determine if the ID is “ active” or “ revoked”) 2. Test Plan 3. Alpha testing 4. Program and testing for Database Conversion a. F. I. R. S. T. data migration from MS Access to Microsoft SQL Server b. Mecklenburg and Durham family data migration ( Microsoft SQL Server to Microsoft SQL Server) 5. Historical non- rewritable weekly back- ups to CD in place 6. Daily ( rewritable) data back- ups 7. Beta testing in Mecklenburg and Durham 8. Report of Test Results 9. Correction of bugs reported in the Beta test 10. Training and user manual Phase VI 1. Provide two, 2- day trainings and two, 1- day trainings and ensure scheduling is done one month prior to the meeting 2. Data Export functionality and provide software for up to 4 Personal Computers that have data export functionality 3. Contractor maintains responsibility for receiving, recording, correcting, and relaying bugs reported and bugs fixed in a timely manner, with the ability to view and prioritize all bugs reported 4. Support for bug fixes should last for at least one year. Three months after completion of the four trainings every bug reported, whether past or present, must be fixed by the contractor within one month Phase VII 1. Provide the ability for the DTC Office to create an infinite number of user groups and assign which sections can be viewed and edited as a member of that user group 51 |