Minnesota  State Archives

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 1. "An electronic system for creating, generating, sending, receiving, storing, displaying, or otherwise processing information." (e)
2. "The organized collection, processing, transmission, and dissemination of information in accordance with defined procedures, whether automated or manual. . . . Most often refers to a system containing electronic records, which involves input or source documents, records on electronic media, and output records, along with related documentation and any indexes." (i)
information systems in order to determine the level of 1. An information system that produces reliable and authentic records.trustworthiness required of your system. The Handbook provides a thorough, effective, and practical set of tools to craft procedures based on the specific and unique needs and information requirements of your government agency.

The Handbook tools can help to answer:

  • What is meant by a trustworthy system?
  • What is the process for establishing trustworthiness?
  • Who should participate in the process?
  • Why are 1. Data about data.
    2. "The description of the data resources, its characteristics, location, usage, and so on. Metadata is used to identify, describe, and define user data." (i)
    metadata and 1. "The act or process of substantiating by recording actions and/or decisions." (i)
    2. "Records required to plan, develop, operate, maintain, and use electronic records. Included are systems specifications, file specifications, codebooks, file layouts, user guides, and output specifications." (i)
    documentation so important?
  • How important is your 1. Data, text, images, sounds, codes, computer programs, software, databases, etc. (e)information?
  • How do you use the Trustworthy Information Systems (TIS) criteria set?
  • What are the criteria for a trustworthy information system?

The Handbook provides additional background and useful information, including:

  • A glossary of terms
  • A bibliography of sources that were the basis for the Handbook
  • The methodology for developing and testing the TIS criteria
  • Pertinent Minnesota laws and policies
  • Relevant citations to case law
  • Case studies of five government agency applications of the TIS criteria
  • Citation of the Handbook

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 1. “Any form containing greatly reduced images, or microimages, usually on microfilm. Roll, or generally serialized, microforms include microfilm on reels, cartridges, and cassettes. Flat, or generally unitized, microforms include microfiche, microfilm jackets, aperture cards, and microcards, or micro-opaques.” (i)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 contain 1. "Symbols, or representations, of facts or ideas that can be communicated, interpreted, or processed by manual or automated means." (i) data, information and/or 1. "Information that is inscribed on a tangible medium or that is stored in an electronic or other medium and is retrievable in perceivable form." (e)
2. Information created or received during the course of government business that becomes part of an official transaction.
3. "All cards, correspondence, discs, maps, memoranda, microfilms, papers, photographs, recordings, reports, tapes, writings and other data, information or documentary material, regardless of physical form or characteristics, storage media or conditions of use, made or received by an officer or agency of the state and an officer or agency of a county, city, town, school district, municipal subdivision or corporation or other public authority or political entity within the state pursuant to state law or in connection with the transaction of public business by an officer or agency." Excluding "data and information that does not become part of an official transaction, library and museum material made or acquired and kept solely or reference or exhibit purposes, extra copies of documents kept only for convenience of reference and stock of publications and processed documents, and bonds, and coupons, or other obligations or evidence of indebtedness, the destruction or other disposition of which is governed by other laws." (g)
records.

  • Data simply asserts facts but provides no context for those facts. Data can be such items as 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. For example, customized reports from a database is information.
  • 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 of the data captured to serve as evidence of an electronic commerce transaction. Though all of the elements of a record may exist within a single computer file, they may also be distributed across a 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 most agencies don't have that luxury. The Handbook is useful at any point during the 1. "A systematic and orderly approach to solving business problems, and developing and supporting resulting information systems." Typical phases of the system development life cycle include: Planning, Analysis, Design, Implementation, and Support. (d) 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!

What is a trustworthy information system? next

Go to Table of Contents

TIS Handbook last updated July 2002, Version 4.