Codetown ::: a software developer's community
Class Family Accord - Abstract
An Accord class family is a hierarchy of classes for which another class hierarchy has been designated as corresponding. Class A0 is the top of the class family, class A1 extends A0, class An extends An-1.
The partner of this class family is B0 at the top, Bn extends Bn-1. Class family A and B are have an Accord relationship if, by design intention, An corresponds to Bn. In each level, there is at least one method that overrides or defines a variant with a behavior representative of the progression of requirements.
The intention of this design concept is to maintain this correspondence when, as requirements evolve, the design calls for extending An and Bn into An+1 and Bn+1. The reason for maintaining this relationship would be that A has new or refined behaviors that only make sense with reference to the state or behaviors of B at the same level.
To realize this relationship in the Java programming language, a designer could simply document the intention. However, coding would inevitably require explicit down cast to force references to the intended levels. This white paper suggests a set of Java annotations to make the Accord relationship between class families explicit and generate the necessary dispatch code and casts. The resulting generated code would in effect provide a parametric override capability.
At a minimum an annotation @Accord designates a class as the head or subclass in a class family. Its attribute has an attribute, partner, to identify the other class family. Methods that are intended to follow the progression are annotated as @Covariant. The effect is to make the method be a covariant override. Its parameter referring to a class at the same inheritance level in the partner family is treated a covariant. A prototype precompiler is (to be) provided for research purposes.
Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.
Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.
Check out the Codetown Jobs group.

Rachael Wonnacott explains why DevEx is a lever, not the destination. Discover the risks of treating your platform as an isolated product and learn how to balance trade-offs between technical expertise, productivity, and business impact for achieving enterprise-scale success.
By Rachael Wonnacott
Buoyant, the company behind the open-source Linkerd service mesh, announced that Linkerd now supports the Model Context Protocol (MCP), making it the first service mesh to natively manage, secure, and observe agentic AI traffic in Kubernetes environments.
By Craig RisiVivek Yadav, an engineering manager from Stripe, shares his experience in building a testing system based on multi-year worth of data. He shares insights into why Apache Spark was the choice for creating such a system and how it fits in the "traditional" engineering practices.
By Vivek Yadav
Engineering Manager Nishant Lakshmikanth showcased LinkedIn's transformation at QCon SF 2025, detailing a shift from legacy batch-based systems to a real-time architecture. By decoupling recommendations and leveraging dynamic scoring techniques, LinkedIn achieved a 90% reduction in offline costs, enhanced session-level freshness, and improved member engagement while future-proofing its platform.
By Steef-Jan Wiggers
Meta has released SAM 3, the latest version of its Segment Anything Model and the most substantial update to the project since its initial launch. Built to provide more stable and context-aware segmentation, the model offers improvements in accuracy, boundary quality, and robustness to real-world scenes, aiming to make segmentation more reliable across research and production systems.
By Robert Krzaczyński
© 2025 Created by Michael Levin.
Powered by
You need to be a member of Codetown to add comments!
Join Codetown