Monolithic design

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

Generally, a monolithic design is given when a software provides its functionality centralised in one or just a few classes. The level of data abstraction is very low.

Such a design does not need a complex architecture. Developer will not have troubles to conceive the software as only a few elements must be studied. Further, such an approach typically ensures fast results when applying the software. However, such an approach may lead to unclear or sleazy code as there is no clear separation to other areas of the software. Further, it is hard to manipulate or change existing code, also extensions may be hard to realize.

In visualization, especially if abstract data, visual structures, and rendering routines are not separated a software is called monolithic.