软件架构师应该知道的97件事 - csdn资讯（97 things that a software architect should know - CSDN information）.docVIP

下载本文档

4
0
约1.42万字
约 21页
2017-08-02 发布于河南
举报
版权申诉

软件架构师应该知道的97件事 - csdn资讯（97 things that a software architect should know - CSDN information）.doc

1、有哪些信誉好的足球投注网站（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

软件架构师应该知道的97件事 - csdn资讯（97 things that a software architect should know - CSDN information） 97 things that a software architect should know . The following is from the title of the book and gives the necessary additional instructions from the books translator, SeanBV (his CSDN blog), to recommend to you. 1. customer needs are more important than Borwankar (Nitin) Customer demand paramount. The new technology for their own resume Gengxuan and fish for fame, and often counterproductive. 2., simplify the fundamental complexity and eliminate the Neal Ford Analysis of problems like the clouds see the month out. 3., the key issue may not be Ramm (Mark) The team is of one mind. 4. to communicate as the center, adhere to concise and clear expression and open-minded leadership style (Mark Richards) Communication should be concise and comprehensive, appropriate levels of detail, not sloppy. The 5. architecture determines performance (Randy, Stafford) What you sow, reap, architecture design is the same. 6. analyze the meaning of customer requirements (Einar, Landre) Unraveling the clairvoyant. Dont be confused by surface demands. 7. standing up (Udi Dahan) Stand up and speak better. 8., the fault will eventually happen (Michael Nygard) Preventive measures should be designed ahead of time to limit failures. 9., we often ignore ourselves in negotiations (Michael, Nygard) Engineers should change roles and learn negotiating skills at the right time. 10. quantitative requirements (Keith, Braithwaite) No manners, no, Cheng Fangyuan. 11., one line of code is more valuable than the five hundred line Schema Specification (Allison, Randal) Working code is the goal; design is only the means of achieving it. 12., there is no universally accepted solution (Randy, Stafford) The software world has no master key. 13., pay attention to performance issues (Rebecca, Parsons) in advance Conduct performance testing as early as possible. 14., architecture design should balance the needs of Stafford