Database Fundamentals

Information Systems and Computer Systems

A database never lives alone: it is the shared memory of an information system. This lesson separates the organisation from its software, and shows why that distinction changes every design decision.

Beginner

Learning objectives

  • Define an information system and list its four components
  • Distinguish an information system from a computer system, and explain why the distinction matters
  • Describe the four functions of an information system: collection, storage, processing, distribution
  • Recognise the three decision levels and the information each one needs
  • Explain why a database is the shared memory of an information system, not the system itself

Prerequisites

  • Data and Information: the distinction between data, information and knowledge

Introduction

The previous lesson established that a database produces information from data. That sentence hides a question: information for whom, and for which decision?

Nobody builds a database for its own sake. A database exists because some organisation — a library, a hospital, a company, a school — must remember facts about the world and act on them. The set of people, rules, procedures and tools that allows that organisation to collect, keep and use those facts is called an information system. The database is only one of its parts: the part that remembers.

This lesson separates three things that beginners constantly confuse: the organisation and its information needs, the information system that serves those needs, and the computer system (hardware and software) that supports the information system. Getting this distinction wrong has a precise, measurable cost: it produces databases designed around the software of today instead of the organisation that must survive tomorrow.

What an information system is

Information system

An information system is the set of people, data, procedures and technologies that, working together, produces and distributes the information an organisation needs in order to operate and to take decisions.

Four components, none of them optional:

Component What it is Library example
Data The facts recorded about the world, with their rules Which copies exist, who borrowed them, which loans are overdue
Procedures The rules that say how data are collected, validated and used "A member may hold at most five loans"; "a loan lasts 30 days"
People Those who produce, maintain and consume the information Librarian, member, director, acquisition officer
Technologies The tools that make the work possible The database, the loan desk client, the report generator

Notice that only the last row is software. A library that keeps its loans on paper cards still has an information system: it is slower and more error-prone, but it collects, stores, processes and distributes information. When we computerise it we do not invent the information system — we replace one of its technologies.

Information system and computer system

Italian, Spanish and French force a distinction that English leaves implicit, and it is worth making explicit in every language:

Term Italian What it covers
Information system sistema informativo The whole organisation-level machinery that produces information: data, rules, people, tools — including paper and speech
Computer system sistema informatico Only the technological part: hardware, software, networks, databases

The two overlap but neither contains the other:

  • A hospital without any software has an information system (forms, protocols, phone calls) and no computer system.
  • A laptop running a video game is a computer system that serves no organisational information need, so it is not an information system in the sense used here.
  • A company with an excellent ERP and no procedures to feed it has a computer system and a broken information system.

The consequence for database design is direct and non-negotiable: the information system is the specification, the computer system is the implementation. Requirements come from the first, constraints (performance, storage, concurrency) come from the second. Module 2 will show how to extract the former; Modules 5 to 8 will show how to satisfy the latter.

The four functions

Every information system, whatever its technology, performs the same four functions. Naming them is useful because each one becomes a concrete responsibility of the database.

1. Collection

Facts enter the system: a loan is registered, a new copy is catalogued, a member enrols. Collection is where most data quality is decided, because it is the only moment in which the person who knows the truth is present.

Two properties are decided here:

  • Completeness: does the system capture everything it will later need? A loan without the due date cannot be checked for lateness later.
  • Correctness at the source: a value typed wrongly is expensive to repair afterwards; a value rejected on entry costs nothing.

2. Storage

Facts are kept, in a form that survives the end of the session, the failure of a disk, and the passage of years. Storage raises questions that are not about meaning but about engineering: how much space, how fast, how many simultaneous users, how to recover after a crash.

Persistence

Persistence is the property of data that outlive the process that created them. A variable in memory disappears when the program ends; a row in a database does not.

3. Processing

Facts are transformed into information: aggregated, filtered, compared, joined, summarised. Processing is where the difference between data and information becomes visible — the same stored rows produce "3 loans are overdue" for the librarian and "the average loan duration fell by 12% this year" for the director.

4. Distribution

Information reaches whoever needs it, in the form and at the time in which it is useful: a screen at the loan desk, a monthly PDF, a notification, an API response. Distribution is the function most often forgotten during design, and the one that most often forces a redesign: a database that cannot answer a question in an acceptable time has failed to distribute.

Three levels of decision, one database

The same organisation takes decisions at three levels, and each level consumes information of a different kind.

Level Who Time horizon Typical question Information needed
Operational Clerk, librarian Minutes, hours "Is this copy available?" One row, exact, current
Tactical Section head Weeks, months "Which sections are understaffed on Saturdays?" Aggregates over periods
Strategic Director Years "Should we open a second branch?" Trends, comparisons, forecasts

Three consequences follow, and they are the reason this lesson exists:

  1. The data are the same, the questions are not. The loan registered at the desk is also the row counted by the tactical report and the trend analysed by the director. Designing three separate stores for the three levels produces three versions of the truth.
  2. Operational data must be exact and current; strategic data must be comparable over time. These are different requirements, and the second is the reason why a well designed database rarely deletes rows: it marks them, so that history remains comparable.
  3. A database that serves only the operational level becomes a data cemetery: full of correct rows that nobody can turn into a decision.

The database as shared memory

Put the pieces together. An information system needs a memory that is:

  • shared — several procedures and several people read and write the same facts;
  • consistent — the same fact must not have two versions;
  • persistent — it must survive the end of the process;
  • controlled — access must follow the rules of the organisation, not the goodwill of the programs.

A file owned by a single program satisfies none of these properties once a second program needs the same fact. That is exactly the situation the next lesson analyses: the age of traditional file archives, where every application kept its own files and the organisation paid the price in redundancy, inconsistency and duplicated work.

A worked example: the library

Take a small municipal library and describe it as an information system, not as software.

People. The librarian at the desk, the member, the director, the acquisition officer.

Procedures.

  • A member may hold at most five loans at a time.
  • A loan lasts 30 days and can be renewed once, unless the copy has been reserved.
  • A copy that is lost is charged to the member at the replacement price.
  • New acquisitions must be approved by the director above 500 euros.

Data. Members, books (works), copies (physical items), loans, reservations, suppliers, orders.

Technologies. The database, the desk client, the label printer, the e-mail service.

Now observe what each of the four functions asks of the database:

Function Concrete requirement Consequence on the model
Collection Register a loan with member, copy, date and due date The due date is derivable from the loan date + 30 days, but it must be stored: the rule may change
Storage Keep ten years of loan history Loans are never deleted, only closed
Processing "How many loans are overdue today?" The due date must be indexed and comparable
Distribution Monthly report by section Loans must be linkable to the section of the work

Notice that no requirement mentions screens, and that every requirement constrains the conceptual schema. This is precisely how Module 2 will proceed: from sentences about the organisation to a list of entities, attributes and rules.

Beginner

Classify the components

A school uses a register app on tablets. The app stores marks and absences; teachers enter them during the lesson; the school secretary prints report cards at the end of each term; a regional office asks for aggregated statistics once a year.

For each of the following items, say whether it belongs to the information system, to the computer system, or to both:

  1. The rule "a mark is an integer from 1 to 10".
  2. The tablet application.
  3. The teacher who decides which mark to enter.
  4. The annual statistics requested by the regional office.
  5. The database table that stores the marks.
Show the commented solution
  1. Information system. It is a procedure — a constraint on the data. It exists whether or not software exists; a paper register would obey the same rule. In the database it will become a CHECK constraint (Module 7).

  2. Computer system (and therefore also a technology of the information system). It is a tool, replaceable without changing the rules.

  3. Information system. People are one of the four components; the decision of which mark to record is not delegable to software.

  4. Information system, and specifically the distribution and processing functions. It is an information need of an actor, not a technology. Note that it imposes a requirement on the model: marks must be linkable to a class, a subject and a period, otherwise the annual statistics cannot be produced.

  5. Both. It is a technological artefact (computer system) that implements a storage procedure (information system). The table is where the two worlds meet, which is why a badly designed table can satisfy the software and betray the organisation.

What this exercise teaches. The distinction is not academic bookkeeping: each answer tells you where the requirement comes from. Requirements 1, 3 and 4 come from the organisation and must be modelled; requirement 2 is a replaceable implementation detail; requirement 5 is the point where a modelling decision becomes a physical object — and the only one you can change later without asking anyone's permission.

Common mistakes

  • "The information system is the software." It is the most frequent mistake, and it produces databases shaped like the current application. When the application is replaced — and it will be — the data are stranded.
  • "The database is the information system." The database is the memory. Procedures, people and distribution channels are outside it, and a design that ignores them will be blamed on the database.
  • Designing for one level of decision. A model that answers only the operational questions becomes a data cemetery; a model built only for reports cannot enforce the rules of daily work.
  • Confusing sistema informativo with sistema informatico. In Italian the two words differ by three letters and by everything else. In English the ambiguity is hidden: say "information system" only when you mean the organisation-level machinery.
  • Treating distribution as an afterthought. If a question must be answered in 200 ms at the desk, that is a design constraint, not a performance tuning task for later.

Summary

  • An information system is the set of people, data, procedures and technologies that produce and distribute the information an organisation needs.
  • A computer system is only its technological part; the information system is the specification, the computer system the implementation.
  • Every information system performs four functions: collection, storage, processing, distribution.
  • Three decision levels — operational, tactical, strategic — consume the same data with different needs; one shared store serves all three, three stores produce three truths.
  • A database is the shared, consistent, persistent and controlled memory of the information system.
  • Requirements come from the organisation; performance, storage and concurrency come from the technology. Confusing the two produces models that are either unimplementable or obsolete.

Verification questions

Try to answer before opening the solution: writing the answer is what makes the difference.

  1. Why is a paper-based register still an information system, while a video game is not?
  2. Give an example, for the library, of a requirement that belongs to the procedures and one that belongs to the technologies.
  3. A database answers the librarian's question in 20 ms and the director's report in four hours. Which function of the information system is failing?
  4. Why is designing from the current screens dangerous?
  5. Explain in one sentence why the three decision levels must share one database.
Show the answers
  1. Because it performs the four functions — collection, storage, processing, distribution — with people and paper instead of software. The video game produces no information for an organisational decision, so it lacks the "for whom" that defines the system.

  2. Procedure: "a loan lasts 30 days and can be renewed once". Technology: "the desk client must print a receipt on the thermal printer". The first constrains the model (a due date must be stored); the second does not.

  3. Distribution — and possibly processing. The data are there and the operational query is fast, but the information does not reach the director in a usable time. The fix may be an index, a summary table or a periodic extraction; the important point is that it is a design problem, not a bug.

  4. Because screens encode the procedures of the past, including the compromises the organisation wants to eliminate. They are an input to the analysis, not its specification.

  5. Because the loan registered at the desk is the same fact counted by the tactical report and analysed by the director; separate stores would produce different versions of the same truth.

Where to go next

Related lessons