Architecture and IT: Difference between revisions

From Federal Burro of Information
Jump to navigationJump to search
No edit summary
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 belie that IT has a lot fo learning to do.
I firmly believe that IT has a lot of learning to do.


There are mature operations out there. but I have 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 lense of other insdusties
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 industru.
An old and large industry.


some things are the same , some things are different.
Some things are the same , some things are different.


* Architecture is regulated IT is not.
* Architecture is '''regulated''', IT is not.


* architecutre has lots of zero, most of the time IT does not. ~1 million $ versus ~10k $ roughly for a sense of scale.
* 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.


architecutre has large teams of specialist.
* 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 smaller teams and althoguht there are specialist, often there is a lone specialis who does a job, for exmaple 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.


arhcitecture doens't involve itself with on going aspect after build as much as IT. IT has support depeartments, 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.
 
so IT does the architecture owrk, but it also does the janitorial work.


== Timelines and planning ==
== Timelines and planning ==


* http://hmhai.com/design-phases/
* http://hmhai.com/design-phases/

Revision as of 17:25, 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

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

Retrieved from "https://wiki.quadratic.net/index.php?title=Architecture_and_IT&oldid=3600"