A public domain systems analysis methodology embodies three separate diagramming techniques: one to show the manner in which different items of information are related to each other(for example, that one item of information, the case record, may refer to more than one defendant). Second, to show the flow of information between users, and third, to show the events which surround each piece of information in the system. The diagram produced by these techniques serve much the same purpose as architectural plans- they are relatively simple follow, and because they use strict conventions for representing different information, they leave little scope for ambiguity or misunderstanding. The diagrams do, however, take a considerable amount of work to prepare, rticularly if they are subject to frequent alterations Computer-aided systems are available to assist with implementing these methods, and particularly to assist with checking the internal consistency of the information models and producing the diagrams. Numerous courses and computer-based training packages are also available The process of analysing the requirements for a computer system will almost invariably require a considerable degree of interaction with the staff of the organisation. The purpose of the analysis is to understand and document, for those processes which the computer system will tackle What information is involved in the processes, where it comes from, how it is stored, who uses it, and for what purposes I. How different pieces of information are inter-related What actions are taken as a result of the information being available The techniques used by computer analysts to determine these details are based largely on interviewing the staff most directly involved in the current processes which the computer system is to replace, as well as with is there managers who may wish to recommend changes to the current procedures and methods of working.It re important that during the analysis stage the computer analysts meet with staff and senior managers to accomplish the following L. Briefing of analysts by senior managers, to specify the scope and boundaries of the proposed system; I. Interviews of relevant staff by the computer analysts I. Diagrams showing the structure of the information currently in use and proposed for the computer system (sometimes called data navigation diagrams), how the information relates to actions and procedures in the office(sometimes called data flow diagrams), and how the information is used or affected(sometimes called entity life history diagrams) L. Review meetings with the staff and senior managers, to check out the detail of the diagrams produced by the The end result of the design phase is a clear and unambiguous specification of what the computer system is required to do, how, in logical terms, it is required to do it, the information which the system will be required to handle and the manner in which the different information items are interlinked 5.6 Data standards In most computer systems, it is beneficial to establish and maintain standards for all the items of information that are held in the system-what each item of information means, for example, and the format in which particular types of information are to be stored. In criminal justice, because of the complexity of the organisational structure, the traditional differences in definitions of terms between agencies, and the considerable volumes of information passing between it is vital to devote significant effort to establishing and maintaining data standards for the whole computerisation syster This means that each component of the information to be held in the computer system should be carefully tabulated, with details of its definition recorded. To take a simple example, most criminal justice computer systemsA public domain systems analysis methodology embodies three separate diagramming techniques: one to show the manner in which different items of information are related to each other (for example, that one item of information, the case record, may refer to more than one defendant). Second, to show the flow of information between users, and third, to show the events which surround each piece of information in the system. The diagrams produced by these techniques serve much the same purpose as architectural plans - they are relatively simple to follow, and because they use strict conventions for representing different information, they leave little scope for ambiguity or misunderstanding. The diagrams do, however, take a considerable amount of work to prepare, particularly if they are subject to frequent alterations. Computer-aided systems are available to assist with implementing these methods, and particularly to assist with checking the internal consistency of the information models and producing the diagrams. Numerous courses and computer-based training packages are also available. The process of analysing the requirements for a computer system will almost invariably require a considerable degree of interaction with the staff of the organisation. The purpose of the analysis is to understand and document, for those processes which the computer system will tackle: I. What information is involved in the processes, where it comes from, how it is stored, who uses it, and for what purposes; I. How different pieces of information are inter-related; I. What actions are taken as a result of the information being available. The techniques used by computer analysts to determine these details are based largely on interviewing the staff most directly involved in the current processes which the computer system is to replace, as well as with the senior managers who may wish to recommend changes to the current procedures and methods of working. It is therefore important that during the analysis stage the computer analysts meet with staff and senior managers to accomplish the following: I. Briefing of analysts by senior managers, to specify the scope and boundaries of the proposed system; I. Interviews of relevant staff by the computer analysts; I. Diagrams showing the structure of the information currently in use and proposed for the computer system (sometimes called data navigation diagrams), how the information relates to actions and procedures in the office (sometimes called data flow diagrams), and how the information is used or affected (sometimes called entity life history diagrams); I. Review meetings with the staff and senior managers, to check out the detail of the diagrams produced by the analyst. The end result of the design phase is a clear and unambiguous specification of what the computer system is required to do, how, in logical terms, it is required to do it, the information which the system will be required to handle, and the manner in which the different information items are interlinked. 5.6 Data Standards In most computer systems, it is beneficial to establish and maintain standards for all the items of information that are held in the system - what each item of information means, for example, and the format in which particular types of information are to be stored. In criminal justice, because of the complexity of the organisational structure, the traditional differences in definitions of terms between agencies, and the considerable volumes of information passing between agencies, it is vital to devote significant effort to establishing and maintaining data standards for the whole computerisation system. This means that each component of the information to be held in the computer system should be carefully tabulated, with details of its definition recorded. To take a simple example, most criminal justice computer systems