SIGMINI '78Pub Date : 1978-08-01DOI: 10.1145/800218.806641
Hans W. Mandt
{"title":"Data management in Electronic Funds Transfer Systems","authors":"Hans W. Mandt","doi":"10.1145/800218.806641","DOIUrl":"https://doi.org/10.1145/800218.806641","url":null,"abstract":"Although Electronic Funds Transfer Systems (EFTS) encompass a large group of financial transaction systems including funds transfers between major banks and transfers among the Federal Reserve Banks over their private network (FEDWIRE), the scope of this paper will be limited to the major application of EFT systems which utilize mini and microcomputers: networks of automatic banking transaction terminals.","PeriodicalId":344026,"journal":{"name":"SIGMINI '78","volume":"200 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1978-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124931108","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}
SIGMINI '78Pub Date : 1978-04-01DOI: 10.1145/800218.806626
Ted G. Lewis
{"title":"Performance evaluation of three microcomputer based systems in a small business dataprocessing environment.","authors":"Ted G. Lewis","doi":"10.1145/800218.806626","DOIUrl":"https://doi.org/10.1145/800218.806626","url":null,"abstract":"In March, 1977 a team of students under the guidance of the author began studying three personal computer systems to determine their strengths and weaknesses when placed in a data processing environment. The three systems were chosen to represent a broad spectrum of contemporary microcomputer based data processing equipment. System W is a firmware BASIC computer originally designed for scientific applications but found being used in a variety of business processing applications. System T is a storage display graphics computer based on the Motorola 6800 microprocessor ROM BASIC, and ROM operating system. System D is an Intel 8080 based computer designed specifically for business dataprocessing.","PeriodicalId":344026,"journal":{"name":"SIGMINI '78","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1978-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129196774","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}
SIGMINI '78Pub Date : 1978-04-01DOI: 10.1145/800218.806632
M. Lane
{"title":"The subsystem approach to enhancing small processor operating systems","authors":"M. Lane","doi":"10.1145/800218.806632","DOIUrl":"https://doi.org/10.1145/800218.806632","url":null,"abstract":"Operating systems for small processors often do not take full advantage of a small processor's resources. The implementation of a subsystem to enhance the standard operating system has proved to be an effective method to increase the utilization of a small processor's resources.\u0000 Several different subsystems for small processors are discussed. The advantages of using the subsystem approach in a small processor environment are given.","PeriodicalId":344026,"journal":{"name":"SIGMINI '78","volume":"61 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1978-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133093689","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}
SIGMINI '78Pub Date : 1978-04-01DOI: 10.1145/800218.806634
M. K. Donegan
{"title":"The design of a space efficient compiler","authors":"M. K. Donegan","doi":"10.1145/800218.806634","DOIUrl":"https://doi.org/10.1145/800218.806634","url":null,"abstract":"Writing a compiler for a small machine with minimal software support can be quite difficult because the program is long and debugging aids are usually inadequate. In addition, the usual techniques for compiler writing tend to produce programs which are quite large when compared to, for example, a BASIC interpreter. This frustrates efforts for producing compilers on small machines. We describe a method which can be used to reduce the size of a compiler and simultaneously provide good debugging tools. The resulting compiler sacrifices little in terms of execution speed (in part because compilers on minicomputers are often I/O bound). We have used this method to write an MPL [1] compiler for a Microdata 32/S minicomputer. The compiler requires approximately 12K bytes of memory as opposed to 32K bytes required by the compiler produced by the manufacturer, and compiles at essentially the same speed. Appendix II outlines the syntax of the MPL language and is included to illustrate the size of the language being compiled. MPL is based on PL/I and is quite similar to the PL/M* [2] language developed by the INTEL Corporation.\u0000 The method described here uses an interpretive language for writing the compiler. Thus the interpreter is the only machine language program written. We coded the interpreter in MPL and used a cross compiler to compile it, however, the interpreter could have been easily coded in assembly language. Figure 1 illustrates the savings of the interpretive language over machine code. The procedure IF_STAT is typical of a routine which might appear in a recursive descent compiler for MPL. The gain in space occurs because machine language instructions carry too much information content when applied to a special purpose (such as compiling). Note for example that a subroutine call for the Microdata requires 6 bytes, but all that is really needed is an opcode to indicate a call and a byte to indicate which of a few subroutines is to be called.","PeriodicalId":344026,"journal":{"name":"SIGMINI '78","volume":"26 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1978-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121975911","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}
SIGMINI '78Pub Date : 1900-01-01DOI: 10.1145/800218.806643
Shmuell Gruber, Meir Tahan, Michael Z. Hanani
{"title":"A mini-micro computer link promotes distributed processing in scientific and engineering computations","authors":"Shmuell Gruber, Meir Tahan, Michael Z. Hanani","doi":"10.1145/800218.806643","DOIUrl":"https://doi.org/10.1145/800218.806643","url":null,"abstract":"Engineering and scientific work often requires complex computations of different types that should be carried out on different types of computers on the one hand, but must communicate and support each other on the other. To facilitate efficient execution of such computations, a network composed of mini and micro computers (DEC PDP 11/40 and Intel 8080) with the support of a large computer (CDC CYBER 73) has been built and is described in this paper. The network enables the realization of involved scientific computations that could not be carried out by any one of the computers on its own. A general description of the entire set-up is followed by a more detailed discussion of the micro-mini link, and examples of projects using the network.","PeriodicalId":344026,"journal":{"name":"SIGMINI '78","volume":"49 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":"125102434","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}
SIGMINI '78Pub Date : 1900-01-01DOI: 10.1145/800218.806637
Daniel F. Langenwalter
{"title":"Decision tables - an effective programming tool","authors":"Daniel F. Langenwalter","doi":"10.1145/800218.806637","DOIUrl":"https://doi.org/10.1145/800218.806637","url":null,"abstract":"The manager or owner of a small to medium size business often has strong ideas on how he wants to run his business. The “packaged” software to go with the mini computer that he can afford just doesn't give him the flexibility he wants. To keep the software costs down and still be able to get the desired programs, a programming method that gets the results at low cost is needed. Two companies reported reductions of 3 to 1, i.e. costs were down to one-third of the previous methods, by using decision tables to write the logic. With such substantial reductions in costs, the mini computer owner can have the tailored programs he wants with a reasonable investment.\u0000 A decision table processor, MUSCL, has been developed and is implemented on mini computers. This paper shows how to write and solve decision tables as implemented.\u0000 Ideally problems are solved in steps. The problem is defined clearly. Criteria or conditions are established. Then a series of actions is taken. The expression that describes the conditions and actions is a “decision rule”. A decision table is the structure for describing a set of decision rules. A decision table gives us a way of recording decision patterns so that we can make consistent decisions and see how to change the patterns to meet changing conditions.","PeriodicalId":344026,"journal":{"name":"SIGMINI '78","volume":"50 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":"128718565","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}
SIGMINI '78Pub Date : 1900-01-01DOI: 10.1145/800218.806633
Patrick W. Ireland, Herbert V. Savage, Earl J. Schweppe
{"title":"Visual interactive production language systems","authors":"Patrick W. Ireland, Herbert V. Savage, Earl J. Schweppe","doi":"10.1145/800218.806633","DOIUrl":"https://doi.org/10.1145/800218.806633","url":null,"abstract":"In earlier work on anticipation and prompting systems for programming languages it was recognized that a more formal approach to development of such interactions with programmers at display terminals was needed. It was observed that the bulk of the data involved in these interactions was in the displays themselves and that certain display drivers operated on action strings similar to those in production language systems. The development of special Floyd-Evans production languages oriented toward a visual interactive environment was therefore undertaken. Based on two experimental interpreters which have been implemented, the language itself has now been substantially refined and compilers for a common language have been designed with one being implemented. In the first implementation which was accomplished on a Datapoint 2200, a substantial portion of the effort was devoted to a pedagogic display of the parsing process. In the second implementation on an Interdata 85, all of the programming was made reentrant so that multiple users can be served using the same or different target languages. Furthermore, some of the basic functions were reduced to microcode, although it was not possible to carry this as far as had been hoped. It was also learned during development of the second system that left-part matching and right-part replacement could be treated as generalized actions—thus simplifying the internal structure of the interpreter. Development of these systems is part of ongoing research with programming languages and automated programmer assistance.","PeriodicalId":344026,"journal":{"name":"SIGMINI '78","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":"124758792","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}
SIGMINI '78Pub Date : 1900-01-01DOI: 10.1145/800218.806638
G. Benincasa, A. Daneels, P. Heymans, C. Serre
{"title":"Structured design benefits to a process control software project","authors":"G. Benincasa, A. Daneels, P. Heymans, C. Serre","doi":"10.1145/800218.806638","DOIUrl":"https://doi.org/10.1145/800218.806638","url":null,"abstract":"A 12-man-year process control software project has been successfully completed in 12 months without interruption of the production process of CERN PS accelerators. After 6 months of careful preparation by a small team, 9 man-years of software, i.e. around 100 control programs amounting to more than 40'000 instructions, have been produced in 6 months by 6 experienced full-time software engineers and 24 part-time engineers and technicians, part of whom had never programmed before. The delivered product met the users specifications, was completed within schedule, conformed to the standards and was fully documented.","PeriodicalId":344026,"journal":{"name":"SIGMINI '78","volume":"61 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":"131724715","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}
SIGMINI '78Pub Date : 1900-01-01DOI: 10.1145/800218.806636
John E. Buxton
{"title":"Basic for realtime control applications","authors":"John E. Buxton","doi":"10.1145/800218.806636","DOIUrl":"https://doi.org/10.1145/800218.806636","url":null,"abstract":"Basic is a general purpose programming language commonly used in business applications. There are many versions of Basic with varying capabilities, ranging from simple games to large multi-terminal business applications. However, Basic is seldom used to implement a large realtime control system. The purpose of this paper is to describe a realtime control system and discuss the advantages and the disadvantages of implementing the system using Basic.","PeriodicalId":344026,"journal":{"name":"SIGMINI '78","volume":"9 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":"127994036","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}