- 1、本文档共29页,可阅读全部内容。
- 2、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
- 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载。
- 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
(设计良好系统的基本原则
外文资料Fundamental Principles of Good System DesignA. Terry Bahill, PE, University of ArizonaRick Botta, BAE SystemsAbstract: This article presents dozens of fundamental principles of good system design that should help make a product better. Not surprisingly, many of these same principles will help make a product reusable in a new system and will help reduce redesign costs when requirements change. These principles apply to simple systems and complex systems. These principles come from hardware, software, system, and test design, but they are general and many can be applied in a large variety of fields (even non-engineering fields).Keywords: System Design, Reuse, Requirements, Systems of Complex SystemsEMJ Focus Areas:Systems EngineeringDesign is a creative activity—consequently, there is no process that will guarantee good designs, but there are some principles that will increase the probability of getting a good design. This article presents dozens of fundamental principles of good system design that should help make a product better. Using these principles will also make a product more reusable for future systems and it will help reduce redesign costs when requirements change. Of course, the customer may mandate or exclude the use of some or all of these principles. Some of these principles are as follows:·Use models to design systems·Use hierarchical, top-down design·Work on high-risk items first·Prioritize·Control the level of interacting entities·Design the interfaces·Produce satisficing designs ·Do not optimize early·Maintain an updated model of the system·Develop stable intermediates·Use evolutionary development·Understand your enterprise·State what, not how·List functional requirements in the use cases ·Allocate each function to only one component·Do not allow undocumented functions·Provide observable states·Rapid prototyping·Develop iteratively and test immediately·Create modules·Create libraries of reusable objects·Use open standards·Identify things that
文档评论(0)