Polylithic design

From InfoVis:Wiki
Revision as of 01:39, 6 July 2006 by Anfe (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Generally, a polylithic design is given when a software provides a high level of data abstraction. The result is a large count of separated classes which are consolidated through several programming techniques like inheritance or generic concepts.

A lot of separations allow developers to change or manipulate existing functionality selectively. Furthermore, a high data abstraction forces developer to implement well thought components which may also work correct when other components have changed. Typically, this results a clear and elaborate architecture. But, the large count of objects may also lead to not considered mistakes and makes it harder to understand the software.

In visualization, especially the separation between abstract data, visual structures, and rendering routines is defined as polylithic design.