2012外文翻译装订及排版要求 (1)

合集下载

外文翻译的格式样式

外文翻译格式样式
标题（黑体小二加粗居中）
（宋体小四空一行）
外文作者署名（楷体小四号居中）
（宋体小四空一行）
1 内容（黑体三号加粗）
1.1内容（黑体四号加粗）
边坡是地壳表部一切具有临空面的地质体，具有一定的坡度和高度，包括人工边坡、自然边坡以及崩滑体。

在重力、风化、侵蚀和其它地质作用下，边坡不断地发生变化，应力重新分布，并且随着边（宋体小四号）……
说明：以上为外文翻译的格式，译文前应附有被翻译的外文原件复印件，为了反映文稿的科学依据和译者尊重他人研究成果的严肃态度及向读者提出有关信息的出处，要求译者按著录/题名/出版事项顺序排列注明，请同学们遵照执行。

期刊：著者，题名，期刊名称，出版年，卷号（期号），起始页码。

书籍：著者，书名、版次（第一版不标注），出版地，出版者，出版年，起始页码。

毕业设计(论文)外文文献译文格式及装订要求

“毕业设计（论文）外文文献译文”格式及装订要求
全校所有专业的学生在完成毕业设计（论文）的同时，必须完成一篇专业外文文献翻译工作（将外文文献翻译成中文），要求译出3000汉字以上的有关技术资料或专业外文文献，内容要与毕业设计（论文）内容相关。

书写时具体格式要求参考“毕业论文（设计说明书）缩写稿格式、版面要求”，装订时按以下顺序独立装订：1、封面；2、外文文献译文；3、外文文献原文。

附件：毕业设计（论文）外文文献译文封面
毕业设计（论文）
外文文献译文及原文
学生：
学号：
院（系）：
专业：
指导教师：
20 年月日。

外文翻译规范要求及模版格式

外文翻译规范要求及模版格式
外文中文翻译规范要求及模板格式可以根据具体需求和要求有所不同，以下是一般常见的外文中文翻译规范要求及模板格式：
1.规范要求：
-符合语法、语言规范和语义准确性；
-译文流畅自然，符合中文表达习惯；
-忠实准确地传达原文信息；
-注意统一使用特定的术语翻译；
-文章结构、段落、标题等要与原文一致；
-保持适当的篇幅，不过度增加或删减内容；
-遵守保密原则。

2.模板格式：
-文章标题（与原文保持一致，可放在正文上方）；
-标题（与原文保持一致）；
-段落（与原文保持一致，首行缩进）；
-字体（常用宋体或黑体，一般字号12或14）；
-行间距（一般1.5倍，可根据需要调整）；
-页边距（上下左右均为2.5厘米）；
-段落间距（一般1.5倍，可根据需要调整）；
以上是一般常见的外文中文翻译规范要求及模板格式，具体要求和格式可以根据具体的翻译项目和要求进行调整。

在翻译过程中，保持准确、流畅、专业是非常重要的。

毕业设计(论文)外文资料和译文格式要求(模板)

成都东软学院外文资料和译文格式要求一、译文必须采用计算机输入、打印，幅面A4。

外文资料原文（复印或打印）在前，译文在后，于左侧装订。

二、具体要求1、至少翻译一篇内容与所选课题相关的外文文献。

2、译文汉字字数不少于4000字。

3、正文格式要求：宋体五号字。

译文格式参见《译文格式要求》，宋体五号字，单倍行距。

纸张纸张为A4纸，页边距上2.54cm、下2.54cm、左3.17cm、右3.17cm。

装订外文资料原文（复印或打印）在前，译文在后封面封面的专业、班级、姓名、学号等信息要全部填写正确。

封面指导教师必须为讲师以上职称，若助教则需要配备一名讲师协助指导。

讲师在前，助教在后。

指导教师姓名后面空一个中文空格，加职称。

页眉页眉说明宋体小五，左端“XX学院毕业设计（论文）”，右端“译文”。

页眉中的学院名称要与封面学院名称一致。

字数本科4000字。

附：外文资料和译文封面、空白页成都东软学院外文资料和译文专业：软件工程移动互联网应用开发班级：2班姓名：罗荣昆学号：12310420216指导教师：2015年 12月 8日Android page layoutUsing XML-Based LayoutsW hile it is technically possible to create and attach widgets to our activity purely through Java code, the way we did in Chapter 4, the more common approach is to use an XML-based layout file. Dynamic instantiation of widgets is reserved for more complicated scenarios, where the widgets are not known at compile-time (e g., populating a column of radio buttons based on data retrieved off the Internet).With that in mind, it’s time to break out the XML and learn how to lay out Android activities that way.What Is an XML-Based Layout?As the name suggests, an XML-based layout is a specification of widgets’ relationships to each other—and to their containers (more on this in Chapter 7)—encoded in XML format. Specifi cally, Android considers XML-based layouts to be resources, and as such layout files are stored in the res/layout directory inside your Android project.Each XML file contains a tree of elements specifying a layout of widgets and their containers that make up one view hierarchy. The attributes of the XML elements are properties, describing how a widget should look or how a container should behave. For example, if a Button element has an attribute value of android:textStyle = "bold", that means that the text appearing on the face of the button should be rendered in a boldface font style.Android’s SDK ships with a tool (aapt) which uses the layouts. This tool should be automatically invoked by your Android tool chain (e.g., Eclipse, Ant’s build.xml). Of particular importance to you as a developer is that aapt generates the R.java source file within your project, allowing you to access layouts and widgets within those layouts directly from your Java code. Why Use XML-Based Layouts?Most everything you do using XML layout files can be achieved through Java code. For example, you could use setTypeface() to have a button render its textin bold, instead of using a property in an XML layout. Since XML layouts are yet another file for you to keep track of, we need good reasons for using such files.Perhaps the biggest reason is to assist in the creation of tools for view definition, such as a GUI builder in an IDE like Eclipse or a dedicated Android GUI designer like DroidDraw1. Such GUI builders could, in principle, generate Java code instead of XML. The challenge is re-reading the UI definition to support edits—that is far simpler if the data is in a structured format like XML than in a programming language. Moreover, keeping generated XML definitions separated from hand-written Java code makes it less likely that somebody’s custom-crafted source will get clobbered by accident when the generated bits get re-generated. XML forms a nice middle ground between something that is easy for tool-writers to use and easy for programmers to work with by hand as needed.Also, XML as a GUI definition format is becoming more commonplace. Microsoft’s XAML2, Adobe’s Flex3, and Mozilla’s XUL4 all take a similar approach to that of Android: put layout details in an XML file and put programming smarts in source files (e.g., JavaScript for XUL). Many less-well-known GUI frameworks, such as ZK5, also use XML for view definition. While “following the herd” is not necessarily the best policy, it does have the advantage of helping to ease the transition into Android from any other XML-centered view description language. OK, So What Does It Look Like?Here is the Button from the previous chapter’s sample application, converted into an XMLlayout file, found in the Layouts/NowRedux sample project. This code sample along with all others in this chapter can be found in the Source Code area of .<?xml version="1.0" encoding="utf-8"?><Button xmlns:android="/apk/res/android"android:id="@+id/button"android:text=""android:layout_width="fill_parent"android:layout_height="fill_parent"/>The class name of the widget—Button—forms the name of the XML element. Since Button is an Android-supplied widget, we can just use the bare class name. If you create your own widgets as subclasses of android.view.View, you would need to provide a full package declara tion as well.The root element needs to declare the Android XML namespace:xmlns:android="/apk/res/android"All other elements will be children of the root and will inherit that namespace declaration.Because we want to reference this button from our Java code, we need to give it an identifier via the android:id attribute. We will cover this concept in greater detail later in this chapter.The remaining attributes are properties of this Button instance:• android:text indicates the initial text to be displayed on the button face (in this case, an empty string)• android:layout_width and android:layout_height tell Android to have the button’swidth and height fill the “parent”, in this case the entire screen—these attributes will be covered in greater detail in Chapter 7.Since this single widget is the only content in our activity, we only need this single element. Complex UIs will require a whole tree of elements, representing the widgets and containers that control their positioning. All the remaining chapters of this book will use the XML layout form whenever practical, so there are dozens of other examples of more complex layouts for you to peruse from Chapter 7 onward.What’s with the @ Signs?Many widgets and containers only need to appear in the XML layout file and do not need to be referenced in your Java code. For example, a static label (TextView) frequently only needs to be in the layout file to indicate where it should appear. These sorts of elements in the XML file do not need to have the android:id attribute to give them a name.Anything you do want to use in your Java source, though, needs an android:id.The convention is to use @+id/... as the id value, where the ... represents your locally unique name for the widget in question. In the XML layout example in the preceding section, @+id/button is the identifier for the Button widget.Android provides a few special android:id values, of the form @android:id/.... We will see some of these in various chapters of this book, such as Chapters 8 and 10.We Attach These to the Java How?Given that you have painstakingly set up the widgets and containers in an XML layout filenamed main.xml stored in res/layout, all you need is one statement in your activity’s onCreate() callback to use that layout:setContentView(yout.main);This is the same setContentView() we used earlier, passing it an instance of a View subclass (in that case, a Button). The Android-built view, constructed from our layout, is accessed from that code-generated R class. All of the layouts are accessible under yout, keyed by the base name of the layout file—main.xml results in yout.main.To access our identified widgets, use findViewById(), passing in the numeric identifier of the widget in question. That numeric identifier was generated by Android in the R class asR.id.something (where something is the specific widget you are seeking). Those widgets are simply subclasses of View, just like the Button instance we created in Chapter 4.The Rest of the StoryIn the original Now demo, the button’s face would show the current time, which would reflect when the button was last pushed (or when the activity was first shown, if the button had not yet been pushed).Most of that logic still works, even in this revised demo (NowRedux). However,rather than instantiating the Button in our activity’s onCreate() callback, we can reference the one from the XML layout:package youts;import android.app.Activity;import android.os.Bundle;import android.view.View;import android.widget.Button; import java.util.Date;public class NowRedux extends Activity implements View.OnClickListener { Button btn;@Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);btn=(Button)findViewById(R.id.button);btn.setOnClickListener(this);upd ateTime();}public void onClick(View view) { updateTime();}private void updateTime() {btn.setText(new Date().toString()); }}The first difference is that rather than setting the content view to be a view we created in Java code, we set it to reference the XML layout (setContentView(yout.main)). The R.java source file will be updated when we rebuild this project to include a reference to our layout file (stored as main.xml in our project’s res/l ayout directory).The other difference is that we need to get our hands on our Button instance, for which we use the findViewById() call. Since we identified our button as @+id/button, we can reference the button’s identifier as R.id.button. Now, with the Button instance in hand, we can set the callback and set the label as needed.As you can see in Figure 5-1, the results look the same as with the originalNow demo.Figure 5-1. The NowRedux sample activity Employing Basic WidgetsE very GUI toolkit has some basic widgets: fields, labels, buttons, etc. Android’s toolkit is no different in scope, and the basic widgets will provide a good introduction as to how widgets work in Android activities.Assigning LabelsThe simplest widget is the label, referred to in Android as a TextView. Like in most GUI toolkits, labels are bits of text not editable directly by users. Typically, they are used to identify adjacent widgets (e.g., a “Name:” label before a field where one fills in a name).In Java, you can create a label by creating a TextView instance. More commonly, though, you will create labels in XML layout files by adding a TextView element to the layout, with an android:text property to set the value of the label itself. If you need to swap labels based on certain criteria, such as internationalization, you may wish to use a resource reference in the XML instead, as will be described in Chapter 9. TextView has numerous other properties of relevance for labels, such as:• android:typeface to set the typeface to use for the label (e.g., monospace) • android:textStyle to indicate that the typeface should be made bold (bold), italic (italic),or bold and italic (bold_italic)• android:textColor to set the color of the label’s text, in RGB hex format (e.g., #FF0000 for red)For example, in the Basic/Label project, you will find the following layout file:<?xml version="1.0" encoding="utf-8"?><TextView xmlns:android=/apk/res/androidandroid:layout_width="fill_parent"android:layout_height="wrap_content"android:text="You were expecting something profound?" />As you can see in Figure 6-1, just that layout alone, with the stub Java source provided by Android’s p roject builder (e.g., activityCreator), gives you the application.Figure 6-1. The LabelDemo sample applicationButton, Button, Who’s Got the Button?We’ve already seen the use of the Button widget in Chapters 4 and 5. As it turns out, Button is a subclass of TextView, so everything discussed in the preceding section in terms of formatting the face of the button still holds. Fleeting ImagesAndroid has two widgets to help you embed images in your activities: ImageView and ImageButton. As the names suggest, they are image-based analogues to TextView and Button, respectively.Each widget takes an android:src attribute (in an XML layout) to specify what picture to use. These usually reference a drawable resource, described in greater detail in the chapter on resources. You can also set the image content based on a Uri from a content provider via setImageURI().ImageButton, a subclass of ImageView, mixes in the standard Button behaviors, for responding to clicks and whatnot.For example, take a peek at the main.xml layout from the Basic/ImageView sample project which is found along with all other code samples at : <?xml version="1.0" encoding="utf-8"?><ImageView xmlns:android=/apk/res/androidandroid:id="@+id/icon"android:layout_width="fill_parent"android:layout_height="fill_parent"android:adjustViewBounds="true"android:src="@drawable/molecule" />The result, just using the code-generated activity, is shown in Figure 6-2.Figure 6-2. The ImageViewDemo sample applicationFields of Green. Or Other Colors.Along with buttons and labels, fields are the third “anchor” of most GUI toolkits. In Android, they are implemented via the EditText widget, which is a subclass of the TextView used for labels.Along with the standard TextView properties (e.g., android:textStyle), EditText has many others that will be useful for you in constructing fields, including:• android:autoText, to control if the fie ld should provide automatic spelling assistance• android:capitalize, to control if the field should automatically capitalize the first letter of entered text (e.g., first name, city) • android:digits, to configure the field to accept only certain digi ts • android:singleLine, to control if the field is for single-line input or multiple-line input (e.g., does <Enter> move you to the next widget or add a newline?)Beyond those, you can configure fields to use specialized input methods, such asandroid:numeric for numeric-only input, android:password for shrouded password input,and android:phoneNumber for entering in phone numbers. If you want to create your own input method scheme (e.g., postal codes, Social Security numbers), you need to create your own implementation of the InputMethod interface, then configure the field to use it via android: inputMethod.For example, from the Basic/Field project, here is an XML layout file showing an EditText:<?xml version="1.0" encoding="utf-8"?><EditTextxmlns:android=/apk/res/androidandroid:id="@+id/field"android:layout_width="fill_parent"android:layout_height="fill_parent"android:singleLine="false" />Note that android:singleLine is false, so users will be able to enter in several lines of text. For this project, the FieldDemo.java file populates the input field with some prose:package monsware.android.basic;import android.app.Activity;import android.os.Bundle;import android.widget.EditText;public class FieldDemo extends Activity { @Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);EditText fld=(EditText)findViewById(R.id.field);fld.setText("Licensed under the Apache License, Version 2.0 " + "(the \"License\"); you may not use this file " + "except in compliance with the License. You may " + "obtain a copy of the License at " +"/licenses/LICENSE-2.0");}}The result, once built and installed into the emulator, is shown in Figure 6-3.Figure 6-3. The FieldDemo sample applicationNote Android’s emulator only allows one application in the launcher per unique Java package. Since all the demos in this chapter share the monsware.android.basic package, you will only see one of these demos in your emulator’s launcher at any one time.Another flavor of field is one that offers auto-completion, to help users supply a value without typing in the whole text. That is provided in Android as the AutoCompleteTextView widget and is discussed in Chapter 8.Just Another Box to CheckThe classic checkbox has two states: checked and unchecked. Clicking the checkbox toggles between those states to indicate a choice (e.g., “Ad d rush delivery to my order”). In Android, there is a CheckBox widget to meet this need. It has TextView as an ancestor, so you can use TextView properties likeandroid:textColor to format the widget. Within Java, you can invoke: • isChecked() to determi ne if the checkbox has been checked• setChecked() to force the checkbox into a checked or unchecked state • toggle() to toggle the checkbox as if the user checked itAlso, you can register a listener object (in this case, an instance of OnCheckedChangeListener) to be notified when the state of the checkbox changes.For example, from the Basic/CheckBox project, here is a simple checkbox layout:<?xml version="1.0" encoding="utf-8"?><CheckBox xmlns:android="/apk/res/android"android:id="@+id/check"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="This checkbox is: unchecked" />The corresponding CheckBoxDemo.java retrieves and configures the behavior of the checkbox:public class CheckBoxDemo extends Activityimplements CompoundButton.OnCheckedChangeListener { CheckBox cb;@Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);cb=(CheckBox)findViewById(R.id.check);cb.setOnCheckedChangeListener(this);}public void onCheckedChanged(CompoundButton buttonView,boolean isChecked) {if (isChecked) {cb.setText("This checkbox is: checked");}else {cb.setText("This checkbox is: unchecked");}}}Note that the activity serves as its own listener for checkbox state changes since it imple ments the OnCheckedChangeListener interface (via cb.setOnCheckedChangeListener(this)). The callback for the listener is onCheckedChanged(), which receives the checkbox whose state has changed and what the new state is. In this case, we update the text of the checkbox to reflect what the actual box contains.The result? Clicking the checkbox immediately updates its text, as you can see in Figures 6-4 and 6-5.Figure 6-4. The CheckBoxDemo sample application, with the checkbox uncheckedFigure 6-5. The same application, now with the checkbox checkedTurn the Radio UpAs with other implementations of radio buttons in other toolkits, Android’s radio buttons are two-state, like checkboxes, but can be grouped such that only one radio button in the group can be checked at any time.Like CheckBox, RadioButton inherits from CompoundButton, which in turn inherits fromTextView. Hence, all the standard TextView properties for font face, style, color, etc., are available for controlling the look of radio buttons. Similarly, you can call isChecked() on a RadioButton to see if it is selected, toggle() to select it, and so on, like you can with a CheckBox.Most times, you will want to put your RadioButton widgets inside of aRadioGroup. The RadioGroup indicates a set of radio buttons whose state is tied, meaning only one button out of the group can be selected at any time. If you assign an android:id to your RadioGroup in your XML layout, you can access the group from your Java code and invoke:• check() to check a specific radio button via its ID (e.g., group.check(R.id.radio1))• clearCheck() to clear all radio buttons, so none in the group are checked• getCheckedRadioButtonId() to get the ID of the currently-checked radio button (or -1 if none are checked)For example, from the Basic/RadioButton sample application, here is an XML layout showing a RadioGroup wrapping a set of RadioButton widgets: <?xml version="1.0" encoding="utf-8"?> <RadioGroupxmlns:android=/apk/res/androidandroid:orientation="vertical"android:layout_width="fill_parent"android:layout_height="fill_parent" ><RadioButton android:id="@+id/radio1"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Rock" /><RadioButton android:id="@+id/radio2"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Scissors" /><RadioButton android:id="@+id/radio3"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Paper" /></RadioGroup>Figure 6-6 shows the result using the stock Android-generated Java forthe project and this layout.Figure 6-6. The RadioButtonDemo sample application Note that the radio button group is initially set to be completely unchecked at the outset. To pre-set one of the radio buttons to be checked, use either setChecked() on the RadioButton or check() on the RadioGroup from within your onCreate() callback in your activity.It’s Quite a ViewAll widgets, including the ones previously shown, extend View, and as such give all widgets an array of useful properties and methods beyond those already described.Useful PropertiesSome of the properties on View most likely to be used include:• Controls the focus sequence:• android:nextFocusDown• android:nextFocusLeft• android:nextFocusRight• android:nextFocusUp• android:visibility, which controls wheth er the widget is initially visible• android:background, which typically provides an RGB color value (e.g., #00FF00 for green) to serve as the background for the widgetUseful MethodsYou can toggle whether or not a widget is enabled via setEnabled() and see if it is enabled via isEnabled(). One common use pattern for this is to disable some widgets based on a CheckBox or RadioButton selection.You can give a widget focus via requestFocus() and see if it is focused via isFocused(). You might use this in concert with disabling widgets as previously mentioned, to ensure the proper widget has the focus once your disabling operation is complete.To help navigate the tree of widgets and containers that make up an activity’s overall view, you can use:• get Parent() to find the parent widget or container• findViewById() to find a child widget with a certain ID• getRootView() to get the root of the tree (e.g., what you provided to the activity via setContentView())Android 页面布局使用XML进行布局虽然纯粹通过Java代码在activity上创建和添加部件，在技术上是可行的，我们在第4章中做的一样，更常见的方法是使用一种基于XML的布局文件。

文献综述和外文翻译撰写要求与格式规范

本科毕业论文（设计)文献综述和外文翻译撰写要求与格式规范一、毕业论文(设计)文献综述（一）毕业论文（设计）文献综述的内容要求1．封面：由学院统一设计，普通A4纸打印即可。

2.正文综述正文部分需要阐述所选课题在相应学科领域中的发展进程和研究方向,特别是近年来的发展趋势和最新成果.通过与中外研究成果的比较和评论，说明自己的选题是符合当前的研究方向并有所进展，或采用了当前的最新技术并有所改进，目的是使读者进一步了解本课题的意义。

文中的用语、图纸、表格、插图应规范、准确,量和单位的使用必须符合国家标准规定，引用他人资料要有标注。

文献综述字数在5000字以上。

正文前须附500字左右中文摘要，末尾须附参考文献。

参考文献的著录按在文献综述中出现的先后顺序编号.期刊类文献书写方法:［序号］作者（不超过3人，多者用等表示）.题(篇）名[J]。

刊名,出版年，卷次（期次）：起止页次.图书类文献书写方法:[序号]作者.书名[M].版本.出版地：出版者,出版年:起止页次。

论文集类文献书写方法:［序号］作者.篇名［C].论文集名.出版地：出版者，出版年:起止页次。

学位论文类书写方法：［序号]作者.篇名[D]。

出版地：单位名称，年份。

电子文献类书写方法:［序号]主要责任者。

题名:其他题名信息[文献类型标志/文献载体标志］出版地:出版者,出版年(更新或修改日期）[引用日期].获取和访问途径。

参考文献篇数应符合学院毕业论文(设计）工作的要求。

（二）毕业论文（设计）文献综述撰写与装订的格式规范第一部分：封面1。

封面：由学院统一设计，“本科生毕业论文（设计）"根据作业实际明确为“论文”或“设计”,其它文本、表格遇此类情况同样处理。

第二部分：文献综述主题1.中文摘要与关键词摘要标题(五号，宋体，顶格，加粗）摘要内容(五号，宋体）关键词标题(五号，宋体，顶格,加粗）关健词内容（五号,宋体，词间用分号隔开）2.正文标题标题最多分四级。

外文翻译格式说明

山东理工大学毕业设计（外文翻译材料）学院：专业：学生姓名：指导教师：电气与电子工程学院自动化于小涵季画外文翻译材料格式要求：1.页边距：上3.8磅；下3.8磅；左3.2，右3.2；页眉距边界2.8，页脚距边界32.原文题目：Arial，小三；间距：段前18磅，段后12磅，间距21磅3.原文正文：Times New Roman，小四；间距：段前0磅，段后6磅，间距21磅4.译文题目：黑体，小三；间距：同原文题目5.译文正文：宋体，小四；间距同原文正文6.页眉页脚：原文页眉处写：外文翻译（原文），宋体，五号。

译文页眉处写：外文翻译（译文），宋体，五号。

原文译文的页脚统一编页码（不要单独编页码）。

Plant Model Generation for PLC SimulationHyeong-Tae ParkAbstract:This paper reports an automated procedure for constructing a plant model for PLC simulation. Since PLC programs contain only the control logic without information on the plant model, it is necessary to build the corresponding plant model to perform the simulation. Conventionally, a plant model for PLC simulation has been constructed manually, which requires much effort and indepth knowledge of the simulation. As a remedy for this problem, we propose an automated procedure for generating a plant model from the symbol table of a PLC program. To do so, we propose a naming rule for PLC symbols so that the symbol names include sufficient information on the plant model. By analysing such symbol names, we extract a plant model automatically. The proposed methodology has been implemented and test runs performed.Keywords: agile manufacturing; CAD/CAM; CAPP; simulation1. IntroductionTo survive and prosper in the modern manufacturing era, manufacturers need to continuously improve their products, as well as their production systems. A modern manufacturing line is a highly integrated system composed of automated workstations, such as robots with tool-changing capabilities, a hardware handling system and storage system, and a computer control system that controls the operations of the- 1 -entire system.Since the implementation of a manufacturing line requires heavy investment, proper verification of a line’s operational status sho uld be performed to ensure that the highly automated manufacturing system will successfully achieve the intended benefits. Simulation technology is considered to be an essential tool in the design and analysis of complex systems that cannot be easily described by analytical or mathematical models . Simulation is useful for calculating utilisation statistics, finding bottlenecks, pointing out scheduling errors, and even for creating manufacturing schedules. Traditionally, various simulation languages, including ARENA and AutoMod, have been used for the simulation of manufacturing systems. These simulation languages have been widely accepted both by industry and by academia; however, they remain as analysis tools for the rough design stage of a production line, because their simulation models are not sufficiently realistic to be utilised for a detailed design or for implementation purposes. For example, real production lines are usually controlled by PLC (Programmable Logic Controller) programs (Rullan 1997), but conventional simulation languages roughly describe the control logic with independent entity flows (job flows) between processes.- 2 -Production systems typically consist of simultaneously operating machines, which are controlled by PLCs, currently the most suitable and widely employed industrial control technology. A PLC emulates the behaviour of an electric ladder diagram. As they are sequential machines, to emulate the workings of parallel circuits that respond instantaneously, PLCs use an input/output symbol table and a scanning cycle. When a program is being run in a PLC it is continuously executing a scanning cycle. The program scan solves the Boolean logic related to the information in the input table with that in the output and internal relay tables. In addition, the information in the output and internal relay tables is updated during the program scan. In a PLC, this Boolean logic is typically represented using a graphical language known as a ladder diagram (IEC 2003).Since the abstraction levels of conventional simulators and PLC programs are quite different, the control logic of conventional simulators cannot be reused for the generation of PLC programs. Usually, electrical engineers manually write PLC programs by referring to the rough control logic of conventional simulators, as shown in Figure 1. Since PLC programming is a very tedious and error-prone job, it is essential to verify the PLC programs offline to reduce the stabilisation time of a production system.Previous approaches to a PLC program can be categorised into two groups:- 3 -(1) verification of a given PLC programand (2) generation of a dependable PLC program. In the first group, various software tools have been developed for the verification of PLC based systems via the use of timed automata, such as UPPAAL2k, KRONOS, Supremica and HyTech, mainly for programs written in a statement list language, also termed Boolean (Manesis and Akantziotis 2005). Such software tools verify PLC programs to a certain extent; however, they remain limited. Since they mainly focus on the checking of theoretical attributes (safety, liveness, and reachability), it is not easy for users to determine whether the PLC programs actually achieve the intended control objectives. In the second group, many researchers have focused on the automatic generation of PLC programs from various formalisms including state diagrams, Petri nets, and IDEF0. These formalisms can help the design process of control logics; however, it is still difficult to find hidden errors, which is the most difficult part of verifying a control program.Figure 2. The concept of PLC simulation.To overcome the aforementioned problems, it is necessary to utilise simulation techniques for PLC program verification. By simulating PLC programs, it is possible to analyse the control logic in various ways and recognise hidden errors more intuitively (David 1998). Although PLC simulation can be a very powerful tool for the detailed verification of a production system, the accompanying construction of a plant model is a major obstacle (the counterpart model of a control program). Since PLC programs only contain the control information, without device models, it is necessary to build a corresponding plant model to perform simulation, as shown in- 4 -Figure 2. However, constructing a plant model requires an excessive amount of time and effort. Sometimes, the plant model construction requires much more time than the PLC programming. This serves as the motivation for exploring the possibility of finding an automatic procedure for generating a plant model from a given PLC program.Figure3.Symbol table of a PLC program.Although the objective of a PLC program is not to describe a plant model (device models), the symbol table of a PLC program can provide a glimpse of the plant model. As shown in Figure 3, symbols in a PLC program usually contain some information related to the plant. For example, ‘EXLINE_MB_AGV_P1’ means that the symbol is a signal that is related to the control of an ‘AGV’ (Auto Guided Vehicl e) belonging to the ‘MB’ station of ‘EXLINE’ line. The above scenario reveals the key idea of the present study. If we can develop a proper naming rule for PLC symbols, then it might be possible to extract a plant model by analysing the symbol names.This paper has two major objectives: (1) to propose a proper naming rule for PLC symbols and (2) to develop a procedure for generating a plant model by analysing the symbol names. The application area of the proposed methodology includes all types of automated manufacturing systems controlled by PLC programs, such as automotive production lines, FMSs (flexible manufacturing systems), and ASRSs (automatic storage and retrieval systems). The overall structure of the paper is as follows. Section 2 addresses the specifications of a plant model for PLC simulation. Section 3 describes a naming rule for PLC symbols, which enables the automatic generation of a plant model. Finally, concluding remarks are given in Section 4.2. Plant model for PLC simulationBefore explaining the specification of a plant model enabling PLC simulation, we want to address the importance of the PLC simulation. Chuang et al. (1999) proposed a procedure for the development of an industrial automated production system that- 5 -- 6 -consists of nine steps, as follows: (1) define the process to be controlled; (2) make a sketch of the process operation; (3) create a written sequence of the process; (4) on the sketch, add the sensors needed to carry out the control sequence; (5) add the manual controls needed for the process setup or for operational checks; (6) consider the safety of the operating personnel and make additions and adjustments as needed;(7) add the master stop switches required for a safe shutdown; (8) create a ladder logic diagram that will be used as a basis for thePLC program; and (9) consider the possible points where the process sequence may go astray. The most time-consuming task for the control logic designers is the eighth step, which is usually done by the repetitive method of code writing, testing, and debugging until the control objectives are achieved (Manesis and Akantziotis 2005). This is the reason why conventional PLC programming is often inefficient and prone to human error. As the configurations of production lines and their control programs become more complicated, there is a strong need for a more efficient PLC simulation environment. It is hoped that this paper will take positive steps in this direction.A PLC can be considered as a dedicated computer system having input and output signals. To run a PLC, the corresponding plant model (the counterpart system) is required to interact with the input and output of the PLC. The behaviour of the plant model should be the same as that of the actual system to achieve PLC verification. Since a production line consists of various devices, including robots, transporters, jigs, solenoids, proximity sensors, and light sensors (Groover 2006), we can consider a plant model as a set of device models. To build such a device model, this paper em ploys Zeigler’s DEVS (Discrete Event Systems Specifications) formalism (Zeigler 1984, Kim 1994), which supports the specification of discrete event models in a hierarchical, modular manner. The semantics of the formalism are highly compatible with object-oriented specifications for simulation models. We use the atomic model of the DEVS formalism to represent the behavior of a device model. Formally, an atomic model M is specified by a 7-tuple:M =〈X, S,Y, sin δ,ext δ,λ ,t a 〉X input events setS sequential states setY output events setsin δ S→S: internal transition functionext δQ*X→S: external transition functionQ={(s, e)∣s ∈S, 0≤e ≤t a (s)}: total state of MλS →Y: output function- 7 -t a S →Real: time advance functionThe four elements in the 7-tuple, namely sin δ,ext δ,λand t a , are called the characteristic functions of an atomic model. The atomic model of the DEVS formalism can be considered as a timed-FSA (finite state automata), and it is suitable for describing the behaviour of a device model. Once the device models (plant model) are obtained, it becomes possible to perform the PLC simulation. Currently, device models should be construed manually, which takes much time and effort. To cope with the problem, the objective of the paper is to propose an automated generation procedure for device models.Before explaining the automatic generation procedure of a plant model, let us take a look at the manual procedure to construct device models. To construct a device model, first it is necessary to identify the set of tasks that are assigned to the device. The activation of each task is normally triggered by an external signal from PLC programs. Once the set of tasks is identified for a device, it is then possible to extract the state transition diagram, which defines an atomic model of the DEVS formalism. Figure 4(a) shows a simple example of an AGV (Automatic Guided Vehicle) with two tasks, T1 (movement from p1 to p2) and T2 (movement from p2 to p1). As the two tasks should be triggered by external events, the shell part of the AGV must have two input ports, termed here as Signal_1 and Signal_2, as shown in Figure 4(b).From the set of tasks, it is possible to instantiate the state transition diagram. For this example, there are four states, P1, DoT1, P2 and DoT2. While P1 and P2 take external events from the input ports (Signal_1, Signal_2) for state transitions, DoT1 and DoT2 take internal events that are the end events of the two tasks (T1 and T2). The DEVS atomic model of the virtual device, corresponding to the AGV, can be described as follows:- 8 -Shell of a virtual device:M=〈X,S,Y,sin δ,ext δ,λ ,t a 〉}2_,1_{Signal Signal =X S={P1,DOT1,P2,DOT2} Y={T1Done,T2Done}sin δ(DOT1)=P2 s i nδ(DOT2)=P1 ext δ(P1,Signal_1)=DOT1 ext δ(P2,Signal_2)=DOT2λ(DOT1)=T1Done λ(DOT2)=T2Donet a (DOT1)=Time_1 t a (DOT2)=Time_2Once a plant model has been constructed, it is possible to perform the PLC simulation, which enables the intuitive verification of a PLC program. Figure 5 shows the connections between a PLC program and a plant model. The plant model includes all device models of a production system, and the PLC program contains the control logic for the plant model. To integrate the plant model and the PLC program, it is necessary to define the mapping between the plant model and the PLC program, which is described by I/O mapping. To enable the visual verification of a PLC program, it is necessary to import 3D graphic models, which are controlled by the logical device models (the state transition diagrams). Since 3D graphic models are not always necessary, they are optional for PLC simulation. As mentioned already, the objective of this paper is to extract device models from the symbol names of PLC programs. To do so, it is necessary to develop a proper naming rule for PLC symbols. The naming rule will be addressed in the next section.3. Symbol naming for plant model generationAlthough IEC 61131-3 provides various standard specifications for a PLC, the naming rules of PLC symbols have rarely been brought into focus. Since there have been no standard rules for the naming of PLC symbols, it has been fully dependent on individual PLC programmers.To generate device models from PLC symbols, it is necessary to make PLC symbols that include enough information concerning the plant model. To achieve this objective, we interviewed many PLC programmers and analysed various conventional rules. As a result, we came up with a naming structure consisting of five fields: (1) line name, (2) process number, (3) device name, (4) input or output, and (5) task name (or state name). Figure 6 shows the naming structure for PLC symbols.If the PLC symbols are named according to the proposed naming structure, then it becomes possible to extract device models (atomic models of DEVS formalism) by simply analysing the symbol names. There are two types of symbols (signals), input or output, which are specified by the fourth field. The purpose of the output signal is to trigger a task that is specified by the fifth field. Thus, it is possible to identify the set of tasks of a device by analysing the output symbols. As mentioned already, once the set of tasks is identified for a device, it is then possible to extract the state transition diagram for the device model, which defines an atomic model of the DEVS formalism. While an output signal (symbol) is issued by a PLC to trigger a task, an input signal (symbol) is issued by a device to report the completion of the task to theδand internal transition functions PLC. This means that external transition functionsextδof a device model can be automatically extracted from the output and input sinsymbols, respectively. We demonstrate the generation procedure of a plant modelfrom PLC symbols using an example, as shown in Figure 7.- 9 -- 10 -In the example cell, we assume a part is loaded manually on the AGV by a worker. When the AGV senses the existence of a part, it moves to transfer the part to the machine. After the transfer, the machine performs machining to convert the part into a finished product. In this case, the plant model consists of two device models: an AGV model and a machine model. The PLC program to control the simple manufacturing cell is shown in Figure 8(a), and its symbol table is shown in Figure 8(b).As shown in Figure 8(b), the AGV model has two output symbols and two input symbols. From the output symbols (EX_OP_AGV_O_GOP1, EX_OP_AGV_O_GOP2), we can intuitively recognise that the AGV has two tasks- 11 -(movement from P2 to P1, and movement from P1 to P2). By using the output symbols, we can extract the state transition diagram, as well as the external transitionfunctions, as shown in Figure 9(a).As mentioned already, an output symbol triggers a task of a device model, and an input symbol is made by the device to notify the completion of the task. Since the execution of a task is performed internally by the device, the internal transition functions of a device model can easily be extracted from the input symbols(EX_OP_AGV_I_DONEGOP1, EX_OP_AGV_I_DONEGOP2). In this way, the device model of the machine can be extracted from the related symbols(EX_OP_MC_, etc.), as shown in Figure 9(b). The procedure for the construction of a device model can be described as follows.- 12 -(1) Identify all corresponding pairs between output symbols and input symbols. While an output symbol triggers a task, the corresponding input symbol reports the completion of the task. For example, EX_OP_AGV_O_GOP1 corresponds toEX_OP_AGV_I_DONEGOP1. (2) Define the states of a device mode using the last naming fields of input/output symbols. In the case of the AGV, we can define four states, GoP1, DoneGoP1, GoP2, and DoneGoP2. (3) Define external (internal) transition functions using output (input) symbols. Once a plant model has been obtained, it becomes possible to perform the PLC simulation by defining the I/O mapping relations between the plant model and the PLC symbols. Through the PLC simulation, we can efficiently check whether the PLC program achieves the control objectives or not.The proposed methodology was implemented in C++language, and test runs were made on a personal computer, as shown in Figure 10. The PLC program shown in Figure 8(a) was written using GX IEC developer version 7.0 provided byMitsubishi Electric Corporation. The GX IEC developer can export a symbol table in the form of an Excel file, as shown in Figure 8(b). The exported symbol table becomes the input for the generation of a plant model. Figure 10 shows that the generated device models by analysing the exported symbol table.4. Discussion and conclusionsThrough PLC simulation, it is possible to analyse control logic in various ways and recognise hidden errors more intuitively. Although PLC simulation can be a very powerful tool for the detailed verification of a production system, the accompanying construction of a plant model requires too much time and effort. To remedy this problem, we have proposed an automated procedure to generate a plant model from the symbol table of a PLC program. To do so, we have also proposed a naming rule for PLC symbols so that the symbol names include sufficient information on the plant model. By analysing the symbol names, a plant model can be extracted automatically. Since a plant consists of various manufacturing devices, we can consider a plant model as a set of device models. To represent such a device model, the proposed method employs Zeigler’s DEVS formalism. We use the atomic model of the DEVS formalism to describe the logical behavior of a device model. In other words, it is necessary to extract the device models from the symbol table in the form of an atomic model of the DEVS formalism. Although the proposed methodology only deals with the local verification of PLC programs, it is also possible to extend the methodologyto include the verification of mechanical aspects of the plant .- 13 -工厂模型生成PLC仿真Hyeong-Tae Park摘要 :本文介绍一个自动程序可编程序控制器(PLC)生成工厂模型仿真。

外文文献翻译格式要求

外文文献翻译格式要求：，行间距设（ 1）摘要，关键词：宋体五号（其中“摘要”和“关键词”为宋体五号加粗）置为 18 磅，段前段后间距设置为 0.5 行，对齐方式选择“两端对齐”方式；各个关键词之间以分号（；）或者（，）隔开，最后一个关键词后不加标点；（ 2）正文一级标题：采用黑体小三号加粗，行间距设置为20 磅，段前段后间距设置为0.5行，一般采用“ 1 引言”样式，其中 1 和“引言”之间用一个空格分开；正文二级标题：采用黑体小三号，行间距设置为20 磅，段前段后间距设置为0.5 行，一般采用“ 2.1 系统原理”样式，其中 1 和“系统原理”之间用一个空格分开；；一级标题和二级标题采用“左对齐”方式；（ 3）正文内容：采用宋体小四号，行间距设置为 20 磅，段前段后间距设置为 0 行，首行缩进 2 字符，正文对齐方式在段落格式设置中选择“两端对齐”，遇正文中有公式的，设置该行（段）行间距为“单倍行距”（ 4）插图：请设置图片版式为“浮于文字上方”，并勾选“居中”，图片大小根据版面，按比例适当进行缩放，图示说明采用“图 1 主控制器的结构图”样式置于图下，图序与说明以一个空格字符间隔，图示说明采用宋体五号，居中对齐，行间距设置为“单倍行距”，段前段后距设置为 0.5 行；（ 5）表格：在表格属性中选择“居中”对齐方式，表格说明采用“表 1 两种方法试验数据比较”样式置于表格上方，表序与说明以一个空格字符间隔，表格说明采用宋体五号，居中对齐，行间距设置为“单倍行距”，段前段后距设置为 0.5 行；（6）参考文献：“参考文献”格式同一级标题格式，参考文献内容采用宋体五号，行间距设置为 18 磅，段前段后间距设置为 0 行，对齐方式选择“左对齐”方式，其中出现的标点一律采用英文标点；Times 以上摘要，关键词，正文，标题及参考文献中出现的英文字符和数字，一律设置为“　New Roman ”字体。

另外：外文文献翻译附于开题报告之后：第一部分为译文，第二部分为外文文献原文，译文与原文均需单独编制页码（底端居中）并注明出处。

外文翻译及外文原文(参考格式)

外文翻译要求：1、外文资料与毕业设计（论文）选题密切相关，译文准确、质量好。

2、阅读2篇幅以上（10000字符左右）的外文资料，完成2篇不同文章的共2000汉字以上的英译汉翻译3、外文资料可以由指导教师提供，外文资料原则上应是外国作者。

严禁采用专业外语教材文章。

4、排序：“一篇中文译文、一篇外文原文、一篇中文译文、一篇外文原文”。

插图内文字及图名也译成中文。

5、标题与译文格式（字体、字号、行距、页边距等）与论文格式要求相同。

下页附：外文翻译与原文参考格式2英文翻译 (黑体、四号、顶格)外文原文出处：(译文前列出外文原文出处、作者、国籍，译文后附上外文原文)《ASHRAE Handbook —Refrigeration 》.CHAPTER3 .SYSTEM Practices for ammonia 3.1 System Selection 3.2 Equipment3.10 Reciprocating Compressors第3章氨制冷系统的实施3.1 系统选择在选择一个氨制冷系统设计时，须要考虑一些设计决策要素，包括是否采用（1）单级压缩（2）带经济器的压缩（3）多级压缩（4）直接蒸发（5）满液式（6）液体再循环（7）载冷剂。

单级压缩系统基本的单级压缩系统由蒸发器、压缩机、冷凝器、储液器（假如用的话）和制冷剂控制装置（膨胀阀、浮球阀等）。

1997 ASHRAE 手册——“原理篇”中的第一章讨论了压缩制冷循环。

图1.壳管式经济器的布置外文翻译的标题与译文中的字体、字号、行距、页边距等与论文格式相同。

英文原文(黑体、四号、顶格)英文翻译2（黑体，四号，顶格）外文原文出处：（黑体，四号，顶格）P. Fanning. Nonlinear Models of Reinforced and Post-tensioned Concrete Beams. Lecturer, Department of Civil Engineering, University College Dublin. Received 16 Jul 2001.非线形模型钢筋和后张法预应力混凝土梁摘要:商业有限元软件一般包括混凝土在荷载做用下非线性反应的专用数值模型。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

电气与新能源学院毕业设计（开题报告）装订、排版顺序及
格式要求
(2011届毕业设计严格按照以下要求执行)
(本页仅为交电子文档时使用)
毕业设计（论文）
开题报告
题目
学生姓名学号
专业班级
指导教师
评阅教师
完成日期年月日
20 1
网络教学的设计与评价研究(宋体小二号加粗居中)
（空一行）
学生：吴雨飞(宋体五号居中)
指导教师：刘向阳(宋体五号居中)
（三峡大学电气与新能源学院）(楷体五号居中)
（空一行）（正文不少于2500汉字）
1课题来源（黑体3号加粗）
本课题为……课题，……。

（空一行）
2 研究的目的和意义（黑体3号加粗）
2.1促进网络教学的发展，提高网络教学的质量（黑体小3号加粗）
由于网络教学可以实现信息资源共享，在网上组织最优秀的教材和教法，使学习者在网上可以学到最新的知识，因此是教学改革发展的方向。

通过本项目的研究与实践，使网络教学更能为学习者提供一个建构主义的学习环境，充分体现学生的首创精神，学生有更多的机会在不同情境下去运用他们所学的知识，而且学生可以根据自身的行动的反馈来形成对客观事物的认识和解决实际问题的方案，从而提供网络教学的质量。

(宋体小四号)
2.2寻找利用计算机技术和网络技术实现学生远程交互自主学习的教
学设计的技术解决方案
2.3完善和发展教学设计理论
网络环境下的教学与传统教学，不仅是教学环境的不同，在教学内容、教学手段、教学传播形式上都有本质的区别。

通过本项目的研究，能够解决网络环境下，教学如何进行教学设计，如何调控教学过程，如何有效实施教学活动以达成教学目标，是对教学设计理论的完善和发展。

（空一行）
3 国内外的研究现状和发展趋势
3.1网络教学的设计理论与方法的研究缺乏系统性
通过对国内外有关的学术刊物（如《电化教育研究》、《中国电化教育》、《Educational Technology》等）、教育网站和国际国内有关学术会议（GCCCE、ICCE、CBE等）的论文集进行分析，网络教学的设计研究主要是关于建构主义学习环境的设计和协作学习的设计等方面，缺乏系统的研究[1][2]。

可以说，网络教学的设计理论的研究还处于初级阶
20 2
段，还有很多问题需要去研究和探索。

例如，在网络环境下如何利用网络资源进行主动学习、利用虚拟情境进行探究学习、利用通讯工具进行协商学习、利用工具进行创造学习的设计以及教师指导性活动的设计等方面，都值得我们去研究。

3.2网络教学的评价研究才刚刚起步
随着Internet应用的普及，网络教学已成为一种重要的教学手段和教学场所。

然而，与传统教学相比，网络教学的质量保证体系却显得不够完善、健全。

如何保证网络教学的质量，建立一个行之有效的网络教学评价模型，已成为网络教学研究的一个重要课题。

时至2000年，教育部批准全国31所高校建立网络教育学院，但却没有制定出如何保证网络教育质量的相关政策。

美国国家教育政策研究所（The Institute For Higher Education Policy）于2000年4月也发表了一份名为"在线教育质量：远程互联网教育成功应用的标准"的报告[3]，然而，这些文章（报告）也仅仅是描述性的定义网络教学的评价指标，而对如何组织评价、如何获取定量数据、评价数据如何促进教学等方面则很少涉及。

目前，网络教学的支撑平台中的学习评价模块往往只含有测试部分，而缺乏相应的分析与反馈。

（空一行）
4 研究的主要内容及设计成果的应用价值
4.1网络教学设计理论体系的研究
包括教学目标的设计、建构性学习环境的设计、学习情境的设计、学习资源的设计、学生自主学习活动的设计、学生协作学习活动的设计、教师指导性活动的设计、学习评价工具的设计等。

4.2基于网络环境下的教学策略与教学模式的研究
网络教学策略的研究，如网络环境下的教学内容组织策略、网络环境下的教学情景营造策略、网络环境下的教学对话组织策略、网络环境下的课堂管理策略等网络教学模式的研究，如项目化学习模式、探索性学习模式、研究性学习模式等网络教学评价的内容体系、方法、步骤与模型的研究
网络教学设计系统软件的开发与应用
网络教学评价系统软件的开发与应用
4.3应用价值
通过课题的研究与实践，总结并形成基于网络环境下学科教学设计的理论与方法，优化中小学课堂教学结构。

通过课题的研究与实践，探索并总结信息化时代如何改革传统的思想和模式，使学生学会利用网络资源进行学习的方法和经验。

20 3
通过课题的研究与实践，探索普通中小学利用网络资源的途径与方法，形成一批优秀的网络教学课例。

通过课题的研究与实践，开发出具有应用推广价值的网络教学的设计工具和评价系统软件。

（空一行）
5工作的主要阶段、进度
（1）2010年秋季学期第11周前
接受毕业设计任务书，学习毕业设计（论文）要求及有关规定。

（2）2010年秋季学期第12~21周
阅读指定的参考资料及文献（包括10万个印刷符号外文资料），基本完成开题报告、外文翻译等任务。

（3）2011年春季学期第1周
进一步修订完善开题报告、外文翻译，使其在内容及格式上符合毕业设计（论文）规范要求。

（4）2011年春季学期第2周
……
.
.
.
（14）2011年春季学期第15周
毕业答辩。

（空一行）
6最终目标及完成时间
完成……，达到……目标。

完成时间：第14周
（空一行）
7现有条件及必须采取的措施
现有……软件，……设备，可以完成……研究与设计。

在设计中必须采取……措施。

（空一行）
8协助单位及要解决的主要问题
本课题的完成应解决……技术问题，同时，需要得到……单位的大力支持和帮助。

20 4
参考文献（黑体3号加粗居中）
（空一行）
［1］刘国钧，陈绍业，王凤翥. 图书馆目录［M］. 北京：高等教育出版社，1957.15-18. ［2］金显贺，王昌长，王忠东，等. 一种用于在线检测局部放电的数字滤波技术［J］. 清华大学学报(自然科学版)，1993，33(4)：62-67.
［3］姜锡洲. 一种温热外敷药制备方案［P］. 中国专利：881056073，1989-07-26.
［4］王明亮. 关于中国学术期刊标准化数据库系统工程的进展［EB/OL］. http://www.
/pub/wml.txt/980810-2.html, 1998-08-16/1998-10-04.
……………
………………（宋体5号）
［15］（必须多于15条）。