1
← Back to quizzesFree quiz
Enterprise Information Systems
Enterprise Information Systems (EIS) are the backbone of modern organizations, enabling the flow of data, support for decision‑making, and integration across functional areas. This course…
0 / 22
Score: 0%
2
In a multi‑level system informatico, which layer is primarily responsible for translating user actions into database commands?
3
A company wants to ensure that data updates from field sensors are reflected instantly in the central repository. Which processing mode best satisfies this requirement?
4
When classifying data as "dati di stato" versus "dati sugli eventi", which characteristic distinguishes the former?
5
A manager needs to compare budgeted versus actual expenses across multiple departments. Which decision‑support system type is most appropriate?
6
Which of the following best describes the main purpose of a Data Warehouse in an OLAP environment?
7
In the context of the DIKW pyramid, which transition represents the creation of actionable recommendations?
8
A firm wants to avoid data redundancy caused by "silos di dati". Which architectural strategy directly addresses this issue?
9
Which CRUD operation is performed when a new customer order is recorded in the system?
10
When a decision‑making process requires evaluating alternatives with known criteria but no unique selection rule, which decision type applies?
11
A retailer wants to segment customers based on purchase frequency and average basket size. Which analytical technique is most appropriate?
12
Which of the following best captures the distinction between OLTP and OLAP systems?
13
In a CRM system, which component is primarily responsible for aggregating interaction data from multiple channels into a single customer view?
14
Which of the following statements best reflects the role of a Decision Support System (DSS) in semi‑structured problems?
15
A company’s information system must guarantee that data is accessible "in the forms and times appropriate" while maintaining correctness. Which quality attribute does this describe?
16
Which of the following best explains why a “social CRM” (S‑CRM) differs from a traditional CRM?
17
When a firm adopts a “rightsizing” strategy, which of the following objectives is it primarily pursuing?
18
In the context of Big Data’s 4V model, which dimension addresses the challenge of data coming from heterogeneous sources?
19
A manager wants to drill down from yearly sales totals to monthly figures in a data cube. Which OLAP operation is being performed?
20
Which of the following best characterizes the difference between a Knowledge‑Driven DSS and a Model‑Driven DSS?
21
In a relational database, which schema design is most suitable for minimizing data redundancy while preserving query simplicity?
22
When applying TF‑IDF weighting, which term would receive the highest score in a corpus where it appears frequently in a single document but rarely elsewhere?
Understanding Enterprise Information Systems
Enterprise Information Systems (EIS) are the backbone of modern organizations, enabling the flow of data, support for decision‑making, and integration across functional areas. This course explores the core concepts that appear in typical certification quizzes, providing clear explanations, real‑world examples, and memory aids to help you master the material.
Why System Architectures Must Evolve
In a dynamic market, the primary driver for evolving an information system architecture is external market dynamics. Companies face shifting customer demands, emerging competitors, and rapid technological change. These forces compel organizations to redesign data models, adopt new platforms, and re‑engineer processes.
- Customer‑specific process changes are important but usually stem from broader market trends.
- Regulatory constraints affect compliance but are less volatile than market forces.
- Internal performance improvements are continuous but do not dictate major architectural shifts.
Memory tip: Think of the market as a storm that forces a ship (your system) to adjust its sails.
Multi‑Level System Architecture: Who Translates User Actions?
Enterprise systems are often organized into layers. The layer that converts user interactions into database commands is the application software layer. This layer sits above the base software and hardware, handling business logic, validation, and the generation of SQL or NoSQL statements.
- Base software provides core services (e.g., operating system, middleware).
- User interface captures input but does not directly issue database commands.
- Hardware layer executes the code but is unaware of business semantics.
Mnemonic: UI → APP → DB – the application sits in the middle, acting as the translator.
Real‑Time Processing vs. Batch and Interactive Modes
When field sensors must update a central repository instantly, the appropriate processing mode is real‑time. Real‑time systems ingest, process, and store data as soon as it arrives, ensuring that downstream applications always see the latest values.
- Batch (lot) processing accumulates data and processes it at scheduled intervals, introducing latency.
- Interactive (online) processing responds to user queries but does not guarantee continuous data propagation.
- Real‑time eliminates the delay, making it ideal for monitoring, control, and alerting scenarios.
How to remember: The letter R in “Real‑time” stands for Rapid – picture a river that never stops flowing.
State Data vs. Event Data
Data can be classified as state data ("dati di stato") or event data. State data describes the current condition of an entity and exhibits low variability. Typical examples include a customer’s name, birthdate, or a product’s static specifications.
- State data changes rarely; when it does, the change is usually a single, significant update.
- Event data captures each occurrence (e.g., a purchase, a sensor reading) and shows high variability over time.
Mnemonic: “Stato = Stabile, Sempre Tranquillo”. Visualize a portrait that stays the same versus a video that constantly evolves.
Decision‑Support Systems (DSS) Types
Managers often need to compare budgeted versus actual expenses across departments. The most suitable DSS for this task is a data‑driven DSS. These systems rely on large data repositories, perform queries, and generate reports that highlight variances.
- Communication‑driven DSS focuses on collaboration (e.g., groupware).
- Model‑driven DSS uses mathematical or simulation models.
- Knowledge‑driven DSS incorporates expert systems and rule‑based reasoning.
Remember: Data‑driven = Data‑heavy analysis of "what happened".
Purpose of a Data Warehouse in OLAP Environments
A Data Warehouse (DW) is designed to integrate and historize data from multiple sources. It consolidates operational, transactional, and external data into a single, subject‑oriented repository optimized for Online Analytical Processing (OLAP).
- It does not replace operational databases; rather, it complements them.
- DW provides a stable, read‑only environment for complex queries, trend analysis, and reporting.
- Historical data enables time‑series analysis, forecasting, and strategic planning.
Tip: Think of the DW as a “library” that stores the entire history of an organization, while operational systems are the “cash registers”.
DIKW Pyramid: From Knowledge to Wisdom
The DIKW hierarchy (Data → Information → Knowledge → Wisdom) illustrates how raw facts become actionable insight. The transition that creates actionable recommendations is the move from Knowledge to Wisdom. Knowledge represents contextualized understanding; wisdom adds judgment, enabling decision‑makers to act.
- Data: Raw symbols without meaning.
- Information: Processed data that answers "who, what, where".
- Knowledge: Interpreted information that answers "how".
- Wisdom: Insightful application of knowledge to answer "why" and guide action.
Memory cue: Wise people turn knowledge into action.
Eliminating Data Silos with Centralized ERP
Data silos—isolated departmental databases—lead to redundancy and inconsistent reporting. The architectural strategy that directly tackles this problem is adopting a centralized Enterprise Resource Planning (ERP) system. ERP integrates core processes (finance, HR, supply chain) into a unified platform, ensuring a single source of truth.
- Isolated databases increase maintenance overhead and hinder cross‑functional analytics.
- Centralized ERP provides standardized data models, real‑time sharing, and streamlined workflows.
- While ERP implementation is complex, the long‑term benefits include reduced duplication and improved decision‑making.
Recall strategy: Picture a single “hub” where all spokes (departments) connect—no more isolated islands.
Key Takeaways for Exam Success
- External market dynamics drive architectural change.
- The application software layer translates user actions into database commands.
- Real‑time processing guarantees immediate data propagation.
- State data is low‑variability and stable; event data is high‑variability.
- Data‑driven DSS is ideal for budget vs. actual comparisons.
- Data warehouses integrate and historize multi‑source data for OLAP.
- Wisdom in the DIKW pyramid represents actionable recommendations.
- Centralized ERP eliminates data silos and redundancy.
Use the mnemonics and visual analogies provided throughout this course to reinforce each concept. Consistent review and application to real‑world scenarios will boost both retention and practical competence.
