ACM '83Pub Date : 1900-01-01DOI: 10.1145/800173.809744
B. Konsynski, J. Nunamaker
{"title":"The MBA and MIS: The integration of mis and management education","authors":"B. Konsynski, J. Nunamaker","doi":"10.1145/800173.809744","DOIUrl":"https://doi.org/10.1145/800173.809744","url":null,"abstract":"Over the past ten years, management information systems has emerged from obscurity to become one of the recognized functional areas of business and government. It is now impossible for most organizations to function without computer-aided information systems, and prospects are that organizations will become even more dependent upon such systems in the future.\u0000 Computerized payroll systems, inventory systems, record and bookkeeping systems were among the first practical applications of modern computer technology in business and governmental organizations. As computer applications in organizations expanded, so did the volume of data collected. By the late 1960s, the need to coordinate this ever-increasing volume of data led to the concept of management information systems.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":"20 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126444586","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}
ACM '83Pub Date : 1900-01-01DOI: 10.1145/800173.809689
Peter P. Chen
{"title":"Considerations in the design of office DBMS's","authors":"Peter P. Chen","doi":"10.1145/800173.809689","DOIUrl":"https://doi.org/10.1145/800173.809689","url":null,"abstract":"“Office Automation” has become a hot topic in recent years. There is considerable interest in developing database management systems (DBMS's) specifically for office applications. Before rushing into the bandwagon of developing office DBMS's the following factors should be considered:","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":"65 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116584298","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}
ACM '83Pub Date : 1900-01-01DOI: 10.1145/800173.809685
J. Sammet
{"title":"Why Ada is not just another programming language","authors":"J. Sammet","doi":"10.1145/800173.809685","DOIUrl":"https://doi.org/10.1145/800173.809685","url":null,"abstract":"Since there have been hundreds of high level languages developed over the past twenty years, many people are asking why there is so much fuss about Ada. The question is frequently asked—why isn't Ada just another programming language.\u0000 Although Ada was developed to meet Department of Defense requirements, those requirements were really for embedded computer systems i.e. those in which the computer is integrated with additional hardware. Such systems certainly exist in the nonmilitary environment e.g. process control, microwave ovens, and so Ada is applicable to many cases which have no connection with the military.\u0000 In addition to being a programming language, Ada provides support for software engineering concepts, as well as a programming support environment, and it is this combination which is unique. Ada is unique non-technically for social, economic, and political reasons which relate to the way in which it was developed and the way in which it is being viewed by many people and organizations. Ada is unique technically because of its support for the concept of software components, its excellent blend of modern useful features, and its support for the production of very large software systems.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":"43 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114671967","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}
ACM '83Pub Date : 1900-01-01DOI: 10.1145/800173.809703
Robert Gilges
{"title":"The future of commercial computing","authors":"Robert Gilges","doi":"10.1145/800173.809703","DOIUrl":"https://doi.org/10.1145/800173.809703","url":null,"abstract":"United States' business computing power is dedicated to the transaction-based activities of companies, not to the needs of senior executives responsible for critical corporate decisions. Software supporting current business systems is absolete and inflexible. Antiquated, inappropriate software undermines business ability to compete. Business requires new better systems that will provide external competitive data, as well as economic and research data vital to strategic decisions concerning products, operations, production, marketing, personnel and investments. There are four approaches to these future systems - redesign, package software, retrofitting, and prototyping. Retrofitting provides a unique approach to the immediate problem of prolonging the aging application portfolio while prototyping will likely be an important future direction in system design and development.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132015429","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}
ACM '83Pub Date : 1900-01-01DOI: 10.1145/800173.809697
P. Bonissone
{"title":"DELTA: An expert system to troubleshoot diesel electric locomotives","authors":"P. Bonissone","doi":"10.1145/800173.809697","DOIUrl":"https://doi.org/10.1145/800173.809697","url":null,"abstract":"In the last few years, expert systems have become the most visible and fastest growing branch of Artificial Intelligence. Their objective is to capture the knowledge of an expert in a particular problem domain, represent it in a modular, expandable structure, and transfer it to other users in the same problem domain. To accomplish this goal, it is necessary to address issues of knowledge acquisition, knowledge representation, inference mechanisms, control strategies, user interface and dealing with uncertainty.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":"17 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126476587","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}
ACM '83Pub Date : 1900-01-01DOI: 10.1145/800173.809695
Anne-Marie Claybrook
{"title":"Directions in computer security","authors":"Anne-Marie Claybrook","doi":"10.1145/800173.809695","DOIUrl":"https://doi.org/10.1145/800173.809695","url":null,"abstract":"One of the primary thrusts in operating system security has come from the Department of Defense (DoD), which early recognized the need for security controls in open use, multi-user, resource-shared computer systems.1 Two features in particular, mandatory access controls and security kernel technology, have been strongly promoted by the DoD. Mandatory access controls, necessary to support a security policy that cannot be circumvented by any user (in DoD's case, the national security policy regarding personnel clearances and data classifications) are being studied for their applicability to business2 and industry security problems. Security kernel technology is an implementation of the reference monitor concept, a security enforcement abstraction which views a computer system as composed of subjects (e.g., processes, users) and objects (e.g., files) and a reference monitor which checks each access by a subject to an object. In the past ten years, several attempts to build secure operating systems have utilized security kernel technology. While none of these attempts was practical from a performance point of view, the security kernel research still serves as a basis for current attempts to build secure systems.\u0000 In a continuing effort to promote secure systems for DoD use, the DoD Computer Security Center was formed in 1981. One of the first tasks of the Center was to draft a “Trusted Computer System Evaluation Criteria” which defines various levels of protection for computer systems.3 In addition to listing feature requirements, including auditing, labelling, mandatory access controls, discretionary access controls, identification and authentication, the criteria discuss both the structure and development techniques used to produce trusted systems.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130868210","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}
ACM '83Pub Date : 1900-01-01DOI: 10.1145/800173.809707
J. Meads
{"title":"Defining the ergonomic buzzwords","authors":"J. Meads","doi":"10.1145/800173.809707","DOIUrl":"https://doi.org/10.1145/800173.809707","url":null,"abstract":"Current software and computer systems are being advertised and sold today as FRIENDLY systems that are EASY TO USE. Most also claim to be EASY TO LEARN as well. But what is it that makes a system FRIENDLY, EASY TO USE, or EASY TO LEARN? Is it sufficient to enshrine a group of interactive features in a video box connected to a single user microcomputer? If a system is EASY TO USE does that make it FRIENDLY? Or does EASY TO LEARN mean that it is EASY TO USE? Does your friendly, easy-going personal computer salesman differentiate between these terms!\u0000 Although the physical aspects of human factors have been studied for several decades and have an established scientific base, there is very little published material on the software aspects of ergonomics that is based upon well controlled experimental investigation. However, there is a fair amount of literature in which individuals describe their experiences in various ad hoc situations. The similarities among these experiences has resulted in a fair amount of “folklore” which may be beneficially applied. The terms: EASY TO LEARN, EASY TO USE, and FRIENDLY are defined below according to this experiential base.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121205613","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}
ACM '83Pub Date : 1900-01-01DOI: 10.1145/800173.809709
J. McGann
{"title":"Microcomputer applications","authors":"J. McGann","doi":"10.1145/800173.809709","DOIUrl":"https://doi.org/10.1145/800173.809709","url":null,"abstract":"Surveys of the use of micros that were made a few years ago suggested that use was concentrated in a few business functions. Calcs and financial reporting packages were expanding in use so rapidly that other types of applications seemed to be unnoticed. However, micros were being introduced in many laboratories and production facilities. A recent survey of departments of companies that use micros reported 98 separate applications that could be grouped under the following organizational areas: accounting, planning, treasurer, purchasing, administration, personnel, operations or production, marketing and other\u0000 Most of the applications were financial in nature although operations or production uses were significant. Financial modeling and calc packages were used not only in financial applications, but they were also used develop a master scheduling job for manufacturing and for administrative and planning applications. Word processing packages were also used to handle many different jobs such as promotion, scheduling, tracking of assignments and automatic editing of information accessed from data bases. Packages are used quite often with micros as generalized development tools. This results in interesting support problems.\u0000 Applications of micros can also be considered in terms of the data communication involved. Most uses of micros have been on a stand alone basis, but an increasing number of applications involve communication with another micro or a host computer. The micro may be an intelligent terminal controlled by the host or it may be directing the other computing system. The micro may also transfer control back and forth to the other system in an integrated application.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":"88 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122764058","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}
ACM '83Pub Date : 1900-01-01DOI: 10.1145/800173.809725
Arthur Fink
{"title":"Are we becoming addicted to computers?","authors":"Arthur Fink","doi":"10.1145/800173.809725","DOIUrl":"https://doi.org/10.1145/800173.809725","url":null,"abstract":"What do we mean by “addicted”? The <underline>Oxford English Dictionary</underline> defines it as: “(1) Delivered over devoted, destined, bound. (2) Attached by one's own act; given up, devoted, ... naturally attached bondage, which displaces free will.” It is a condition in which really objective self-examination does not and probably cannot guide our behavior. It is generally regarded as a pitiful state, over which one has little control.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":"52 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124943349","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}
ACM '83Pub Date : 1900-01-01DOI: 10.1145/800173.809724
J. Schaeffer
{"title":"Long-range planning in computer chess","authors":"J. Schaeffer","doi":"10.1145/800173.809724","DOIUrl":"https://doi.org/10.1145/800173.809724","url":null,"abstract":"A serious deficiency in game-playing, tree-searching programs is their short-sightedness. Program strategy revolves around the maximization/minimization of what is attainable within the scope of the search tree with little consideration of what lies beyond. This paper describes Planner, a long-range chess strategist that assesses positions, determines a long-range strategy, and makes moves in the short-term (within the scope of the search tree) consistent with a long-term objective (beyond the depth of the search tree). In effect then, Planner allows the program to “see” beyond the limitations of the search tree.","PeriodicalId":306306,"journal":{"name":"ACM '83","volume":"27 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125103088","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}