Browse
Search
Agenda - 02-20-2001-9d
OrangeCountyNC
>
Board of County Commissioners
>
BOCC Agendas
>
2000's
>
2001
>
Agenda - 02-20-2001
>
Agenda - 02-20-2001-9d
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/2/2008 9:01:56 AM
Creation date
8/29/2008 10:28:47 AM
Metadata
Fields
Template:
BOCC
Date
2/20/2001
Document Type
Agenda
Agenda Item
9d
Document Relationships
Minutes - 02-20-2001
(Linked To)
Path:
\Board of County Commissioners\Minutes - Approved\2000's\2001
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
21
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
STS <br />N.C. Oewment of Cemmece <br />onrce or Mfymahen recmroros. seMrrs <br />20, <br />Category Risk Mitigation Strategy <br />Technical ¦ Failure to close critical technology, ' Identify standards and design / <br /> function, standards, and information gaps develop system architecture based <br /> • <br />Backward browser compatibility beyond <br />on approved standards <br /> version 4,51 Netscape and 4.0 IE will • Identify and obtain buy-in on <br /> prevent use of DHTML in overall design of functional and business <br /> site. requirements <br /> ' Hire skilled and experienced contract <br /> personnel as needed <br /> • Develop plan and manage <br /> knowledge transfer <br /> • Provide links to download newer <br /> versions of browers <br />Operational Failure to properly assess OCIS • Review processes to optimize <br /> information systems to determine the resources and identify functions to <br /> required level and method of integration be included in enhancement <br /> • Develop a detailed design <br /> specification that includes a detailed <br /> data model and maps all required <br /> data interfaces. <br />Organizational. Failure to obtain organizational / agency • Establish consensus among agency <br /> buy-in senior management <br /> ' Develop effective communication <br /> plans <br />13. Technologies Employed and/or Application Architecture <br />The technical architecture, as mandated by IRMC, must accommodate rapid rates of change in both <br />business and technical environments. The proposed web design should support standard browsers as <br />the interface for the user. In addition, standard developmental tools for accessing and updating the <br />site(s) must be defined. <br />The site architectural requirements should effectively address the site life cycle. This includes navigation, <br />data submission and acquisition, and authentication. Specifically, the site must also include the <br />architecture to support shared or common applications; GroupWise communications tools, and secure <br />transactions. <br />Lastly, the architecture should include the necessary components to effectively manage the site long <br />term. This includes technical support, operation and storage management, performance monitoring and <br />tuning, security services, and disaster recovery. Reference the IRM Technical Architecture Standards <br />website for the detailed technical architecture requirements.
The URL can be used to link to this page
Your browser does not support the video tag.