Browse Prior Art Database

Computer System Organization: Problems of the 1980's Disclosure Number: IPCOM000131233D
Original Publication Date: 1978-Sep-01
Included in the Prior Art Database: 2005-Nov-10
Document File: 15 page(s) / 55K

Publishing Venue

Software Patent Institute

Related People

Henry Apfelbaum: AUTHOR [+8]


Soon, system architects will treat all system components -- hardware as well as software, user interfaces as well as data bases --as structural or architectural elements.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 7% of the total text.

Page 1 of 15


This record contains textual material that is copyright ©; 1978 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Contact the IEEE Computer Society (714-821-8380) for copies of the complete work that was the source of this textual material and for all use beyond that as a record from the SPI Database.

Computer System Organization: Problems of the 1980's

Henry Apfelbaum

Sperry Univac
Richard P. Case
IBM Corporation
J. Egil Juliussen

Texas Instruments
Bruce Shriver
University of Southwestern Louisiana
Harold S. Stone
University of Massachusetts
James E. Thornton
Network Systems Corporation

Soon, system architects will treat all system components -- hardware as well as software, user interfaces as well as data bases --as structural or architectural elements.

In this paper we identify design and organization problems of computer systems in the 1980's. We also project developments that will influence the organization of such systems. The overall goal of these systems is to enhance the productivity of the end user. Computer systems are, of course, assemblages of software and hardware. The most important software components that are visible to the end user of contemporary multilevel systems are operating systems, data-base management systems, teleprocessing systems, and various programming languages and application packages. The study of the hardware components of the system normally comes under the purview of the computer architect, who is concerned with the characteristics and interconnection of the basic building blocks of information processing engines -- with processors, memories, peripherals, and local and remote interconnection structures.

Computer system design involves skills of the hardware designer, the computer system architect, and the software programmer. It is highly desirable that each type of designer have skills in all three disciplines in order for the overall organization of the computer system to be viable. Unfortunately, this is not always the case.

Those who design computer systems must create systems that are easy to use, reliable, maintainable, secure, expandable, and cost effective; we refer to these ever more demanding requirements as the "user pull." In addition to being pulled by the user,

This article represents a consensus of the authors views but does not necessarily reflect their individual opinions or those of the organizations they represent.

computer system architects are being "pushed by the technology." With the emergence of very- largescale integration as a production technology, we must address the question, "What will we put on the chip?" Several important potential constraints face the system architect when undertaking a design. Some users have an extremely large financial investment in existing programs and data bases. A new system may have to accommodate the support of thi...