Editing Lumpers and splitters (section)

=== Software modelling ===
[[Software engineering]] often proceeds by building models (sometimes known as [[model-driven architecture]]). A lumper is keen to generalize, and produces models with a small number of broadly defined objects. A splitter is reluctant to generalize, and produces models with a large number of narrowly defined objects. Conversion between the two styles is not necessarily symmetrical. For example, if error messages in two narrowly defined classes behave in the same way, the classes can be easily combined. But if some messages in a broad class behave differently, every object in the class must be examined before the class can be split. This illustrates the principle that "splits can be lumped more easily than lumps can be split".<ref name=Pugh2005>{{cite book|last=Pugh|first=Ken|title=Prefactoring|date=2005|publisher=O'Reilly Media|pages=14–15|isbn=9780596008741|url=https://books.google.com/books?id=8nykB7qerJYC&pg=PA15|access-date=2014-10-21}}</ref>