Joseph E. Hollingsworth

Publication List Details

Period

1992 - 2008

Number

17

Co-Authors

Which Pointer Errors Do Students Make? (2008)

Bruce Adcock, Paolo Bucci, Wayne D. Heym, Joseph E. Hollingsworth

A model and a taxonomy to characterize pointer manipulations are introduced, along with an instrumentation technology that leverages them to provide students with immediate reports of pointer errors...

T The Resolve Software Verification Vision (2008)

William F. Ogden, Joseph E. Hollingsworth, Joan Krone, Murali Sitaraman, Bruce W. Weide

HE overall Resolve vision is that of a future in which no production software is considered properly engineered unless it has been fully specified, and fully verified as satisfying these...

An Infrastructure to Study and Address Students ’ Difficulties with Pointers (2008)

Paolo Bucci, Wayne D. Heym, Joseph E. Hollingsworth, Timothy Long, Bruce W. Weide

A model and a taxonomy to characterize pointer manipulations are introduced, along with an instrumentation technology that leverages them to provide students with immediate reports of their pointer...

Which Pointer Errors Do Students Make? (2008)

Bruce Adcock, Paolo Bucci, Wayne D. Heym, Joseph E. Hollingsworth

A model and a taxonomy to characterize pointer manipulations are introduced, along with an instrumentation technology that leverages them to provide students with immediate reports of pointer errors...

Checkmate: Cornering C++ Dynamic Memory Errors With Checked Pointers (2007)

Scott M. Pike, Bruce W. Weide, Joseph E. Hollingsworth

Pointer errors are stumbling blocks for student and veteran programmers alike. Although languages such as Java use references to protect programmers from pointer pitfalls, the use of garbage...

Component Technology for Pointers: Why and How (2003)

Greg Kulczycki, Gregory Kulczycki, Murali Sitaraman, Murali Sitaraman, William F. Ogden, William F. Ogden, ...

Abstract. Key software engineering questions concerning ease of understanding, reasoning, and efficient and predictable performance can be traced to the use of pointers in imperative programming...

Experience report: Using RESOLVE/C++ for commercial software (2000)

Joseph E. Hollingsworth

Academic research sometimes suffers from the “ivory tower” problem: ideas that sound good in theory do not necessarily work well in practice. An example of research that potentially could impact...

Experience report: Using RESOLVE/C++ for commercial software (2000)

Joseph E. Hollingsworth

jholly @ hollysoftware.com Academic research sometimes suffers from the "ivory tower" problem: ideas that sound good in theory do not necessarily work well in practice. An example...

Experience Report: Using RESOLVE/C++ for Commercial Software (2000)

Joseph E. Hollingsworth, Lori Blankenship

Academic research sometimes suffers from the "ivory tower" problem: ideas that sound good in theory do not necessarily work well in practice. An example of research that potentially could...

Experience report: Using RESOLVE/C++ for commercial software (2000)

Joseph E. Hollingsworth

Academic research sometimes suffers from the “ivory tower” problem: some ideas that sound good in theory do not necessarily work well in practice. An example of research that potentially could...

Bibliography (1995)

Robert Bogdan And, Robert C. Bogdan, Biklen Qualitative, Paolo Bucci, Joseph E. Hollingsworth, Joan Krone, ...

Software Specification, volume 86 of Lecture Notes in Computer Science, pages 292--332, New York, NY, 1980. Springer-Verlag. [4] R. A. DeMillo, R. J. Lipton, and A. J. Perlis. Social processes and...

On Local Certifiability of Software Components (1994)

Bruce W. Weide, Joseph E. Hollingsworth

Large software systems, like other large engineered systems, consist of components that are meant to be independent except at their interfaces. An important aspect of any large system is the need for...

Reverse Engineering of Legacy Code is Intractable (1994)

Bruce W. Weide, Wayne D. Heym, Joseph E. Hollingsworth

Reverse engineering of large legacy software systems is widely recognized to be a difficult problem. How bad is it? By an argument that identifies key underlying sources of the difficulty, reverse...

Reverse Engineering of Legacy Code is Intractable (1994)

Bruce W. Weide, Wayne D. Heym, Joseph E. Hollingsworth

recognized to be a difficult problem. How bad is it? By an argument that identifies key underlying sources of the difficulty, reverse engineering of legacy code is shown to be intractable in the...

Software component design-for-reuse : a language-independent discipline applied to Ada / (1992)

Hollingsworth, Joseph E.

Photocopy of microfilm. Ann Arbor, MI : UMI Dissertation Information Service, 1993.

Engineering 'Unbounded' Reusable Ada Generics (1992)

Joseph E. Hollingsworth, Bruce W. Weide

Most current programming languages (including Ada) provide some means of allowing the programmer to dynamically allocate and deallocate heap storage. This permits construction of “unbounded ”...