root/logseq_notes
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Auto saved by Logseq

Browse source
This commit is contained in:
Ryan 2023-06-15 20:42:19 +08:00
parent a9d2d54dd7
commit 60f5c3ec51
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
pages/总复习2023t1.md
View file

@ -2014,7 +2014,7 @@
- A lack of _commitment_ - A lack of _commitment_
- A lack of _skills_ - A lack of _skills_
- ## Topic 10: ==Intellectual Property== - ## Topic 10: ==Intellectual Property==
collapsed:: true deck:: 2023t1/product/t10
- 知识产权分类 #flashcard - 知识产权分类 #flashcard
id:: 648ae540-d111-47d6-8742-5709ab330e29 id:: 648ae540-d111-47d6-8742-5709ab330e29
collapsed:: true collapsed:: true
@ -2114,6 +2114,7 @@
- 所有者可以控制并从使用他们的知识产权中获得回报，这鼓励了进一步的创新和创造，对我们所有人都有好处。The owner can control and be rewarded for the use of their IP, and this encourages further innovation and creativity to the benefit of us all. - 所有者可以控制并从使用他们的知识产权中获得回报，这鼓励了进一步的创新和创造，对我们所有人都有好处。The owner can control and be rewarded for the use of their IP, and this encourages further innovation and creativity to the benefit of us all.
- DONE Week 3 - DONE Week 3
- ## Topic 11: ==System Level Design== - ## Topic 11: ==System Level Design==
deck:: 2023t1/product/t11
collapsed:: true collapsed:: true
- 系统级设计（System-level Design） - 系统级设计（System-level Design）
产品架构可以描述为 :“ 将产品的功能元素排列成物理块以及块之间相互作用的方案”功能性——有助于整体绩效的单个操作和转换.物理–实现产品功能的零件、组件和子组件（通俗来讲，顺序是完成相应功能的零件 component--->组件 chunks---->产品，产品架构就是以实体组件来实现产品的各功能单元，并使各组件相互作用的配置方案） Product Architecture can be described as: 1."the **scheme** by which the functional elements of the product are arranged into physical chunks and by which the chunks interact” 2.**Functional** – individual operations and transformations that contribute to its overall performance 3.**Physical** – parts, components and subassemblies that implement the product’s functions 产品架构可以描述为 :“ 将产品的功能元素排列成物理块以及块之间相互作用的方案”功能性——有助于整体绩效的单个操作和转换.物理–实现产品功能的零件、组件和子组件（通俗来讲，顺序是完成相应功能的零件 component--->组件 chunks---->产品，产品架构就是以实体组件来实现产品的各功能单元，并使各组件相互作用的配置方案） Product Architecture can be described as: 1."the **scheme** by which the functional elements of the product are arranged into physical chunks and by which the chunks interact” 2.**Functional** – individual operations and transformations that contribute to its overall performance 3.**Physical** – parts, components and subassemblies that implement the product’s functions
@ -2176,6 +2177,7 @@
- 首先是基本的相互作用关系 (fundamental interaction), 它与 示意图中连接各组件的那些线条相对应。例如， 一张纸从纸张托盘移动到打印装置中，因为 这种基本的相互作用关系是系统运行的基础，所以，在最早设计示意图时就应该计划好，并 要很好地加以理解。其次是附属的相互作用关系 (incidental interaction), 它是功能单元特定的 实体设置或组件之间具体的几何排列造成的。例如，纸张托盘中的传动器所引起的震动会干 扰打印墨盒在 X 轴的精确定位。 It is most likely that a different person or group will be assigned to design each chunk ¡ Because the chunks interact with one another in both planned and unintended ways, these different groups will have to coordinate their activities and exchange information ¡ To manage this coordination process better, the team should identify the known interactions between chunks during the system-level design phase There are two categories of interaction l Fundamental ¡ Those which correspond to the lines on the schematic that connect the chunks to one another ¡ These are the fundamental interactions of the systems operation l Incidental ¡ Those that arise because of l the particular physical implementation of functional elements, or l because of the geometric arrangement of the chunks ¡ An incidental interaction graph is used to document this type of interaction, see next slide - 首先是基本的相互作用关系 (fundamental interaction), 它与 示意图中连接各组件的那些线条相对应。例如， 一张纸从纸张托盘移动到打印装置中，因为 这种基本的相互作用关系是系统运行的基础，所以，在最早设计示意图时就应该计划好，并 要很好地加以理解。其次是附属的相互作用关系 (incidental interaction), 它是功能单元特定的 实体设置或组件之间具体的几何排列造成的。例如，纸张托盘中的传动器所引起的震动会干 扰打印墨盒在 X 轴的精确定位。 It is most likely that a different person or group will be assigned to design each chunk ¡ Because the chunks interact with one another in both planned and unintended ways, these different groups will have to coordinate their activities and exchange information ¡ To manage this coordination process better, the team should identify the known interactions between chunks during the system-level design phase There are two categories of interaction l Fundamental ¡ Those which correspond to the lines on the schematic that connect the chunks to one another ¡ These are the fundamental interactions of the systems operation l Incidental ¡ Those that arise because of l the particular physical implementation of functional elements, or l because of the geometric arrangement of the chunks ¡ An incidental interaction graph is used to document this type of interaction, see next slide
- -
- ## ==Topic 12 / 13: Detail Design and Prototypes== - ## ==Topic 12 / 13: Detail Design and Prototypes==
deck:: 2023t1/product/t12
collapsed:: true collapsed:: true
- 此阶段的部门职责是 #flashcard - 此阶段的部门职责是 #flashcard
id:: 648afdb9-8ccf-4d7e-854d-5a9e89be62b0 id:: 648afdb9-8ccf-4d7e-854d-5a9e89be62b0