By Topic

The state of design [software design]

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Fowler, M. ; ThoughtWorks

A useful way to talk about design is to identify principles that lead to well-designed systems. This principle is relatively easy to understand, yet applying it in a determined effort to remove duplication in code often leads to effective designs. A central design idea is to break a system into modules that hide complex implementations behind clear interfaces. Object-oriented systems are well known for decomposing systems into small objects with interfaces, but we must treat these kinds of interfaces differently from those that are exposed across a network or shared between teams. A significant issue in software design is determining where design fits in the overall software process. Design involves people, so in addition to considering how design fits into a process, you also have to think about how it fits with an organization's people. Three primary purposes for models: conceptual, specification, and implementation.

Published in:

Software, IEEE  (Volume:22 ,  Issue: 6 )