Sources:
    Edit
    Topics:
      Edit
      Types:
        Edit
        of  26
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)
        An Approach to End-User Application Design (1981)

        Embed document

        An Approach to End-User Application Design (1981)

        ABSTRACT

        Soon every desk will have a computer on it. Software to do mundane things such as payroll, mail, and text processing exists and as a by-product produces vast quantities of on-line in- formation. Many users want to manipulate this data, often in unanticipated ways. These unexpected uses cannot justify substantial programming costs. This paper argues that the relational data model and operators combined with a screen-oriented forms design and display system answers many of the needs of such users. In such a system, all data are represented in terms of records and fields. The user defines the screens (forms) he wants to see, and then specifies the mapping between fields of these screens and fields of the ....read more

        Edit
        Report copyright violation

        COMMENTS

        DOCUMENT INFO

        • TypeReport
        • PriceFree
        • FormatPDF
        • Size602 KB
        • LanguageEnglish
        • Stacks0
        • Postedalmost 4 years ago
        • AuthoredMar 01, 1981
        • Added byTarek Koudsi
        Search in: