A zero-one programming approach to Gulliksen's matched random subtests method

Wim J. van der Linden, Ellen Boekkooi-Timminga

Research output: Book/ReportReportOther research output

35 Downloads (Pure)

Abstract

In order to estimate the classical coefficient of test reliability, parallel measurements are needed. H. Gulliksen's matched random subtests method, which is a graphical method for splitting a test into parallel test halves, has practical relevance because it maximizes the alpha coefficient as a lower bound of the classical test reliability coefficient. This paper formulates this same problem as a zero-one programming problem, the advantage being that it can be solved by algorithms already existing in computer code. Focus is on giving Gulliksen's method a sound computational basis. How the procedure can be generalized to test splits into components of any length is shown. An empirical illustration of the procedure is provided, which involves the use of the algorithm developed by A. H. Land and A. Doig (1960), as implemented in the LANDO program. Item difficulties and item-test correlations were estimated from a sample of 5,418 subjects--a sample size that is large enough to prevent capitalizing on chance in the Gulliksen method. Two data tables and one graph are provided.
Original languageEnglish
Place of PublicationEnschede, the Netherlands
PublisherUniversity of Twente, Faculty Educational Science and Technology
Publication statusPublished - 1986

Publication series

NameOMD research report
PublisherUniversity of Twente, Faculty of Educational Science and Technology
No.86-04
NameProject Psychometric Aspects of Item Banking
PublisherUniversity of Twente, OMD
No.5

Keywords

  • Difficulty level
  • Algorithms
  • Test reliability
  • Computer software
  • Graphs
  • Estimation (Mathematics)
  • Computer assisted testing
  • Programming
  • Test items

Fingerprint

Dive into the research topics of 'A zero-one programming approach to Gulliksen's matched random subtests method'. Together they form a unique fingerprint.

Cite this