Presentation is loading. Please wait.

Presentation is loading. Please wait.

+ A brief history of data and databases Spanning thousands and thousands of years Unattributed pictures from University of Rochester History SiteUniversity.

Similar presentations


Presentation on theme: "+ A brief history of data and databases Spanning thousands and thousands of years Unattributed pictures from University of Rochester History SiteUniversity."— Presentation transcript:

1 + A brief history of data and databases Spanning thousands and thousands of years Unattributed pictures from University of Rochester History SiteUniversity of Rochester History Site

2 + Teams – getting to know you Your teams are actually forming a mini-company. Your job will be to implement an on-line database based application (TBD). You will need to do the work from the SRS through the final product including any training and technical documentation. Today, you are meeting for the first time and need to organize the responsibilities. (These may change, but this will give you a first pass at primary responsibilities for the project tasks.) In your group, fill out the group worksheet indicating who will fulfill which roles. For all but the manager, you may identify 1 or 2 people. There can be only one manager.

3 + Roles to identify Team manager – will be responsible for organizing meetings, making sure minutes are taken (for tasks and deadlines), and keeping the group on task to meet the implementation deadlines. Interface designer – will be responsible for designing the user interface including the overall flow of the application. Programmer – will be responsible for the front end coding and connecting the front end user interface to the database. Database designer / implementer – will take primary responsibility for the design of the database and implementing and populating the database. Technical Writer – will take primary responsibility for all types of written documentation including SRS, design documents, and final user and technical documentation of the system.

4 + In your groups Come up with a company name Exchange contact information Make a case for the role(s) that you wish to serve on and get consensus among the group about who will do which roles. Fill out the company organizational worksheet. Consider where you feel you are the strongest and also where you feel the weakest among the strengths and weaknesses of the individual team members. About 20 minutes

5 + Record Keeping – How long? Source: http://www.ancientscripts.com/cuneiform.htmlhttp://www.ancientscripts.com/cuneiform.html picture - wikipedia

6 + Why? We use records to measure “stuff”. And most of these records are not digital.

7 + Jacquard Loom

8 From ancestry.com (1790 census, Pittsford, NY) Marriage book, Rochester, NY, chronological filing of marriage licenses.

9 + Card Catalogs

10 + It didn’t indicate whether the book was available, just where it should be found.(example cards)example Creating the cards required the expertise of librarians.

11 + Problem As the US Census Bureau approached the 1890 census it had a problem. 1880 census was concluded in 1887 and the population just kept growing. Needed to find a way to increase the efficiency of the census processing. Enter Herman Hollerith.Herman Hollerith

12 + Hollerith’s device pantographHollerith card Integrating machine

13 + First computers The program, the data, the JCL – all done with punchcards

14 + Electronic files – Early computing 1950s – 1970s Originally, files were associated with particular applications on particular computers. There were no generic programs (like Word or Excel). The computer and application software were customized for the different applications. Different kinds of data were in these different files. Integration of data was very difficult. Different uses of the data required program change. File storage was expensive and limited. File storage was primarily sequential (slow access)

15 + Enter the database – Early 1960s Objects in a database can be related to one another. Y Hierarchical – One record leads to the related record. (Like a tree) Network – Allowed for multiple relationships (like a network) The databases used pointers to relate one record to another.

16 + Charles Bachman BS in Mechanical Engineering from University of Pittsburg. His early work with Dow Chemical headed their Central Data Processing Unit and worked toward simplifying file processing and data retrieval in anticipation of a new IBM mainframe. Never was able to see his theory implemented. At GE, he created IDS or Integrated Data Store. Considered one of the first database management systems. (Now called IDMS). Included an Integrated Data Dictionary inside of the database itself. DBAs interacted with the IDD using a Data Dictionary Definition Language. (DDDL) Based on the CODASYL network model.

17 + Hierarchical IBMs DBMS, based on Bachman’s work, but implemented in a strictly hierarchical fashion. IMS or Information Management System. Still used in some network based systems.

18 + Some issues While an improvement over file based systems, These systems required knowledge of the structures to use them. No built in search mechanism. Very few users understood the structures, access limited to an elite few. Queries were complex. Took time to get new information and expensive programmer time to produce.

19 + Enter the relational DBMS 1970, Edgar Codd Relational DBMS Mathematician at IBM Based on Relational Calculus and set theory U of Michigam MicroDBMS IBM System R First implementation of SQL Led to Oracle IBM DB2 Informix Sybase MS SQL Server (based on Sybase)

20 + Relational Ideas Data is represented as a series of tables. The tables are Related to one another through a series of keys and foreign keys. A standard language is used to define the database (DDL) and to query the database (DML). Tables within the database contain the data about the database (meta data).

21 + Why relational? It is easy for most people to “see” and “get it”. Makes the data accessible for a wider number of users through user friendly query tools. Through good database design, space usage is efficient (although this has become less of an issue of late).

22 + The Future? Object Oriented Databases – Combine data and operations on those data – Allows for inheritance – Cache’ (Intersystems Corp) – Oracle (Object-Relational Database) – Postgre(open source) XML and XML DBMS – XML designed to transport and store data initially envisioned as moving data across the web (w3schools.com)w3schools.com – XML Database Management System manages that data

23 + Next up – modelling data and relational dbms terms


Download ppt "+ A brief history of data and databases Spanning thousands and thousands of years Unattributed pictures from University of Rochester History SiteUniversity."

Similar presentations


Ads by Google