本文发表在 rolia.net 枫下论坛One person could work in different job roles at the same time. an SE can be either one, or a combination of the three. The objective of an SE is to sell the right solution to the production level, including hardware, software, professional services, maintenance configurations and provide cost case/ROI. An architect may or may not go down to the product level. Many times, it is required that the architect to stay at a high level and maintain vendor neutral to avoid possible conflict of interest to exclude the company he/she represents from participating the bidding process later on.
Analyzing the requirements-需要输出什么文档?
A: Functional aspects can be represented in use cases and/or component module. Non functional requirement document and/or operational module can be used to list all the operational aspects of the requirement. i am quite flexible in terms of format - some times i just create a WORD document and name it as customer requirements.
Creating models at the right level of abstraction-通常用什么方法?
A: depending if this is a infrastructure project, or an application development project, or both. I am in infrastructure area, so I can easily adopt existing reference architectures for my project. How different can it be between two IP Telephony solutions in terms of moduling? LOL. I guess for software engineering, it involves much more work effort.
Providing a decision trail-需要给客户做presentation
A: i always present my solution with all important architectural decisions documented and rationalized - including the description, justification, alternatives, constraints, dependancy, risks by doing or not doing, associated cost, impact to business etc etc. The reason is that, after a year or so when I left the project, someone will always ask who the dummy senior architect made that laughable decision at that time and made all their life miserable. LOL.更多精彩文章及讨论，请光临枫下论坛 rolia.net