Tobias Kuipers - researchr profile publications

researchr

You are not signed in
Sign in
Sign up

[Clear Filters]

Publications tagged Cobol

Cobol minefield detectionNiels P. Veerman, Ernst-Jan Verhoeven. SPE, 36(14):1605-1642, 2006. [doi]

Learning program organization through COBOLWilliam H. Friedman. SIGCSE, 36(2):77-81, 2004. [doi]

The ASF+SDF Meta-environment: A Component-Based Language Development EnvironmentMark G. J. van den Brand, Arie van Deursen, Jan Heering, H. A. de Jong, Merijn de Jonge, Tobias Kuipers, Paul Klint, Leon Moonen, Pieter A. Olivier, Jeroen Scheerder, Jurgen J. Vinju, Eelco Visser, Joost Visser. CC 2001: 365-370 [doi]

Critical Issues in the Proposed ISO Object-Oriented COBOL 2002 StandardGuido Dedene. TOOLS 2000: 491-500 [doi]

COBOL Script: A Business-Oriented Scripting LanguageTetsuji Imajo, Tatsuki Miyake, Shinobu Sato, Toshiyuki Ito, Daisuke Yokotsuka, Yoshihide Tsujihata, Shunsuke Uemura. edoc 2000: 231 [doi]

The Case for Continued Cobol EducationDonald Carr, Ronald J. Kizior. IEEE Software, 17(2):33-36, 2000. [doi]

Identifying Procedural Structure in Cobol ProgramsJohn Field, Ganesan Ramalingam. PASTE 1999: 1-10 [doi]

A Type Discipline for Solving Year 2000 Problems in COBOL ProgramsMads Tofte. mfcs 1999: 442

COBOL: Is Is Dying - or Thriving?Robert L. Glass. DB, 30(1):15-18, 1999. [doi]

Cobol: A Historic Past, A Vital Future?Robert L. Glass. IEEE Software, 16(4):118-120, 1999. [doi]

Rapid System Understanding: Two COBOL Case StudiesArie van Deursen, Tobias Kuipers. IWPC 1998: 90-97 [doi]

Re-Engineering Legacy Cobol ProgramsJay K. Joiner, W. T. Tsai. CACM, 41(5):185-197, 1998.

COBOL: Is it dying or thriving?Robert L. Glass. jss, 39(3):197-199, 1997. [doi]

The COBOL Jigsaw Puzzle: Fitting Object-Oriented and Legacy Applications TogetherElizabeth Spangler Flint. IBMSJ, 36(1):49-65, 1997.

Cobol - A Contradiction and an EnigmaRobert L. Glass. CACM, 40(9):11-13, 1997.

Automating the Modularization of Large COBOL Programs: Application of an Enabling Technology for ReengineeringPhilip Newcomb, Lawrence Markosian. WCRE 1993: 222-230

Grace meets the real world : tutoring COBOL as a second languageBob Radlinski, Jean McKendree. chi 1992: 343-350 [doi]

Softwareentwicklung in COBOL mit PersonalcomputernKlaus Huckert, Gerhard Schröer. wi, 32(5):459-466, 1990.

Knowledge Represen1ation in Automatic COBOL ProgrammerHolmes S. Liao, Abraham Kandel, R. Chris Lacher. seke 1989: 38-41

What s really wrong with COBOL?jss, 7(4):251-252, 1987. [doi]

A Major COBOL 85 ApplicationG. Hall. compcon 1987: 136-137

COBOL Standardization ProcessJim T. Panttaja. compcon 1987: 134-135

The COBOL 1985 LanguageDonald F. Nelson. compcon 1987: 130-133

Should Cobol Support CoroutinesB. Dwyer. acj, 17(2):62-66, 1985.

CIDRE - Eine interaktive Software-Entwurfs- und Entwicklungsumgebung mit Zielsprache COBOLMechthild Budde, Christoph Knabe, Werner Simonsmeier. programmier 1984: 171-183

Modules in COBOL 83R. P. Watkins. acj, 16(3):82-89, 1984.

On the Readability of COBOL ManualsRonald S. Lemos. ijmms, 19(4):377-389, 1983.

An Experimental COBOL Restructuring SystemMehdi T. Harandi. SPE, 13(9):825-846, 1983.

The Proposed COBOL Standard - Its SignificanceJ. M. Triance. cj, 26(1):60-67, 1983.

Cobol, Comments and correctnessB. Dwyer. acj, 14(2):42-47, 1982.

A linguistic comparison of MUMPS and COBOLThomas Munnecke. afips 1980: 723-729 [doi]

Programmer Productivity in COBOL Application TuningBarbara J. Walter. cmg 1979: 477-516

Towards More Portable COBOLT. J. Howkins, Mehdi T. Harandi. cj, 22(4):290-295, 1979.

Ist COBOL unsterblich?Peter Schnupp. programmier 1978: 28-44

A Study of COBOL PortabilityJ. M. Triance. cj, 21(3):278-281, 1978.

Elements of Style Among Machine-Generated Cobol FlowchartsNorman D. Peterson. Comp. Lang., Syst. \& Struct., 3(1):1-11, 1978.

Some Consequences of Deferred Binding in COBOLBarry G. T. Lowden, I. R. MacCallum. cj, 20(1):51-55, 1977.

A Comparison of Cobol, Fortran, PL-I and SpitbolAlan L. Tharp. Comp. Lang., Syst. \& Struct., 2(14):171-178, 1977.

The GEM COBOL Monitor SystemAntonio Salvadori. eci 1976: 310-322

A Study of Errors, Error-Proneness, and Error Diagnosis in CobolCharles R. Litecky, Gordon B. Davis. CACM, 19(1):33-37, 1976.

The Significance of the 1974 COBOL StandardJ. M. Triance. cj, 19(4):295-300, 1976.

An overview of the 1974 COBOL standardMargaret M. Cook, George N. Baird, William M. Holmes, Patrick M. Hoyt, L. Arnold Johnson, Paul Oliver. afips 1975: 301-307 [doi]

Letters to the editor: On combining FORTRAN and COBOL in problem solvingSanford Elkin. CACM, 8(10):594, 1965. [doi]

The use of FORTRAN in subroutines with COBOL main programsZalman A. Shavell. CACM, 8(4):221-223, 1965. [doi]

The COBOL sorting verbJ. B. Paterson. CACM, 6(5):255-258, 1963. [doi]

Syntactical charts of COBOL 61Richard Berman, Joseph Sharp, Lawrence Sturges. CACM, 5(5):260, 1962. [doi]

Why COBOL?Joseph F. Cunnigham. CACM, 5(5):236, 1962. [doi]

Floating-point arithmetic in COBOLO. Kesner. CACM, 5(5):269-271, 1962. [doi]

COBOL and compatabilityA. Lippitt. CACM, 5(5):254-255, 1962. [doi]

COBOL: a sample problemThomas N. Mackinson. CACM, 4(8):340-346, 1961. [doi]

runs on WebDSL