Contribution 5

From WikiContent

(Difference between revisions)
Jump to: navigation, search
Line 5: Line 5:
Architecting is about much more than just the technical aspects (of modularizing systems, applying patterns, optimizing performance, etc.); architecting is about balancing the needs of all the stakeholders in a system, from users to CEOs to operations personnel to future programming staff, over the short and long term, in the way that is appropriate to the context at hand.
Architecting is about much more than just the technical aspects (of modularizing systems, applying patterns, optimizing performance, etc.); architecting is about balancing the needs of all the stakeholders in a system, from users to CEOs to operations personnel to future programming staff, over the short and long term, in the way that is appropriate to the context at hand.
-
--[[User:Randy.stafford|Randy.stafford]] 17:26, 13 May 2008 (PDT)
+
--[[User:Randy.stafford|Randy Stafford]] 17:26, 13 May 2008 (PDT)
Back to [[97 Things Every Software Architect Should Know]] home page
Back to [[97 Things Every Software Architect Should Know]] home page

Revision as of 00:30, 14 May 2008

Contribution 5: Architecting is About Balancing...

(note: the current revision of this page, and the following text, is serving as a placeholder, to be further elaborated very soon)

Architecting is about much more than just the technical aspects (of modularizing systems, applying patterns, optimizing performance, etc.); architecting is about balancing the needs of all the stakeholders in a system, from users to CEOs to operations personnel to future programming staff, over the short and long term, in the way that is appropriate to the context at hand.

--Randy Stafford 17:26, 13 May 2008 (PDT)

Back to 97 Things Every Software Architect Should Know home page

Personal tools