Book Image

Turning Spreadsheets into Corporate Data

By : Bill Inmon
Book Image

Turning Spreadsheets into Corporate Data

By: Bill Inmon

Overview of this book

Spreadsheets are a popular way to store and communicate business data, but, although they are easy to create and update, they are not reliable enough to be used for making important corporate decisions. With this book, you can gain insight into how to maintain spreadsheets, how to format them, and then convert them into a database of reliable and useful information. Turning Spreadsheets into Corporate Data starts with a quick history of spreadsheet usage. You’ll learn the basics of formatting spreadsheets, including how to handle special characters and column headings, and how to convert the spreadsheet first into an intermediate database and then into corporate data. You will also learn how to utilize the mnemonic dictionary that is created along with the intermediate database. The later chapters discuss the immutability of data and the importance of organizational and political considerations during the data transformation. By the end of this book, you’ll have the skills and knowledge needed to convert your spreadsheets into reliable corporate data.
Table of Contents (16 chapters)
Free Chapter
1
Introduction
14
13: Case Study
15
Glossary
16
Index

1: Brief History of Spreadsheets

A long time ago, the IT department ran all aspects of corporate computing. Most computing was done on a large centralized computer. There was a computer budget. There were programmers and analysts. But in short order, this model began to fall apart. Programs, once written, needed to be maintained. End users needed to use a system that was never designed or built with them in mind. Development projects started to take years. The end user was asked to just “wait” until the new system was in place.

And the way systems were developed began to grow more complex and more Byzantine by the day. Users would submit requirements that never resulted in any systems being built. The frustration level grew and never got any better.

The end user was asked to submit his/her requirements into a development process that IT had concocted that could best be described as a labyrinth.