Very rapid prototyping of wearable computers: a case study of custom versus off-the-shelf design methodologies

Authors:
Asim Smailagic;Daniel P. Siewiorek;Richard Martin;John Stivoric
Affiliations:
Engineering Design Research Center, Carnegie Mellon University, Pittsburgh, PA;Engineering Design Research Center, Carnegie Mellon University, Pittsburgh, PA;Engineering Design Research Center, Carnegie Mellon University, Pittsburgh, PA;Engineering Design Research Center, Carnegie Mellon University, Pittsburgh, PA
Venue:
DAC '97 Proceedings of the 34th annual Design Automation Conference
Year:
1997

Citing 4
Cited 3

Interdisciplinary concurrent design methodology as applied to the navigator wearable computer system

Journal of Computer and Software Engineering - Special issue: hardware-software codesign
Benchmarking an interdisciplinary concurrent design methodology for electronic/mechanical systems

DAC '95 Proceedings of the 32nd annual ACM/IEEE Design Automation Conference
Rapid design and manufacture of wearable computers

Communications of the ACM
A Case Study in Embedded-System Design: The VuMan 2 Wearable Computer

IEEE Design & Test

System Level Design as Applied to CMU Wearable Computers

Journal of VLSI Signal Processing Systems - Special issue on system level design
The Evolution of Army Wearable Computers

IEEE Pervasive Computing
A mobile system for industrial maintenance support based on embodied interaction

Proceedings of the fifth international conference on Tangible, embedded, and embodied interaction

Quantified Score

Hi-index	0.00

Visualization

Abstract

The Wearable Computer Project is a testbed integratingresearch on rapid design and prototyping. Based onrepresentative examples from six generations of wearablecomputers, the paper focuses on the differences in rapidprototyping using custom design versus off-the-shelfcomponents. The attributes characterizing these two designstyles are defined and illustrated by experimentalmeasurements. The off-the-shelf approach required ten timesthe overhead, 30% more cost, fifty times the storage resources,20% more effort, five times more power, but 30% less effort toport software than the embedded approach.