j2ee开发项目10大风险总结(下)（J2EE development project 10 risk summary (next)）.docVIP

下载本文档

1
0
约1.12万字
约 12页
2017-09-05 发布于河南
举报
版权申诉

j2ee开发项目10大风险总结(下)（J2EE development project 10 risk summary (next)）.doc

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

j2ee开发项目10大风险总结(下)（J2EE development project 10 risk summary (next)）

j2ee开发项目10大风险总结(下)（J2EE development project 10 risk summary (next)） The risk of choosing the wrong provider 5: Project phase: Provider selection Influence of stage: Design, development and stabilization / load test, mature The influence on the system: Scalability, performance, maintainability and stability Symptom: Developers want to use more time to deal with problems rather than tools, it is effective to use these tools In order to cope with the known and unknown problem, and have carried out significant system redesign Between different tools difficult to integrate (application server and IDE tools, IDE tools and debuggers, source control and synthesis tools, etc.) For the IDE tools and debuggers, developers tend to exclude them and respected their love tools Avoidance scheme: In order to avoid the risk of 5, you need a good provider selection process, risk aversion is also applicable to the 10. To be a true measure of IDE tools are the most suitable for use is really. And the only method to evaluate a J2EE application is to establish a concept test to prove to you, including the application framework in the experiment. In fact, you dont want to undertake training and development in spent 3 months of time, some bug also found that when in use. If time to half in the development, you suddenly discovered that the tool set has a problem, then you should know, some tools are more important than others. If you choose the application server can not fully meet your needs, youll have to modify the original settings. If the IDE is not good, you need to set the minimum code standard, and let the developers think they choose the most effective tool. Remarks: To really understand where a supplier is most suitable for a particular task, in fact, is not a one-time decision. You need to constantly track and evaluate the market. For example, in the past year I have used 4 different IDE tools, this depends on the use of the application server, what kind of platform for me, whethe