Organizational Systems and Information Design

The Three Levels of Management

Information systems must be designed to meet the unique needs of different decision-makers. Management in an organization typically exists on three horizontal levels:

1. Operations Control: These managers oversee the day-to-day operating details of the organization. They make decisions based on predetermined rules that lead to predictable outcomes.
2. Managerial Planning and Control: Middle management focuses on short-term planning and resource allocation. Their decisions often sit at the intersection of operational and strategic needs.
3. Strategic Management: These leaders look outward toward the future and the external environment. They operate in highly uncertain environments and make the high-level decisions that guide the rest of the organization.

Exam Tip: When asked how information needs change across an organization, remember that as you move from Operations to Strategic management, the uncertainty of the environment increases, and the time horizon for decision-making lengthens.

Organizational Culture and Design

Beyond the formal hierarchy, the "personality" of an organization—its organizational culture—profoundly impacts how information systems are designed and used. Culture is expressed through both verbal and nonverbal symbolism:

• Verbal Symbolism: Includes myths, metaphors, visions, and even humor.
• Nonverbal Symbolism: Includes shared artifacts (like trophies), rites and rituals (such as promotions or birthdays), and even office placement or clothing.

Analysts must recognize these subcultures because a system that works for one department might fail in another if it clashes with the local culture.

Modern Organizational Structures: Virtual Organizations and ERP

As technology evolves, the physical boundaries of organizations are blurring.

Virtual Organizations use computer networks and communication technology to bring together "virtual teams" that may be located in different physical parts of the world. This offers benefits such as reduced facility costs, faster response to customers, and greater flexibility for employees to manage familial obligations.

To support these complex, interconnected structures, many organizations implement Enterprise Resource Planning (ERP) systems. An ERP is an integrated organizational information system—a suite of software designed to facilitate the seamless flow of information between all functional areas of the company.

Graphical Modeling of Systems

To understand and communicate how a system works, analysts use several graphical modeling techniques:

1. Context-Level Data Flow Diagrams (DFD)

A context-level DFD focuses on the high-level movement of data. It shows what data flows into the system, what data flows out, and how that data is processed.

2. Entity-Relationship (E-R) Models

While DFDs focus on flow, E-R models focus on the "things" (entities) within the system and how they relate to one another.

• Entities: Can be fundamental, associative, or attributive.
• Relationships: These define how entities connect, typically in three forms: one-to-one, one-to-many, or many-to-many.

3. Use Case Modeling

Use case modeling provides a logical model of what a system does without getting bogged down in the technical "how". It is highly effective for communicating with users because it captures "user stories".

A use case consists of three main components:

1. An Actor: A role played by a user (can be a primary actor who initiates an event, or a supporting actor who helps the system run).
2. An Event: The trigger that starts the use case.
3. The Use Case: The specific task or action performed.

Analysts often use Use Case Scenarios to provide a detailed description of the steps performed, including any conditions or assumptions.

Summary Table: Modeling Comparison