Modular design

From Wikipedia, the free encyclopedia

The introduction to this article provides insufficient context for those unfamiliar with the subject. Please help improve the article with a good introductory style.

In the context of systems engineering, modular design — or "modularity in design" — is an approach aiming to subdivide a system into smaller parts (modules) that can be independently created and then used in different systems to drive multiple functionalities. Besides reduction in cost (due to lesser customization, and less learning time), and flexibility in design, modularity offers other benefits such as augmentation (adding new solution by merely plugging in a new module), and exclusion. Examples of modular systems are cars, computers and high rise buildings. Computers, in fact, are the first systems in which modularity in architecture was implemented to overcome changing customer demands and to make the manufacturing process more adaptive to change (see modularity in programming).^[1] Modular design is an attempt to combine the advantages of standardization (high volume normally equals low manufacturing costs) with those of customization.

A simple example of the use of modular design in cars would be to note the fact that while many cars come as a basic model, paying extra will allow for "snap in" upgrades. Such as a more powerful engine or seasonal types; these do not require any change to other units of the car such as the chassis, steering or exhaust systems.

"Characterized by: (1) Functional partitioning into discrete scalable, reusable modules consisting of isolated, self-contained functional elements; (2) Rigorous use of well-defined modular interfaces, including object-oriented descriptions of module functionality; (3) Ease of change to achieve technology transparency and, to the extent possible, make use of industry standards for key interfaces."^[2]

A downside to modularity (and this depends on the extent of modularity) is that modular systems are not optimized for performance. This is usually due to the cost of putting up interfaces between modules.^{[citation needed]}

[edit] Further reading

• Erixon, O.G. and Ericsson, A., "Controlling Design Variants" USA: Society of Manufacturing Engineers 1999 ISBN 0-87263-514-7 [1]
• Clark, K.B. and Baldwin, C.Y., "Design Rules. Vol. 1: The Power of Modularity" Cambridge, Massachusetts: MIT Press 2000 ISBN 0262024667
• Baldwin, C.Y., Clark, K.B., "The Option Value of Modularity in Design" Harvard Business School, 2002 [2]
• Modularity in Design Formal Modeling & Automated Analysis
• "Modularity: upgrading to the next generation design architecture", an interview

[edit] References