q0qo
I/
Invited PresentationThis paper describes a ten-year-long technical and social experiment in our department to build a laboratory that designs and fabricates microelectronic systems in support of research in computer architecture. This experiment has been fairly successful by several measures: We have built and demonstrated a number of systems, some of significant size and complexity, spanning a fairly wide range of approaches and applications. We have validated the laboratory's original premise, demonstrating economies of scale by sharing a system-building facility over multiple projects. Most importantly, we have fielded experimental systems on a long-term, maintainable basis. Our Microelectronic Systems Laboratory (MSL) may serve as a useful model for others who want to develop system-building capability in a university setting. III describe the model in three parts:I. An outline of the context, purpose, organization, and working style of the lab, along with a brief chronology and description of the experimental systems we have built.
Laboratory ModelThe MSL exists within the Computer Science department at UNC, so a few words about the department are needed to understand the lab's context. It is relatively small (currently 22 faculty and 120 graduate students) and is primarily involved in graduate education and research. There are no undergraduate majors, though about 30 Math BS's graduate each year with a computer science concentration. The department does first-class research in interactive computer graphics and is also fairly strong in microelectronic design, natural 0 language processing, programming languages, and functional languages and machines. Founded as an autonomous department, it is not associated, for example, with electrical engineering (there are no traditional engineering curricula at Chapel Hill).Fred Brooks, the department's founder, has strongly stamped the its research style. Experimental computer science is emphasized; several groups have built complete, full-scale systems and put them in the hands of users, typically from outside the department and often outside computer science. Brooks measures success by asking questions such as, "Does the system allow users to produce useful, publishable results tON SATMNrV A Apzoved tot public thlons" 2 91 IL 10