Beyond Objects

1991-09-30 · Source: cs.SE updates on arXiv.org · Field: Technology & Digital — Software Development & Engineering, Artificial Intelligence & Machine Learning · Depth: Expert, extended

Summary

A core principle of object orientation (OO), which partitions system functionality among objects corresponding to problem domain individuals, has profoundly influenced software development for over fifty years. This paper argues that this partitioning is neither natural nor straightforward, leading to inevitable problems like fragmentation and conflation of functionality, making software difficult to write, read, and maintain. It critiques how actions involving multiple individuals are often arbitrarily assigned to single objects, resulting in poor modularity and problematic dependencies, even in modern web frameworks utilizing object-relational mappers. The article proposes an alternative "concept" approach, which decouples problem domain individuals from functional modules. This method uses "concepts" to encapsulate actions and relations over individuals, allowing a single individual to participate in multiple concepts and coordinating behaviors through declarative action synchronization, aiming for stronger modularity, clearer separation of concerns, and better alignment with problem domain types.

Key takeaway

For AI Architects and Software Engineers designing new systems or refactoring existing ones, understand that object orientation's core principle of assigning computations to domain objects often creates fragmented and tightly coupled code. This leads to conflation and technical debt. Instead, explore "relational modularity" using concepts. This approach decouples domain individuals from functional modules, coordinating via action synchronization. It promises clearer separation of concerns and improved legibility, especially with LLM-based code generation.

Key insights

Object orientation's core principle of assigning computations to domain objects inherently causes modularity issues.

Principles

• Object orientation's core principle leads to fragmentation and conflation.
• Decouple domain individuals from functional modules for better modularity.
• Externalize coordination between modules via action synchronization.

Method

The "concept" approach defines modules (concepts) that encapsulate actions and relations over individuals, allowing individuals to span multiple concepts. Coordination occurs via declarative action synchronization rules.

In practice

• Represent concepts as classes in object-oriented languages.
• Use event-driven architectures for concept synchronization.
• Generate concept specifications and implementations one at a time.

Topics

• Object-Oriented Critique
• Software Modularity
• Concept-Oriented Design
• Relational Modularity
• Action Synchronization
• Software Architecture

Code references

• winterrrrrff/realWorld-server

Best for: AI Scientist, Software Engineer, Research Scientist, AI Architect

Related on AIssential

• Engineering Verifiable Modularity in Transformers via Per-Layer Supervision — Architectural interventions and per-layer supervision can engineer verifiable modularity in Transformers, overcoming the "Hydra effect."
• Organizing productive platform teams — Organizational structure dictates platform design; align teams to desired architecture, not existing complexity.
• Fragments: April 14 — AI's transformative power necessitates adapting established software engineering principles like TDD and abstraction, while designing for AI restraint.
• Microskill Architecture: A Modular Skill-Driven Framework for AI-Native Code Generation — MicroSkill Architecture uses modular, semantically-routed skill capsules to optimize context and improve AI-native code generation efficiency.
• The design handoff is dead—replaced by continuous sync — A common challenge in software development is the divergence of "sources of truth" between design and code, where design artifacts often lack direct representation or full elevation within the codebas…
• The Timeless Way of Building — A "pattern language" defines a library of interconnected concepts for building, influencing a creation's inherent "life."

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by cs.SE updates on arXiv.org.