Architecture and IT: Difference between revisions
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
I think that IT could and should learn from other industries. | I think that IT could and should learn from other industries. | ||
I firmly | I firmly believe that IT has a lot of learning to do. | ||
There are mature operations out there | There are mature IT operations out there, but I have a lot of learning to do. | ||
So I look at IT through the | So I look at IT through the lens of other industries. | ||
Here I will look at it through Architecture. | Here I will look at it through Architecture. | ||
An old and large | An old and large industry. | ||
Some things are the same , some things are different. | |||
* Architecture is regulated IT is not. | * Architecture is '''regulated''', IT is not. | ||
* | * Architecture has lots of zero, most of the time IT does not. ~1 million $ versus ~10k $ roughly for a sense of scale. | ||
The pattern of behavior is different also. | The pattern of behavior is different also. | ||
* Architecture has large teams of specialist. IT has smaller teams and although there are specialist, often there is a lone specialist who does a job, for example one "enterprise architect" , one DBA, one network person. | |||
IT has | Architecture doesn't involve itself with on going aspect after build as much as IT. IT has support departments, architect typically walk away from builds after build is done. LEED changes that. But for the most part this is true. | ||
So IT does the architecture work, but it also does the janitorial work. | |||
== Timelines and planning == | |||
* http://hmhai.com/design-phases/ | |||
[[Image:phases-w-interiors.png]] | |||
* https://www.archtoolbox.com/representation/specifications/project-planning-and-scheduling.html | |||
** got notes on critical path | |||
[[image:critical-path-method-diagram.png]] | |||
http://legalteamusa.net/civillaw/2012/11/21/substantial-completion-when-exactly-does-it-occur/ | |||
== Further reading == | == Further reading == | ||
Latest revision as of 18:24, 9 January 2018
I think that IT could and should learn from other industries.
I firmly believe that IT has a lot of learning to do.
There are mature IT operations out there, but I have a lot of learning to do.
So I look at IT through the lens of other industries.
Here I will look at it through Architecture.
An old and large industry.
Some things are the same , some things are different.
- Architecture is regulated, IT is not.
- Architecture has lots of zero, most of the time IT does not. ~1 million $ versus ~10k $ roughly for a sense of scale.
The pattern of behavior is different also.
- Architecture has large teams of specialist. IT has smaller teams and although there are specialist, often there is a lone specialist who does a job, for example one "enterprise architect" , one DBA, one network person.
Architecture doesn't involve itself with on going aspect after build as much as IT. IT has support departments, architect typically walk away from builds after build is done. LEED changes that. But for the most part this is true.
So IT does the architecture work, but it also does the janitorial work.
Timelines and planning
- https://www.archtoolbox.com/representation/specifications/project-planning-and-scheduling.html
- got notes on critical path
http://legalteamusa.net/civillaw/2012/11/21/substantial-completion-when-exactly-does-it-occur/
Further reading
Design Assist https://www.bdcnetwork.com/design-assist-way-really-fly-aia-course
Information architecture , http://journalofia.org/volume3/issue2/03-resmini/ loosely related :P
