Software architect: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
| (5 intermediate revisions 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'''' 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. | 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 18: | Line 18: | ||
Other similar titles in use, but without consensus on their exact meaning, include: | Other similar titles in use, but without consensus on their exact meaning, include: | ||
* [[:en:Solution architect]], which may refer to a person directly involved in advancing a particular business solution needing interactions between multiple applications. May also refer to an [[application architect]]. | * [[:en:Solution architect]], which may refer to a person directly involved in advancing a particular business solution needing interactions between multiple applications. May also refer to an [[:en:application architect]]. | ||
* System architect (singular), which is often used as a synonym for [[:en:application architect]]. However, if one subscribes to Systems theory and the idea that an enterprise can be a system, then System Architect could also mean | * System architect (singular), which is often used as a synonym for [[:en:application architect]]. However, if one subscribes to Systems theory and the idea that an enterprise can be a system, then System Architect could also mean enterprise architect. | ||
* [[:en:Systems architect]] (plural), which is often used as a synonym for enterprise architect or solution architect. | * [[:en:Systems architect]] (plural), which is often used as a synonym for enterprise architect or solution architect. | ||
| 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 | ||
| Line 52: | Line 52: | ||
==See also== | ==See also== | ||
* [[Electrical engineering]] | * [[:en:Electrical engineering]] | ||
* [[Electronics engineering]] | * [[:en:Electronics engineering]] | ||
* [[Electronics engineering]] | * [[:en:Electronics engineering]] | ||
* [[Hardware architecture]] / [[hardware architect]] | * [[:en:Hardware architecture]] / [[:en:hardware architect]] | ||
* [[Requirements analysis]] / [[requirements engineer]] | * [[:en:Requirements analysis]] / [[:en:requirements engineer]] | ||
* [[Software architectural model]] | * [[:en:Software architectural model]] | ||
* [[Software architecture]] | * [[:en:Software architecture]] | ||
* [[Software engineering]] / [[software engineer]] | * [[:en:Software engineering]] / [[:en:software engineer]] | ||
* [[Systems architecture]] / [[systems architect]] | * [[:en:Systems architecture]] / [[:en:systems architect]] | ||
* [[Systems design]] | * [[:en:Systems design]] | ||
* [[Systems engineering]] / [[systems engineer]] | * [[:en:Systems engineering]] / [[:en:systems engineer]] | ||
== References == | == References == | ||
