CS4101嵌入式系统概论DesignandDevelopment.ppt

  1. 1、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。。
  2. 2、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  3. 3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
CS4101嵌入式系统概论DesignandDevelopment.ppt

CS4101 嵌入式系統概論 Design and Development 金仲達教授 國立清華大學資訊工程學系 Recap More and more physical things will be augmented or embedded with computing Things become “smarter” Computing becomes ubiquitous An embedded system is a system that is embedded with programmable computers for specific applications of that system Why embedded systems? Faster, more flexible development at lower cost More complex functionalities Suppose You Have a Product Idea To develop a device that can record, for each day, the number of stairs that the user has climbed up or down From this number, we can then calculate the amount of CO2 saved and calories burned Let us call this device stair counter How to start from here? Typical Design Flow Requirements Plain language description of what the user wants and expects to get e.g. to develop a device that can record, for each day, the number of stairs that the user has climbed up or down Describe how the end product is used by the user May be developed in several ways: talking directly to customers talking to marketing representatives providing prototypes to users for comment Requirements Often need to know target customers and business model Stair counter as an add-on of cell phone Stair counter as a consumer product Stair counter as a gift … Requirements Functional requirements: Internals as a black box and describe only the outputs as a function of input; Show number of stairs climbed up or down Show amount of CO2 saved Do not count in other cases Non-functional requirements: Performance, reliability, etc. Size, weight, etc. Power consumption Cost … Requirements Form Specification More precise, usually quantitative description of the system: Should not imply a particular architecture List assumptions e.g., update screen 0.25 sec after each step, error rate 95%, cost $300 May include functional and non-functional elements May be executable or may be in mathematical form for proofs e.g. UML (Unified Modeling Language) Architecture Design Wh

文档评论(0)

magui + 关注
实名认证
内容提供者

该用户很懒,什么也没介绍

版权声明书
用户编号:8140007116000003

1亿VIP精品文档

相关文档