A concept should have an articulated purpose; without it, there is no reason from the user’s point of view.

Entities in the same semantic neighborhood but without a typed relation to this one — candidates for new edges or unrecognized duplicates.

• A concept should not attempt to serve two distinct purposes; this leads to conflicts and confusion.claim0.832
  No overloading criterion.
• Concepts are not just subjective mental constructs, but are objective features of a system's design: increments of functionality that were consciously introduced by a designer to serve particular purposes.concept0.817
  Central definition from the abstract.
• A concept is a structure invented to give a coherent account of the immediate consequences of actions in a complex system.claim0.807
  Jackson's operational definition of a software concept.
• Concepts are the building blocks of software systems, objective features of a system’s design.claim0.797
  Asserts that concepts are not just mental but concrete design elements.
• A concept is a structure that is invented to give a coherent account of the immediate consequences of actions in a complex system.concept0.781
  Operational definition of concept.
• The four concept criteria (motivation, no redundancy, no overloading, uniformity) are neither necessary nor sufficient but can explain design flaws.claim0.781
  Acknowledging the heuristic nature of the criteria.
• Two concepts should not have the same purpose; additional concepts for the same purpose create needless complexity.claim0.779
  No redundancy criterion.
• The purpose of abstraction is not to be vague, but to create a new semantic level in which one can be absolutely precise.concept0.774
  Dijkstra's epigraph encapsulates the core philosophy of denotational design: abstraction enables rigor rather than obscurity.