DOCSLIB.ORG

Charles W. Bachman: Database Software Pioneer

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Charles W. Bachman: Database Software Pioneer [3B2-9] man2011040070.3d 3/11/011 19:30 Page 70 Biographies Charles W. Bachman: Database Software Pioneer Thomas Haigh University of Wisconsin, Milwaukee Editor: Thomas Haigh Charles W. Bachman was born in position based on a straight-line extrapolation of its Manhattan, Kansas, in 1924 but did previous trajectory. This convinced him both of the im- not stay there long. His father, a portance of predictive control loops and the difficulty Hall of Fame football coach, moved of accurately hitting future targets. After the war their family several times before set- ended, he returned to Michigan State and completed tling in East Lansing, Michigan, for a his mechanical engineering degree in 1948. long spell working at what was then It was time to leave East Lansing again. An interest in Michigan State College. The youn- thermodynamics led Bachman to graduate school at ger Bachman retained a lifelong in- the University of Pennsylvania, although ‘‘it wasn’t terest in sports, playing on several until I arrived there that I had realized that the engi- teams during high school. He earned strong grades in neering graduate school at Penn was a night school’’ most subjects but decided on an engineering career at and that his classmates all had day jobs. He filled the an early age. At 11 years old, he had triumphed in a daylight hours with management courses from Penn’s local Soap Box Derby, in which children custom build Wharton School, satisfying most of the coursework and race small, unpowered cars.1 When I interviewed requirements for an MBA even though there was no for- him in 2004, he told me, ‘‘I was never interested in any- mal joint degree in engineering and business. In the thing else. I was always going to be an engineer.’’ summer of 1949, he married his college sweetheart, Connie Hadley, two weeks after her graduation from Early Education and Career Michigan State. Before Bachman could realize this dream, there was the Thenextyearhegraduated amid the uncertainty little matter of World War II, which was raging that accompanied the outbreak of the Korean War. throughout his high school years. Resolving to enter A search for work in the Great Lakes region culminated the military with a little additional preparation, he in a job with Dow Chemical in Midland, Michigan. graduated a semester early from high school to spend Bachman’s career at Dow began with a nine-month the spring and summer of 1943 satisfying freshman spell rotating through the plant’s various departments. college requirements at Michigan State University. He After that, he settled down to his role as ‘‘an engineer, spent two years in the Army Antiaircraft Artillery at a drafting table, in a room with more than one hun- Corp, serving in New Guinea, Australia, and the Philip- dred engineers.’’ The chemical industry is oriented pines. Antiaircraft guns of this era used a simple me- around networks of processes, as the products of one re- chanical computer to target a plane’s predicted future action become the inputs for another. He worked in a Background of Charles W. Bachman Born: 1924, Manhattan, Kansas technology subsection, and manager of data manage- Education: BSc (mechanical engineering), Michigan ment software for the advanced system division), State University, 1948; MS (mechanical engineering), 1964–1970; Honeywell Information Systems, chief University of Pennsylvania, 1950. staff engineer, 1970–1980; Cullinane Database Sys- Professional Experience: Dow Chemical, assign- tems, 1980–1983; Bachman Information Systems, ments in engineering, finance, manufacturing, and sys- president and CEO, 1983–1988, and chairman, tems work, 1950–1955, manager of corporate data 1988–1996; Cayenne Software, president, 1996–1997; processing, 1956–1959; and manager of data process- Constellar, consultant, 2002–2006; InfiniteIQ, consul- ing research, 1960; General Electric, Integrated Sys- tant, 2009–2010. tems Project in Production Control Services, 1960– Honors and Awards: ACM Turing Award, 1973; 1964; Computer Department (titles include manager Distinguished Fellow of the British Computer Society, of software product planning, manager of applied 1977. 70 IEEE Annals of the History of Computing Published by the IEEE Computer Society 1058-6180/11/$26.00 c 2011 IEEE [3B2-9] man2011040070.3d 3/11/011 19:30 Page 71 group responsible for the water, steam, and for the new operation. By May 1958, Bach- electrical power systems that kept these pro- man had hired 30 people and the department cesses running at its Midland plants. Bach- was beginning to plan its applications. But man’s work centered more on economic Dow ran into economic trouble and began trade-offs than purely technical designs, ana- to lay off its newest hires, slashing 10 posi- lyzing design choices within the context of tions from his group. Others on his team larger set of assumptions to optimize quit in search of more promising positions, expected returns. and Dow eventually cancelled the IBM He recalled having independently rein- order, although not before constructing an vented concepts such as discounted cash empty computer room in its new headquar- flow as part of an effort dubbed the ‘‘Equiva- ters building. lent Capital Project.’’ By 1952, this led to Ordering a 709 had qualified Dow Chem- work analyzing the capital cost of building ical for membership in Share, the group for all Dow manufacturing plants, for which users of large IBM scientific computers. At a Bachman commandeered time with the me- time when IBM itself provided only a limited chanical punched-card machines in the Ac- selection of system programs for its machines counting Department to iteratively solve and there was no independent software in- networks of simultaneous equations repre- dustry, Share played a vital role in establish- senting data collected from several Dow ing a common library of programs and plants. He wired plug boards and operated subroutines between sites. Its committees the machines himself. In 1954, he worked sponsored the joint development of new in the Pricing Department and was responsi- projects, including the ambitious SOS project ble for the pricing of agricultural chemicals. to produce a standard and powerful operat- In 1955, he shifted from analysis to pro- ing system for the 709. duction for two years, working first as a pro- Bachman quickly became a leader among cess engineer at the Saran plant and then as the smaller community of computing cen- the number two manager of the Styron 475 ters intending to use the 709 primarily for plant. These experiences exposed him to business applications. At his second Share many different aspects of business, reinforc- meeting, he met Harry Tellier of General ing his tendency to see activities as part of a Electric, manager of its computer team unified system. working in the Hanford Atomic Reserva- tion. Tellier’s group had created an inge- Share and 9PAC nious system for the earlier IBM 702 In 1957 Dow Chemical decided to join the computer that generalized the laborious computer age. On the recommendation of programming work involved in maintain- its treasurer, with whom Bachman had ing master data files on tape and generating worked closely on his capital accounting reports based on the data contained in project, Bachman was chosen to head its them. This inspired many subsequent new corporate Data Processing Department. systems, including IBM’s own widely used His first job was to recommend a machine Report Program Generator (RPG) family.3 to purchase. As he recalled, Bachman quickly recognized the value of such a system to Dow, and Tellier and he be- I don’t think we ever did a feasibility study. came founding members of the Share Data The idea was that ‘‘Everyone else is doing it. Processing Committee. The committee spon- We should be doing it.’’ Which one should sored a collaborative project to create what we buy was the question. ... It wasn’t clear became known as 9PAC, an updated version what was going to happen with these com- of the Hanford report generator package for 2 puters, what they were good for. the 709. (I have previously discussed the de- velopment of 9PAC and its importance to He was courted by IBM, with a tour of its the development of data management soft- Poughkeepsie factory, and by Univac which ware,soIwillnotdosoindetailhere.4 It provided a two-week programming course. entered use in 1959 and was widely Impressed by its ability to handle both busi- deployed. Among its most important innova- ness data processing and technical comput- tions, which Bachman credits to discussion ing, he recommended renting an IBM 709. between himself and Russ McGee of GE’s Computer customers generally waited a Hanford group, was support for hierarchical year or two for delivery, during which time parent-child relationships within a magnetic- they hired and trained data processing staff tape file—for example, following each October–December 2011 71 [3B2-9] man2011040070.3d 3/11/011 19:30 Page 72 Biographies customer record with records for the orders General Electric was therefore investing placed by that customer. heavily in the latest management methods It is a tribute both to the practical flexibil- and technologies. One of the responsibilities ity of Bachman’s intelligence and Share’s ef- of its corporate-level teams was to research fectiveness in allowing participants to learn areas such as operations research, simulation, from the experiences of others that he forecasting, and automation so that effective could play a significant role in the 9PAC de- new practices could be spread across its di- sign without having written a data process- verse empire. Bachman was recruited to its ing application or ever actually taking prosaically named Production Control Ser- delivery of a computer. Share also established vices Group, headed by H.
Load more

Recommended publications
  • Appendix E: an Overview of the Network Data Model
    Elmasri_APPC Page 1 Monday, April 3, 2006 3:40 PM An Overview of the APPENDIXE Network Data Model This appendix provides an overview of the network data model.1 The original network model and language were presented in the CODASYL Data Base Task Group’s 1971 report; hence it is sometimes called the DBTG model. Revised reports in 1978 and 1981 incorporated more recent concepts. In this appendix, rather than concentrating on the details of a particular CODASYL report, we present the general concepts behind net- work-type databases and use the term network model rather than CODASYL model or DBTG model. The original CODASYL/DBTG report used COBOL as the host language. Regardless of the host programming language, the basic database manipulation commands of the net- work model remain the same. Although the network model and the object-oriented data model are both navigational in nature, the data structuring capability of the network model is much more elaborate and allows for explicit insertion/deletion/modification semantic specification. However, it lacks some of the desirable features of the object mod- els that we discussed in Chapter 11, such as inheritance and encapsulation of structure and behavior. 1. The complete chapter on the network data model and about the IDMS system from the second edition of this book is available at http://www.awl.com/cseng/titles/0-8053-1755-4. This appendix is an edited excerpt of that chapter. E–1 Elmasri_APPC Page 2 Monday, April 3, 2006 3:40 PM E–2 Appendix E / An Overview of the Network Data Model E.1 Network Data Modeling Concepts There are two basic data structures in the network model: records and sets.
    [Show full text]
  • Charles Bachman 1973 Turing Award Recipient Interviewed by Gardner Hendrie February 4, 2015 Lexington, Massachusetts Video Inter
    Oral History of Charles W. (Charlie) Bachman Charles Bachman 1973 Turing Award Recipient Interviewed by Gardner Hendrie February 4, 2015 Lexington, Massachusetts Video Interview Transcript This video interview and its transcript were originally produced by the Computer History Museum as part of their Oral History activities and are copyrighted by them. CHM Reference number: X7400.2015 © 2006 Computer History Museum. The Computer History Museum has generously allowed the ACM to use these resources. Page 1 of 58 Oral History of Charles W. (Charlie) Bachman GH: Gardner Hendrie, interviewer CB: Charles Bachman, 1973 Turing Award Recipient GH: …Alright. We have here today with us Charlie Bachman, who’s graciously agreed to do an oral history for the Computer History Museum. Thank you very much Charlie. I think I’d like to start out with a very simple question: What is your earliest recollection of what you wanted to do when you grew up? CB: Well I guess the best answer, I don’t really think of any early recollection... GH: Okay. CB: …about that. I just kind of grew into it. GH: Alright. Now I have read that you decided to become a mechanical engineer relatively early. How did that come about? What influenced you to make that decision? And when did you make it? CB: Well I grew up in East Lansing, Michigan, which is the heart of General Motors and Ford and Chrysler, building automobiles. And so you thought engineers were people who designed cars and things that go with them, and that’s mainly mechanical engineering. So I just somehow thought that was the general course you took in engineering; if you didn’t know what kind of engineer you want to be, you do mechanical engineer.
    [Show full text]
  • Database History
    History of Database Systems JIANNAN WANG SIMON FRASER UNIVERSITY JIANNAN @ SFU 1 Database Systems in a Half Century (1960s – 2010s) When What Early 1960 – Early 1970 The Navigational Database Empire Mid 1970 – Mid 1980 The Database World War I Mid 1980 – Early 2000 The Relational Database Empire Mid 2000 – Now The Database World War II References. • https://en.wikipedia.org/wiki/Database#History • What Goes Around Comes Around (Michael Stonebraker, Joe Hellerstein) • 40 Years VLDB Panel JIANNAN @ SFU 2 The Navigational Database Empire (Early1960 – Early 1970) Data Model 1. How to organize data 2. How to access data Navigational Data Model 1. Organize data into a multi-dimensional space (i.e., A space of records) 2. Access data by following pointers between records Inventor: Charles Bachman 1. The 1973 ACM Turing Award 2. Turing Lecture: “The Programmer As Navigator” JIANNAN @ SFU 3 The Navigational Database Empire (Early1960 – Early 1970) Representative Navigational Database Systems ◦ Integrated Data Store (IDS), 1964, GE ◦ Information Management System (IMS), 1966, IBM ◦ Integrated Database Management System (IDMS), 1973, Goodrich CODASYL ◦ Short for “Conference/Committee on Data Systems Languages” ◦ Define navigational data model as standard database interface (1969) JIANNAN @ SFU 4 The Birth of Relational Model Ted Codd ◦ Born in 1923 ◦ PHD in 1965 ◦ “A Relational Model of Data for Large Shared Data Banks” in 1970 Relational Model ◦ Organize data into a collection of relations ◦ Access data by a declarative language (i.e., tell me what you want, not how to find it) Data Independence JIANNAN @ SFU 5 The Database World War I: Background One Slide (Navigational Model) ◦ Led by Charles Bachman (1973 ACM Turing Award) ◦ Has built mature systems ◦ Dominated the database market The other Slide (Relational Model) ◦ Led by Ted Codd (mathematical programmer, IBM) ◦ A theoretical paper with no system built ◦ Little support from IBM JIANNAN @ SFU 6 The Database World War I: Three Big Campaigns 1.
    [Show full text]
  • Historical Reflections How Charles Bachman Invented the DBMS, a Foundation of Our Digital World
    viewpoints VDOI:10.1145/2935880 Thomas Haigh Historical Reflections How Charles Bachman Invented the DBMS, a Foundation of Our Digital World His 1963 Integrated Data Store set the template for all subsequent database management systems. IFTY-THREE YEARS AGO a small team working to automate the business processes of the General Electric Company built the first database man- Fagement system. The Integrated Data Store—IDS—was designed by Charles W. Bachman, who won the ACM’s 1973 A.M. Turing Award for the accomplish- ment. Before General Electric, he had spent 10 years working in engineering, finance, production, and data process- ing for the Dow Chemical Company. He was the first ACM A.M. Turing Award winner without a Ph.D., the first with a background in engineer- ing rather than science, and the first to spend his entire career in industry rather than academia. Some stories, such as the work of Babbage and Lovelace, the creation of the first electronic computers, and the emergence of the personal computer industry have been told to the public again and again. They appear in popu- lar books, such as Walter Isaacson’s recent The Innovators: How a Group of Hackers, Geniuses and Geeks Created the Digital Revolution, and in museum exhibits on computing and innova- tion. In contrast, perhaps because da- tabase management systems are rarely Figure 1. This image, from a 1962 internal General Electric document, conveyed the idea COURTESY OF CHARLES W. BACHMAN AND THE CHARLES BABBAGE INSTITUTE. BABBAGE AND THE CHARLES BACHMAN W. OF CHARLES COURTESY experienced directly by the public, of random access storage using a set of “pigeon holes” in which data could be placed.
    [Show full text]
  • Database Management Systems Ebooks for All Edition (
    Database Management Systems eBooks For All Edition (www.ebooks-for-all.com) PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sun, 20 Oct 2013 01:48:50 UTC Contents Articles Database 1 Database model 16 Database normalization 23 Database storage structures 31 Distributed database 33 Federated database system 36 Referential integrity 40 Relational algebra 41 Relational calculus 53 Relational database 53 Relational database management system 57 Relational model 59 Object-relational database 69 Transaction processing 72 Concepts 76 ACID 76 Create, read, update and delete 79 Null (SQL) 80 Candidate key 96 Foreign key 98 Unique key 102 Superkey 105 Surrogate key 107 Armstrong's axioms 111 Objects 113 Relation (database) 113 Table (database) 115 Column (database) 116 Row (database) 117 View (SQL) 118 Database transaction 120 Transaction log 123 Database trigger 124 Database index 130 Stored procedure 135 Cursor (databases) 138 Partition (database) 143 Components 145 Concurrency control 145 Data dictionary 152 Java Database Connectivity 154 XQuery API for Java 157 ODBC 163 Query language 169 Query optimization 170 Query plan 173 Functions 175 Database administration and automation 175 Replication (computing) 177 Database Products 183 Comparison of object database management systems 183 Comparison of object-relational database management systems 185 List of relational database management systems 187 Comparison of relational database management systems 190 Document-oriented database 213 Graph database 217 NoSQL 226 NewSQL 232 References Article Sources and Contributors 234 Image Sources, Licenses and Contributors 240 Article Licenses License 241 Database 1 Database A database is an organized collection of data.
    [Show full text]
  • Introduction to the Mumps Language
    Introduction to the Mumps Language A Quick Introduction to the Mumps Programming Language Kevin C. O'Kane Professor Emeritus Department of Computer Science University of Northern Iowa Cedar Falls, IA 50614 [email protected] A full text on this topic in both print and ebook formats is available on Amazon.com Videos are available on youtube.com: https://www.youtube.com/channel/UC5oHS9h-prWeBrBNzXm8rYA Copies of the software used in this tutorial are are available at: http://www.cs.uni.edu/~okane/ http://threadsafebooks.com/ November 4, 2017 Mumps History 1 Mumps (Massachusetts General Hospital Utility Multi-programming System) is a general purpose programming language environment that provides ACID (Atomic, Consistent, Isolated, and Durable) database access by means of program level subscripted arrays and variables. The Mumps database allows schema-less, key-value access to disk resident data organized as trees that may also be viewed as sparse multi-dimensional arrays. Beginning in 1966, Mumps (also referred to as M), was developed by Neil Pappalardo and others in Octo Barnett's lab at the Massachusetts General Hospital (MGH) on a PDP-7, the same architecture on which Unix was being implemented at approximately the same time. Initial experience with Mumps was very positive and it soon was ported to a number of other architectures including the PDP-11, the VAX, Data General, Prime, and, eventually, Intel x86 based systems, among others. It quickly became the basis for many early applications of computers to the health sciences. Mumps History 2 When Mumps was originally designed, there were very few general purpose database systems in existence.
    [Show full text]
  • History of Database Applications Moaz Mansour (47) Wengang Yang (77) University of Rochester University of Rochester 500 Joseph C
    History of Database Applications Moaz Mansour (47) Wengang Yang (77) University of Rochester University of Rochester 500 Joseph C. Wilson Blvd., Rochester, NY 14627 500 Joseph C. Wilson Blvd., Rochester, NY 14627 +1(585)733-7670 +1(585)629-2778 [email protected] [email protected] ABSTRACT Databases and database management systems have become a very provide more sophisticated programming logic within the database essential part of today’s information systems. Most of our day-to- structure. day activities certainly include a database interaction. It starts nowadays with the newly born children who get a record number in most of the governments in our modern world. It is involved in everything after that, going to school, graduating, getting a job, 2. Database Development Timeline: running or managing a business, buying travel tickets or even getting your groceries. 2.1 The Sixties The purpose of this project is to take a look on the origins of Back to 1960’s, Cobol and with Cobol, and later Fortran, the first databases from different perspectives (1) Its development over the non-proprietary programming language has been developed. And years (2) different technologies adopted and (3) to take a look this makes it possible to create enterprise computer systems. Based forward at what the future may hold for databases. on this, two main data models were developed, which are network model by C.W.Bachman (Bachman 1965) and hierarchical model IMS (Information Management System). 1. INTRODUCTION In the late 1960’s, IBM created the very first commercial system The ancient or modern society, humans and organizations always IMS for American Airlines to help them store reservation data.
    [Show full text]
  • Database Management Systems
    Database Management Systems As one of the oldest components associated with computers, the database management system, or DBMS, is a computer software program that is designed as the means of managing all databases that are currently installed on a system hard drive or network. Different types of database management systems exist, with some of them designed for the oversight and proper control of databases that are configured for specific purposes. Here are some examples of the various incarnations of DBMS technology that are currently in use, and some of the basic elements that are part of DBMS software applications. As the tool that is employed in the broad practice of managing databases, the DBMS is marketed in many forms. Some of the more popular examples of DBMS solutions include Microsoft Access, FileMaker, DB2, and Oracle. All these products provide for the creation of a series of rights or privileges that can be associated with a specific user. This means that it is possible to designate one or more database administrators who may control each function, as well as provide other users with various levels of administration rights. This flexibility makes the task of using DBMS methods to oversee a system something that can be centrally controlled, or allocated to several different people. There are four essential elements that are found with just about every example of DBMS currently on the market. The first is the implementation of a modeling language that serves to define the language of each database that is hosted via the DBMS. There are several approaches currently in use, with hierarchical, network, relational, and object examples.
    [Show full text]
  • Database Management System’S
    Page 1 of 10 Database Management System’s 8.1 A database is an organized collection of data. The data are typically organized to model aspects of reality in a way that supports processes requiring information. For example, modelling the availability of rooms in hotels in a way that supports finding a hotel with vacancies. Database management systems (DBMSs) are specially designed software applications that interact with the user, other applications, and the database itself to capture and analyze data. A general-purpose DBMS is a software system designed to allow the definition, creation, querying, update, and administration of databases. Well-known DBMSs include MySQL, PostgreSQL, Microsoft SQL Server, Oracle, SAPand IBM DB2. A database is not generally portable across different DBMSs, but different DBMSs can interoperate by using standards such as SQL and ODBC or JDBC to allow a single application to work with more than one DBMS. Database management systems are often classified according to the database model that they support; the most popular database systems since the 1980s have all supported the relational model as represented by the SQL language. Terminology and overview Formally, "database" refers to the data themselves and supporting data structures. Databases are created to operate large quantities of information by inputting, storing, retrieving and managing that information. Databases are set up so that one set of software programs provides all users with access to all the data. A "database management system" (DBMS) is a suite of computer software providing the interface between users and a database or databases. Because they are so closely related, the term "database" when used casually often refers to both a DBMS and the data it manipulates.
    [Show full text]
  • Interview with Charles W
    An interview with Charles W. Bachman1 OH XXX Conducted by Thomas Haigh On 25-26 September, 2004 Tucson, Arizona Interview conducted for the Special Interest Group on the Management of Data (SIGMOD) of the Association for Computing Machinery (ACM). Transcript and original tapes donated to the Charles Babbage Institute. Charles Babbage Institute Center for the History of Information Processing University of Minnesota, Minneapolis Copyright 2004, Charles Babbage Institute 1 The transcript has been edited by Thomas Haigh, and subsequently edited and clarified by Charlie Bachman, his wife, Connie Bachman, and Russ McGee, who was a major player in the following story. Charles W. Bachman, Oral History with Thomas Haigh 2 ABSTRACT Charles W. Bachman reviews his career. Born during 1924 in Kansas, Bachman attended high school in East Lansing, Michigan before joining the Army Anti Aircraft Artillery Corp, with which he spent two years in the Southwest Pacific Theater, during World War II. After his discharge from the military, Bachman earned a B.Sc. in Mechanical Engineering in 1948, followed immediately by an M.Sc. in the same discipline, from the University of Pennsylvania. On graduation, he went to work for Dow Chemical in Midland, Michigan. Bachman discusses his experiences as an engineer there, focusing on engineering economics issues, including his work on the development of methods for return-on-investment calculations, using punched card machines. In 1957, he was appointed the first head of Dow’s Central Data Processing department, where he was responsible for preparing the way for the arrival of its first big digital computer. Bachman organized a feasibility study to select a new machine and hired a staff of programmers and analysts.
    [Show full text]
  • Course Introduction & History of Database Systems
    Course Introduction & History of Database Systems CMPT 843, SPRING 2019 JIANNAN WANG https://sfu-db.github.io/dbsystems/ CMPT 843 - 2019 SPRING - SFU 1 Introduce Yourself What’s your name? Where are you from? M.Sc. or Ph.D.? Which year? What do you want to get out of the course? CMPT 843 - 2019 SPRING - SFU 2 Course Introduction CMPT 843 - 2019 SPRING - SFU 3 Why this course? Objective 1. Stand on the shoulders of giants! ◦ A Half Century DB Research ◦ VLDB = Very Large Data Base (founded in 1975) ◦ Four Turing Awards ◦ $50 billion Market Per Year Objective 2. Master essential skills for being a researcher ◦ Reading Papers ◦ Giving Talks ◦ Reviewing Papers ◦ Asking Questions CMPT 843 - 2019 SPRING - SFU 4 Prerequisites Undergraduate Database Systems Courses ◦ Testing yourself: Relational Model, SQL, Query Optimization, Transaction, Concurrency Control, ACID, etc. If not, you have to spend extra time on ◦ Textbook: “Database Management Systems” ◦ Online Courses: Stanford, Berkeley CMPT 843 - 2019 SPRING - SFU 5 Part 1: Traditional Database Systems and Techniques (20 papers) 39 papers Part 2: Modern Database Systems and Techniques (18 papers) CMPT 843 - 2019 SPRING - SFU 6 Part 1: Traditional Database Systems and Techniques (before 2000) CMPT 843 - 2019 SPRING - SFU 7 Part 1: Traditional Database Systems and Techniques (before 2000) CMPT 843 - 2019 SPRING - SFU 8 Part 1: Traditional Database Systems and Techniques (before 2000) CMPT 843 - 2019 SPRING - SFU 9 Part 1: Traditional Database Systems and Techniques (before 2000) CMPT 843 - 2019
    [Show full text]
  • Network Model
    APPENDIX A Network Model In the relational model, the data and the relationships among data are represented by a collection of tables. The network model differs from the relational model in that data are represented by collections of records, and relationships among data are rep- resented by links. A.1 Basic Concepts A network database consists of a collection of records connected to one another through links. A record is in many respects similar to an entity in the E-R model. Each record is a collection of fields (attributes), each of which contains only one data value. A link is an association between precisely two records. Thus, a link can be viewed as a restricted (binary) form of relationship in the sense of the E-R model. As an illustration, consider a database representing a customer-account relationship in a banking system. There are two record types, customer and account.Aswesaw earlier, we can define the customer record type, using Pascal-like notation: type customer = record customer-name: string; customer-street: string; customer-city: string; end The account record type can be defined as type account = record account-number:strinstring; balance: integer; end 1 2 Appendix A Network Model Hayes Main Harrison A-102 400 A-101 500 Johnson Alma Palo Alto A-201 900 Turner Putnam Stamford A-305 350 Figure A.1 Sample database. The sample database in Figure A.1 shows that Hayes has account A-102, Johnson has accounts A-101 and A-201, and Turner has account A-305. A.2 Data-Structure Diagrams A data-structure diagram is a schema representing the design of a network database.
    [Show full text]