Software architect: Difference between revisions

@@ Line 3: / Line 3: @@
 {{TOCright}}
 ==History==
-The software architect concept began to take hold when object-oriented programming or OOP, was coming into more widespread use (in the late 1990s and early years of the 21st century).{{Citation needed|date=January 2011}} OOP allowed ever-larger{{Quantify|date=June 2018}} and more complex{{Quantify|date=June 2018}} applications to be built, which in turn required increased{{Quantify|date=June 2018}} high-level application and system oversight.{{Citation needed|date=June 2018}}
+The software architect concept goes back at least to Harlan Brooks, author of ''''The Mythical Man Month'''' who was designer of the highly successful System 360/370 software architecture in the mid 1960s. Subsequently the commercial job title began to appear in wage labor markets but this was a generation later and contrary to what is stated in the English wiki, had relatively little to do with the dominance of OOP which wasn't substantial until the mid 1990s. OOP does join threads of computer history such as structured programming in calling for improved design based on its paradigm but this is distinct from the activity of architecting systems and it's false that the two have actually been joined as the article there states.
 ==Duties==

Navigation menu