Software architect: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
{{TOCright}} | {{TOCright}} | ||
==History== | ==History== | ||
The software architect concept goes back at least to Fred Brooks, author of ''''The Mythical Man Month''''<ref>[[:en:Mythical Man Month | The software architect concept goes back at least to Fred Brooks, author of ''''The Mythical Man Month''''<ref>[[:en:Mythical Man Month|ibid]]</ref> 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 stated when this one was drafted. | ||
==Duties== | ==Duties== | ||
| Line 42: | Line 42: | ||
| detailed | | detailed | ||
|- | |- | ||
| [[application architect]] | | [[:en:application architect]] | ||
| component re-use, maintainability | | component re-use, maintainability | ||
| centered on single application | | centered on single application | ||
