Principles versus artifacts in computer science curriculum design

Computer Science is a subject which has difficulty in marketing itself. Further, pinning down a standard curriculum is difficult-there are many preferences which are hard to accommodate. This paper argues the case that part of the problem is the fact that, unlike more established disciplines, the subject does not clearly distinguish the study of principles from the study of artifacts. This point was raised in Curriculum 2001 discussions, and debate needs to start in good time for the next curriculum standard. This paper provides a starting point for debate, by outlining a process by which principles and artifacts may be separated, and presents a sample curriculum to illustrate the possibilities. This sample curriculum has some positive points, though these positive points are incidental to the need to start debating the issue. Other models, with a less rigorous ordering of principles before artifacts, would still gain from making it clearer whether a specific concept was fundamental, or a property of a specific technology. (C) 2003 Elsevier Ltd. All rights reserved.

An evaluation of active lecturing in a computer networks course

The article describes an attempt to improve student learning outcomes in a computer networks course by making lectures more active learning experiences. Quick quizzes, group and individual exercises, the review of student questions, as well as multiple breaks, were incorporated into the weekly three-hour lectures. Student responses to the modified lectures was overwhelmingly positive: over 85% of respondents agreed that the lectures aided understanding, with large majorities of the respondents finding the individual activities useful to their learning. Although student examination performance improved over the previous year, performance on an examination question that was designed to examine deep understanding remained unchanged.

API documentation with executable examples

The rise of component-based software development has created an urgent need for effective application program interface (API) documentation. Experience has shown that it is hard to create precise and readable documentation. Prose documentation can provide a good overview but lacks precision. Formal methods offer precision but the resulting documentation is expensive to develop. Worse, few developers have the skill or inclination to read formal documentation. We present a pragmatic solution to the problem of API documentation. We augment the prose documentation with executable test cases, including expected outputs, and use the prose plus the test cases as the documentation. With appropriate tool support, the test cases are easy to develop and read. Such test cases constitute a completely formal, albeit partial, specification of input/output behavior. Equally important, consistency between code and documentation is demonstrated by running the test cases. This approach provides an attractive bridge between formal and informal documentation. We also present a tool that supports compact and readable test cases; and generation of test drivers and documentation, and illustrate the approach with detailed case studies. (C) 2002 Elsevier Science Inc. All rights reserved.

Insights into the structural basis for zinc inhibition of the glycine receptor

Histidines 107 and 109 in the glycine receptor ( GlyR) alpha(1) subunit have previously been identified as determinants of the inhibitory zinc-binding site. Based on modeling of the GlyR alpha(1) subunit extracellular domain by homology to the acetylcholine-binding protein crystal structure, we hypothesized that inhibitory zinc is bound within the vestibule lumen at subunit interfaces, where it is ligated by His(107) from one subunit and His(109) from an adjacent subunit. This was tested by co-expressing alpha(1) subunits containing the H107A mutation with alpha(1) subunits containing the H109A mutation. Although sensitivity to zinc inhibition is markedly reduced when either mutation is individually incorporated into all five subunits, the GlyRs formed by the co-expression of H107A mutant subunits with H109A mutant subunits exhibited an inhibitory zinc sensitivity similar to that of the wild type alpha(1) homomeric GlyR. This constitutes strong evidence that inhibitory zinc is coordinated at the interface between adjacent alpha(1) subunits. No evidence was found for beta subunit involvement in the coordination of inhibitory zinc, indicating that a maximum of two zinc-binding sites per alpha(1)beta receptor is sufficient for maximal zinc inhibition. Our data also show that two zinc-binding sites are sufficient for significant inhibition of alpha(1) homomers. The binding of zinc at the interface between adjacent alpha(1) subunits could restrict intersubunit movements, providing a feasible mechanism for the inhibition of channel activation by zinc.