Chapter 5: General Systems Theory, Cybernetics and Complexity

1. Introduction

Information technology is often described in terms of hardware, software, data, networks and users. Such descriptions are necessary, but they are insufficient for understanding the behavior of contemporary digital environments. A cloud platform is not merely a collection of servers; it is an operational system involving software, infrastructure, organizations, suppliers, policies, users and regulatory constraints. Similarly, an artificial-intelligence service is not only an algorithm. Its outputs depend on data, organizational objectives, human interpretation, feedback, incentives and the social context in which it is deployed.

Systems thinking provides a conceptual foundation for examining these relationships. General Systems Theory focuses on common patterns across biological, technical, organizational and social systems. Cybernetics examines communication, control, regulation and feedback. Complexity theory investigates nonlinear interactions, emergence, adaptation, uncertainty and the behavior of systems that cannot be fully understood by analyzing isolated components.

For doctoral-level information-technology research and practice, these perspectives are particularly important because digital systems are increasingly interconnected, autonomous and socio-technical. A change to an application may affect security, privacy, business processes, employee behavior and public trust. The central task is therefore not simply to optimize components, but to understand relationships, boundaries, feedback loops, system purposes and unintended consequences.

2. Learning Objectives

By the end of this chapter, learners should be able to:

1. Explain the foundations and intellectual development of General Systems Theory, cybernetics and complexity theory.

2. Distinguish systems, components, environments, boundaries, hierarchies and networks.

3. Analyze positive and negative feedback, control, communication and adaptation in technical and organizational settings.

4. Apply concepts of emergence, nonlinearity, resilience and self-organization to socio-technical systems.

5. Critically evaluate systems models, including their assumptions, limitations and ethical implications.

6. Design system interventions that account for uncertainty, stakeholder interests and unintended effects.

7. Assess the strategic importance of systems thinking for digital transformation, governance and innovation.

3. Meaning and Concept

A system is an organized set of interacting elements that forms a coherent whole and performs, or is intended to perform, one or more functions. The elements may be physical objects, people, rules, information, processes or ideas. A system is identified not only by its parts but also by the relationships among those parts and by the purpose attributed to the whole.

General Systems Theory, associated particularly with Ludwig von Bertalanffy, argues that similar structural principles can be found in different domains. Open systems exchange matter, energy or information with their environments. They maintain relative stability through regulation while also changing over time. The theory challenges reductionism when reductionism assumes that the behavior of a whole can be explained completely by studying isolated parts.

Cybernetics, developed through the work of scholars such as Norbert Wiener, studies control and communication in animals, machines and organizations. Its central concern is how a system compares actual conditions with desired conditions and uses information to reduce discrepancies. A thermostat is a simple example: it measures temperature, compares it with a set point and activates heating or cooling. In organizational and digital settings, the same logic may involve performance indicators, monitoring systems, escalation procedures and corrective action.

Complexity theory examines systems composed of many interacting elements whose collective behavior is difficult to predict from individual behavior. Complexity does not simply mean that a system has many parts. A complex system also tends to exhibit nonlinearity, adaptation, path dependence, emergence and sensitivity to context. A small change can sometimes have a large effect, while a major intervention may produce little visible change.

Systems thinking is therefore a way of seeing and investigating. It asks: What is the system of interest? What is outside its boundary? Which actors and processes interact? What feedback loops sustain or destabilize behavior? What patterns emerge over time? Who defines the system’s purpose, and who benefits or bears the costs?

4. Fundamental Principles

4.1 Wholeness and relationship

A system has properties that arise from relationships among its elements. Removing or redesigning one component may change the behavior of other components. In an information system, a database, interface and business process may each function adequately in isolation but fail when their assumptions are inconsistent.

4.2 Openness and environmental dependence

Most real information and organizational systems are open systems. They receive inputs, transform them and produce outputs while exchanging information, resources and influence with their environments. A cybersecurity program, for example, is affected by attackers, suppliers, laws, employee practices, technologies and public expectations.

4.3 Boundaries and perspective

A system boundary defines what is included in analysis. Boundaries are analytical choices rather than purely objective facts. A project manager may define a system as a software team, whereas a privacy researcher may include data subjects, third-party platforms and regulators. Narrow boundaries can simplify analysis but may hide important causes and consequences.

4.4 Hierarchy and levels

Systems often contain subsystems and belong to larger systems. An application may be part of a digital service, which is part of an organizational process, which is part of an industry ecosystem. Hierarchical analysis helps identify where decisions are made and how constraints at one level influence behavior at another.

4.5 Feedback and circular causality

In linear reasoning, cause precedes effect in a one-directional chain. Systems thinking recognizes circular causality: an action changes conditions, changed conditions influence subsequent action, and the cycle continues. Feedback may stabilize behavior or amplify it.

4.6 Equifinality and multifinality

Equifinality means that different starting conditions or paths can produce similar outcomes. Different organizations may achieve reliable service through different architectures. Multifinality means that similar initial conditions can produce different outcomes because of context, interpretation and interaction.

4.7 Emergence

Emergent properties arise from interactions and are not located in any single component. Organizational culture, market confidence, traffic congestion and online misinformation are examples. Emergence means that system-level outcomes require attention to patterns of interaction rather than only to component quality.

4.8 Adaptation and learning

Adaptive systems modify behavior in response to experience or environmental change. Machine-learning systems adapt through data and retraining; organizations adapt through learning, policy revision and experimentation. Adaptation can improve fitness, but it can also reproduce bias or create new risks.

4.9 Nonlinearity and uncertainty

Nonlinear systems do not respond proportionally to inputs. A small configuration error may cause a major outage, while a large investment may yield little improvement if a structural bottleneck remains. Complexity therefore requires scenario thinking, monitoring and iterative intervention rather than confidence in precise long-term prediction.

4.10 Resilience and viability

Resilience is the capacity to absorb disturbance, continue essential functions, recover and, where appropriate, transform. Viability concerns the capacity of a system to remain capable of operating under changing conditions. Resilience is not identical to resistance: a resilient system may bend, degrade temporarily, learn and reorganize rather than remain unchanged.

5. Major Components / Elements

A systems analysis commonly identifies the following elements:

• Purpose: the function, value or outcome the system is intended to achieve.
• Elements: people, technologies, resources, rules and information.
• Relationships: dependencies, communication channels, authority structures and workflows.
• Inputs: resources, data, requests, energy or disturbances entering the system.
• Transformations: processes that convert inputs into outputs.
• Outputs: services, decisions, products, information or consequences.
• Environment: conditions and actors outside the selected boundary.
• Boundary: the analytical distinction between system and environment.
• Feedback mechanisms: information about performance or effects that influences later action.
• Controls: policies, procedures, technical safeguards and managerial interventions.
• State: the system’s condition at a particular time.
• Trajectories: patterns of change through time.
• Stakeholders: actors who affect or are affected by the system.

These elements should not be treated as a simple checklist. Their significance lies in how they interact. A performance metric, for example, is not neutral: it can alter employee incentives and therefore change the behavior being measured.

6. Process / Framework / Methodology

A practical systems inquiry can be organized into the following stages.

Stage 1: Define the system of interest

State the problem and purpose without prematurely assuming the solution. “Slow customer service” may be a more useful starting point than “the service needs a new application.”

Stage 2: Identify stakeholders and perspectives

Map users, operators, managers, suppliers, regulators, communities and indirectly affected groups. Record differences in goals, authority, knowledge and exposure to risk.

Stage 3: Establish boundaries and levels

Specify what is included and excluded. Examine the system at multiple levels, such as individual interaction, team process, organizational governance and external ecosystem.

Stage 4: Map structure and behavior

Use rich pictures, stakeholder maps, process models, causal-loop diagrams, stock-and-flow models, architecture diagrams or event logs. Compare the formal process with actual practice.

Stage 5: Identify feedback and delays

Ask what information is measured, who receives it, how quickly it arrives and what actions it triggers. Delays often explain why corrective action arrives too late or why a policy produces oscillation.

Stage 6: Analyze risks, resilience and failure modes

Consider single points of failure, hidden dependencies, cascading effects, adaptive responses and recovery capability. Analyze not only component failure but also coordination failure.

Stage 7: Develop and test interventions

Prefer interventions that address structural causes. Use prototypes, simulations, tabletop exercises, pilot deployments and red-team testing. Evaluate direct results and second-order effects.

Stage 8: Monitor, learn and revise

Treat implementation as an ongoing learning process. Establish indicators for service quality, safety, equity, privacy, reliability and unintended outcomes. Revise the model as evidence changes.

7. Important Theories and Models

7.1 General Systems Theory

General Systems Theory emphasizes openness, interdependence, hierarchy, equifinality and system-environment relationships. It is valuable for preventing narrow technical analysis, but its broadness can make empirical testing difficult unless concepts are operationalized carefully.

7.2 First- and second-order cybernetics

First-order cybernetics studies observed systems, control mechanisms and feedback. Second-order cybernetics includes the observer in the analysis. The analyst’s categories, measurements and interventions influence what is seen and how the system responds. This is particularly relevant in organizational research, where a new performance dashboard may change behavior rather than simply report it.

7.3 The viable system model

Stafford Beer’s Viable System Model describes the functions required for an organization to remain viable: operational units, coordination, monitoring, development and policy. It distinguishes immediate operational control from functions that interpret environmental change and establish identity. The model helps diagnose organizations that are efficient in routine work but unable to adapt strategically.

7.4 The cybernetic control loop

A basic control loop consists of a desired state, sensors, a comparator, an actuator and a controlled process. Control quality depends on measurement accuracy, response time, authority to act and the stability of the process. Excessive control can create rigidity, while insufficient control can permit drift.

7.5 Causal-loop diagrams

Causal-loop diagrams represent reinforcing and balancing feedback. A reinforcing loop may describe how better service increases trust, which increases usage, generating revenue for further improvement. A balancing loop may show how capacity constraints eventually reduce service quality and user satisfaction. Such diagrams clarify circular relationships but do not by themselves establish empirical causality.

7.6 Complexity and adaptive systems

Complex adaptive systems contain agents that follow local rules, learn and respond to one another. Collective patterns emerge without central design. Open-source communities, financial markets, digital platforms and cyber-threat ecosystems exhibit this character. Management should therefore combine direction with conditions that support safe experimentation and rapid learning.

7.7 The Cynefin framework

The Cynefin framework distinguishes contexts in which relationships are obvious, complicated, complex, chaotic or confused. In an obvious context, established procedures may be appropriate. In a complicated context, expert analysis is useful. In a complex context, leaders should probe, observe and respond. In a chaotic context, immediate action is required to create stability before deeper analysis.

8. Practical Applications

Systems concepts support enterprise architecture, requirements analysis, cybersecurity, service management, digital transformation, public administration and organizational change. In requirements engineering, stakeholders may define success differently, and requirements can conflict across levels. Systems thinking reveals that a technically correct feature may reduce usability or increase operational workload.

In cybersecurity, defensive measures and attacker behavior form an adaptive system. A stricter authentication policy may reduce unauthorized access but also increase workarounds, shared credentials or support requests. Effective security therefore combines technical controls with usable processes, feedback and continuous learning.

In digital transformation, replacing a legacy application without changing incentives, governance or skills often produces disappointing results. Transformation is a system intervention, not merely a technology installation. Leaders must examine decision rights, data ownership, process dependencies, supplier relationships and organizational identity.

In project management, a schedule pressure may lead to reduced testing, which produces defects, rework and further delay. This is a reinforcing loop. Adding staff may not solve the problem if onboarding increases coordination demands. A systems approach seeks leverage points, such as stabilizing requirements, automating tests or changing release practices.

9. Examples

A university learning platform can be analyzed as a socio-technical system. Its components include software, identity management, instructors, students, support teams, policies and content. A platform outage affects teaching, assessment and institutional reputation. If administrators measure only uptime, they may miss accessibility problems, confusing workflows and inequitable effects on students with limited connectivity.

A hospital information system illustrates hierarchy and emergence. A medication-ordering interface, clinical workflow, staffing levels and alert policies interact. Excessive alerts may produce alert fatigue, which reduces attention to important warnings. The problem is not necessarily a defective alert mechanism alone; it is an emergent result of design, workload, clinical practice and governance.

An online marketplace demonstrates network effects. More sellers attract more buyers, and more buyers attract sellers. This reinforcing loop can accelerate growth. However, fraud, misinformation or poor service can also spread through network interaction. Platform governance must therefore address both growth and systemic trust.

10. Technology and Digital Applications

Systems thinking is directly relevant to cloud computing, distributed systems, artificial intelligence, Internet of Things environments and digital platforms. In distributed computing, no single component may possess a complete view of system state. Delays, partial failure and inconsistent information require explicit consideration of observability, fault tolerance and graceful degradation.

In artificial intelligence, the model is embedded in a data and decision system. Training data, labeling practices, deployment context, user feedback and organizational incentives affect outcomes. A model can become less reliable when users adapt strategically to it or when the environment changes. Monitoring should therefore include data drift, performance across groups, human override patterns and downstream effects.

Internet of Things systems create feedback between digital measurements and physical environments. Smart energy systems may alter consumption through dynamic pricing, while sensors introduce privacy and security risks. Digital twins and simulation can support scenario analysis, but their conclusions depend on model assumptions and data quality.

DevOps and site reliability engineering apply cybernetic principles through continuous monitoring, automated deployment, incident feedback and service-level objectives. These practices can improve resilience when combined with disciplined change management, capacity planning and learning-oriented incident reviews.

11. Strategic / Managerial Importance

For managers, systems thinking changes the question from “Who caused the failure?” to “What conditions and interactions made this failure likely?” This does not eliminate accountability; it improves the quality of accountability by distinguishing individual negligence from structural design problems.

Strategic decisions should consider interdependencies, time delays and second-order consequences. An organization that optimizes departmental productivity may increase total cycle time if work is transferred between departments. A procurement decision that minimizes immediate cost may increase long-term dependency on a fragile supplier.

Systems thinking also supports portfolio governance. Technology investments should be assessed against capabilities, architecture, skills, risk appetite, regulatory obligations and organizational purpose. The goal is not maximum complexity or maximum control, but an appropriate balance between efficiency, adaptability and resilience.

12. Detailed Case Study

Background

The following is a fictional case for illustration. Meridian Municipal Services operates a digital platform through which residents request waste collection, report street problems and receive service updates. The platform includes a mobile application, call center, contractor systems and municipal databases.

Problem

After a major application upgrade, reported service delays increased. Management initially concluded that the contractor was underperforming. Residents submitted duplicate requests because status information was delayed, while call-center staff created additional records to respond to complaints. The resulting volume overloaded dispatch teams.

Analysis

A narrow analysis focused on contractor completion rates. A systems analysis mapped the entire service. The upgrade had changed data formats, creating delays in synchronizing contractor updates. The public interface displayed “request received” for several days, encouraging repeated submissions. Managers evaluated the call center by average handling time, so staff closed interactions quickly rather than resolving root causes. These actions reinforced demand and obscured the actual backlog.

The system contained several feedback loops. Delayed status information increased uncertainty; uncertainty increased duplicate requests; duplicates increased workload; workload further delayed updates. A balancing response—adding temporary staff—provided limited relief because the data synchronization defect remained. The system boundary had also excluded the contractor’s scheduling software, despite its critical role.

Strategy / Solution

Meridian established a cross-organizational service team including residents, call-center staff, municipal IT, dispatchers and the contractor. It corrected the synchronization interface and introduced explicit status states with expected response times. Duplicate requests were linked rather than processed independently. Performance measures were revised to include end-to-end resolution, repeat contact and data quality rather than only handling speed.

The team introduced daily operational dashboards, weekly review of failure patterns and a monthly resilience exercise. It also created a change-impact assessment requiring business-process, accessibility, privacy and supplier review before major releases.

Outcome

Within three months, duplicate requests declined substantially, status accuracy improved and the backlog became visible. Service completion performance improved more slowly because capacity constraints remained, but managers could now distinguish demand problems from data problems. The platform became easier to govern because responsibility and feedback paths were explicit.

Learning Points

The case illustrates that system performance is produced by interactions across technical and organizational boundaries. Local optimization can worsen total performance. Reliable digital services require shared measures, timely feedback, inclusive boundary definition and iterative learning. Most importantly, the correct intervention was not simply to add resources; it was to change the structure generating avoidable demand.

13. Advantages / Benefits

Systems thinking provides a holistic view, reveals hidden dependencies and supports analysis of unintended consequences. It improves cross-functional communication because stakeholders can discuss relationships rather than defend isolated departments. Cybernetic monitoring supports early detection of drift, while complexity perspectives encourage experimentation and adaptation. These approaches are useful for resilience planning, digital governance, service design and responsible innovation.

14. Limitations / Challenges

Systems models can become excessively broad and difficult to validate. Defining boundaries involves judgment and may reflect the interests of powerful stakeholders. Causal-loop diagrams can create an appearance of rigor without adequate evidence. Complexity does not excuse weak planning or prevent all prediction; many systems contain both predictable and uncertain domains.

Systems thinking may also be difficult to implement in organizations structured around departments, budgets and short-term performance targets. Data may be incomplete, incompatible or politically contested. Cross-system interventions can require authority that no single manager possesses. Finally, a model may identify systemic causes without providing an easy solution, particularly where values and interests conflict.

15. Ethical and Governance Considerations

System boundaries determine whose interests are visible. Analysts should include marginalized and indirectly affected stakeholders, not only those who control budgets. Data collection and monitoring must respect privacy, proportionality, consent and legitimate purpose. Automated feedback systems should be evaluated for discrimination, manipulation and exclusion.

Governance should clarify accountability when decisions are distributed among algorithms, operators, suppliers and managers. Resilience measures must not become justification for unnecessary surveillance or permanent emergency powers. Transparency requires communicating model assumptions, uncertainty and limitations. Ethical systems design also considers accessibility, environmental impact, labor effects and the possibility that optimization for one group may impose costs on another.

16. Current and Emerging Trends

Important developments include autonomous and adaptive AI systems, algorithmic ecosystems, digital twins, cyber-physical infrastructure, platform governance and climate-resilient digital services. These developments increase the importance of continuous monitoring because system behavior may change after deployment.

Organizations are also moving toward resilience engineering, which studies how normal work succeeds under variable conditions rather than examining only failures. Observability platforms increasingly combine technical telemetry with business and user signals. Federated and decentralized architectures seek to reduce concentration risk, although they may create new coordination and governance challenges.

17. Best Practices

1. Define the system purpose and boundary explicitly, then revisit both as evidence develops.

2. Include technical, organizational, human and environmental factors.

3. Map dependencies, feedback loops, delays and failure cascades.

4. Distinguish indicators from actual outcomes; avoid optimizing proxies blindly.

5. Use multiple perspectives and involve affected stakeholders.

6. Design for graceful degradation, recovery and learning, not only prevention.

7. Combine quantitative data with qualitative inquiry and operational experience.

8. Test interventions through pilots, simulations and adversarial review.

9. Monitor second-order effects and revise assumptions.

10. Align governance, incentives and accountability with the system’s real structure.

18. Future Scope

Future research will need to address systems that combine human agents, autonomous software, physical infrastructure and ecological constraints. Key questions concern how to govern adaptive algorithms, how to verify emergent behavior, how to measure resilience and how to preserve human agency in increasingly automated environments.

Doctoral research can contribute by developing better methods for boundary critique, causal inference in complex systems, socio-technical simulation, responsible AI monitoring and resilience metrics. Interdisciplinary collaboration will be essential because no single technical discipline can adequately represent the social, economic and ethical dimensions of digital systems.

19. Chapter Summary

General Systems Theory explains systems as wholes composed of interdependent elements in relationship with environments. Cybernetics emphasizes communication, control and feedback. Complexity theory addresses emergence, nonlinearity, adaptation, self-organization and uncertainty. Together, these perspectives provide a rigorous foundation for analyzing technical, organizational and socio-technical systems.

Effective systems analysis defines purpose and boundaries, identifies stakeholders and levels, maps feedback and delays, examines resilience and tests interventions iteratively. The approach improves strategic decision-making but requires careful attention to evidence, ethics, power and model limitations. In information technology, systems thinking is indispensable because digital services are embedded in wider organizational and social arrangements.

20. Key Terms

1. System: An organized set of interacting elements forming a functional whole.

2. Systems thinking: Analysis focused on relationships, patterns, boundaries and wholes.

3. General Systems Theory: A theory identifying common principles across different systems.

4. Cybernetics: The study of control, communication and feedback in systems.

5. Complex adaptive system: A system whose interacting agents learn and adapt.

6. Boundary: The analytical distinction between a system and its environment.

7. Hierarchy: Arrangement of systems, subsystems and superordinate systems.

8. Feedback: Information about effects that influences subsequent action.

9. Reinforcing loop: Feedback that amplifies change.

10. Balancing loop: Feedback that counteracts change and promotes stability.

11. Emergence: System-level behavior arising from interactions among components.

12. Nonlinearity: A relationship in which effects are not proportional to inputs.

13. Adaptation: Adjustment of behavior or structure in response to conditions.

14. Resilience: Capacity to absorb disturbance, recover and continue or transform.

15. Viability: Capacity to remain capable of functioning over time.

16. Equifinality: Achievement of similar outcomes through different paths.

17. Open system: A system exchanging information, resources or influence with its environment.

18. Control loop: A process that measures conditions, compares them with goals and acts to reduce discrepancies.

21. Review Questions

Short Answer Questions

1. Define General Systems Theory and explain its relevance to information technology.

2. Distinguish reinforcing feedback from balancing feedback.

3. What is meant by an analytical system boundary?

4. Define emergence and provide one digital example.

5. Explain the difference between resilience and resistance.

Long Answer Questions

1. Critically compare General Systems Theory, cybernetics and complexity theory.

2. Explain how feedback, delays and measurement can influence organizational performance.

3. Discuss the role of systems thinking in cybersecurity governance.

4. Evaluate the usefulness and limitations of the Viable System Model for digital organizations.

5. Explain why digital transformation should be treated as a socio-technical systems intervention.

Analytical / Application Questions

1. Construct a causal-loop explanation for how poor service-status information can increase demand on a digital support service.

2. A machine-learning system performs well at deployment but deteriorates six months later. Analyze the problem using adaptation, feedback, environmental change and resilience concepts.

3. Select a large socio-technical system and propose an intervention. Identify its boundary, stakeholders, likely unintended effects and measures for evaluating success.

22. Multiple Choice Questions with Answers

Question 1

Which characteristic most clearly distinguishes a complex adaptive system from a merely complicated system?

A. It contains a large number of technical components.

B. Its agents interact, learn and alter behavior in response to one another.

C. It can be fully understood through detailed documentation.

D. It operates without any external inputs.

Correct Answer: B. Its agents interact, learn and alter behavior in response to one another.

Question 2

A service dashboard causes employees to prioritize easily measured tasks while neglecting important unmeasured work. Which systems concept best explains this effect?

A. Equifinality

B. Open-system exchange

C. Feedback changing the behavior being measured

D. Hierarchical decomposition

Correct Answer: C. Feedback changing the behavior being measured

Question 3

Which intervention is most likely to address a reinforcing loop in which delayed updates create duplicate customer requests?

A. Measure only average call duration.

B. Add a second reporting form for customers.

C. Improve status synchronization and link duplicate requests.

D. Exclude contractor systems from the analysis.

Correct Answer: C. Improve status synchronization and link duplicate requests.

Question 4

In cybernetics, the primary function of a comparator in a control loop is to:

A. Store historical data permanently.

B. Compare actual conditions with a desired state.

C. Replace all human decision-makers.

D. Increase system complexity.

Correct Answer: B. Compare actual conditions with a desired state.

Question 5

Why is defining a system boundary a substantive analytical decision rather than a neutral technical step?

A. Boundaries determine which actors, causes and consequences are considered.

B. Boundaries eliminate uncertainty from the system.

C. Boundaries always correspond to organizational departments.

D. Boundaries prevent feedback from occurring.

Correct Answer: A. Boundaries determine which actors, causes and consequences are considered.

Question 6

A small configuration change causes a major outage in a distributed service. This is most directly an example of:

A. Linearity

B. Nonlinearity and sensitivity to system conditions

C. Equifinality

D. Static equilibrium

Correct Answer: B. Nonlinearity and sensitivity to system conditions

Question 7

Which response best reflects resilience engineering?

A. Assume that failures can be eliminated through stricter procedures alone.

B. Focus only on assigning blame after an incident.

C. Design for graceful degradation, recovery and learning under disturbance.

D. Remove all system interdependencies regardless of cost.

Correct Answer: C. Design for graceful degradation, recovery and learning under disturbance.

Question 8

In a complex context under the Cynefin framework, an appropriate managerial approach is generally to:

A. Apply a fixed procedure without experimentation.

B. Probe, observe patterns and respond iteratively.

C. Wait until complete information is available.

D. Centralize every operational decision permanently.

Correct Answer: B. Probe, observe patterns and respond iteratively.

Question 9

Which example best illustrates emergence?

A. A server executes a programmed instruction.

B. A database stores a record in a specified field.

C. Platform trust develops from interactions among users, sellers and governance mechanisms.

D. A sensor reports a measured temperature.

Correct Answer: C. Platform trust develops from interactions among users, sellers and governance mechanisms.

Question 10

What is a major ethical risk of using narrow system boundaries in digital governance?

A. The system may become easier to document.

B. Indirectly affected or marginalized stakeholders may be excluded from consideration.

C. The organization may collect less irrelevant data.

D. Technical performance may become more measurable.

Correct Answer: B. Indirectly affected or marginalized stakeholders may be excluded from consideration.