We describe two current development projects at the Library of Congress using high-density optical storage, both of which require more advanced and improved computer-based information retrieval methodologies than existing bibliographic retrieval systems. A much greater emphasis will be placed on the information content of the articles rather than on the broad subject categories in general use for computer retrieval citations to book materials. Needed approaches include the linking of selected external reference sources and the extraction of character-encoded index information from the page images by OCR techniques. Our position is that extremely high density storage of articles in a single subject area requires a finer resolution in the retrieval system accessing the material. A single side of a 12-inch digital optical disk, for example, can hold 15 years of the Journal of the ACM.
{"title":"Optical storage of page images and pictorial data - opportunities and needed advances in information retrieval","authors":"W. Nugent, J. R. Harding","doi":"10.1145/800173.809705","DOIUrl":"https://doi.org/10.1145/800173.809705","url":null,"abstract":"We describe two current development projects at the Library of Congress using high-density optical storage, both of which require more advanced and improved computer-based information retrieval methodologies than existing bibliographic retrieval systems. A much greater emphasis will be placed on the information content of the articles rather than on the broad subject categories in general use for computer retrieval citations to book materials. Needed approaches include the linking of selected external reference sources and the extraction of character-encoded index information from the page images by OCR techniques. Our position is that extremely high density storage of articles in a single subject area requires a finer resolution in the retrieval system accessing the material. A single side of a 12-inch digital optical disk, for example, can hold 15 years of the Journal of the ACM.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1983-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127717892","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Equipment changes - moving, adding or removing units in a central computer facility - can have a devastating effect on a computer center. Equipment failures and cable problems can result in prolonged service outages, user disservice and management frustration. Risks from these changes can be effectively controlled by means of sound implementation planning tools. An effective methodology based on a graphics technique that accurately represents equipment location in a computer room on standard size paper provides the planning tools that minimizes the risk of outages.
{"title":"Reducing risk for central site equipment moves","authors":"Roger W. Kleffman, Rick Glesener, Jerry Brzeczek","doi":"10.1145/800173.809720","DOIUrl":"https://doi.org/10.1145/800173.809720","url":null,"abstract":"Equipment changes - moving, adding or removing units in a central computer facility - can have a devastating effect on a computer center. Equipment failures and cable problems can result in prolonged service outages, user disservice and management frustration. Risks from these changes can be effectively controlled by means of sound implementation planning tools. An effective methodology based on a graphics technique that accurately represents equipment location in a computer room on standard size paper provides the planning tools that minimizes the risk of outages.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116778951","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
A software manufacturing paradigm is described which deals effectively with many issues long associated with software development and maintenance. In essence, Computer Aided Programming (CAP) is to software manufacturing what CAD/CAM is to conventional manufacturing. CAP is the first of a new generation of software manufacturing systems based on a standard sub-assembly approach. CAP provides an automated software development environment in which the computer handles the bulk of the work required to build and to maintain code. Featuring automatic assembly and customization of reusable code modules and generated code, CAP builds a complete program from specific goal-oriented instructions supplied by the user. The techniques of software manufacturing are applicable to all areas of software development where recurring problem classes can be identified.
{"title":"Computer Aided Programming: Techniques for software manufacturing","authors":"P. Bassett","doi":"10.1145/800173.809690","DOIUrl":"https://doi.org/10.1145/800173.809690","url":null,"abstract":"A software manufacturing paradigm is described which deals effectively with many issues long associated with software development and maintenance. In essence, Computer Aided Programming (CAP) is to software manufacturing what CAD/CAM is to conventional manufacturing. CAP is the first of a new generation of software manufacturing systems based on a standard sub-assembly approach. CAP provides an automated software development environment in which the computer handles the bulk of the work required to build and to maintain code. Featuring automatic assembly and customization of reusable code modules and generated code, CAP builds a complete program from specific goal-oriented instructions supplied by the user. The techniques of software manufacturing are applicable to all areas of software development where recurring problem classes can be identified.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116587507","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
By the early to middle 1970's it was clear that education in computer science and related fields was failing to meet many of the needs of business and industry. In self-defense, many firms adopted the practice of hiring PhD's to lead programming projects (on the grounds that the PhD's were bright). Other firms chose to hire bright Bachelors, most of whom had little or no formal training in programming or software engineering (on the grounds that bright people could learn on the job). A side effect of these practices was that most of the PhD's were being siphoned off into industry and were thus unavailable to staff the rapidly growing computer science departments in higher education. At the same time, bright computer science Bachelors were enticed directly into industry by high salaries, and thus did not pursue advanced degrees. These factors were no doubt part of the reason for the severe shortage of computer scientists available to higher education.
{"title":"Combining management and technology in a master's degree for information system professionals","authors":"T. Kurtz, A. Morton","doi":"10.1145/800173.809745","DOIUrl":"https://doi.org/10.1145/800173.809745","url":null,"abstract":"By the early to middle 1970's it was clear that education in computer science and related fields was failing to meet many of the needs of business and industry. In self-defense, many firms adopted the practice of hiring PhD's to lead programming projects (on the grounds that the PhD's were bright). Other firms chose to hire bright Bachelors, most of whom had little or no formal training in programming or software engineering (on the grounds that bright people could learn on the job).\u0000 A side effect of these practices was that most of the PhD's were being siphoned off into industry and were thus unavailable to staff the rapidly growing computer science departments in higher education. At the same time, bright computer science Bachelors were enticed directly into industry by high salaries, and thus did not pursue advanced degrees. These factors were no doubt part of the reason for the severe shortage of computer scientists available to higher education.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129337461","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
The “operational approach” to software development is based on separation of problem-oriented and implementation-oriented concerns, and features executable specifications and transformational implementation. “Operational specification languages” are executable specification languages designed to fit the goals, assumptions, and strategies of the operational approach. This paper defines the operational approach and surveys the existing operational specification languages, viz., the graphic notation of the Jackson System Development method, PAISLey, Gist, and modern applicative languages.
{"title":"Operational specification languages","authors":"P. Zave","doi":"10.1145/800173.809737","DOIUrl":"https://doi.org/10.1145/800173.809737","url":null,"abstract":"The “operational approach” to software development is based on separation of problem-oriented and implementation-oriented concerns, and features executable specifications and transformational implementation. “Operational specification languages” are executable specification languages designed to fit the goals, assumptions, and strategies of the operational approach. This paper defines the operational approach and surveys the existing operational specification languages, viz., the graphic notation of the Jackson System Development method, PAISLey, Gist, and modern applicative languages.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121184342","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
A wheel supported open top receptacle such as a railway car is provided with a liner arrangement comprising a plurality of belt members arranged between the end walls of the car with the sides of adjacent ones of the belts overlapped in the direction between the end walls, and with each belt overlying the side walls and bottom wall of the car. One end of each belt member is attached to the upper end of the corresponding one of the side walls and, by upward displacement of the other end, each belt is adapted to be displaced upwardly relative to the car. Material in the car is progressively unloaded laterally outwardly of the car by sequential displacement of the belts in accordance with the pattern of overlap.
{"title":"Personal computers in the corporate environment: Software","authors":"G. A. Heidenrich","doi":"10.1145/800173.809711","DOIUrl":"https://doi.org/10.1145/800173.809711","url":null,"abstract":"A wheel supported open top receptacle such as a railway car is provided with a liner arrangement comprising a plurality of belt members arranged between the end walls of the car with the sides of adjacent ones of the belts overlapped in the direction between the end walls, and with each belt overlying the side walls and bottom wall of the car. One end of each belt member is attached to the upper end of the corresponding one of the side walls and, by upward displacement of the other end, each belt is adapted to be displaced upwardly relative to the car. Material in the car is progressively unloaded laterally outwardly of the car by sequential displacement of the belts in accordance with the pattern of overlap.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132110535","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Personal Information Retrieval Systems (PIRs) for microcomputers have not yet had the same kind of impact as have Database Management Systems (DBMSs) for microcomputers. This may be attributed to the differences in the kinds of problems the two systems address. What a retrieval system can do, that a DBMS cannot, is to surmise what a record (document) is about. It can help find things that the user cannot clearly describe - sometimes even by subject matter. It is this capability that developers of PIRs should accentuate, because increasingly, personal databases are becoming sufficiently large so that finding relevant records is a recognized problem. If PIRs offer little more than DBMSs they will fail to meet that need. Fortunately, twenty-five years of research have produced some techniques (mostly statistical) that can improve the ability of retrieval systems to find relevant items. Even though these techniques have not been implemented by the large-scale retrieval services or mainframe-based retrieval systems, they could be; in fact, it is quite possible to implement them efficiently in a microcomputer-based PIR.
{"title":"Use of statistical techniques in Personal Retrieval Systems","authors":"Matthew B. Koll","doi":"10.1145/800173.809733","DOIUrl":"https://doi.org/10.1145/800173.809733","url":null,"abstract":"Personal Information Retrieval Systems (PIRs) for microcomputers have not yet had the same kind of impact as have Database Management Systems (DBMSs) for microcomputers. This may be attributed to the differences in the kinds of problems the two systems address. What a retrieval system can do, that a DBMS cannot, is to surmise what a record (document) is about. It can help find things that the user cannot clearly describe - sometimes even by subject matter. It is this capability that developers of PIRs should accentuate, because increasingly, personal databases are becoming sufficiently large so that finding relevant records is a recognized problem.\u0000 If PIRs offer little more than DBMSs they will fail to meet that need. Fortunately, twenty-five years of research have produced some techniques (mostly statistical) that can improve the ability of retrieval systems to find relevant items. Even though these techniques have not been implemented by the large-scale retrieval services or mainframe-based retrieval systems, they could be; in fact, it is quite possible to implement them efficiently in a microcomputer-based PIR.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130041527","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
ADA was used as a design language in a software engineering course. Students were able to become familiar with the features of ADA as a programming language and to improve their software development skills. ADA proved to be a powerful and flexible language for the expression of the design of a home environmental control system.
{"title":"Using ADA as a design language - classroom experience","authors":"G. Corliss","doi":"10.1145/800173.809702","DOIUrl":"https://doi.org/10.1145/800173.809702","url":null,"abstract":"ADA was used as a design language in a software engineering course. Students were able to become familiar with the features of ADA as a programming language and to improve their software development skills. ADA proved to be a powerful and flexible language for the expression of the design of a home environmental control system.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129864687","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
With a fast growth in the quantity and quality of software applications for office systems and advanced workstations, it is becoming clear that the trend is towards a more integrated software architecture for workstation or office systems. A critical piece in a truly integrated system is a well-designed general purpose database mangement system (DBMS) that supports all applications running on the workstation (or office system). Sophisticated DBMSs have been developed on the main frames, primarily for large data processsing (DP) applications. Is it true, then, that all we need is to transport these systems to the workstation? The first problem that one faces to move a full scale DBMS to a workstation is the size. It is not clear that trimming a big DBMS down is an easy task. Some of the advanced capabilities might be modular and relatively easy to remove. Others could be quite difficult as the code is distributed throughout the system. In some cases, it might not even be possible to “trim” when the general capability is needed but to a lesser extent. In practice, most major DBMSs are built without serious concern on the space restrictions. It might be easier to design and implement a new system with “smallness” in mind than to trim down a huge one. The considerations on smallness include the data structures, control blocks, interfaces, buffer requirements, configuration and packaging of the system, as well as the number of lines of code. Size is only the beginning. Smallness makes the DBMS possible to run on a workstation. Because of the new operating environment, there are new requirements for the DBMS which are different from the traditional DP environment on a main frame. The real challenge is to determine what these requirements are and how to design a system accordingly. On an advanced workstation, one has to support word processing, data processing, engineering and scientific, administrative, as well as
{"title":"Database for office automation","authors":"David M. Choy","doi":"10.1145/800173.809688","DOIUrl":"https://doi.org/10.1145/800173.809688","url":null,"abstract":"With a fast growth in the quantity and quality of software applications for office systems and advanced workstations, it is becoming clear that the trend is towards a more integrated software architecture for workstation or office systems. A critical piece in a truly integrated system is a well-designed general purpose database mangement system (DBMS) that supports all applications running on the workstation (or office system). Sophisticated DBMSs have been developed on the main frames, primarily for large data processsing (DP) applications. Is it true, then, that all we need is to transport these systems to the workstation?\u0000 The first problem that one faces to move a full scale DBMS to a workstation is the size. It is not clear that trimming a big DBMS down is an easy task. Some of the advanced capabilities might be modular and relatively easy to remove. Others could be quite difficult as the code is distributed throughout the system. In some cases, it might not even be possible to “trim” when the general capability is needed but to a lesser extent. In practice, most major DBMSs are built without serious concern on the space restrictions. It might be easier to design and implement a new system with “smallness” in mind than to trim down a huge one. The considerations on smallness include the data structures, control blocks, interfaces, buffer requirements, configuration and packaging of the system, as well as the number of lines of code.\u0000 Size is only the beginning. Smallness makes the DBMS possible to run on a workstation. Because of the new operating environment, there are new requirements for the DBMS which are different from the traditional DP environment on a main frame. The real challenge is to determine what these requirements are and how to design a system accordingly.\u0000 On an advanced workstation, one has to support word processing, data processing, engineering and scientific, administrative, as well as","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130287292","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Cryptography is the science of secret writing. It has been used since the dawn of writing itself to conceal messages from an adversary. Throughout history, the use of cryptography has been largely confined to diplomatic and military communications. But in the last 10 years the tremendous advances in communication technology have created a serious need for cryptographic protection of private sector communications. Electronic funds transfer systems and satellite voice/digital networks are particularly vulnerable to compromise, without the use of cryptography. Recognizing the need for data protection apart from national security concerns, the National Bureau of Standards issued a call for a data encryption algorithm in 1973. During the subsequent discussions and debates, the mathematicians and computer scientists involved realized that cryptography was not an established science in the unclassified literature. They began the task of creating the foundations for this young discipline. In 1977, the NBS published the Data Encryption Standard (DES). Its use is required to protect sensitive governmental information not related to national security. Several national and international standards organizations have also adopted the DES.
{"title":"Cryptography and data security overview of panel discussion","authors":"Michael Willett","doi":"10.1145/800173.809712","DOIUrl":"https://doi.org/10.1145/800173.809712","url":null,"abstract":"Cryptography is the science of secret writing. It has been used since the dawn of writing itself to conceal messages from an adversary. Throughout history, the use of cryptography has been largely confined to diplomatic and military communications. But in the last 10 years the tremendous advances in communication technology have created a serious need for cryptographic protection of private sector communications. Electronic funds transfer systems and satellite voice/digital networks are particularly vulnerable to compromise, without the use of cryptography. Recognizing the need for data protection apart from national security concerns, the National Bureau of Standards issued a call for a data encryption algorithm in 1973. During the subsequent discussions and debates, the mathematicians and computer scientists involved realized that cryptography was not an established science in the unclassified literature. They began the task of creating the foundations for this young discipline. In 1977, the NBS published the Data Encryption Standard (DES). Its use is required to protect sensitive governmental information not related to national security. Several national and international standards organizations have also adopted the DES.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131231961","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：