James K. Huggins

dblp:76/6771 · also James Huggins 0001, Jim Huggins 0001 · DBLP profile ↗
← Back
17ranked-venue papers
4as first author
3since 2021 · last 2026
0000-0002-2173-7365ORCID · verified

Domains — the database's venue-derived domains; a paper can count in several

Human-computer interaction and ubiquitous computing · 9 · 3 first-author · 3 since 2021Systems, architecture and hardware · 3 · 1 first-authorSoftware engineering, systems software and programming languages · 3Applied, interdisciplinary, general and emerging computing · 2Theory of computation · 1
YearPublicationVenuePosition
2026 It Seemed Like a Good Idea at the Time ('No, Not Like That!' edition)
Dan Garcia 0001, James K. Huggins, Brian Law, Narges Norouzi, Jaimin Patel, Michael Shindler
SIGCSE (2)2
2023 It Seemed Like a Good Idea at the Time: ("Let Me Help You with That" edition)
abstract
Conference presentations usually focus on successful innovations: new ideas that yield significant improvements to current practice. Yet we often learn more from failure than from success. In this panel, we present five case studies of "good ideas" for improving CS education that didn't go as planned, related to offering additional help to students. Each contributor will describe their "good idea," the situation that resulted, and wider lessons for the CS community.
Dan Garcia 0001, James K. Huggins, Lauren J. Bricker, Adam M. Gaweda, David J. Malan, Joël Porquet-Lupine, Kristin Stephens-Martinez
SIGCSE (2)2
2022 It Seemed Like a Good Idea at the Time (COVID-19 edition)
abstract
Conference presentations usually focus on successful innovations: new ideas that yield significant improvements to current practice. Yet we often learn more from failure than from success. In this panel, we present five case studies of "good ideas" for improving CS education (most related to the COVID-19 pandemic) that didn't go as planned. Each contributor will describe their "good idea", the situation that resulted, and wider lessons for the CS community.
Dan Garcia 0001, James K. Huggins, Christine Alvarado, Paul V. Gestwicki, Andy Gunawardena, Victoria Hong, Ellen Spertus
SIGCSE (2)2
2020 It Seemed Like a Good Idea at the Time (Hindsight is 2020)
abstract
Conference presentations usually focus on successful innovations: new ideas that yield significant improvements to current practice. Yet educators know that we often learn more from failure than from success. In this panel, we present four case studies of "good ideas" for improving CS education that resulted in failures. Each contributor will describe their "good idea", the failure that resulted, and wider lessons for the CS community.
Dan Garcia 0001, James K. Huggins, Kevin Lin 0001, Raja Sooriamurthi, Leo C. Ureel II, Ursula Wolz
SIGCSE2
2019 Education and Licensure Requirements for Automated Motor Vehicles
abstract
This paper addresses the need for an effective method of educating automated vehicle operators and a collaboration between industry, government, and professional organizations to create licensure programs. Research was compiled on current laws regarding licensure to operate automated motor vehicles, consumer knowledge of automated vehicles, and methods of training. There was found to be a lack of legislation regarding licensure, as well as a failure to provide educational programs for consumers. Licensure legislation, in combination with proper training for each level of autonomy, is considered necessary in order to protect against crashes and improper or unsafe operation of automated motor vehicles. To address this, the paper outlines a driver education program for operators of automated vehicles. A method of visually identifying the level of automation within the vehicle is also presented. The SAE J3016 standard is used throughout to reference levels of vehicle autonomy.
Olivia C. Wanless, Chanc D. Gettel, Charles W. Gates, James K. Huggins, Diane L. Peters
ISTAS4
2018 What Belongs in a Computer Science Syllabus?
abstract
This work-in-progress research paper studies the role of the syllabus in a computer science course. There is considerable literature detailing why a syllabus is an important part of a lecturer`s tools, and what items a syllabus ought to contain. However, there is little empirical evidence to back up these claims. We investigate what computer science students report seeing (and wishing to see) on a syllabus, and compare those results against advice given in various syllabus design guides. We find that several topics listed as points of emphasis on syllabus guidelines are named by students both as important and as areas for improvement in syllabi. We do this as a first step towards developing a research program to derive meaningful data on what a useful computer science syllabus really contains.
Mitch J. Duncan, James K. Huggins
FIE2
2018 Flipping Unplugged: An Experience Report
abstract
This Research-To-Practice Full Paper discusses the use of the flipped classroom format. Within the CS community, numerous papers discussing the use of flipped classrooms have appeared in recent years. We discuss the use of flipped classroom techniques without requiring the use of modern digital technology. We argue that the principal goals of flipped classrooms do not a priori require such technologies, and that instructors should not feel limited by a lack of access to technology when considering flipped classroom designs. This paper gives an experience report regarding the use of “unplugged” flipped classroom techniques in a computing history and ethics course over the last ten years.
James K. Huggins
FIE1
2013 Nifty computing in society case studies (abstract only)
abstract
This session is being organized by ACM SIGCAS (Computers and Society) for those with an interest in addressing the social and ethical consequences of computing in our society within their curricula. This year we will share case studies as a means to teaching a variety of issues resulting from the impact of computing in our society. Our discussion leaders will introduce briefly favorite case studies in their fields of interest and will encourage all participants to share examples of their own. Ways for dealing and solving current problems will be tackled. We will provide a plan of how to incorporate the case studies presented into our classes along with a handout of how to do so. Topics of interest include legal issues, social media, privacy, and sustainability.
James K. Huggins, Alfreda Dudley, Karla Carter, Dee A. B. Weikle, Netiva Caftori
SIGCSE1
2009 It seemed like a good idea at the time
abstract
No abstract available.
Jonas Boustedt, Robert McCartney, Katherine Deibel, James K. Huggins, Beth Simon, Suzanne Westbrook, The Mystery Presenter
SIGCSE4
2003 A Method of Implementing UML Virtual Machines With Some Constraints Based on Abstract State Machines
abstract
UML has become a standard language for designing software systems. To help software developers design a correct UML model for a software system has become an important goal for many UML CASE tools. We propose a new UML virtual machine based on abstract state machines. We combine the UML meta-model, UML model and user objects model into one under the ASM virtual machine for UML. Since the ASM virtual machine for UML supports OCL, software developers can precisely design a software model and then find some errors such as inconsistency in the model with the help of the ASM virtual machine.
Wuwei Shen, Kevin J. Compton, James K. Huggins
APSEC3
2003 Survivor: getting through that class the first time
abstract
No abstract available.
James K. Huggins, Joseph Bergin, James Caristi, Ellen Lowenfeld Walker
SIGCSE1
2002 A Toolset for Supporting UML Static and Dynamic Model Checking
abstract
The Unified Modeling Language has become widely accepted as a standard in software development. Several tools have been produced to support UML model validation. However most of them support either static or dynamic model checking; and no tools support to check both static and dynamic aspects of a UML model. But a UML model should include the static and dynamic aspects of a software system. Furthermore, these UML tools translate a UML model into a validation language such as PROMELA. But they have some shortcomings: there is no proof of correctness (with respect to the UML semantics) for these tools. In order to overcome these shortcomings, we present a toolset which can validate both static and dynamic aspects of a model; and this toolset is based on the semantic model using Abstract State Machines. Since the toolset is derived from the semantic model, the toolset is correct with respect to the semantic model.
Wuwei Shen, Kevin J. Compton, James K. Huggins
COMPSAC3
2001 A UML Validation Toolset Based on Abstract State Machines
abstract
The Unified Modeling Language has become widely accepted as a standard in software development. Several tools have been produced to support UML model validation. These tools translate a UML model into a validation language such as PROMELA. However they have some shortcomings: there is no proof of correctness (with respect to the UML semantics) for these tools; and there is no tool that supports validation for both the static and dynamic aspects of a UML model. In order to overcome these shortcomings, we present a toolset which is based on the semantic model using abstract state machines. Since the toolset is derived from the semantic model, the toolset is correct with respect to the semantic model. In addition, this toolset can be used to validate both the static and dynamic aspects of a model.
Wuwei Shen, Kevin J. Compton, James K. Huggins
ASE3
1998 Functional Verification of a Multiple-issue, Out-of-Order, Superscalar Alpha Processor - The DEC Alpha 21264 Microprocessor
abstract
DIGITAL's Alpha 21264 processor is a highly out-of-order, superpipelined, superscalar implementation of the Alpha architecture, capable of a peak execution rate of six instructions per cycle and a sustainable rate of four per cycle. The 21264 also features a 500 MHz clock speed and a high-bandwidth system interface that channels up to 5.3 Gbytes/second of cache data and 2.6 Gbytes/second of main-memory data into the processor. Simulation-based functional verification was performed on the logic design using implementation-directed, pseudo-random exercisers, supplemented with implementationspecific, hand-generated tests. Extensive functional coverage analysis was performed to grade and direct the verification effort. The success of the verification effort was underscored by first prototype chips which were used to boot multiple operating systems across several different prototype systems. Keywords Alpha, microprocessor, verification, validation, architecture, pseudo-random, coverage an...
Scott A. Taylor, Michael Quinn, Darren Brown, Nathan Dohm, Scot Hildebrandt, James K. Huggins, Carl Ramey
DAC6
1998 Zen and the art of Alpha verification
abstract
The advanced architecture of the Alpha 21264 microprocessor compelled the verification team to invent far-reaching techniques to achieve the goal of booting multiple operating systems on first silicon. These techniques, built on traditional verification methodology, exposed a number of esoteric bugs prior to tape-out. Verification engineers took focused testing, pseudo-random testing, and coverage analysis to new levels in order to meet the challenge of verifying a highly out-of order, superscalar machine. A new hybrid exerciser and a method for predicting the future enhanced pseudo-random testing. A new way of looking at coverage analysis was devised. Random behavior was added to hand-coded rests, several methods were created for tackling atomic operations, and a shadow reference model was written for the most advanced branch predictor implemented to date in a commercial microprocessor. Verification techniques were also expanded to include test pattern generation and post-silicon debugging.
Nathan Dohm, Carl Ramey, Darren Brown, Scot Hildebrandt, James K. Huggins, Michael Quinn, Scott A. Taylor
ICCD5
1998 Specification and verification of pipelining in the ARM2 RISC microprocessor
abstract
Gurevich Abstract State Machines (ASMs) provide a sound mathematical basis for the specification and verification of systems. An application of the ASM methodology to the verification of a pipelined microprocessor (an ARM2 implementation) is described. Both the sequential execution model and final pipelined model are formalized using ASMs. A series of intermediate models are introduced that gradually expose the complications of pipelining. The first intermediate model is proven equivalent to the sequential model in the absence of structural, control, and data hazards. In the following steps, these simplifying assumptions are lifted one by one, and the original proof is refined to establish the equivalence of each intermediate model with the sequential model, leading ultimately to a full proof of equivalence of the sequential and pipelined models.
James K. Huggins, David Van Campenhout
ACM Trans. Design Autom. Electr. Syst.1
1997 Equivalence is in the Eye of the Beholder
Yuri Gurevich, James K. Huggins
Theor. Comput. Sci.2