|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/getting-design-right-part-4/
课程评论：没有评论
课程名称：深入思考系统设计的结构 课程概述：本课程是康奈尔系统工程计划“设计正确八步法”的第五步，重点介绍系统架构的开发。作为系列课程中的核心，旨在帮助学习者理解系统的工作原理及其描述方法。课程涵盖了许多对所有参与系统设计的人士至关重要的新考虑因素，适用于各种规模的项目。 架构开发过程涉及创建系统的描述，包括其子系统及其协作方式。设计师的挑战在于创建一种能够有效传达信息的描述，确保设计团队的所有成员（例如，具备机械或电气工程背景的硬件工程师与精通计算机科学的软件工程师）都能理解，尽管这些团队可能使用行业特定的语言。课程使用先前引入的基本概念来创建一个通用的系统架构描述语言，使团队中的每个人都能理解。 这门课程在多个方面独特，强调架构的重要性，而这一点通常在六西格玛设计方法中被忽视。同时，本课程提出了一种行为基础的架构观，这在系统工程中同样常被忽略。学习者会发现，设计过程所产生的大多数工作成果源自运营描述。这种以行为为中心的方法集成了系统的多样视角，对最终用户具有巨大益处，确保产品或服务使用的每一个方面都经过充分考虑。 系统思维要求兼顾细节和抽象。通过使用亲和流程从详细的运营描述中提取系统行为，管理者可以提升团队的系统思维能力。采用这种方法的管理者或设计师，能够更好地思考系统的协调与控制，并为子系统分配功能和性能。
This course presents step five in the Cornell Systems Engineering Program's Eight Steps for Getting Design Right: developing the architecture. This is the central course in the series for developing your understanding of how systems work and how to describe how they work. In addition, it covers many new considerations important to everyone engaged in system design. The concepts and tools presented here are relevant to a wide variety of projects, large and small.The process of developing the architecture involves creating a description of the system in terms of its subsystems and how they work together. The challenge for the designer is to create a description that communicates effectively to all members of the design team-for example, to hardware engineers versed in mechanical or electrical engineering as well as to software engineers versed in computer science-even though these groups may speak discipline-specific languages. This course uses basic concepts introduced earlier in the series to develop a general language for describing system architecture that everyone on the team can understand.This course is unique in several ways. It emphasizes the role of architecture, a role typically ignored in Design for Six Sigma approaches. It presents a behavioral basis for architecture that likewise is often overlooked in systems engineering. In this course, the learner finds that most of the work products resulting from the design process are derived from operational descriptions. This behavior-centered approach integrates otherwise diverse views of the system and has enormous benefits for the end-user, ensuring that every aspect of the product's or service's use has been thoroughly thought through.Systems thinking requires both detail and abstraction. A manager can develop her team's systems-thinking skills by using the affinity process to abstract system behavior from detailed operational descriptions. Anyone using this approach, manager or designer, learns to think through the coordination and control of the system and to allocate functionality and performance to subsystems.
