毕设外文翻译--单片机基础

毕设外文翻译--单片机基础
毕设外文翻译--单片机基础

毕设外文翻译--单片机基础

毕业设计(论文)外文资料翻译

系别: 电气系

专业: 电气工程及其自动化

班级:

姓名:

学号:

外文出处: Atomation Professional English Course

(用外文写) Pressed By Machinery Industry Press

附件:1、外文原文;2、外文资料翻译译文。

指导教师评语:

签字:

年月日注:请将该封面与附件装订成册。

1、外文原文(复印件)

A: Fundamentals of Single-chip Microcomputer

The single-chip microcomputer is the culmination of both the development of the digital computer and the integrated circuit arguably the tow most significant inventions of the 20th century [1].

These tow types of architecture are found in single-chip microcomputer. Some employ the split program/data memory of the Harvard architecture, shown in Fig.3-5A-1, others follow the philosophy, widely adapted for general-purpose computers and microprocessors, of making no

logical distinction between program and data memory as in the Princeton architecture, shown in Fig.3-5A-2.

In general terms a single-chip microcomputer is characterized by the incorporation of all the units of a computer into a single device, as shown in Fig3-5A-3.

Program

Input& memory

Output

CPU unit

Data

memory

Fig.3-5A-1 A Harvard type

Input&

Output CPU memory

unit

Fig.3-5A-2. A conventional Princeton computer

External Timer/ System Timing Counter clock components

Serial I/O

Reset ROM

Prarallel

I/O

Interrupts RAM

CPU

Power

Fig3-5A-3. Principal features of a microcomputer

Read only memory (ROM).ROM is usually for the permanent,

non-volatile storage of an applications program .Many microcomputers and microcontrollers are intended for high-volume applications and hence the economical manufacture of the devices requires that the contents of the program memory be committed permanently during the manufacture of chips . Clearly, this implies a rigorous approach to ROM code development since changes cannot be made after manufacture .This development process may involve emulation using a sophisticated development system with a hardware emulation capability as well as the use of powerful software tools.

Some manufacturers provide additional ROM options by including in their range devices with (or intended for use with) user programmable memory. The simplest of these is usually device which can operate in a microprocessor mode by using some of the input/output lines as an address and data bus for accessing external memory. This type of device can behave functionally as the single chip microcomputer from which it

is derived albeit with restricted I/O and a modified external circuit. The use of these ROMless devices is common even in production circuits where the volume does

not justify the development costs of custom on-chip ROM[2];there can still be a significant saving in I/O and other chips compared to a conventional microprocessor based circuit. More exact replacement for ROM devices can be obtained in the form of variants with 'piggy-back'

EPROM(Erasable programmable ROM )sockets or devices with EPROM instead

of ROM 。These devices are naturally more expensive than equivalent ROM device, but do provide complete circuit equivalents. EPROM based devices are also extremely attractive for low-volume applications where they provide the advantages of a single-chip device, in terms of on-chip I/O, etc. ,with the convenience of flexible user programmability.

Random access memory (RAM).RAM is for the storage of working

variables and data used during program execution. The size of this memory varies with device type but it has the same characteristic width (4,8,16 bits etc.) as the processor ,Special function registers, such as stack pointer or timer register are often logically incorporated into

the RAM area. It is also common in Harard type microcomputers to treat the RAM area as a collection of register; it is unnecessary to make distinction between RAM and processor register as is done in the case of a microprocessor system since RAM and registers are not usually

physically separated in a microcomputer .

Central processing unit (CPU).The CPU is much like that of

any microprocessor. Many applications of microcomputers and microcontrollers involve the handling of binary-coded decimal (BCD) data (for numerical displays, for example) ,hence it is common to find that the CPU is well adapted to handling this type of data .It is also common to find good facilities for testing, setting and resetting individual

bits of memory or I/O since many controller applications involve the turning on and off of single output lines or the reading the single line.

These lines are readily interfaced to two-state devices such as switches, thermostats, solid-state relays, valves, motor, etc.

Parallel input/output. Parallel input and output schemes vary somewhat in different microcomputer; in most a mechanism is provided to at least allow some flexibility of choosing which pins are outputs and which are inputs. This may apply to all or some of the ports. Some I/O lines are suitable for direct interfacing to, for example, fluorescent displays, or can provide sufficient current to make interfacing other components straightforward. Some devices allow an I/O port to be configured as a system bus to allow

off-chip memory and I/O expansion. This facility is potentially

useful as a product range develops, since successive enhancements may become too big for on-chip memory and it is undesirable not to build on the existing software base.

Serial input/output .Serial communication with terminal

devices is common means of providing a link using a small number of lines. This sort of communication can also be exploited for interfacing special function chips or linking several microcomputers together .Both the common asynchronous synchronous communication schemes require protocols that provide framing (start and stop) information .This can be implemented as a hardware facility or U(S)ART(Universal(synchronous) asynchronous receiver/transmitter) relieving the processor (and the applications programmer) of this low-level, time-consuming, detail. t is merely necessary to selected a baud-rate and possibly other options

(number of stop bits, parity, etc.) and load (or read from) the serial transmitter (or receiver) buffer. Serialization of the data in the appropriate format is then handled by the hardware circuit.

Timing/counter facilities. Many application of single-chip

microcomputers require accurate evaluation of elapsed real

time .This can be determined by careful assessment of the execution time of each branch in a program but this rapidly becomes inefficient for all but simplest programs .The preferred approach is to use timer circuit that can independently count precise time increments and generate an interrupt after a preset time has elapsed .This type of timer is usually arranged to be reloadable with the required count .The timer then decrements this value producing an interrupt or setting a flag when the counter reaches zero. Better timers then have the ability to automatically reload the initial count value. This relieves the programmer of the responsibility of reloading the counter and assessing elapsed time before the timer restarted ,which otherwise wound be necessary if continuous precisely timed interrupts were required (as in a clock ,for example).Sometimes associated with timer is an event counter. With this facility there is usually a special input pin ,that can drive the counter directly.

Timing components. The clock circuitry of most microcomputers requires only simple timing components. If maximum performance is required,a crystal must be used to ensure the maximum clock frequency is approached but not exceeded. Many clock circuits also work with a

resistor and capacitor as low-cost timing components or can be driven from an external source. This latter arrangement

is useful is external synchronization of the microcomputer is required.

WORDS AND TERMS

culmination n.顶点

spilt adj.分离的

volatile n. 易变的

commit v.保证

albeit conj.虽然

custom adj.定制的

variant adj.不同的

piggy-back adj.背负式的

socket n. 插座

B:PLC[1]

PLCs (programmable logical controller) face ever more complex challenges these days . Where once they quietly replaced relays and gave an occasional report to a corporate mainframe, they are now grouped into cells, given new job and new languages, and are forced to compete against a growing array of control products. For this year's annual PLC technology update ,we queried PLC makers on these topics and more .

Programming languages

Higher level PLC programming languages have been around for some

time ,but lately their popularity has mushrooming. "As Raymond Leveille,

vice president & general manager, Siemens Energy &Automation .inc; Programmable controls are being used for more and more sophisticated operations, languages other than ladder logic become more practical, efficient, and powerful. For example, it's very difficult to write a trigonometric function using ladder logic ."Languages gaining acceptance include Boolean, control system flowcharting, and such function chart languages as Graphcet and its variation .And there's increasing interest in languages like C and BASIC.

PLCs in process control

Thus far, PLCs have not been used extensively for continuous process control .Will this continue? "The feeling that I've gotten," says Ken Jannotta, manger, product planning, series One and Series Six

product ,at GE Fanuc North America ,'is that PLCs will be used in the process industry but not necessarily for process control."

Several vendors -obviously betting that the opposite will

happen -have introduced PLCs optimized for process

application .Rich Ryan, manger, commercial marketing, Allen-bradley Programmable Controls Div., cites PLCs's increasing use such industries as food ,chemicals ,and petroleum. Ryan feels there are two types of applications in which they're appropriate. "one," he says," is where the size of the process control system that's being automated doesn't

justify DCS[distributed control system].With the starting price tags of chose products being relatively high, a programmable controller makes sense for small, low loop count application .The second is where you

have to integrate the loop closely with the sequential logical .Batch controllers are prime example ,where the sequence and maintaining the process variable are intertwined so closely that the benefits of having a programmable controller to do the sequential logical outweighs some of the disadvantages of not having a distributed control system."

Bill Barkovitz, president of Triconex, predicts that "all future controllers that come out in the process control system business will embrace a lot of more PLC technology and a lot more PLC functionality than they ever did before ."

Communications and MAP

Communications are vital to an individual automation cell and to be automated factory as a whole. We've heard a lot about MAP in the last few years ,and a lot of companies have jumped on the bandwagon.[2]Many, however, were disappointed when a fully-defined and completed MAP specification didn't appear immediately .Says Larry Komarek: "Right now, MAP is still a moving target for the manufacturers, a specification that is not final .Presently, for example. people are introducing products to meet the MAP2.1standard .Yet2.1-based products will be obsolete when the new standard for MAP3.0 is introduced."

Because of this, many PLC vendors are holding off on full MAP implementations. Omron, for example, has an ongoing

MAP-compatibility program;[3]but Frank Newburn, vice president of Omron's Industrial Division ,reports that because of the lack of a firm definition ,Omron's PLCs don't yet talk to MAP.

Since it's unlikely that an individual PLC would talk to broad MAP anyway, makers are concentrating on proprietary networks. According to Sal Provanzano, users fear that if they do get on board and vendors withdraw from MAP, they'll be the ones left holding a communications structure that's not supported.

Universal I/O

While there are concerns about the lack of compatible communications between PLCs from different vendors, the connection

at the other end-the I/O-is even more fragmented .With rare exceptions, I/O is still proprietary .Yet there are those who feel that I/O will eventually become more universal .GE Fanuc is hoping to do that with its Genius smart I/O line. The independent I/O makers are pulling

in the same direction.

Many say that I/O is such a high-value item that PLC makers will always want to keep it proprietary .As Ken Jannotta, says: "The I/O is going to be a disproportionate amount of the hardware sale. Certainly each PLC vendor is going to try to protect that. "For that reason, he says, PLC makers won't begin selling universal I/O system from other vendor. "if we start selling that kind of product, "says jannotta, "what do we manufacture?"

With more intelligent I/O appearing, Sal Provanzano feels this will lead to more differentiation among I/O from different makers. "Where the I/O becomes extremely intelligent and becomes part of the system, "he says, "it really is hard to define which is the I/O and which is CPU. It

really CPU, if you will, is equally integrated into the system as the

I/O."

Connecting PLC I/O to PCs

While different PLCs probably will continue to use proprietary I/O, several vendors make it possible to connect5 their I/O to IBM PC-compatible equipment. Alle-bradeley, Could, and Cincinnati Milacron already have, and rumor has it that GE is planning something along these same lines .[4]Bill Ketelhut, manage of product planning at GE Fanuc North America ,sees this sort of thing as alternative to universal

I/O."I think the trend ,instead of toward universal I/O, will be

multiple host interface ," he says .Jodie Glore ,director of marking, Square D Automation Products, Views it as another indication that PLCs are, and have been for some time, industrial computers.

PLCs VS PCs

If the IBM 7552, the Action Instruments BC22,and other computers are appearing on the factory floor, won't this mean new competition for PLCs? Rich Ryan: "There are some control functions that are better jobs for computers. Programmable controllers have been forced to fit into those applications. "Yet, the majority of vendors we surveyed don't like the "PC invasion" will pose a problem for them .Most said that PLCs and PCs are enough apart in architecture that they will usually do the control. They don't feel that PCs will take jobs from PLCs just because PLC I/O modules can now be connected to PCs; they believe this simply means that PLCs and PCs will be able to share the same data.

"There are inherent architectural differences between a general purpose computer," says Rich Ryan, "and a programmable

controller .There are hardware constructs built into almost every manufacture's programmable controller today that customize the hardware to run ladder logic and to solve machine code. "One fundamental difference he cites is called state of the machine .Ryan: "When you shut the machine off, or interrupt the cycle, or you jump to another spot in the cycle, programmable controllers inherently remember the state of the machine: what the timers were, what the counters were ,what the states of all the latches were .Computers don't inherently do that."

WORDS AND TERMS

bet v.确信

optimized n.优化程序

corporate adj.共同的

mushroom v.迅速发展

trigonometric function 三角函数

vendor n.厂商

tag n.标签

smart adj.智能型的

compatible adj.兼容的

2、外文资料翻译译文

单片机基础

单片机是电脑和集成电路发展的巅峰,有据可查的是他们也是20世

纪最有意义的两大发明。

这两种特性在单片机中得到了充分的体现。一些厂家用这两种

特性区分程序内存和数据内存在硬件中的特性,如图3-5A-1,依据同样

的原理广泛的适用于一般目的的电脑和微电脑,一些厂家在程序内存和数

据内存之间不区分的像Princeton特性,展示如图3-5A-2.

只读存贮器(ROM). ROM是通常的永久性的,非应用程序的易失性存

储器。不少微机和单片机用于大批量应用,因此,经济的设备制造要求的

程序存储器的内容是在制造期间永久性的刻录在芯片中,这意味着严谨的

方法,因为修改ROM代码不能制造之后发展。这一发展过程可能涉及仿真, 使用硬件仿真功能以及强大的软件工具使用先进的开发系统。

一些制造商在其提供的设备包括的范围(或拟使用)用户可编程内存.

其中最简单的通常是设备能够运行于微处理器模式通过使用一些输入/输

出作为地址线额外的ROM选项和数据总线访问外部内存.这种类型的设备

可以表现为单芯片微型计算机尽管有限制的I / O和外部修改这些设备的

电路.小内存装置的应用是非常普遍的在永久性内存的制造中 [2];但仍

然可以在我节省大量成本I/ O和其它芯片相比,传统的基于微处理器电

路.更准确的ROM设备更换,可在与'形式变种背驮式'EPROM(可擦除可编

程只读存储器)插座或存储器,而不是ROM器件。这些器件自然价格比同

等ROM设备贵,但不提供完整的等效电路.EPROM的设备也非常有吸引力对于低容量应用中,他们提供的单芯片器件的优势,在以下方面的板载I / O等,在灵活的用户可编程带来的便利。

随机存取存储器(RAM)。RAM用于变量和工作在程序使用该存储器的执行.随数

据存储设备的大小不同类型而有所不同,但具有相同的特征宽度(4,8,16 比特等)作为处理器。特殊功能寄存器,如栈指针或定时器寄存器,往往逻辑纳入内存区域.

它也在型微电脑的硬件中做集中内存,它是不必要的区分内存和处理器之间的区别在通常不物理上分开的微机中。

中央处理单元(CPU)。CPU是很象微型电子计算机和微控制器的任何微电脑.许多微电脑和微控制器涉及到二进制编码(十进制处理(BCD)的数据为例)数字显示,因而,常常可以发现该CPU是很适合处理这种类型的数据。对设施良好与否进行的测试,设置和重置单个位的内存或I / O控制器的应用程序,也是常见的因为许多涉及打开和关闭的单输出线或在单线.这些线很容易连接到二进制的设备,如开关,恒温器,固态继电器,阀门,电机等

并行输入/ 输出.并行输入和输出的计划有所不同,在不同的微机,在大多数设立一个机制,至少选择让其中一些引脚输出,一些引脚输如是非常灵活的。这可能适用于所有或端口.有些I / O线直接连接到适当的设备,例如,荧光显示器,也可以提供足够的电流,使接口和其他设备直接相连.一些设备允许一个I / O端口,其他组件将作为系统总线配置为允许片外存储器和I / O扩展。这个设施是潜在有用的一个产品系列的发展,因为连续增强可能成为太上存储器,这是不可取的,不是建立在现有的软件基础上的。

串行输入/输出。串行通信是指与终端设备的链接使用少量的通讯线.这种通讯也可利用特殊的接口连接功能芯片使几个微型机连在一起。双方共同异步同步通信方案要求的规则提供成帧(启动和停止)的信息。这可以作为一个硬件设施或U(拧)艺术(通用执行(同步)异步接收器/发送器)减轻处理器(和应用程序)的这种低层次的确费时.它也只需要选择一个波特率及其他可能的选择(停止位,奇偶校验等)和负载号码(或读取),串行发送器(或接收)的缓冲器.进行适当的格式的数据串行处理,然后由硬件电路完成。

定时/计数器设施。许多应用的单片机需要对过去的真实时间准确的评价。这可以由每个程序中的执行时间分支认真评估,但除最简单的程序外,他的工作效率

不高。首选方法是使用计时器电路,能独立计算精确的时间增量,并生成一个预设的时间后中断的时间。这种类型的定时器通常在所要求的数量可重载中应用。计时器然后减少此值产生中断或设置标记时,计数器到达零.更好的计时器有自动加载初始值的功能。这将缓解重新加载计数器和评估所用的时间,计时器重新启动之前这是必要的。有时候与定时器相关的是一个事件计数器。这个设备通常有一个特殊的输入引脚,可直接驱动计数器。

定时元件。大多数微型计算机时钟电路只需要简单的计时元件.如果要求最高性能,必须使用晶体以确保最大时钟频率接近,但不会超出。许多时钟电路,还具有电阻和低电容工作成本定时元件,也可以从外部源驱动。这后一种安排是有用的在微机外部同步是必需的时候。

B:PLC[1]

今天的PLC(可编程逻辑控制器)将面对日益复杂的挑战。一旦他们悄悄地取代继电器,偶尔向主机报告,如果他们将他们比作细胞,赋予新的工作和新的语言,将被迫和大量的控制产品竞争。对于今年的年度PLC技术的更新,我们对PLC的制造商会就这些主题提出更多问题.

编程语言

更高水平的PLC编程语言已经推行有一段时间了,但最近的流行,如雨后春笋般。正如雷蒙德莱韦耶,副总裁兼总经理,西门子能源和自动化公司,可编程控制正在为更复杂的操作使用,梯形逻辑比语言变得更加实际,有效和强大的。举例来说,很难写三角函数使用梯形逻辑。“语言为人们所接受,包括布尔,控制系统流程图,这种功能图及其变化图表语言。而且有越来越多像C和BASIC语言的兴趣。”

在过程的PLC控制

到目前为止,PLC的没有大量用于连续过程控制,会继续吗,“我感觉到了,PLC将用于过程工业,但不一定过程控制。” Jannotta说。几个供应商,显然是把赌注押在相反会发生,已经实行了PLC的应用优化的过程。富瑞安的经理认为PLC将越来越多地使用食品等行业,化工,石化.Ryan认为有两种类型的应用程序中,他们是合适的。“之一,”他说,“是其中的过程控制系统,目前已被没有理由自动化DCS的大小[分布式控制系统]随着价格标签开始。产品的选择是比较高,可编程控制器为小,低环数的应用意义。第二种是你必须融入顺序逻辑。批次控制循环密切合作是最好的例子,那里的顺序和维持过程变量是交织在一起的密切合作,使拥有一个可编程控制器的逻辑顺序做的好处远远超过了不具有分布式控制系统的一些缺点。”

Bill Barkovitz, Triconex的总统,预言:“今后所有的控制器在过程控制系统的业务将引用更多的PLC技术, PLC功能比以往任何时候都要多。”

通信和规范

在整体上通信是至关重要的个人自动化单元对自动化工厂来说。我们听说了很多规范在过去数年,许多公司都纷纷跟进。[2]但是,不少人失望的发现完成地图规范并没有立即出现。拉里科马雷克说:“现在,规范仍然是一个移动目标,规范没有最终决定,对于制造商。目前,正在推出的产品样本.人们使其产品满足MAP2.1标准。然而,新标准MAP3.0被引进时,MAP2.1为基础的产品将被淘汰时。”

正因为如此,许多PLC厂商正在制定完整的规范. 例如Omron,拥有一个完整的兼容程序; [3],但弗兰克纽伯恩,副欧姆龙工业部总裁,报告说,由于缺乏公司的定义,欧姆龙的PLC还谈不上规范。

由于不太可能将个人的PLC广泛的交谈,制造商更专注于专有的网络.按照萨尔Provanzano说法,用户担心,如果他们不从规则上和供应商妥协,他们将要加大对通信结构的不支持。

通用的I / O

然而大多数PLC的兼容问题不同厂商的沟通不够,在另一端连接的I / O问题,更是支离破碎的。除了少数例外,I / O是仍然专有技术。然而,谁是那些感觉的I / O最终将成为更具有普遍性。GE Fanuc的希望这样做与天才智能I / O线.各个独立I / O制造商都在同一方向进发。

许多人说,I / O是这样一个高价值项目, PLC制造商将永远希望保持它的专有性。由于肯Jannotta。说:“ I / O将在硬件销售中不成比例。当然每个PLC供应商将试图保护这一点。”出于这个原因,他说,PLC的制造商将不会开始销售通用I / O和其他厂商的系统。“如果我们开始销售该产品的实物,那我们还有什么可生产的,”

Jannotta说道

随着更多智能I / O出现,萨尔Provanzano认为在不同的制造商中间这将导致更多的分化。“哪里的I / O变得非常聪明,并成为系统的一部分真的很难定义,哪些是I / O,哪些是CPU.随着分布式的发展,如果你愿意,CPU也同样可以纳入作为I / O的系统”

PLC的 I / O和个人电脑的连接

虽然不同的PLC厂商可能会继续用专有的I / O,但一些厂商使I / O连接到IBM PC这样的兼容设备成为可能.Alle - bradeley和辛辛那提米拉克龙公司已经拥有,并有传言说,通用的电气计划将沿着同样的思路。克特尔胡特, GE Fanuc 北美的产品规划经理,认为是I/ O的普及“我想多个主机接口将代替I/O的趋

势,”他说。朱迪格洛尔,市场经理,Square D Automation Products,将PLC看做是工业电脑。

PLC VS电脑

如果IBM 7552,行动仪器BC22,和其他计算机出现在工厂,这意味着不会对PLC的新的竞争,富瑞安:“有一些控制功能,可用于电脑.可编程程序控制器更好的工作已被迫适应这些应用。“然而,在我们调查的厂商多数不认为“个人电脑入侵”将对他们产生问题。大多表示PLC和PC结构上的差别决定他们不同的作用,PC将主管通讯和管理,PLC则进行控制,他们相信这只是意味着,PLC和个人电脑将能够共享相同的数据。

富瑞恩说:“通用的计算机内在结构不同,可编程控制器硬件结构有内置到几乎每一个制造商的可编程控制器。今天定制的硬件来运行梯形逻辑,解决机器代码。”在根本的区别上,他引用了一个称呼“机器状态”。富瑞安说:“当你关闭机器,或中断周期,或者跳转到另一个周期,现场可编程控制器本身记得机器的状态:定时器状态是什么,计数器状态是什么,锁存的状态是什么,但计算机本身不这样做。”

信息与计算科学中英文对照外文翻译文献

(文档含英文原文和中文翻译) 中英文对照外文翻译 基于拉格朗日乘数法的框架结构合理线刚度比的研究 【摘要】框架结构是一种常见的多层高层建筑结构;列的合理线刚度比研究是框架结构优化设计中的一个重要方面。本论文研究合理线刚度比时,框架梁、柱的

侧移刚度根据拉格朗日乘数法结构优化的理论和在框架梁、柱的总物质的量一定的前提下,取得最高值。与传统的估计方法和试算梁柱截面尺寸不同,梁、柱的合理的截面尺寸可以在初步设计阶段由派生的公式计算。这种方法不仅作为计算框架梁、柱的截面尺寸基础,确认初步设计阶,而且也被用做类似的结构梁柱合理线刚度比研究的参考。此外,在调整帧梁、柱的截面尺寸的方法的基础上,降低柱的轴向的压缩比,从而达到剪切压缩比和提高结构的延展性。 【关键词】拉格朗日数乘法框架结构刚度比截面尺寸 1 引言 在混凝土框架结构初步设计的期间,通常,框架梁截面高度通过跨度来估算,和截面宽度根据高宽比估算; 框架柱的截面尺寸是根据柱轴压缩的支持柱的面积的比率估算[1]。然而,在估计过程中,初步设计阶段中的一个重要的链,未考虑到柱侧移刚度的影响[2]。列侧移刚度越大,结构层间位的刚度越大,剪切型框架结构的层间位移将越较小。所以,总结构越小的侧向位移将减少地震灾害[3] 所造成的损失。论文的核心是如何得到列侧移刚度的最大值。 同时,列侧移刚度的值与框架梁-柱线刚度直接相关。本论文的目的是为了得到一个合理的框架梁 - 柱的线刚度比,在某个控制范围内获得列侧移刚度的最大值。 计算列横向位移的方法有两种方法:刚度拐点点法和修改拐点法。拐点的方法假定关节的旋转角度为0(当梁柱线性刚度比是大于或等于3时,柱的上端和下端的关节的旋转角度可以取为0,因为它实际上是相当小),即梁的弯曲刚性被视为无穷大。拐点的方法主要是应用于具有比较少层的框架结构。但对于多层、高层框架结构,增加柱截面会导致梁柱线刚度比小于3,在水平荷载作用下,框架结构的所有关节的旋转角度的横向位移会发生不可忽视。因此,一位日本教授武藤提出修改拐点法[4],即D-值方法。本文采用D-值列侧移刚度的计算法,因为它着重于多层、高层框架结构。 少数在国内外对框架梁柱合理线刚度比的研究,只有梁七黹,源于列侧移刚度的计算方法,比D-值法更加应用广泛;申得氏指出在多层、高层框架结构的柱侧向刚度计算中存在的问题,补充和修改底部和顶部层的列侧向刚度计算公式;

毕设外文资料翻译.

理工学院 毕业设计外文资料翻译 专业:计算机科学与技术 姓名:马艳丽 学号: 12L0752218 外文出处:The Design and Implementation of 3D Electronic Map of Campus Based on WEBGIS 附件: 1.外文资料翻译译文;2.外文原文。

附件1:外文资料翻译译文 基于WebGIS的校园三维电子地图的设计与实现 一.导言 如今,数字化和信息化是当今时代的主题。随着信息革命和计算机科学的发展,计算机技术已经渗透到科学的各个领域,并引起了许多革命性的变化,在这些科目,古代制图学也不例外。随着技术和文化的不断进步,地图变化的形式和内容也随之更新。在计算机图形学中,地理信息系统(GIS)不断应用到Web,制作和演示的传统方式经历了巨大的变化,由于先进的信息技术的发展,地图的应用已经大大延长。在这些情况下,绘图将面临广阔的发展前景。电子地图是随之应运而生的产品之一。随着计算机技术,计算机图形学理论,遥感技术,航空摄影测量技术和其他相关技术的飞速发展。用户需要的三维可视化,动态的交互性和展示自己的各种地理相关的数据处理和分析,如此多的关注应支付的研究三维地图。东北石油大学及其周边地区的基础上本文设计并建立三维电子地图。 二.系统设计 基于WebGIS的校园三维电子地图系统的具有普通地图的一般特性。通过按键盘上的箭头键(上,下,左,右),可以使地图向相应的方向移动。通过拖动鼠标,可以查看感兴趣的任何一个地方。使用鼠标滚轮,可以控制地图的大小,根据用户的需求来查看不同缩放级别的地图。在地图的左下角会显示当前鼠标的坐标。在一个div层,我们描绘了一个新建筑物的热点,这层可以根据不同的地图图层的显示,它也可以自动调整。通过点击热点,它可以显示热点的具体信息。也可以输入到查询的信息,根据自己的需要,并得到一些相关的信息。此外,通过点击鼠标,人们可以选择检查的三维地图和卫星地图。 主要功能包括: ?用户信息管理:检查用户名和密码,根据权限设置级别的认证,允许不同权限的用户通过互联网登录系统。 ?位置信息查询:系统可以为用户提供模糊查询和快速定位。

电气专业毕业设计外文翻译

附录1:外文资料翻译 A1.1外文资料题目 26.22 接地故障电路开关 我们目前为止报道的接地方法通常是充分的, 但更加进一步的安全措施在某些情况下是必要的。假设例如, 有人将他的手指伸进灯口(如Fig.26.45示)。虽然金属封入物安全地接地, 但那人仍将受到痛苦的震动。或假设1个120V 的电炉掉入游泳池。发热设备和联络装置将导致电流流入在水池中的危害,即使电路的外壳被安全地接地,现在已经发展为当这样的事件发生时,设备的电源将被切断。如果接地电流超过5mA ,接地开关将在5 ms 内跳掉,这些装置怎么运行的? 如Fig.26.46所示,一台小变流器缠绕上导线 ,第二步是要连接到可能触发开合120 V 线的一台敏感电子探测器。 在正常情况下流过导体的电流W I 与中性点上的电流N I 准切的相等,因此流经核心的净潮流(N W I I -)是零。 结果,在核心没有产生电流,导致的电压F E 为零,并且开关CB 没有动作。 假设如果某人接触了一个终端(图Fig.26.45示),故障电流F I 将直接地从载电线漏到地面,这是可能发生的。如果绝缘材料在马达和它的地面封入物之间断开,故障电流也会被产生。在以下任何情况下,流经CT 的孔的净潮流等于F I 或L I ,不再是零。电流被产生,并且产生了可以控制CB 开关的电压F E 。 由于5 mA 不平衡状态只必须被检测出,变压器的核心一定是非常有渗透性的在低通量密度。 Supermalloy 是最为常用的,因为它有相对渗透性典型地70000在通量密度仅4mT 。 26.23 t I 2是导体迅速发热的因素 它有时发生于导体短期内电流远大于正常值的情况下,R I 2损失非常大并且导体的温度可以在数秒内上升几百度。例如,当发生严重短路时,在保险丝或开关作用之前,会有很大的电流流过导体和电缆。 此外,热量没有时间被消散到周围,因此导体的温度非常迅速地增加。 在这些情况下什么是温度上升? 假设导体有大量m ,电阻R 和热量热容量c 。 而且,假设电流是I ,并且那它流动在t 少于15秒期间。 在导体上引起的热 Rt I Q 2= 从Eq.3.17,在功率一定的情况下我们可以计算导体上升的温度差:

1外文文献翻译原文及译文汇总

华北电力大学科技学院 毕业设计(论文)附件 外文文献翻译 学号:121912020115姓名:彭钰钊 所在系别:动力工程系专业班级:测控技术与仪器12K1指导教师:李冰 原文标题:Infrared Remote Control System Abstract 2016 年 4 月 19 日

红外遥控系统 摘要 红外数据通信技术是目前在世界范围内被广泛使用的一种无线连接技术,被众多的硬件和软件平台所支持。红外收发器产品具有成本低,小型化,传输速率快,点对点安全传输,不受电磁干扰等特点,可以实现信息在不同产品之间快速、方便、安全地交换与传送,在短距离无线传输方面拥有十分明显的优势。红外遥控收发系统的设计在具有很高的实用价值,目前红外收发器产品在可携式产品中的应用潜力很大。全世界约有1亿5千万台设备采用红外技术,在电子产品和工业设备、医疗设备等领域广泛使用。绝大多数笔记本电脑和手机都配置红外收发器接口。随着红外数据传输技术更加成熟、成本下降,红外收发器在短距离通讯领域必将得到更广泛的应用。 本系统的设计目的是用红外线作为传输媒质来传输用户的操作信息并由接收电路解调出原始信号,主要用到编码芯片和解码芯片对信号进行调制与解调,其中编码芯片用的是台湾生产的PT2262,解码芯片是PT2272。主要工作原理是:利用编码键盘可以为PT2262提供的输入信息,PT2262对输入的信息进行编码并加载到38KHZ的载波上并调制红外发射二极管并辐射到空间,然后再由接收系统接收到发射的信号并解调出原始信息,由PT2272对原信号进行解码以驱动相应的电路完成用户的操作要求。 关键字:红外线;编码;解码;LM386;红外收发器。 1 绪论

框架结构毕业设计任务书和指导书范本

框架结构毕业设计任务书和指导书 1 2020年4月19日

毕业设计基本要求 1目的 (1)综合运用所学专业理论知识与设计技能,处理建筑设计中有关方针、政策、功能、经济、安全、美观等方面的问题。解决总体、单体、空间等关系,以创造富有时代气息的优美建筑形象与环境。依据建筑设计完成结构体系的布置、结构在各种荷载工况下的计算、构造和施工图。 (2)掌握一般建筑工程的设计思路,进而举一反三熟悉有关建筑工程的设计、施工、预算等建设过程。为即将走上工作岗位奠定基础。 (3)学以致用,学习科学技术和技能的目的是应用。一个工程师在设计、建设实际工程中应具备的知识,都是我们在毕业设计中应予以加强的。因此深切领悟总体概念设计、掌握具体理论设计和实际工程技术处理措施的结合作为重点来训练。 (4)树立正确的设计思想,全面对待建筑与结构的关系, 2 2020年4月19日

培养勤奋、严谨、认真的工作作风及分析解决一般工程技术问题的能力。 (5)掌握调查研究、理论联系实际的学习方法,养成既能独立思考,又能相互配合密切合作的工作态度。 (6)使学生对一般工业与民用建筑的土建设计的内容和构成有比较全面的了解,并熟悉有关设计标准、规范、手册和工具书,增强毕业后到生产第一线工作的适应能力。 2成果形式及要求 (1)计算书和说明书: 字数应不少于1万字,书写要工整,字迹要清楚,可采用计算机打印。计算书内容要阐明设计依据或标准,方案构思、特点、必要的经济指标,结构选型、构造处理、材料特点及计算上的主要问题,还应包括结构计算全过程,计算要正确、完整、思路清晰、简图明了。计算书格式:应严格按照毕业设计手册中的要求。 (2)图纸: 3 2020年4月19日

STC89C52处理芯片-毕业论文外文翻译

中文翻译 STC89C52处理芯片 电气工程的研究和解决方案中心(ceers) 艾哈迈德为吉.波特 首要性能: 与MCS-51单片机产物兼容、8K字节在系统可编程视频存储器、1000次擦拭周期,全静态操作:0Hz~33Hz、三级加密程序存储器,32个可编程I/O接口线、三个16位定时器(计数器),八个中断源、低功能耗空闲和掉电模式、掉电后间断可唤醒,看门狗定时器、双数值指针,掉电标示符。 关键词:单片机,UART串行通道,掉电标示符等 前言 可以说,二十世纪跨越了三个“点”的时代,即电气时代,电子时代和现已进入的电脑时代。不过,这种电脑,通常指的是个人计算机,简称PC机。还有就是把智能赋予各种机械的单片机(亦称微控制器)。顾名思义,这种计算机的最小系统只用了一片集成电路,即可进行简单的运算可控制。因为它体积小,通常都是藏在被控机械的内部里面。它在整个装置中,起着有如人类头脑的作用,他出了毛病,整个装置就会瘫痪。现在,单片机的种类和适用领域已经十分广泛,如智能仪表、实施工控、通讯设备、导航系统、家用电器等。各种产品一旦用上了单片机,就你能起到产品升级换代的功效,常在产品名称前冠以形容词——“智能型”,如智能洗衣机等。接下来就是关于国产STC89C52单片机的一些基本参数。 功能特性描述: STC89C52单片机是一种低功耗、高性能CMOS8位微控制器,具有8K在系统可编程视频播放存贮器使用高密度非易失性存储器技术制造,与工业80C51 产物指令和引脚完全兼容。片上反射速度允许程序存储器在系统可编程,也适用于常规的程序编写器。在其单芯片上,拥有灵敏小巧的八位中央处理器和在线系统可编程反射,这些使用上STC89C52微控制器为众多嵌入式的控制应用系统提供高度矫捷的、更加有用的解决方案。STC89C52微控制器具有以下的标准功效:8K字节的反射速度,256字节的随机存取储存器,32位I/O串口线,看门狗定时器,2个数值指针,三个16 为定时器、计数器,一个6向量2级间断结构,片内晶振及钟表电路。另外,STC89C52可降至0HZ静态逻辑操作,支持两种软件可选择节电模式、间断继续工作。空闲模式下,CPU停止工作,允许RAM、定时器/计数器、串口、间断继续工作。掉电保护体式格局下,RAM内容被生成,振动器被冻结,单片机一切的工作停止,直到下一个间断或者硬件复位为止。8位微型控制器8K字节在系统中可编程FlashSTC89C52.。

外文翻译1

译文(一) THE ACCOUNTING REVIEW V ol. 83, No. 3 2008 pp. 823–853 市场参与者的杜邦分析的使用 马克?t?Soliman 华盛顿大学 文摘:杜邦分析,一种常见的财务报表分析,依靠于净营业资产收益率的两个乘法组件:利润率和资产周转率。这两个会计比率衡量不同的构造。因此,有不同的属性。之前的研究已经发现,资产周转率的变化是未来收益的变化正相关。本文全面探讨了杜邦组件和沿着三个维度有助于文学。首先,本文有助于财务报表分析文献,发现在这个会计信息信号实际上是增量学习会计信号在先前的研究在预测未来收益。其次,它有助于文学在股票市场上使用的会计信息通过检查眼前和未来的股本回报投资者应对这些组件。最后,它增加了分析师的文献处理会计信息的再次测试直接和延迟反应的分析师通过同期预测修正以及未来预测错误。一致的跨市场加入者的两组,结果表明是有用的信息就是明证杜邦组件和股票收益之间的联系以及维度分析师预测。然而,我发现预测未来预测错误和异常返回信息处理表明似乎没有完成。平均水平,分析表明杜邦组件代表增量和可行的操作特征信息的公司。 关键词:财务报表分析、杜邦分析、市场回报、分析师预估。 数据可用性:在这项研究中使用的数据是公开的来源显示的文本。 在本文中,我分析杜邦分析中包含的信息是否与股市回报相关和分析师预测。之前的研究文档组件从杜邦分析,分解的净营业资产收益率为利润率和资产周转率,有解释力对未来盈利能力的变化。本文增加了文献综合研究投资者和分析师反应杜邦组件三个维度。首先,它复制先前记录的预测能力和检查是否健壮和增量其他预测已经考虑在文学的存在。其次,它探讨了使用这些组件的股市投资者通过观察同生和未来收益。在同时代的长窗协会和短时期限信息测试,结果显示积极联系杜邦组件和股本回报率。但小未来异常返回交易策略显示的信息可能不完整的处理。最后,检查当前预测修正由卖方分析师和未来的预测错误。尽管他们似乎修改他们的预测未来收益与这些杜邦组件中的信息一致,修订似乎不完整就是明证可预测的未来预测错误。一致的市场参与者,在两组同期结果表明,信息是有用的,但是未来的测试表明,信息处理似乎没有完成。 由金矿和笔者(2001)提供了一个使用剩余收益的股票估值方法框架,给出了一个简单的财务比率分析的直接映射到股票估值。特别是他们用杜邦分析,分解公司的净营业资产收益率(RNOA)利润率(PM)和资产周转率(ATO)点的地方1。PM和ATO会计信号,测量不同结构对一个公司的业务2。PM 往往是来自定价权,如产品创新,产品定位,品牌知名度,先发优势和市场定位。ATO措施资产利用率和效率,通常来自于有效的利用财产,工厂和设备,有效的库存流程;和其他形式的资本管理工作3。 我们有理由期待竞争力量的影响这两个来源盈利能力不同。大的利润率通常吸引新进入者进入市场或快速模仿新思想从现有的竞争对手。由此产生的竞争导致高利润率回归正常水平,暗示更多暂时的利益。与利润不同,然而,竞争可能少威胁要部署一个有效的资产。更难以模仿另一个公司的高效生产流程因为这样模仿通常包括大型和昂贵的改革目前的工厂和操作。 1.具体来说,RNOA营业收入/平均净营业资产,PM营业收入/销售和ATO销售 /平均净营业资产。此后,点和ATO被称为“杜邦公司组成”。另一个常见的形式是分解罗伊(利润杠杆资产周转率)或(NI /产品销售/资产资产/股本)。讨论的“估值理论和RNOA”部分,我在分析使用RNOA为了专注于操作,因此抽象从公司的融资决策。 2.例如,阿伯克龙比和惠誉赚取高额利润通过出售used-looking服装被认为是时髦和青少年所要

电气工程外文翻译

毕业设计(论文)外文资料翻译 学院:电气信息学院 专业:电气工程及其自动化 姓名:郭骥翔 学号: 081001227 外文出处: Adaptive torque control of variable speed wind turbines 附件: 1.外文资料翻译译文;2.外文原文。 指导教师评语: 签名: 年月日(用外文写)

附件1:外文资料翻译译文 多种风力涡轮机的适应性转矩控制 4.5 使用SymDyn进行仿真 所有先前所描述的模拟是使用SimInt来演示的,其中,如前所述,包括唯一的转子角速度自由度,与复杂的仿真工具比,如SymDyn和FAST,他能够更快的运行。然而,为了确认目的,与其他更流行的仿真工具比较SimInt在适应运行上的增益是很有价值的。适应性的增加并不是期望它能够同等的适应每一个仿真工具,因为每个仿真工具都有其独到的涡轮机模型。但是如果每个涡轮机的造型都相同,如同本例,那么在SimInt 和SymDyn中则有着基本相似的适应性增益(CART)。在数据4-10中,这种相似性被明显的显示出来。 SimInt和SymDyn仿真工具都是由零时刻开始,而且大多数参数初值都相同,如M,角速度等。然而,尽管这两个涡轮机模型都设立了最佳转矩控制M*,但是CP表面却有着不同程度的峰值。因此为了使初始过程大致相同,初始Pfavg值应有相同的最大比例,而不是相同的绝对值。在显示标准化M值4-10的上图中,显示了合理的类似数据。但在30到60小时后,仿真工具的适应性增益开始出现分歧。但在此之后,他们再次互相接近,在从模拟开始100小时到模拟结束这段时间,他们保持基本重合。从下图中也可以清楚的观察出,每个仿真工具都在调整他们的增益M,并采集最大输出功率。 尽管SimInt仿真速度差不多是SymDyn仿真速度的五倍,在图4-10中所显示的SymDyn 数据是唯一一个可以验证适应性增益法则的模拟工具。在这个展示了两个模拟工具合理

多层混凝土框架结构设计文献综述

多层混凝土框架结构设计 1.前言 随着社会的发展,钢筋混凝土框架结构的建筑物越来越普遍.由于钢筋混凝土结构与砌体结构相比较具有承载力大、结构自重轻、抗震性能好、建造的工业化程度高等优点;与钢结构相比又具有造价低、材料来源广泛、耐火性好、结构刚度大、使用维修费用低等优点。因此,在我国钢筋混凝土结构是多层框架最常用的结构型式。近年来,世界各地的钢筋混凝土多层框架结构的发展很快,应用很多。 一般框架结构是由楼板、梁、柱及基础4种承重构件组成的,由主梁、柱与基础构成平面框架,各平面框架再由连续梁连接起来而形成的空间结构体系。文献[1]认为,在合理的高度和层数的情况下,框架结构能够提供较大的建筑空间,其平面布置比较的灵活,可适合多种工艺与使用功能的要求。 多层钢筋混凝土框架结构设计可以分为四个阶段:一是方案设计,二是结构分析,三是构件设计,四是绘施工图。结构分析和构件设计是结构设计中的计算阶段,在现代,已由电子计算机承担这一工作,常采用PKPM建模计算。但是,结构的计算并不能代替结构的设计。文献[2]中认为:良好的结构设计的重要前提,应该是合理组织与综合解决结构的传力系统、传力方式,良好的结构方案是良好结构设计的重要前提。2.关于框架结构设计文献回顾 2.1框架结构的优缺点 框架结构体系是由横梁与柱子连接而成.梁柱连接处(称为节点)一般为刚性连接,有时为便于施工和其他构造要求,也可以将部分节点做成铰接或者半铰接.柱支座一般为固定支座,必要时也可以设计成铰支座.框架结构可以分为现浇整体式,装配式,现浇装配式. 文献[3]中提到:框架结构的布置灵活,容易满足建筑功能和生工艺的多种要求.同时,经过合理设计,框架结构可以具有较好的延性和抗震性能.但是,框架结构承受水平力(如风荷载和水平地震作用)的能力较小.当层树较多或水平力较大时,水平位移较大,在强烈地震作用下往往由于变形过大而引起非结构构件(如填充墙)的破坏.因此,为了满足承载力和侧向刚度的要求,柱子的截面往往较大,既耗费建筑材料,又减少使用面积.这就使框架结构的建筑高度受到一定的限制.目前,框架结构一般用于多层建筑和不考虑抗震设防,层数较少的的高层建筑(比如,层数为10层或高度为30米以下) 2.3框架结构的布置 多层框架结构的平面布置形式非常的灵活,文献[4]中将框架结构按照承重方式的不同分为以下三类:(1)横向框架承重方案,以框架横梁作为楼盖的主梁,楼面荷载主要由横向框架承担.由于横向框架数往往较少,主梁沿横向布置有利于增强房屋的横向刚度.同时,主梁沿横向布置还有利于建筑物的通风和采光.但由于主梁截面尺寸较大,当房屋需要大空间时,净空较小,且不利于布置纵向管道. (2)纵向框架承重方案以框架纵梁作为楼盖的主梁,楼面荷载由框架纵梁承担.由于横梁截面尺寸较小,有

毕业设计外文翻译

毕业设计(论文) 外文翻译 题目西安市水源工程中的 水电站设计 专业水利水电工程 班级 学生 指导教师 2016年

研究钢弧形闸门的动态稳定性 牛志国 河海大学水利水电工程学院,中国南京,邮编210098 nzg_197901@https://www.360docs.net/doc/31638071.html,,niuzhiguo@https://www.360docs.net/doc/31638071.html, 李同春 河海大学水利水电工程学院,中国南京,邮编210098 ltchhu@https://www.360docs.net/doc/31638071.html, 摘要 由于钢弧形闸门的结构特征和弹力,调查对参数共振的弧形闸门的臂一直是研究领域的热点话题弧形弧形闸门的动力稳定性。在这个论文中,简化空间框架作为分析模型,根据弹性体薄壁结构的扰动方程和梁单元模型和薄壁结构的梁单元模型,动态不稳定区域的弧形闸门可以通过有限元的方法,应用有限元的方法计算动态不稳定性的主要区域的弧形弧形闸门工作。此外,结合物理和数值模型,对识别新方法的参数共振钢弧形闸门提出了调查,本文不仅是重要的改进弧形闸门的参数振动的计算方法,但也为进一步研究弧形弧形闸门结构的动态稳定性打下了坚实的基础。 简介 低举升力,没有门槽,好流型,和操作方便等优点,使钢弧形闸门已经广泛应用于水工建筑物。弧形闸门的结构特点是液压完全作用于弧形闸门,通过门叶和主大梁,所以弧形闸门臂是主要的组件确保弧形闸门安全操作。如果周期性轴向载荷作用于手臂,手臂的不稳定是在一定条件下可能发生。调查指出:在弧形闸门的20次事故中,除了极特殊的破坏情况下,弧形闸门的破坏的原因是弧形闸门臂的不稳定;此外,明显的动态作用下发生破坏。例如:张山闸,位于中国的江苏省,包括36个弧形闸门。当一个弧形闸门打开放水时,门被破坏了,而其他弧形闸门则关闭,受到静态静水压力仍然是一样的,很明显,一个动态的加载是造成的弧形闸门破坏一个主要因素。因此弧形闸门臂的动态不稳定是造成弧形闸门(特别是低水头的弧形闸门)破坏的主要原是毫无疑问。

电气毕业设计外文文献

外文文献: The Intelligent Building One of the benefits of the rapid evolution of information technology has been the development of systems that can measure, evaluate, and respond to change。An enhanced ability to control change has sparked developments in the way we design our physical environment, in particular, the buildings in which we work。As a result, we are witnessing significant growth in the area of "Intelligent Buildings"--buildings that incorporate information technology and communication systems, making them more comfortable, secure, productive, and cost-effective What is an Intelligent Building? An Intelligent Building is one equipped with the telecommunications infrastructure that enables it to continuously respond and adapt to changing conditions, allowing for a more efficient use of resources and increasing the comfort and security of its occupants。An Intelligent Building provides these benefits through automated control systems such as: heating, ventilation, and air-conditioning (HVAC);fire safety;security;and energy/lighting management。For example, in the case of a fire, the fire alarm communicates with the security system to unlock the doors。The security system communicates with the HVAC system to regulate the flow of air to prevent the fire from spreading。 What benefits do Intelligent Buildings offer their owners and occupants? The introduction in the workplace of computers printers photocopiers, and fax machines has increased indoor pollution。Electrical and telecommunications facilities in office buildings are under pressure to satisfy the demands created by the rapid growth of computer and networking technologies。These factors have a definite impact on productivity. New technology can be used to create Intelligent Buildings that address these problems by providing a healthier, more productive, and less energy-intensive work environment。As these are critical factors for business

5外文翻译原文1

A Case Study of Pattern-based Software Framework to Improve the Quality of Software Development Chih-Hung Chang, Chih-Wei Lu Dept. of Information Management, Hsiuping Institute of Technology No.11, Gongye Rd., Dali City, Taichung County, Taiwan(R.O.C.) 886-4-24961123 ext 3112 {chchang,cwlu}@ https://www.360docs.net/doc/31638071.html,.tw William C. Chu Dept. of Computer Science and Information Engineering, Tunghai University No.181, Sec. 3, Taichung Port Rd.,Taichung City, Taiwan (R.O.C.) 886-4-23508983 cchu@https://www.360docs.net/doc/31638071.html,.tw Nien-Lin Hsueh Dept. of Information Engineering and Computer Science, Feng Chia University No. 100 Wenhwa Rd., Taichung, Taiwan (R.O.C.) 886-4- 24517250 ext 3773 nlhsueh@https://www.360docs.net/doc/31638071.html,.tw Chorng-Shiuh Koong Dept. of Computer and Information Science, Taichung University No.140, Ming-Sheng Rd., Taichung City, Taiwan (R.O.C.) 886-4-22183804 csko@https://www.360docs.net/doc/31638071.html,.tw ABSTRACT In recent years, development of the software industry and demand for software systems have increased rapidly, but developers often does not know whose suggestion to follow regarding methodologies of software engineering. One reason for that is the difficulty in applying new software engineering technologies. Developers take a long time to train. Another reason is the difficulty in integrating CASE toolsets. So many indeterminate factors make the development process more and more complex. On the other hand, software development is too customized, and software reuse is difficult. T he reasons above are the cause for software development and maintenance to become more complex and difficult to control. In this paper we explore the importation of a software pattern-based framework, and the development of an ERP/support chain system. Based on software patterns, developers can separate development and business so as to reduce problems caused by the developer’s lack of business experience. T he quality of the product can thus be enhanced, software development costs be reduced, and software maintenance be improved. Keywords Design Pattern, Framework, Software Development Process, XML 1.INTRODUCTION In Object-Oriented T echnology, the property of inheritance allows software components to be reused, which can obviously reduce the cost of software development. For this reason, to produce a highly reusable software component is an important goal of software engineering. However, programmers are usually focused on code reuse while ignoring design reuse. Design patterns provide a clear concept of design structure by describing the relationships of inheritance and reference between components of the system. Design patterns are a series of familiar usages and constructions utilized throughout system design. Design patterns allow rapid coding of certain components by following certain patterns of steps. T his can improve the documentation and maintenance of existing systems by providing an explicit specification of class, object interactions and their underlying intents. One of the main purposes of design patterns is to help software engineers to understand the common characteristics of software objects/components in specialized domain. In recent years, due to the development and maturation of WWW and Java [14] technologies, many applications are now web applications or leaning in that direction. Many software concepts are utilized for the web as well, such as Design Patterns and Frameworks. The Apache Struts [12] and Spring Framework [13] are both open source frameworks used to address and reduce the complexity of developing an enterprise application. T he advantage of using a framework is the layered architecture it provides. Layered architecture allowed users to choose the component desired, while also providing the integration framework when developing application using J2EE. T hese developing web concepts can facilitate the development of web applications. However, these very useful tools and concepts lack a systematic organization. We hope to use these open source software technologies to develop a software framework which can be applied to web application. T his should solve the problem of web applications lacking a good structure, while through applying these open source software technologies, software development costs will be reduced. Furthermore, a guideline for programmers who wants to use these open source technologies will be provided. This paper is organized as follows: In the next section, we discuss works related to our project; in section 3, the open source technologies used in the paper and the system implementation will be described; Section 4 is a sample experiment. T he conclusion is given in section 5.

电气工程及其自动化专业_外文文献_英文文献_外文翻译_plc方面

1、 外文原文 A: Fundamentals of Single-chip Microcomputer Th e si ng le -c hi p m ic ro co mp ut er i s t he c ul mi na ti on of both t h e de ve lo pm en t o f t he d ig it al co m pu te r an d th e i n te gr at ed c i rc ui t a rg ua bl y t h e to w m os t s ig ni f ic an t i nv en ti on s o f t he 20th c e nt ur y [1]. Th es e t ow ty pe s of ar ch it ec tu re a re fo un d i n s in g le -ch i p m i cr oc om pu te r. So m e em pl oy t he spl i t pr og ra m/da ta m e mo ry o f th e H a rv ar d ar ch it ect u re , sh ow n in Fi g.3-5A -1, o th ers fo ll ow t he p h il os op hy , wi del y a da pt ed f or ge n er al -p ur po se co m pu te rs a nd m i cr op ro ce ss o r s, o f ma ki ng n o log i ca l di st in ct ion be tw ee n p r og ra m an d d at a m e mo ry a s i n t he P r in ce to n ar ch ite c tu re , sh ow n i n F ig.3-5A-2. In g en er al te r ms a s in gl e -chi p m ic ro co mp ut er i s c h ar ac te ri ze d b y t h e i nc or po ra ti on o f a ll t he un it s of a co mp uter i n to a s in gl e d ev i ce , as s ho wn in Fi g3-5A -3. Fig.3-5A-1 A Harvard type Program memory Data memory CPU Input& Output unit memory CPU Input& Output unit

毕设外文文献翻译

xxxxxxxxx 毕业设计(论文)外文文献翻译 (本科学生用) 题目:Poduct Line Engineering: The State of the Practice 生产线工程:实践的形态 学生姓名:学号: 学部(系): 专业年级: 指导教师:职称或学位: 2011年3月10日

外文文献翻译(译成中文1000字左右): 【主要阅读文献不少于5篇,译文后附注文献信息,包括:作者、书名(或论文题目)、出版社(或刊物名称)、出版时间(或刊号)、页码。提供所译外文资料附件(印刷类含封面、封底、目录、翻译部分的复印件等,网站类的请附网址及原文】 Requirements engineering practices A precise requirements engineering process— a main driver for successful software development —is even more important for product line engineering. Usually, the product line’s scope addresses various domains simultaneously. This makes requirements engineering more complex. Furthermore, SPL development involves more tasks than single-product development. Many product line requirements are complex, interlinked, and divided into common and product-specific requirements. So, several requirements engineering practices are important specifically in SPL development: ? Domain identification and modeling, as well as commonalities and variations across product instances Separate specification and verification for platform and product requirements ? Management of integrating future requirements into the platform and products ? Identification, modeling, and management of requirement dependencies The first two practices are specific to SPL engineering. The latter two are common to software development but have much higher importance for SPLs. Issues with performing these additional activities can severely affect the product line’s long-term success. During the investigation, we found that most organizations today apply organizational and procedural measures to master these challenges. The applicability of more formal requirements engineering techniques and tools appeared rather limited, partly because such techniques are not yet designed to cope with product line evelopment’s inherent complexities. The investigation determined that the following three SPL requirements engineering practices were most important to SPL success. Domain analysis and domain description. Before starting SPL development, organizations should perform a thorough domain analysis. A well-understood domain is a prerequisite for defining a suitable scope for the product line. It’s the foundation for efficiently identifying and distinguishing platform and product requirements. Among the five participants in our investigation, three explicitly modeled the product line requirements. The others used experienced architects and domain experts to develop the SPL core assets without extensive requirements elicitation. Two organizations from the first group established a continuous requirements management that maintained links between product line and product instance requirements. The three other organizations managed their core assets’ evolution using change management procedures and versioning concepts. Their business did not force them to maintain more detailed links between the requirements on core assets and product instances. The impact of architectural decisions on requirements negotiations. A stable but flexible architecture is important for SPL development. However, focusing SPL evolution too much on architectural issues will lead to shallow or even incorrect specifications. It can cause core assets to ignore important SPL requirements so that the core assets lose relevance for SPL development. Organizations can avoid this problem by establishing clear responsibilities for requirements management in addition to architectural roles. The work group participants reported that a suitable organizational tool for balancing requirements and architecture is roundtable meetings in which requirements engineers,

相关文档
最新文档