Safe Compositional Network Sketches: NetSketch Tool Implementation

Numerous problems exist that can be modeled as traffic through a network in which constraints exist to regulate flow. Vehicular road travel, computer networks, and cloud based resource distribution, among others all have natural representations in this manner. As these networks grow in size and/or complexity, analysis and certification of the safety invariants becomes increasingly costly. The NetSketch formalism introduces a lightweight verification framework that allows for greater scalability than traditional analysis methods. The NetSketch tool was developed to provide the power of this formalism in an easy to use and intuitive user interface.

Campus-based publishing partnerships: A guide to critical issues

Campus-based publishing partnerships offer the academy greater control over the intellectual products that it helps create. To fully realize this potential, such partnerships will need to evolve from informal working alliances to long-term, programmatic collaborations. SPARCâ s Campus-based Publishing Partnerships: A Guide to Critical Issues addresses issues relevant to building sound and balanced partnerships, including: Establishing governance and administrative structures; Identifying funding models that accommodate the objectives of both libraries and presses; Defining a partnershipâ s objectives to align the missions of the library and the press; Determining what services to provide; and Demonstrating the value of the collaboration. SPARCâ s Campus-based Publishing Partnerships will help libraries, presses, and academic units to define effective partnerships capable of supporting innovative approaches to campus-based publishing.

Library Technology Services at Boston University: an un-roadmap

A working paper for discussion

Cuckoo: a Language for Implementing Memory- and Thread-safe System Services

This paper is centered around the design of a thread- and memory-safe language, primarily for the compilation of application-specific services for extensible operating systems. We describe various issues that have influenced the design of our language, called Cuckoo, that guarantees safety of programs with potentially asynchronous flows of control. Comparisons are drawn between Cuckoo and related software safety techniques, including Cyclone and software-based fault isolation (SFI), and performance results suggest our prototype compiler is capable of generating safe code that executes with low runtime overheads, even without potential code optimizations. Compared to Cyclone, Cuckoo is able to safely guard accesses to memory when programs are multithreaded. Similarly, Cuckoo is capable of enforcing memory safety in situations that are potentially troublesome for techniques such as SFI.