+ Quote(s)
← Older revision
Revision as of 14:13, 16 August 2013
Line 3:
Line 3:
{{Author-stub}}
{{Author-stub}}
−
== Sourced ==
+
== Quotes ==
* A system composed of 100,000 lines of [[C++]] is not be sneezed at, but we don't have that much trouble developing 100,000 lines of COBOL today. The real test of OOP will come when systems of 1 to 10 million lines of code are developed.
* A system composed of 100,000 lines of [[C++]] is not be sneezed at, but we don't have that much trouble developing 100,000 lines of COBOL today. The real test of OOP will come when systems of 1 to 10 million lines of code are developed.
** Yourdon (1990) cited in: Andreas Paepcke (1991) ''Object-oriented Programming Systems, Languages and Applications''. p.166
** Yourdon (1990) cited in: Andreas Paepcke (1991) ''Object-oriented Programming Systems, Languages and Applications''. p.166
+
+
== About Ed Yourdon ==
+
* Systems engineering as an approach and [[methodology]] grew in response to the increase size and complexity of [[system]]s and [[project]]s. It "''recognizes each [[system]] is an integrated whole even though composed of diverse, specialized structures and sub-functions''..." ([[Harold Chestnut|Chestnut]], 1965) This engineering approach to the management of complexity by modularization was re-deployed in the software engineering discipline in the 1960s and 1970s with a proliferation of structured methodologies that enabled the the analysis, design and development of information systems by using techniques for modularized description, design and development of system components. [[:w:Edward Yourdon|Yourdon]] and [[Tom DeMarco|DeMarco]]'s Structured Analysis and Design, ''SSADM'', [[James Martin (author)|James Martin]]'s Information Engineering, and [[Michael A. Jackson|Jackson]]'s Structured Design and Programming are examples from this era. They all exploited modularization to enable the parallel development of data, process, functionality and performance components of large software systems. The development of [[:w:Object-oriented analysis and design|object orientation]] in the 1990s exploited modularization to develop reusable software. The idea was to develop modules that could be mixed and matched like Lego bricks to deliver to a variety of whole system specifications. The modularization and reusability principles have stood the test of time and are at the heart of modern software development.
+
** Peter Allen, Steve Maguire, Bill McKelvey (2011) ''The SAGE Handbook of Complexity and Management''. p. 35
== External links ==
== External links ==