|
|
此文章由 aperson 原创或转贴，不代表本站立场和观点，版权归 oursteps.com.au 和作者 aperson 所有！转贴必须注明作者、出处和本声明，并保持内容完整
Addition to above, my two cents
1：作为一个架构师，通过什么样的途径学习的架构设计？
first stage - Collect - Learn from best practice, learn from others.
Second stage - Organise - Summarize and refine
Third stage - Enhanced - Teach others in order to fine tune your own knowledge
It is a generic rule to learn anything
2：如果一个系统在上线的第一天，发现系统非常的慢，作为架构师的你，应该怎么做？
Depends on who ask this question. They want different answers
if business people ask, they want to understand if you have strong business focus or not. Make sure you are not just a bloody techie who just dives into technical terms directly(no offense, that's typical biz people's perception) .
Anything can go wrong. It is not a time to point fingers. be cool, man. Working closely with your PM to activate contingincy plan if there is. I am surprised if there isn't. But If not, Assist your PM to get all parties involved together to understand and assess the business impact and severity of the issue. seek for a technical solution while seeking for a workaround (regardless it is a business process workaround or a techinical workaround)
As an architect, you have various specialist and external consultants who support you. Your responsability is not to dive into details directly but to direct right techinical resource to the right place.
3：完成了用户需求后，你作为架构师，到客户那边，你所需要做的主要事情是什么？
1. High level validation of the spec
2. PR
3. Gather some other information that the spec can't capture. fg. people, organisation structure and their relationship. Don't think it is not important. It sometimes will determine the live or death of your solution. Don't touch some taboo
4. Test the water of some of your solution design. So no surprises in future. You will know that you will design a solution they really "love".
What's more, you are there to entertain your customers too, make them happy
[ 本帖最后由 aperson 于 2009-11-18 16:16 编辑 ] |
评分
-
查看全部评分
|
2014 —— 秋之摄，晒叶子，晒蘑菇，晒人 (2014-4-29) 老陶 
楼主:panada
发表于 2009-11-18 15:00
。
