“Work on what was to become “structured design” began in the early 1960s. Structured design, as a well-defined and named concept, did not achieve appreciable visibility until the publication of an article in the IBM Systems Journal in 1974 (Stevens et al., 1974). There is more than one way to accomplish a “structured design.””

—  Edward V. Berard

Abstract
Object‐Oriented Design (2002)

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "Work on what was to become “structured design” began in the early 1960s. Structured design, as a well-defined and named…" by Edward V. Berard?
Edward V. Berard photo

Related quotes

Jacques Lacan photo

“The father, the Name-of-the-father, sustains the structure of desire with the structure of the law- but the inheritance of the father is that which Kierkegaard designates for us, namely, his sin.”

Jacques Lacan (1901–1981) French psychoanalyst and psychiatrist

Of the Network of Signifiers
The Four Fundamental Concepts of Psycho Analysis (1978)

Fred Brooks photo

“… the organization chart will initially reflect the first system design, which is almost surely not the right one [… ] as one learns, he changes the design [… ]. Management structures also need to be changed as the system changes…”

Fred Brooks (1931) American computer scientist

The Mythical Man-Month: Essays on Software Engineering (1975, 1995)

“Concepts of uncertainty and information processing are used to integrate the diverse organization design/structure literatures. This approach more fully explicates the concept of congruence which lies at the heart of contingency ideas. The review suggests a contingency approach to design which develops a feasible set of structural alternatives from which the organization can choose.”

David A. Nadler (1948–2015) American organizational theorist

Source: "Information Processing as an Integrating Concept in Organizational Design." 1978, p. 613: Abstract

Grady Booch photo

“Structured design does not scale up well for extremely complex systems, and this method is largely inappropriate for use with object-based and object-oriented programming languages.”

Grady Booch (1955) American software engineer

Source: Object-oriented design: With Applications, (1991), p. 19

Linus Torvalds photo

“…git actually has a simple design, with stable and reasonably well-documented data structures. In fact, I'm a huge proponent of designing your code around the data, rather than the other way around, and I think it's one of the reasons git has been fairly successful […] I will, in fact, claim that the difference between a bad programmer and a good one is whether he considers his code or his data structures more important. Bad programmers worry about the code. Good programmers worry about data structures and their relationships.”

Linus Torvalds (1969) Finnish-American software engineer and hacker

Message to Git mailing list, Torvalds, Linus, 2006-06-27, 2006-08-28 http://lwn.net/Articles/193245/,
2000s, 2006

Alan Moore photo

“There is no future. There is no past. Do you see? Time is simultaneous, an intricately structured jewel that humans insist on viewing one edge at a time, when the whole design is visible in every facet.”

Alan Moore book Watchmen

Source: Watchmen

“Encapsulation is the key to increasing the value of such software metrics as reusability, refinability, testability, maintainability, and extensibility. Object-oriented languages provide a number of mechanisms for improving encapsulation, but it is during the design phase that the greatest leverage can be realized.
The data-driven approach to object-oriented design focuses on the structure of the data in a system. This results in the incorporation of structural information in the definitions of classes. Doing so violates encapsulation.
The responsibility-driven approach emphasizes the encapsulation of both the structure and behavior of objects. By focusing on the contractual responsibilities of a class, the designer is able to postpone implementation considerations until the implementation phase.
While responsibility-driven design is not the only technique addressing this problem, most other techniques attempt to enforce encapsulation during the implementation phase. This is too late in the software life-cycle to achieve maximum benefits.”

Rebecca Wirfs-Brock (1953) American software engineer

Source: Object-oriented design: a responsibility-driven approach (1989), p. 75: Conclusion

Eduardo Torroja photo

“Mathematics is merely a convenient tool by which the designer determines the physical proportions and details of a planned structure in order to transform his ideas… to the actuality of a finished structure.”

Eduardo Torroja (1899–1961) Spanish architect

p, 125
Philosophy of Structures (1958)

“It is worth stressing that once the entailment structure for a subject matter is available, together with its task structure, these can be used to design any kind of course or curriculum.”

Gordon Pask (1928–1996) British psychologist

Source: Conversation, Cognition and Learning (1975), p. 395.

Richard L. Daft photo

“Organizations are (1) social entities that (2) are goal-directed, (3) are designed as deliberately structured and coordinated activity systems, and (4) are linked to the external environment.”

Richard L. Daft (1964) American sociologist

Source: Organization Theory and Design, 2007-2010, p. 10; Cited in: Jan A. P. Hoogervorst (2009), Enterprise Governance and Enterprise Engineering, p. 80.

Related topics