tomorrow presentation

本文深入探讨了模块设计的核心原则,包括抽象、信息隐藏、分离关注点等,并详细阐述了如何将这些原则应用于实际的模块设计中,以提高代码的可维护性和复用性。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

0. abstraction
–TheAPI should abstract the behavior of the module to the extent possible
»Definethe “essence” of the module. (abstraction)
»Avoidunnecessary publishing of implementation details. (information hiding)
»Insteadof using the approach of putting something in the API in case someone may need it, take the approach ofnot putting something in the API unless someone really needs it.

1. Information Hiding
–Designdecisions are “hidden” from other modules.
»Preventsother modules from becoming dependent upon non-essential aspects of yourmodule.
»Allowsthe design decision to be changed with minimal “ripple effect”.

Requires the designer to recognize design decisions that are likely to change or that are not an essential aspect of the module being designe

隐藏/封装:  一个设计得好的模块可以将它所有的实现细节隐藏起来,彻底地将提供给外界的API和自己的实现分隔开来。这样一来,模块与模块之间就可以仅仅通过彼此的API相互通信,而不理会模块内部的工作细节。

advantages:

1.1 使各个子系统之间脱耦,从而允许他们独立地被开发、优化、使用、阅读以及修改

1.2 虽然信息隐藏本身并不能带来更好的性能,但是它可以使性能的有效调整变得容易,一旦确认某个模块是性能的障碍时,设计人员可以针对这个模块本身进行优化,而不必担心影响到其他的模块。

1.3 信息隐藏可以促进软件的复用。由于每一个模块都不依赖与其他模块而存在,因此每个模块都可以独立地在其他的地方使用。 一个系统的规模越大,信息隐藏就越是重要,其威力也就越明显。

1.4 迪米特法则的主要用意是控制信息的过载。使用时注意:

a) 在类的划分上,应当创建有弱耦合的类。类之间的耦合越弱,就越有利于复用。一旦被修改,不会对有关系的类造成波及。

b) 每一个类都应当尽量降低成员的访问权限。

c) 在类的设计上,只要有可能,一个类应当设计成不变类。

d) 在对其他类的引用上,一个对象对其对象的引用应降到最低。


Separation of Concerns
–separating a program into distinctfeatures that overlap as little as possible 同样是脱耦!--易于阅读、修改。。。
–eases understanding by supporting the ability to “focus” on a feature


2. A basa module contains three major components:
–Makefile_<module>.mk
–API
–Implementation

The API is in a separate subproject.
–Thisallows other projects to pull in the API without pulling in the implementation.
–Thisis especially critical if test code for clients of the module need to “stub out” theAPI for unit testing purposes.

A module’s API is broken into multiple files:
–Configurabletypes
–Callouts: decouple, for the module && by the module???
–Typesshared by all of these

3. void Application_Initialization(void)

{

   SAL_Thread_Attr_T thread_attributes;

   SAL_Config_T      sal_configuration;

   bool              status_ok;

   SAL_Thread_Id_T   thread_id;


   APM_Get_SAL_Config(&sal_configuration);


   status_ok = SAL_Init(&sal_configuration);

  

   SAL_Init_Thread_Attr(&thread_attributes);

   APM_Get_Thread_Attr(&thread_attributes);


   thread_id = SAL_Create_Thread(APM_Task,

                                     NULL,&thread_attributes);

   PBC_Ensure((APM_THREAD_ID == thread_id),

              “Failed to create APM_THREAD_ID”);

 

   SAL_Run();

}


Fora single-process system, this is handled by the “application manager” block(sample code shown to the right)
The application manager is responsible for starting the other threads in the systemin a controlled manner
In a multi-process system, each process would perform a similar sequence


The type SAL_Application_Id_T is declared by the system and is the static list of all “applications” in the system that use XSAL.

4. MOST
4.1Explain the plug-n-playconcept of MOST
MOST is a ring network where nodes can join or leave without disturbing the remainderof the network
4.2 a synchronous network: transport data and clock signal
4.3 FBlock
MOST defines Functional units, called Function Blocks(FBlocks) which are standardized,object-oriented interfaces to the respective applications.
–Variousdevices from different manufacturers must interact in a sophisticated way inmodern multimedia systems.

The Net Block is a special type of Function Block
It provides functions related to the entire device
Every device must have at least twoFunction Blocks, one being the Net Block

A MOST Device may contain multiple components such as AM/FM Tuners, CD player, Amplifier, Tape Player, etc.
Each of these components requires a Function Block appropriate to  that component

A MOST Device will always include at least one Transceiver and a Physical Interface


内容概要:本文深入解析了扣子COZE AI编程及其详细应用代码案例,旨在帮助读者理解新一代低门槛智能体开发范式。文章从五个维度展开:关键概念、核心技巧、典型应用场景、详细代码案例分析以及未来发展趋势。首先介绍了扣子COZE的核心概念,如Bot、Workflow、Plugin、Memory和Knowledge。接着分享了意图识别、函数调用链、动态Prompt、渐进式发布及监控可观测等核心技巧。然后列举了企业内部智能客服、电商导购助手、教育领域AI助教和金融行业合规质检等应用场景。最后,通过构建“会议纪要智能助手”的详细代码案例,展示了从需求描述、技术方案、Workflow节点拆解到调试与上线的全过程,并展望了多智能体协作、本地私有部署、Agent2Agent协议、边缘计算插件和实时RAG等未来发展方向。; 适合人群:对AI编程感兴趣的开发者,尤其是希望快速落地AI产品的技术人员。; 使用场景及目标:①学习如何使用扣子COZE构建生产级智能体;②掌握智能体实例、自动化流程、扩展能力和知识库的使用方法;③通过实际案例理解如何实现会议纪要智能助手的功能,包括触发器设置、下载节点、LLM节点Prompt设计、Code节点处理和邮件节点配置。; 阅读建议:本文不仅提供了理论知识,还包含了详细的代码案例,建议读者结合实际业务需求进行实践,逐步掌握扣子COZE的各项功能,并关注其未来的发展趋势。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值