Are you asking what's architecture, or how to make good architectures
If you are asking what's Architecture, then it can be said as a high level and a long lasting blue print of a system. This defenetly includes thought process because an architect needs to always have the 'big picture' in mind which is never given in the requirements doc :). And for this clear thought process is required. As far as practice is concerned,...it has become a practice in the recent times because of the maturity it has gained. And i do not think architecture is a pattern. Infact patterns emerge from different architectures. So as and when there are new needs, there would be new architetcures and thus new patterns also would emerge from these architetcures.
But if you are asking what makes a good architect, then i think it's the combination of all. He needs to defenetly be able to think and therefore good thought process is required. But just with thought process one cannot have exposure. So he must practice to get enough exposure. And more exposure he gets. more patterns he comes to know and can use these patterns in his solutions.
I believe Architecture is something which is a super set of many things which of course includes Practices, Patterns, and what not... A blurry boundry in the universe of IT which is consistantly redifining its parameters.
The Quality required by architecture are many fold. Which goes right from ease of usage to ease of development to ease of maintenence. And this i guess is from Application Architecture point of view. However as you move higher, for example enterprise architecture, the quality list increases dramitically and so does the scope.
However i believe you need to narrow down you question to exactly what question are u seeking an answer to
To me architecture is the organization of the right technologies assets to address the needs of a business. These assets may be hardware, software, processes or knowledge stores.
Part of the answer to your question may be another question. Do you mean the result or the process of getting to the result. Architects use thought processes, practices and patterns. A pattern may be used to describe part of the architecture. But I think architecture as an end result is much bigger.
Of course that is just my opinion. That is the thing about architecture. Everyone has a different opinion about it.
Architecting a System is a Thought Process or Practice or Combination of both of these or others too
version2
Are you asking what's architecture, or how to make good architectures
If you are asking what's Architecture, then it can be said as a high level and a long lasting blue print of a system. This defenetly includes thought process because an architect needs to always have the 'big picture' in mind which is never given in the requirements doc :). And for this clear thought process is required. As far as practice is concerned,...it has become a practice in the recent times because of the maturity it has gained. And i do not think architecture is a pattern. Infact patterns emerge from different architectures. So as and when there are new needs, there would be new architetcures and thus new patterns also would emerge from these architetcures.
But if you are asking what makes a good architect, then i think it's the combination of all. He needs to defenetly be able to think and therefore good thought process is required. But just with thought process one cannot have exposure. So he must practice to get enough exposure. And more exposure he gets. more patterns he comes to know and can use these patterns in his solutions.
Regards,
Anjana
Blue Einstein
JohnD90
Hi Rohan,
This is not a simple question, where the answer will be in one line or few lines, but I believe the answer will be the every ones point of view !!!
Therefore, it is open to discuss.
I think you also agree with me.
:)
Chompin
I believe Architecture is something which is a super set of many things which of course includes Practices, Patterns, and what not... A blurry boundry in the universe of IT which is consistantly redifining its parameters.
The Quality required by architecture are many fold. Which goes right from ease of usage to ease of development to ease of maintenence. And this i guess is from Application Architecture point of view. However as you move higher, for example enterprise architecture, the quality list increases dramitically and so does the scope.
However i believe you need to narrow down you question to exactly what question are u seeking an answer to
Thanks
CyK
To me architecture is the organization of the right technologies assets to address the needs of a business. These assets may be hardware, software, processes or knowledge stores.
Part of the answer to your question may be another question. Do you mean the result or the process of getting to the result. Architects use thought processes, practices and patterns. A pattern may be used to describe part of the architecture. But I think architecture as an end result is much bigger.
Of course that is just my opinion. That is the thing about architecture. Everyone has a different opinion about it.
Hope that helps.
Tim Murphy
JockForrester