Linux应用于嵌入式系统
UNIX引起了全然不同的情绪：因其能力和灵活性而受到一些人的青睐，但因其复杂且神秘的命令而受到另一些人的藐视。在计算世界里，UNIX已建立起一个褒义不一的声誉。
易用性
UNIX因其过于神秘、不易记忆和含义模糊的大量键盘命令而名声不佳，这些命令每个都有很多命令行开关，这可能造成昏药而不易记忆。它的SVR4版本拥有2000多个命令，其中很多功能可通过管道和重定向进行组合。这反映了UNIX的基本设计思想之一：生成数量很大的专用和模块化命令，把它们结合起来就能完成各种复杂的任务。
虽然UNIX过去基本上限于大学和应用开发公司中的软件专业人员使用，其复杂的命令行语法和由此而得到的灵活性被看作一个优点而不是问题。但是在面向商业的市场中使用UNIX，却产生了一个重大的缺陷——系统越灵活，它就变得越难学会和操作。
UNIX的原本（或脚本）语言提供某种形式的帮助。利用原本语言，系统管理员能很快地把系统裁剪成满足一组用户的需求。
克服UNIX神秘命令语言之困难的另一种方法是用图形用户接口GUI，如Motif,SunView或OpenLook。然而，图形用户接口在已经很复杂的系统上增添了另一层不兼容性问题。
Motif已经移植到差别非常大的不同体系结构上（由于它仿效Presentation Manager的风格），而且在外观与感觉上也许是最接近于诸如Microsoft Windows一类的PC接口。SunView由于有很大的装机数和很多应用程序员已熟悉按它的规范写软件，所以也是一种主流图形用户接口。
二进制兼容性
UNIX的销售者以某种羡慕的心情关注着DOS世界中可能的大量简装应用程序，并承诺不同系统的二进制兼容的应用程序即将面世。这些承诺远未让人满足。虽然二进制兼容性尚未获得，但现在不同机器上共享数据和应用程序正在变得更加容易。
可移植性
与多数操作系统源码相比，UNIX程序容易移植。它用C语言编写，而不用汇编语言，使用UNIX能移植到不同的体系结构上。但是把UNIX移植到一个新系统上也不是一件一蹴而就的事情，常常是要几个人年的工作，还可能造成故障和失灵，从而在性能上产生难以捉摸的不一致性。这些故障往往是难以识别与纠正的。
拥有你自己的计算机操作系统的源码，既有益，也有害；如果操作系统缺少某些所需功能，公司自己拥有源码能大大增强公司进行必要修改的能力。
另一方面，具有新的或修改特性的操作系统定制版本，在日后可能出现与更新的版本或购买的应用程序不兼容的问题。
为什么用LINUX？
用于接口、监控、通信和控制应用程序的职能专用系统和设备越来越要求高级的现代操作系统的这些服务。许多这样的系统需要如下的高级性能：高分辨率和用户友好的图形用户界面：TCP/IP链接；用可靠的闪存固态盘代替常规的磁盘机；支持32位的超高速CPU；使用大存储器阵列；以及似乎是无限容量的存储设备，包括CD-ROM和硬盘。
这不是以前的独立代码，自己写的核，或简单的老是DOS，那些日子已永远过去。
另外也考虑到硬件和芯片迅速加速的革新步伐——伴随着老设备相当快地淘汰。结合这两种情况，就能知道为什么对商用实时操作系统供应商而言，跟上硬件设备的不断出新已变成巨大的挑战。及时地支持最新设备，甚至不去理会不愿退让的、大力推销的逐渐过时的芯片组，你需要大量和不断的资材投入。如果商用实时操作系统供应商必须奋力紧跟硬件发展的话，那么编写独立的代码或写自己的核，这种单枪匹马的做法一定是毫无意义的。
因为选择范围很小，嵌入式系统的开发商面临这样的一种困境：
一方面，今天高度复杂的，且授权的智能嵌入式系统（基于最新的芯片和硬件性能）所需要的正式流行的高档操作系统（如Windows）提供的那种能力、精致性，以及通用性。
另一方面，嵌入式系统要求非常高的可靠性（不停机，无人照管的操作），加上有能力把操作系统改编成符合应用系统的独特的要求。
其窘境是：通用桌面操作系统（如Windows）不能很好地适应于类似设备的嵌入式系统的独特需求。然而，商用实时操作系统，虽然设计成满足嵌入式应用的可靠性和配置灵活性的要求，但由于他们缺乏标准化以及没有能力跟上技术的速度发展步伐，它们日益不合需要。
开发人员做什么？
幸运的是，一种新的、令人兴奋的选择系统已经出现：开放源码Linux。Linux 提供功能强大的和高级系统管理设施。丰富的设备支持，在可靠性和鲁棒性，以及广泛详尽的文档方面有极好的声誉。最好的（对系统开发人员而言）是Linux 不要钱——有完全免费的源代码。
Linux是不是像Windows那样太大以及需要系统资源太多，以致不能满足嵌入式系统的约束要求呢？与Windows不同，Linux本来就是模块化的，并且能够很容易缩减成紧缩配置，这种配置几乎与DOS差不多大，甚至能放到一张软盘上。此外，因为Linux源码是免费可用的，所以可以按照独特的嵌入式系统要求改编该操作系统。
这样，并不令人惊奇，开放源码Linux已建成了一个新的操作系统开发和支持范例，在那里数以千计的开发人员继续贡献于不断发展的Linux代码库。此外，几十家面向Linux的软件公司已经出现——他们热切支持那些为建立从工厂自动化到智能设备范围很广的应用系统的开发人员的要求。
小Linux
对许多嵌入式系统，为了适应诸如RAM、固态盘、处理机速度，以及功耗的约束，嵌入的Linux的主要任务是，使系统所需的资源最小。嵌入式操作系统可能需要从一个芯片盘或紧凑闪存固态盘上自举；或者自举和运行在没有显示器和键盘（“无头”操作）的环境，或经有以太网连接，从远程设备装入应用程序。
现成的小Linux有许多来源，其中有日益增多的面向应用的Linux配置和分发版，这些都被修改成适应于特定的应用。例如路由器、防火墙、互联网/网络设备、网络服务器、网关等。
你也可能选择建立你自己喜欢的嵌入式Linux，从一个标准分发版开始，略去不要的模块。虽然如此，还应该考虑从别人的工作配置基础上开始你的工作，因为他们的版本的源仅是完全合法的，而且也是被鼓励。
实时Linux
许多嵌入式系统需要对现实世界的一些事件可预测，并且受限响应。这样的实时系统包括工厂自动化、数据采集和控制系统、音频/视频应用，以及许多其他计算机化的产品和设备。什么是“实时系统”？通常接受的“实时”性能的定义是，现实世界时间必须在确定的、可预测的，以及在相对短的时间间隔内得到响应。
虽然Linux不是一个实时操作系统（Linux内核不提供所需要的事件优先级和抢占功能），但当前有几个扩充选项可用，这些选项把实时能力带给基于Linux的系统，最通常的方法是双内核方法。用这个方法，通用（非实时）OS 运行作为实时内核的一个任务。通用操作系统提供诸如磁盘读/写、LAN/通信、串行/并行I/O、系统初始化、内存管理等功能，而实时内核处理时限世界事件。你可以把这个看作两者兼得，因为它能够保持流行的通用操作系统好处，而增加了实时OS的能力。就Linux来说，你能保持与标准Linux兼容，而以非干扰的方式增加了实时功能。
当然，也可以专研并修改Linux，把改变成实时操作系统，因为它的源码是公开可用的，但如果这样做，你会面临这样严重缺点，即不论特性方面，还是驱动程序方面都不能与主流Linux同步前进。简言之，你的制定Linux将不能从Linux的不断进展中获得好处，而这种进展是世界范围内数以千计的开发人员共同协力的结果。
Linux是一个操作系统，它担当计算机系统硬件与软件间的通信服务，Linux 内核包含了你在任何操作系统所期望的所有特性。
原文：
Using Linux in Embedded Systems
UNIX evokes a wide range of emotions: loved by some for its power and flexibility, despised by others for its eomplex and arcane commands. UNIX has established a checkered reputation in the world of computing.
EASE OF USE
UNIX is infamous for its glut of arcane , non-mnemonic, and cryptic keyboard commands, each with many command-line switches, which can be incredibly confusing to remember. Its SVR 4 implementation contains more than 2,000 comands. Many of these functions can be combined, using pipes and redirection. This illustrates one of UNIX’s design fundamentals: the creation of a large assortment of very specialized and modular commands that can be combined to accomplish complex tasks.
While UNIX was essentially limited to use by software professionals at universities and in applications development houses, its complex command-line syntax and resulting flexibility were considered an advantage rather than a problem.But this same flexibility also creates a major drawback for using UNIX in a business-oriented market—the more flexible a system is, the more difficult it becomes to learn and operate.
UNIX’s script languages provide one form of help. Using scripts, a system administrator can tailor the system to a set of users’ needs quickly.
Another factor mitigating the difficulties of UNIX’s arcane command language are the Graphic User Interfaces(GUIs), such as Motif, SunView, or OpenLook. GUIs, however, place another level of incompatibility problems on what is already a complex system.
Motif has been ported to the most different architectures and (because it follows the Presentation Manager style ) is perhaps closest in look and feel to a PC interface such as Microsoft Windows. Sun View is also dominant because of its large installed base and the numbers of applications programmers who have become familiar with writing software to its specifications.
BINARY COMPATIBILITY
UNIX marketers have looked with some envy at the huge-base of shrink-wrapped applications available in the DOS world and have promised that binary-compatible applications for systems is just around the corner. These promises have yet to be met in any significant way. While binary compatibility is not yet available, it is getting easier to share data and applications across different machines.
PORTABILITY
Compared with most operating system sources, UNIX code is quite move UNIX to different architectures. But a UNIX port to a new system is not a trivial matter, offen taking several man-years of work, and can result in glitches and malfunctions, which may create very subtle inconsistencies in performance. These bugs are often difficult to identify and correct.
Having the source code available for your computer’s operating system is beneficial and detrimental: if the OS lacks certain desirable featuers, having the sources in-house greatly enhances a company’s ability to make necessary changes.
On the other hand, the customized version of the operating system, with its new or modified features may later present compatibility problems with newer releases or purchased application.
Why Linux?
Intelligent dedicated systems and applicances used in interface, monitoring , communications, and control applications increasingly demand the services of a sophisticated, state-of-the-art operating systems. Many such systems require advanced capabilities like: high resolution and user-friendly graphical user interfaces(GUIs); TCP/IP connectivity; substitution of reliable( and low power)flash memory solid state disk for conventional disk drives; support for 32-bit ultra-high-speed CPUs; the use of large memory arrays; and seemingly infinite capacity storage devices including CD-ROMs and hard disks.
This is not the stuff of yesteryear’s “standalone”code, “roll-your-own”kernels, or “plain old DOS”, No, those days are gone—forever.
Then too, consider the rapidly accelerating pace of hardware and chipset innovation—accompanied by extremely rapid obsolescence of the older https://www.doczj.com/doc/6d14500615.html,bine
these two, and you can see why it’s become an enormous challenge for commercial RTOS vendors to keep up with the constant churning of hardware devices . Supporting the newest devices in a timely manner—even just to stay clear of the unrelenting steamroller of chipset obsolescence–takes a large and constant resource commitment. If it’s a struggle for the commercial RTOS vendors to keep up, going it alone by writing standalone code or a roll-your-own kernel certainly makes no sense.
With the options narrowing, embedded system developers find themselves faced with a dilemma:
On the one hand, today’s highly sophisticated and empowered intelligent embedded systems—based on the newest chips and hardware capabilities—demand noting less than the power, sophistication, and currency of support provided by a popular high-end operating system like windows.
On the other hand, embedded systems demand extremely high reliability(for non-stop, unattended operation)plus the ability to customize the OS to match an application’s unique requirements.
The dilemma is: common desktop operating system ( such as Windows ) are not well adapted to the similar equipment to the unique needs of embedded system. However, commercial real-time operating system, although designed to meet the embedded application reliability and configuration flexibility requirements, but due to their lack of standardization and inability to keep up with the speed of technology development, which is undesirable.
Developers do?
Fortunately, a new, exciting alternative systems have emerged: the open source Linux. Linux provides powerful and advanced system management facilities. A wealth of equipment support, the reliability and robustness, and extensive documentation has an excellent reputation. The best ( for developers ) is Linux not money -- are completely free source code.
Linux is it right? Like Windows is too large and the need for system resources too much, so can not meet the requirements of embedded system? Unlike Windows, Linux is a modular, and can easily be reduced into compact configuration, this configuration is
almost almost DOS, even on a single floppy disk. In addition, because the Linux source code is freely available, so it can be in accordance with the unique requirements of embedded systems to adapt the operating system.
So, not surprisingly, the open source Linux has built a new operating system development and support the paradigm, where thousands of developers continue to contribute to the development of the Linux code library. In addition, dozens of Linux oriented software companies have emerged -- they eager to support those built from factory automation to intelligent devices are a wide range of application systems development personnel requirements.
Small Linux
For many embedded systems, such as RAM, in order to adapt to the solid state disk, processor speed, and power constraint, embedded Linux is a major task, the system resources required minimum. Embedded operating system may need from a chip disk or compact flash solid state disk bootstrap; or bootstrap and operation in the absence of the display and the keyboard (" headless" operation ) environment, or by the Ethernet connection, from a remote device in application.
Small ready-made Linux has many sources, including the increasing application oriented Linux configuration and distribution, these are modified into adapted to specific application. For example, router, firewall, Internet / network equipment, network server, gateway.
You may also choose to build your own like embedded Linux, from a standard distribution version, omitting don't module. Even so, also should be taken from the work of others on the basis of the allocation to begin your work, because their version of the source is perfectly legal, but also be encouraged.
Real time Linux
Many embedded systems need to real-world events can be predicted, and limited response. Such a system include factory automation, data acquisition and control system, audio / video applications, as well as many other computer products and equipment. What is" real time system"? The generally accepted" real-time" performance is defined, the real world time must be identified, predictable, and within a relatively short time
interval in response.
Although Linux is not a real-time operating system ( Linux cores do not provide the required priority and preemption features ), but currently a few expansion options available, these options to bring real-time ability based on Linux system, the most common method is the double kernel method. Using this method, the general ( real time) OS running as a real-time kernel of a task. General purpose operating system such as disk read / write, LAN / communication, serial / parallel I / O, system initialization, memory management functions, and the real-time kernel processing period of world events. You can see this as both, because it maintains the popular general operating system benefits, and increasing the real-time ability of OS. Linux, you can keep with the standard Linux compatibility, and non interference mode adds real-time function.
Of course, also can inquiry and modify Linux, change into a real-time operating system, because it is the source of publicly available, but if you do, you will face such serious shortcomings, namely whether characteristics, or the driver can not synchronize with the mainstream Linux. Jane's words, you will not make Linux from Linux development benefit, but this progress is within the scope of the world thousands of developers to collaborate on results.
Linux is an operating system, it play of computer system hardware and software communication service, the Linux kernel contains the operating system you in any desired all properties.
毕业设计（论文）外文文献翻译 文献、资料中文题目：软件开发概念和设计方法文献、资料英文题目： 文献、资料来源： 文献、资料发表（出版）日期： 院（部）： 专业： 班级： 姓名： 学号： 指导教师： 翻译日期： 2017.02.14
外文资料原文 Software Development Concepts and Design Methodologies During the 1960s, ma inframes and higher level programming languages were applied to man y problems including human resource s yste ms,reservation s yste ms, and manufacturing s yste ms. Computers and software were seen as the cure all for man y bu siness issues were some times applied blindly. S yste ms sometimes failed to solve the problem for which the y were designed for man y reasons including: ?Inability to sufficiently understand complex problems ?Not sufficiently taking into account end-u ser needs, the organizational environ ment, and performance tradeoffs ?Inability to accurately estimate development time and operational costs ?Lack of framework for consistent and regular customer communications At this time, the concept of structured programming, top-down design, stepwise refinement，and modularity e merged. Structured programming is still the most dominant approach to software engineering and is still evo lving. These failures led to the concept of "software engineering" based upon the idea that an engineering-like discipl ine could be applied to software design and develop ment. Software design is a process where the software designer applies techniques and principles to produce a conceptual model that de scribes and defines a solution to a problem. In the beginning, this des ign process has not been well structured and the model does not alwa ys accurately represent the problem of software development. However,design methodologies have been evolving to accommo date changes in technolog y coupled with our increased understanding of development processes. Whereas early desig n methods addressed specific aspects of the
农业产业化外文翻译文献(文档含中英文对照即英文原文和中文翻译)
农业产业化：从农场到交易市场 Mark R. Edwards and Clifford. J. Shultz 摘要 农业产业化就是农业以市场需求为导向，有效的满足客户以及市场要求的一系列的链条。这种变革需要一个更广泛的概念化和更准确的定义，传达一个致力于创造价值和可持续利用食物，纤维，可再生资源的更有活力，系统性，综合性和纪律性的系统。我们讨论的力量，推动这一转移到市场，提供了新的和更具有代表性农业产业化的定义，提供模型以说明一些最引人注目的趋势，并阐明这些模型关键因素和影响。 关键词：农业产业化的定义，概念模型，市场为中心，市场体系
1 绪论 农业产业化在1955年开始作为一个独特的研究领域，当时约翰.戴维斯将它定义为：农业产业化是以农场生产为中心，然后商品化。这个定义当时是最适当的，那是农业行动的重点是最大限度地生产食物和纤维。戴维斯和高德博格用新鲜的见解，将农业产业化定义为:制造和分销农场用品：在该农场生产经营、储存、加工、分销所有的农产品的商品和物品所涉及的所有业务的总和。类似的定义也有其他的人提出，如唐尼和埃里克森：农业产业化，包括所有这些业务和管理活动由公司提供投入到农业部门，生产农产品，运输，金融，处理农产品的全部过程。 这些传统的定义，随着时间的推移，对农场或生产的单位所反映农业产业化的焦点，如农业交易中心已数十年之久。今天，一个就业散点图显示，虽然超过百分之三十的就业机会农业产业化提供的，少于百分之一的人直接参与农场生产。农业产业化已不再是以农场为中心。二十一世纪农业产业化包含了更广泛的一系列行动，主要是外围行动，包括以市场为导向的可持续利用食物，纤维，和可再生资源。
通信工程学院 毕业设计外文翻译 毕业设计题目基于ANDRIO的智能家居 系统的设计与实现 外文题目UBIQUITOUS SMART HOME SYSTEM USING ANDROID APPLICATION 专业：通信工程 学号： 学生姓名： 指导教师姓名： 指导教师职称：副教授 日期：2015 年 1 月10 日
International Journal of Computer Networks & Communications (IJCNC) V ol.6, No.1, January 2014 基于Android应用的无处不在的智能家居系统 Shiu Kumar Department of Information Electronics Engineering, Mokpo National University, 534-729, Mokpo, South Korea 摘要 本文提出了一种灵活独立的，低成本的智能家居系统，它是基于Android应用与微web服务器通信，不仅仅提供交换功能。Arduino以太网的使用是为了避免使用个人电脑从而保证整个系统成本最低，语音激活时用来实现切换功能的。光开关，电源插头，温度传感器，湿度传感器，电流传感器，入侵检测传感器，烟雾/气体传感器和警报器等这些设备集成在系统中，表明了所提出的智能家居系统的有效性和可行性。经过检测，智能家居应用程序可以成功地进行智能家居操作，例如开关功能，自动环境监测，和入侵监测，在监测到有不法入侵后，系统会自动发送一个邮件，并响警笛。 关键字： Android智能手机，智能家居，物联网（loTs），远程控制 1.引言 随着移动设备受欢迎程度的不断增长和人们日常生活中对无处不在的先进的移动应用的功能需求不断增加，利用Web服务是提供远程访问服务的最开放和可互操作的方式，并且使应用程序能够彼此通信。一个有吸引力的市场产品自动化和网络化是忙碌的家庭和有生理缺陷的个人的代表。 loTs可以被描述为连接智能手机，网络电视，传感器等到互联网，实现人们之间沟通的新形势。过去几年中loTs的发展，创造了一个新层面的世界。这使得人们可以在任何时间，任何地点，联通任何期望的东西。物联网技术可用于为智能家居创建新的概念和广阔的空间，以提供智能，舒适的发展空间和完善生活质量。 智能家居是一个非常有前途的领域，其中有各种好处，如增加提供舒适性，更高安全性，更合理地使用能源和其他资源。这项研究的应用领域非常重要，未来它为帮助和支持有特殊需求老的人和残疾人士提供了强有力的手段。设计一个智能家居系统时需要考虑许多因素，该系统应该是经济实惠的，是可伸缩的，使得新的设备可以容易地集成到系统中，此外，它应该是用户友好的。 随着智能手机用户的急剧增加，智能手机已经逐渐变成了具备所有功能的便携式设备，为人们提供了日常使用。本文介绍了一种低成本的控制和监视家居环境控制的无线智能家居系统。利用Android设备，可以通过一个嵌入式微Web服务器与实际的IP连接，访问和控制电器和远程的其它设备，这可以利用任何支持Android的设备。Arduino Ethernet 用于微Web服务器从
会计内部控制中英文对照外文翻译文献(文档含英文原文和中文翻译)
内部控制透视：理论与概念 摘要：内部控制是会计程序或控制系统，旨在促进效率或保证一个执行政策或保护资产或避免欺诈和错误。内部是一个组织管理的重要组成部分。它包括计划、方法和程序使用，以满足任务，目标和目的，并在这样做，支持基于业绩的管理。内部控制是管理阶层的平等与控制可以帮助管理者实现资源的预期的有效管理的结果通过。内部控制应减少或违规错误的风险关联未被发现的，但设计和建立有效的内部控制不是一个简单的任务，不可能是一个实现通过快速修复短套。在此讨论了内部文件的概念的不同方面的内部控制和管制。 关键词：内部控制，管理控制，控制环境，控制活动，监督 1、介绍 环境需要新的业务控制变量不为任何潜在的股东和管理人士的响应因子为1，另外应执行/她组织了一个很大的控制权。控制是管理活动的东西或以上施加控制。思想的产生和近十年的发展需要有系统的商业资源和控制这种财富一个新的关注。主题之一热一回合管制的商业资源是分析每个控制成本效益。 作为内部控制和欺诈的第一道防线，维护资产以及预防和侦查错误。内部控制，我们可以说是一种控制整个系统的财务和其他方面的管理制定了为企业的顺利运行;它包括内部的脸颊，内部审计和其他形式的控制。 COSO的内部控制描述如下。内部控制是一个客观的方法用来帮助确保实现。在会计和组织理论，内部控制是指或目标目标的过程实施由组织的结构，工作和权力流动，人员和具体的管理信息系统，旨在帮助组织实现。这是一种手段，其中一个组织的资源被定向，监控和测量。它发挥着无形的（重要的作用，预防和侦查欺诈和保护组织的资源，包括生理（如，机械和财产）和乙二醇，声誉或知识产权，如商标）。在组织水平，内部控制目标与可靠性的目标或战略的财务报告，及时反馈业务上的成就，并遵守法律，法规。在具体的交易水平，内部控制是指第三方采取行动以实现一个具体目标（例如，如何确保本组织的款项，在申请服务提供有效的。）内部控制程序reduce程变异，导
Microcomputer Systems Electronic systems are used for handing information in the most general sense; this information may be telephone conversation, instrument read or a company’s accounts, but in each case the same main type of operation are involved: the processing, storage and transmission of information. in conventional electronic design these operations are combined at the function level; for example a counter, whether electronic or mechanical, stores the current and increments it by one as required. A system such as an electronic clock which employs counters has its storage and processing capabilities spread throughout the system because each counter is able to store and process numbers. Present day microprocessor based systems depart from this conventional approach by separating the three functions of processing, storage, and transmission into different section of the system. This partitioning into three main functions was devised by Von Neumann during the 1940s, and was not conceived especially for microcomputers. Almost every computer ever made has been designed with this structure, and despite the enormous range in their physical forms, they have all been of essentially the same basic design. In a microprocessor based system the processing will be performed in the microprocessor itself. The storage will be by means of memory circuits and the communication of information into and out of the system will be by means of special input/output(I/O) circuits. It would be impossible to identify a particular piece of hardware which performed the counting in a microprocessor based clock because the time would be stored in the memory and incremented at regular intervals but the microprocessor. However, the software which defined the system’s behavior would contain sections that performed as counters. The apparently rather abstract approach to the architecture of the microprocessor and its associated circuits allows it to be very flexible in use, since the system is defined almost entirely software. The design process is largely one of software engineering, and the similar problems of construction and maintenance which occur in conventional engineering are encountered when producing software. The figure1.1 illustrates how these three sections within a microcomputer are connected in terms of the communication of information within the machine. The system is controlled by the microprocessor which supervises the transfer of information between itself and the memory and input/output sections. The external connections relate to the rest (that is, the non-computer part) of
附录 一、英文原文 Hardware/Software Design and Development Process Everett Lumpkin and Michael Gabrick Delphi Corporation, Electronics and Safety Division INTRODUCTION Process and technology advancements in the semiconductor industry have helped to revolutionize automotive and consumer electronics. As Moore’s Law predicted, the increase in complexity and operating frequencies of today’s integrated circuits have enabled the creation of system applications once thought to be impossible. And systems such as camera cell phones, automotive infotainment systems, advanced powertrain controllers and handheld personal computers have been realized as a result. In addition to the increases in process technology, the Electronic Design Automation (EDA) industry has helped to transform the way semiconductor integrated circuits (IC) and subsequent software applications are designed and verified. This transformation has occurred in the form of design abstraction, where the implementation continues to be performed at higher levels through the innovation of design automation tools. An example of this trend is the evolution of software development from the early days of machine-level programming to the C++ and Java software written today. The creation of the assembler allowed the programmer to move a level above machine language, which increased the efficiency of code generation and documentation, but still tied the programmer to the underlying hardware architecture. Likewise, the dawn of C / C++ compilers, debuggers and linkers helped to move the abstraction layer further away from the underlying hardware, making the software completely platform independent, easier to read, easier to debug and more efficient to manage. However, a shift to higher levels of software abstraction has not translated to a reduction in complexity or human resources. On the contrary, as integrated systems have become more feature rich, the complexity of the operating system and corresponding applications have increased rapidly, as have the costs associated with the software implementation and verification activities. Certainly the advancements in embedded software tools such as static code checkers, debuggers and hardware emulators have helped to solve some of the software verification problems, but software verification activities have become more time and resource consuming than the actual software creation. Time-to-market constraints have pushed software verification activities to the system-level, and led to a greater demand for production hardware to be made available earlier in
外文翻译 原文 Title:Agricultural Industrialization Organization of Marketing Strategy Analysis Material source:2010 International Conference on Industry Engineering and Management Author:Zhao Yanhong, Ren Aihua Abstraet:Agricultural industrialization is the development direction of world agriculture, it is also the main form of the agricultural operation in developed countries. Vigorously develop the industrialization of agriculture is to enhance the competitiveness of China’s agricultu re is an effective means of marketing innovation in agriculture. It is related to the industrialization of agriculture an important factor in business success. In this paper, product, place, promotion, three organizations, the face of the industrialization of agriculture marketing innovation of the corresponding development proposals. Keywords:Product;Channel Innovation;Promotion 1 Introduction Although China has already established a number of agricultural industrialization organization, but very few successful cases, reason, the product can not sell that influence their development, an important factor. At present the industrialization of agriculture organizations in product development, sales channels and marketing methods. There are many ways to solve urgent problems, we can say, marketing has become a bottleneck restricting development of the organization. In this Paper, the development of marketing concept, mainly based on the content of the theory of 4P, from development to meet consumer demand for products. Innovation in the channel, flexible use of marketing mix and so the organization seeking to promote the industrialization of agriculture marketing of innovative measures. 2 Development of Products to Meet Consumer Demand 4C theory holds that companies should give top priority to the pursuit of customer satisfaction, then theagricultural industry of the organization must first develop a customer satisfaction products. Marketing believes that demand for the
本科毕业设计（论文）外文参考文献译文及原文 学院信息工程学院 专业测控技术与仪器 （光机电一体化方向) 年级班别 2011级（1）班 学号 学生姓名 指导教师
目录 1应用程序基础 (1) 1.1应用程序组件 (1) 1.2激活组件：intent (3) 1.3 关闭组件 (4) 1.4manifest文件 (5) 1.5Intent过滤器 (6) 1.6基于XML的布局 (7) 1Application Fundamentals (8) 1.1 Application Components (8) 1.2Activating components:intent (11) 1.3 Shutting down components (12) 1.4 The manifest file (13) 1.5Intent filters (14) 1.6XML-Based Layout (15)
1 应用程序基础 Android应用程序使用Java编程语言开发。aapt工具把编译后的Java代码连同应用程序所需的其他数据和资源文件一起打包到一个Android包文件中，这个文件使用.apk作为扩展名。此文件是分发并安装应用程序到移动设备的载体；是用户下载到他们的设备的文件。单一.apk文件中的所有代码被认为是一个应用程序。 从多个角度来看，每个Android应用程序都存在于它自己的世界之中： 1 默认情况下，每个应用程序均运行于它自己的Linux进程中。当应用程序中的任何代码需要被执行时，Android启动此进程，而当不再需要此进程并且其它应用程序又请求系统资源时，则就关闭了这个进程。 2 每个进程都有其独有的虚拟机（VM），所以应用程序代码与所有其它应用程序代码是隔离运行的。 3 默认情况下，每个应用程序均被赋予一个唯一的Linux用户ID，并加以权限设置，使得应用程序的文件仅对此用户及此应用程序可见——尽管也有其它的方法使得这些文件同样能为其他应用程序所访问。 1.1 应用程序组件 Android的一个核心的特性就是一个应用程序可以使用其它应用程序的元素（如果那个应用程序允许的话）。例如，如果你的应用程序需要显示一个图片卷动列表，而另一个应用程序已经开发了一个合用的而又允许别的应用程序使用的话，你可以直接调用那个卷动列表来完成工作，而不用自己再开发一个。你的应用程序并没有吸纳或链接其它应用程序的代码。它只是在有需求的时候启动了其它应用程序的那个功能部分。 为达到这个目的，系统必须能够在一个应用程序的任何一部分被需要时启动一个此应用程序的进程，并将那个部分的Java对象实例化。因此，不像其它大多数系统上的应用程序，Android应用程序并没有为应用程序提供一个单独的入口点（比如说，没有main()函数），而是为系统提供了可以实例化和运行所需的必备组件。一共有四种组件类型： (1)Activity
附录A
附录B 如何监测内部控制 内部控制是任何组织有效运行的关键,董事会、执行长和内部审计人员都为实现这个企业的目标而工作;该内部控制系统是使这些团体确保那些目标的达成的一种手段。控制帮助一个企业有效率地运转。此外,运用一种有效的风险系统,风险可被降低到最小。同时,控制促进经营和与经营有关的信息的可靠性。全美反舞弊性财务报告委员会发起组织(COSO；1992) 在它发布的具有开创性的文件《内部控制整合框架》中,将内部控制定义为：企业风险管理是一个过程，受企业董事会、管理层和其他员工的影响，包括内部控制及其在战略和整个公司的应用，旨在为实现经营的效率和效果、财务报告的可靠性以及法规的遵循提供合理保证。该委员会还指出,一个的内部控制的系统包括五个要素。它们是：控制环境、风险评估、信息和沟通、控制活动、监控。 COSO的定义及五个要素已被证明确实对不同的团体,如董事会和首席执行官起到作用。这些群体对内部控制系统的监管以及系统设计与运行有责任。而且,内部审计人员已经发现COSO的指导是有用的。这群人员可能会被董事会或管理层要求去测试控制。COSO最近发布的一份讨论文件，指出五个要素监控,其中的五个要素的确定在1992 frame work COSO原本。中国发展简报的题为《内部控制-整合框架：内部控制体系监督指南》(COSO，2007)。在文件中,COSO 强调监控的重要性，以及这些信息常常被没有充分利用。 因为董事会、执行长,和内部审计人员都在一个公司的内部控制中扮演着重要角色，内部控制的各要素,包括监测,都对所有的团体有着非常重要的意义。同时,外审计人员对监测有兴趣。《萨班斯-奥克斯利法案》（2002）为外部审计师创建了一个新的监督体制。所有的五个要素,包括监测,必须加以考虑。另外,内部控制审计必须结合对财务报告的检查。在一体化审计之前，在首席执行官的领导下，也许也在内部审计活动的支持下的管理，评估了内控制体系的有效性。随后外部审计人员对控制出具意见。起监督角色的董事会，将阅读内部审计、管理层和首席执行官出具的报告。文件关于监测对每一个团体的指导起了帮助,因为他们分别为各自的角色而劳动。 第一，什么是监测。监测的组成可评估内部控制系统在过去一段时间发挥效用的质量。其对控制功能的评估有助于企业确定其控制在有效地运作中。在执行监测活动时，相关人员参与审查系统的设计及其运行效果。这种检查必须进行及时,目的是为了提供给企业最大的利益。管理层负责做出适当的行动以回应这些结果。当事人对内部控制有兴趣,可以充分依赖这个内部控制系统,如果合适的监
外文文献资料 Distributed Temperature Sensor 1.Sensor introduction 1.1 Temperature sensor background In the human living environment, temperature playing an extremely important role。No matter where you live, engaged in any work, ever-present dealt with temperature under. Since the 18th century, industry since the industrial revolution to whether can master send exhibition has the absolute temperature touch. In metallurgy, steel, petrochemical, cement, glass, medicine industry and so on, can say almost eighty percent of industrial departments have to consider the factors with temperature. Temperature for industrial so important, thus promoting the development of the temperature sensor. 1.2 Temperature sensor development Major general through three sensor development phase: analog integrated temperature sensor. The sensor is taken with silicon semiconductor integrated workmanship, therefore also called silicon sensor or monolithic integrated temperature sensor. Such sensing instruments have single function (only measuring temperature), temperature measurement error is smaller, price low, fast response, the transmission distance, small volume, micro-consumption electronic etc, suitable for long distance measurement temperature, temperature control, do not need to undertake nonlinear calibration, peripheral circuit is simple. It is currently the most common application at home and abroad, an integrated sensor。Typical products have AD590 AD592, TMP17, LM135, etc.jAnalog integrated temperature controller. Analog integrated temperature controller mainly include temperature control switch, programmable temperature controller, a typical product have LM56, AD22105 and MAX6509. Some increase strength type integrated temperature controller (for example TC652/653) also contains the A/D converter and cure good sequence, this process with the intelligent temperature sensor some similarities. But it is not its system, work by micro processing device control, this is the main difference between. Intelligent temperature sensor. intelligent temperature sensor (also called digital temperature degrees sensor) is in the mid 1990s launch. It is microelectronics technology, computer technology and the dynamic testing technology (ATE) crystallization. Intelligent temperature sensor internal contain temperature sensor, A/D converter, signal processor,
软件开发外文翻译本页仅作为文档页封面，使用时可以删除 This document is for reference only-rar21year.March
Requirements Phase The chances of a product being developed on time and within budget are somewhat slim unless the members of the software development team agree on what the software product will do. The first step in achieving this unanimity is to analyze the client’s current situation as precisely as possible. For example, it is inadequate to say, “ They need a computer-aided design system because they claim their manual design system, there is lousy. “ Unless the development team knows exactly what is wrong with the current manual system, there is a high probability that aspects of the new computerized system will be equally “lousy. “ Similarly, if a personal computer manufacturer is contemplating development of a new operating system, the first step is to evaluate the firm’s current operating system and analyze carefully exactly why it is unsatisfactory. To take an extreme example, it is vital to know whether the problem exists only in the mind of the sales manager, who blames the operating system for poor sales, or whether users of the operating system are thoroughly disenchanted with its functionality and reliability. Only after a clear picture of the present situation has been gained can the team attempt to answer the critical question, What must the new product be able to do The process of answering this question is carried out during the requirements phase. A commonly held misconception is that , during the requirements phase, the developers must determine what software the client wants. On the contrary, the real objective of the requirements phase is to determine what software the client needs. The problem is that many clients do not know what they need. Furthermore, even a client who has a good idea of what is needed may have difficulty in accurately conveying these ideas to the developers, because most clients are less computer literate than the members of the development team.