|
ABSTRACT
This paper describes and analyzes the design of TigerSwitch, a PC-based private branch exchange (PBX) designed at Princeton University. Building TigerSwitch required creating custom hardware and software designed to fit onto a standard IBM PC-compatible platform. Our design experience provides several lessons which we believe extend to other embedded design domains: the system architecture required to meet performance goals is often not isomorphic to the structure of the specification; system-level performance analysis is an essential part of system architecture design; architectural decisions must be made on the basis of estimates before complete implementations of the components are available; and most allocations of functions to software or custom hardware are obvious, while a few are very difficult.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
L. A. Baxter, P. R. Berkowitz, C. A. Buzzard, J. J. Horenkamp, and F. E. Wyatt, "System 75: communications and control architecture," AT&T Technical Journal, 64(1), January, 1985, pp. 153--173.
|
| |
2
|
John Bellamy, Digital Telephony, second edition, John Wiley and Sons, 1991.
|
| |
3
|
|
| |
4
|
James M. Kasson, "The Rolm Computerized Branch Exchange: an advanced digital PBX," IEEE Computre, June, 1979, pp. 24--31.
|
 |
5
|
|
| |
6
|
|
| |
7
|
Wayne Wolf, "Hardware-software co-design of embedded systems," Proceedings of the IEEE, July, 1994.
|
| |
8
|
|
| |
9
|
|
|