Structured programming and structured design wouldn't necessarily be the same thing. Structured design in general is going to focus on breaking things down into structured elements. There are a bunch of approaches that are equally valid here, but I would say that most of them focus on information hiding.
Object Oriented Design obviously breaks things down into objects with operations and data held together in tightly bound classes related in hierarchies
Abstract Data Types are essentially non-OO equivalents where the data and operations are held together but are not bound in quite the same sense as in object oriented design. Hierarchy and inheritance don't play a role with ADTs, at least not in those that I've seen.
Metaprogramming focuses on building generic types and then specializing them appropriately for specific data types
Programming to a contract focuses on avoiding direct inheritance. Typically it combines Contract Interfaces with implementation by composition of multiple classes.
Design Patterns focus on high-level meta-designs (patterns) that can be implemented in almost any context, although they are most commonly seen in discussions of OO design.
Knowing how to structure programs in multiple paradigms is always going to be valuable knowledge. Knowing how to talk about the structure of a design is more finicky but ultimately even more valuable.
我同意 Mike Burton 的作者的观点广告可能缺乏线索，但是您可以很容易地温习“模块耦合”和“模块内聚”，如果您可以在图书馆找到它们，那么这些书就值得一读。我只能在 IBM 付费网站上找到原始论文。
In the classic works on composite/structured design by Myers and by Yourdon and Constantine, the two most important principles are
Coupling (how different modules relate to one another)
Cohesion (how a module is structured internally)
I agree with Mike Burton that the author of the ad probably lacks a clue, but you can brush up on "module coupling" and "module cohesion" easily enough, and if you can get them at a library, the books are worth reading. I can find the original paper only at an IBM pay site.
What I always refer to is a ancient article in IEEE Micro Magazine October 1981 by G. D. Bergland of Bell Telephone Laboritories - belive it or not. It's about thirteen pages long and gives you most everything you need to know. Trouble is you may not be able to find it - even at IEEE & even if your a member.
You can find another very good (though old) book "Tutorial on Software Design Techniques" by Peter Freeman (Editor) at Amazon.
发布评论
评论（3）
结构化编程和结构化设计不一定是同一件事。一般来说，结构化设计将重点关注将事物分解为结构化元素。有很多方法在这里同样有效，但我想说它们中的大多数都专注于信息隐藏。
知道如何在多种范式中构建程序始终是有价值的知识。知道如何谈论设计的结构更加挑剔，但最终更有价值。
Structured programming and structured design wouldn't necessarily be the same thing. Structured design in general is going to focus on breaking things down into structured elements. There are a bunch of approaches that are equally valid here, but I would say that most of them focus on information hiding.
Knowing how to structure programs in multiple paradigms is always going to be valuable knowledge. Knowing how to talk about the structure of a design is more finicky but ultimately even more valuable.
在 Myers 和 Yourdon 和 Constantine，两个最重要的原则是
耦合（不同模块如何与一个模块相关）另一个）
内聚（模块内部如何构造）
我同意 Mike Burton 的作者的观点广告可能缺乏线索，但是您可以很容易地温习“模块耦合”和“模块内聚”，如果您可以在图书馆找到它们，那么这些书就值得一读。我只能在 IBM 付费网站上找到原始论文。
In the classic works on composite/structured design by Myers and by Yourdon and Constantine, the two most important principles are
Coupling (how different modules relate to one another)
Cohesion (how a module is structured internally)
I agree with Mike Burton that the author of the ad probably lacks a clue, but you can brush up on "module coupling" and "module cohesion" easily enough, and if you can get them at a library, the books are worth reading. I can find the original paper only at an IBM pay site.
我总是引用贝尔电话实验室的 GD Bergland 于 1981 年 10 月发表在 IEEE Micro 杂志上的一篇古老文章 - 不管你信不信。它大约有十三页长，为您提供了您需要了解的大部分内容。问题是你可能找不到它——即使是在 IEEE & IEEE。即使您是会员。
您可以在亚马逊找到另一本非常好的（虽然很旧）书“软件设计技术教程”，作者是 Peter Freeman（编辑）。
http:// www.amazon.com/gp/offer-listing/0818605146/ref=dp_olp_0?ie=UTF8&redirect=true&condition=all
What I always refer to is a ancient article in IEEE Micro Magazine October 1981 by G. D. Bergland of Bell Telephone Laboritories - belive it or not. It's about thirteen pages long and gives you most everything you need to know. Trouble is you may not be able to find it - even at IEEE & even if your a member.
You can find another very good (though old) book "Tutorial on Software Design Techniques" by Peter Freeman (Editor) at Amazon.
http://www.amazon.com/gp/offer-listing/0818605146/ref=dp_olp_0?ie=UTF8&redirect=true&condition=all