General systems theory: Which of the following is NOT a typical characteristic of a system?

Introduction / Context:
A system is a set of components that interact to achieve a purpose. Understanding core characteristics helps analysts model organizations, software, and processes effectively. Many systems contain diverse parts with different roles; homogeneity is not a requirement and often not true in practice.

Given Data / Assumptions:

• Systems are purposeful and bounded.
• Components interact and depend on each other.
• Components are often specialized, not identical.

Concept / Approach:
Key properties include purpose, boundary, environment, inputs, outputs, feedback, and interdependent components. Heterogeneity enables division of labor: in computing, CPU, memory, storage, and network cards play distinct roles; in organizations, departments specialize (finance, operations, marketing). Therefore, “has homogeneous components” is not a defining characteristic. Many successful systems rely on diversity for resilience and performance.

Step-by-Step Solution:

Verification / Alternative check:
Systems literature and modeling approaches (for example, UML, enterprise architecture) depict heterogeneous components collaborating through interfaces and feedback loops.

Why Other Options Are Wrong:

• Purpose/objective: central to system identity.
• Interacting components: define systemic behavior.
• Boundary: distinguishes system from environment and defines scope.

Common Pitfalls:
Assuming uniform components simplify design; over-uniformity can reduce adaptability and specialization benefits.

Final Answer:
Has homogeneous (identical) components