| About
the TIS Working Group Acknowledgements |
Ohio Trustworthy Information Systems Handbook: Section 2
|
How do you use this handbook? |
|
|
|
Use this handbook to look at all of the technical and non-technical workings of information systems in order to determine the level of trustworthiness required of your system. The Handbook provides a practical set of tools to craft procedures based on the unique needs and information requirements of your government agency. The Handbook tools can help to answer:
The Handbook provides additional background and useful information, including:
Use of the Handbook should not be limited to computer-based information systems, although they are the focus. Systems frequently are connected to, or interface with, other information systems in different formats, such as paper and microforms. They also may encompass legacy systems that contain similar data from an earlier time period and other platforms. The Handbook can be applied to systems that include data, information and/or records. Data simply asserts facts but provides no context for those facts. Data can be the discrete elements in a field in a database or the dynamic components of a web page. Information has meaning to us based on the context of its creation and use. Information can be a customized report from a database or the results of a database query. Records, on the other hand, are accessed, understood and retained as evidence of a particular situation or event. These could include the minutes from a meeting or all the data captured to serve as evidence of an electronic commerce transaction. The evidentiary value of records is seriously diminished if the records are not placed and maintained in their appropriate administrative context. Thus, information management is different from data management since it requires the creation and maintenance of context. Records management, in addition to managing context, must also ensure that the data or information has evidentiary value. Though all of the elements of a record may exist within a single computer file, they may also be distributed across the entire state network. The integrity of these elements and the links between them are much more important than where they physically reside. You can use the Handbook at any time during information system development. It is never too late to think about system trustworthiness. However, the earlier during the system development life cycle that you consider its trustworthiness, the better off you’ll be. During the analysis phase of system development, before a lot of time and money is spent on system design, is the most opportune time to weigh all of the TIS criteria that might be important to implement. At this time, you can think about the big picture without the constraints of a system that’s already well along in development or operation. That’s the ideal, but there are times when agencies won’t have that luxury. The Handbook is useful at any point during the system development life cycle. The Handbook also can be used to examine the trustworthiness of systems that are already in place—your legacy systems. You can document what you presently have and establish how well the system is set up to meet various requirements. Information systems are not static; they must respond to changes all of the time. Changes in software, hardware, platforms, means of communications, and growth as systems are becoming more interconnected necessitate considering and revisiting the TIS criteria on a periodic basis. The Handbook can be used for evaluating the trustworthiness of any government information system—large or small, old or new. It provides a valuable set of proven tools that your agency can apply, practically and efficiently. We encourage you to make this handbook your own! |
Ohio TIS Handbook last updated
November 2001, Version 1.
Ohio Electronic Records Committee