HCI Bibliography Home | HCI Conferences | DOC Archive | Detailed Records | RefWorks | EndNote | Hide Abstracts
DOC Tables of Contents: 82838485868889909192939495

ACM Third International Conference on Systems Documentation

Fullname:3rd International Conference on Systems Documentation
Editors:Sergio Figueroa Balderas; Hugo Moncayo López
Location:Mexico City, Mexico
Dates:1984-May-16 to 1984-May-18
Standard No:ACM DL: Table of Contents hcibib: DOC84; ISBN 0-89791-148-2
The file descriptor: Use of a descriptive tool to retrieve general queries to files BIBAFull-Text 1-10
  Adolfo Guzmán
The file descriptor is a data structure that describes or documents the characteristics (position type, initial value, etc.) of the information within a file. Each file containing information possesses a unique file descriptor. The file descriptors for a collection of related files are stored together in a file named DESCRIPTORS.
   This paper explains the use of the file descriptor for:
  • answering general queries to a file- "retrieve all records satisfying predicate P" This is embodied in a tool called the consultator.
  • a general tool for data input -- the capturer -- which allows inputting appropriate data for any file.
  • a tool for report production -- the report printer -- which allows design of arbitrary output reports.
  • a specification for transformations from several input files into one or more output files -- the file transformer -- and its corresponding tool (program to interpret such notation). The above tools allow for input, consultation or retrieval, transformations ("computation" or "processing" of data into results) among files, and report generation, all of these without writing programs in high level languages (Pascal, Cobol, ...). Instead, we use a simpler description of (a) the screen to be presented for inputting data; (b) the query or predicate; (c) the transformation; (d) the report.
       The description used in (a) through (d) can be considered as a concise language for specifying data-manipulation (v. gr, administrative or managerial) tasks. If the tools prove to be useful, one can expect considerable savings in the time and effort spent in specifying and programming such data-manipulation tasks. The system in being implemented in Pascal for an IBM-PC network.
  • Adapting user documentation for a customized package payroll system BIBFull-Text 11-13
      Karyl Severson
    A multidimensional approach to documentation of APL systems BIBFull-Text 14-20
      A Pablo Noriega B. V.; Javier Fernández Pacheco
    Documentation to or for, by, with or from data dictionaries: A case study BIBFull-Text 21-22
      Diana Patterson
    On line documentation for information systems BIBFull-Text 23-25
      J. Alemón; W. Antonioli; H. Moncayo; E. Tenorio
    New approaches to writing effective computer documentation BIBFull-Text 26-28
      Joseph C. Mancuso
    Systems documentation BIBAFull-Text 29-32
      Ricardo Ameneyro; Carolina Arena; Ruben Colmenares; Pedro Cornejo; Rafael Garcia; Eloy Hernandez; Genaro Mariscal; Socrates Rivera
    We present as a practical case the payroll system developed for the Education Planning and Culture Offices of the Ministry of Public Education. It is the old payroll problem, but payment normativity in the Mexican government and the characteristics of the education sector involve greater complexity.
       Because the system is for employees' payment, it is important that any modification to the system be done as soon as possible (not more than a week) and with maximum reliability to get the expected results. With these considerations in mind, one of the principal objectives at the beginning of the project was that documentation must be good enough to permit a programmer to become familiar with the system and perform maintenance easily and accurately, even if he or she was not a member of the team that developed it.
    Systems analysis and system documentation BIBFull-Text 33-35
      Chris Hallgren
    A system for automatic Cobol program documentation BIBFull-Text 36-43
      Vicente Lopez Trueba; Julio Cesar Leon Carrillo; Oscar Olvera Posadas; Carlos Ortega Hurtado
    Empirical guidelines for writing computer documentation BIBFull-Text 44-48
      Darlene Clement
    Guide for the elaborations of a user's manual BIBFull-Text 49-52
      Elisa González de Lule; Erick Sustalta Torres
    Automated documentation is it for your organization or not? BIBFull-Text 53-56
      Thomas A. Murray
    Some aspects of software documentation BIBAFull-Text 57-59
      Enrique Arce Medina
    The documentation of software systems is discussed in this paper. It describes the contents, organization and purpose -- of the internal documentation and the -- user's manual.
    Software tools in the service of documentation BIBFull-Text 60-70
      Daniel Brantley; David Dillard
    MARCO -- a monitoring system to analyze, and control systems requirements. BIBAFull-Text 71-75
      A Ortiz de Montellano S.; A López Contreras G.; A Escobedo C&os A.; A Pérez Pedraza A.
    Based on the overall context -- of a system that takes us from software engineering thru computer tools to specify requirements; a computer based system to aid in the -- analysis is presented. The system is used to define a structured analysis according to TOM DE MARCO'S ideas (13). The tool was developed at the Universidad de las Americas. A brief -- explanation of what is and how is used is also included. The BASIC language was used in ordered to compiled the system under a VAX-VMS -- system.
    Issues concerning the development and use of online information BIBFull-Text 76-85
      Tom Connolly; Annette Bradford; Roger Grice; Jim Steipp
    The systems approach to computational systems: The documentation case BIBAFull-Text 86-94
      A Arturo Moreno G.; A Gerardo Mancillas B.; Cari De Sinfin
    In this paper the authores explore the possible causes for the lack of proper systems documentation; regard the situation not as a single cause attribute, but rather as a many and varied interrelated factors. The authors then put forward a documentation methodology associated to a computer model based on basic principles of Systems Analysis. The model presented in this paper can evolve from the simple case of one organization, one system, one programme application to more complex documentation cases; it uses a relational database and is implemented in a microcomputer.
    Case study of the methodology of J. D. Warnier to design structured programs as systems documentation BIBAFull-Text 95-100
      R. Escalona
    It is well known that a programmer's main idea is to generate results, but these are often only partially done. Generally, they want to finish the program well to document it afterwards; however, they never do so. Sometimes they are assigned to a new project, and they expect to have an opportunity to document what they have written at a later date. Other times, programmers have their own ideas, like ownership or professional secrets, and so on and so forth, but the truth is, few programmers document their programs, and fewer document them well.
       If there is a method that allows the programmer to document before writing a program or while he is writing it, such a program will, obviously, be documented in the most proper manner.
       This paper will describe some experiences in using the method of J.D. Warnier to design programs, and, therefore, its graphs are used as documentation.
    Documentation of a Fortran compiler study of a case BIBFull-Text 101-102
      Ignacio Canals Navarrete
    Development of the instituto de investigaciones electricas integrate system of financial information BIBFull-Text 103-106
      Gabriel Ruiz Huerta; Eliza González de Lule
    A software quality assurance program through reusable code BIBAFull-Text 107-113
      A Benito Zychlinski Z.; A Mario Palomar A.
    The purpose of this article is to present in the context of Software Engineering, and specifically to Quality Assurance, the development and implementation of two automated tools: Static Code Checker and Program Support Library. These tools, duly combined, allow the usage of a computer to make easier the instrumentation of a Software Quality Assurance Program.