The concept of a code smell is defined as representing a potential problem within a system, typically a programming design system. The idea of a code smell was introduced in 1999 with a list of 22 low-level code smells and an associated description on how to identify them. This paper revisits code smells with several good examples, and then explores the meta-model with the acronym CRIO, which is created from capacity, role, integration, and organization. The authors then examine a multiagent organizational approach, the agent-oriented software process for engineering complex systems (ASPECS).

The contents of this paper are very complex and require advanced knowledge in computer-aided software engineering (CASE) tools and concepts. The conclusions suggest the paper is a contribution to the work already done in multiagent systems, a claim that only an expert in this field could verify; this paper is not suitable for laypeople. However, I would certainly recommend it to academics and researchers working in this area.