下载文档原格式
《广东工业大学本科生优秀毕业设计（论文）选编》格式样本一、文章应包含如下内容：1、标题2、作者、指导老师3、学院，邮编4、作者出生年月，性别，专业、学位类别5、中文摘要6、中文关键词7、评阅人评语（评语人，职称）8、正文（约3000字）9、参考文献10、英文标题11、作者英文姓名(王启乐英文姓名格式为Qile Wang)12、英文摘要13、英文关键词二、版面要求作者提交论文电子版时，要将全文按如下格式编辑，图片大小适当。
全文（含图片）控制在四个版面内。
超过篇幅的自行缩减。
1* 指导教师：谷 整、可行、实用、先进的方案。
（评阅人：万频副教授）1 扩展性、性价比以及开发商（用户）对投资费用的承受能力。
……2 2.1基于HFC 的智能化住宅小区信息传输网络如图1所示，……2.1.1对家庭用户，用户PC 通过10/100BASE-T 自适应以太网接口直接连接CM ，实现上行10Mbps ，下行36Mbps 1 张振昭,许锦标,万频主编.楼宇智能化技术. Abstract: The article mostly introduced液体式驱动超微进给装置的研究叶庆坚*指导教师：傅惠南（广东工业大学机电工程学院，广州，510090）摘要：微驱动和操作是微观操作控制不可或缺的手段，平稳、精确、微小、可靠、方便、操作容易的驱动方法是人们探索追求的目标，具有高的难度。
课题探索采用液体式驱动控制方式，采用两级微驱动机构以达到微小、稳定、可靠微位移操作、控制的目的。
关键词：原子力显微镜（AFM）实时可控微量进给评阅人评语：本论文创新性提出液体微驱动式进给装置，通过实验证明弹簧-浮室容器-液室容器进给装置能有效实现刀具的快速精密进给，设计了光路系统对在进给过程中装置稳定性的动态检测，思路新颖，课题探索采用的两级微驱动机构是一可行、实用、操作容易的方案。
（评阅人：马平教授）1微进给技术的背景及课题研究的内容微进给技术广泛应用于微型机械、微电子、生物、航天航空等领域，引起国内外极大关注。
![[VIP专享]广东工业大学毕业设计(论文)相关表格下载](https://uimg.taocdn.com/483f28bf0722192e4536f6c4.webp)
成都东软学院外文资料和译文格式要求一、译文必须采用计算机输入、打印，幅面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.封面：学校统一印制2.扉页：格式同封面3.摘要：包括中文摘要，关键词;英文摘要，关键词(中英文摘要各占一页)4.目录：5.论文正文6.7.附录(可根据论文所需决定是否增加附录)(二)具体要求：毕业论文(设计)打印一律采用单面打印，纸张为A4复印纸。
页边距要求：上边距2.54厘米，下边距2.54厘米，左边距4.17厘米，右边距3.17厘米。
按封面左侧装订线装订。
目录要求如下，“目录”两字为三号黑体字居中，两字之间空四格。
空一行后打印各级标题及对应页码。
一级标题用黑体四号字，二级标题用小四号宋体字，均为一倍行距。
目录内容最好在一页。
(如需要可在目录体现三级标题)(一)论文(设计)题目论文(设计)题目应简短、明确，把毕业论文的内容、专业特点概括出来。
题目主标题字数一般不宜超过20个字，可以设副标题。
主标题用宋体三号字加粗;副标题用宋体小三号字，均在文本居中位置。
(二)摘要及关键词(中文在前，英文在后)另起一页打印英文摘要和关键词，英文摘要的内容应与中文摘要相符，一般以200个英文单词左右为宜。
空一行后打印英文标题，再空一行居中位置打印四号加黑“ABSTRACT”字样，另起一行小四号打英文摘要。
使用的英文应该准确、通顺。
“Key Words”加黑并加冒号，左对齐，多个关键词之间用分号分隔。
英文全部采用Times New Roman字体。
(三)正文毕业论文正文中各级标题顺序为：一、(一)、1、(1)、①。
毕业设计可采用下列标题顺序：1、1.1、1.1.1、①。
一级标题即“一”用四号黑体打印，每一部分结束后另起一页开始下一部分。
正文内小标题力求简短、明确，题末不用标点符号。
二级标题(一)用黑体小四号字。
三级标题1后用点“.”，宋体小四号字加黑。
四级标题(1)，字体字号同正文，为宋体小四号字，行距为1.5倍。
文中如有插图和照片，应比例适当，清楚美观;插图应标明图序和图题，序号和图题之间空一格;图序以阿拉伯数字连续编号，图题一般居中位于图的下方。
广东工业大学研究生手册广东工业大学研究生学位文撰写规范研究生学位论文是研究生科学研究工作的全面总结，是描述其研究成果，代表其研究水平的重要学术文献资料，是申请和授予相应学位的基本依据。
学位论文撰写是研究生培养过程的重要环节和基本训练之一，必须按照确定的规范认真执行。
指导教师应加强指导，严格把关。
论文撰写应符合国家及各专业部门制定的有关标准，符合汉语语法规范。
硕士（含：专业学位）和博士学位论文，除在字数、理论研究的深度及创造性成果等方面的要求不同外，对其撰写规范的要求基本一致。
本撰写规范主要参照GB7713-87科学技术报告、学位论文和学术论文的编写格式及CAJ-CD中国学术期刊（光盘版）检索与评价数据规范。
第一部分论文撰写一、基本要求1.硕士学位论文应能表明作者确已在本门学科上掌握了坚实的基础理论和系统的专门知识，并对所研究课题有新的见解，有从事科学研究工作或独立担负专门技术工作的能力。
2.博士学位论文应能表明作者确已在本门学科上掌握了坚实宽广的基础理论和系统深入的专门知识，并具有独立从事科学研究工作的能力，在科学或专门技术上做出了创造性的成果。
3.学位论文一般应用中文撰写，硕士学位论文正文应不少于2万字，博士学位论文正文要求5至8万字。
学位论文应立论正确、推理严谨、文字简练、层次分明、说理透彻，数据真实可靠。
4.论文作者应在选题前后阅读有关文献，并进行必要的分析综合。
硕士学位申请人的文献阅读量不少于30篇，其中外文文献不少于10篇；博士学位申请人的文献阅读量不少于60篇，其中外文文献不少于40篇。
分析综合是对所读文献加以分析概括，了解选题的状态。
5.在论文中引用了文献内容的，必须将其列入参考文献表，并在正文中引用内容处注明参考文献编号（按出现先后顺序编）。
6.量和单位及其符号均应符合国家标准的规定，国家标准中未规定的，应执行国际标准或行业标准；不同的量必须用不同的符号表示，不得一符号多义，含义相同的量则必须用同一符号表示。
广东工业大学高等教育自学考试毕业论文（设计）撰写规范一、毕业论文（设计）完成后应提交的资料（一）毕业论文或毕业设计说明书，包括：1．封面2．中（英）文摘要或设计总说明3．目录4．正文5．致谢6．参考文献7．附录（二）影印件（三）工程图纸、软盘等二、毕业论文（设计）印刷与装订（一）印刷⑴毕业论文（设计）须用计算机打印，一律采用A4打印纸，单面印刷，胶装印制8本。
⑵面纸张要求：皮纹，蓝色。
⑶书脊印刷要求：书脊须用宋体印刷：论文题名、作者姓名、“广东工业大学高等教育自学考试本科毕业论文（设计）”字样，字体大小应根据论文厚度选用适当字号。
（二）电子文档除按规定印刷论文外，还需提交与印刷论文相同格式的电子版毕业论文（设计）（采用Word2003格式，以适应“论文相似性检测系统”软件使用）。
（三）装订毕业论文（设计）使用统一的封面，资料装订顺序为：毕业论文（设计）、译文及原文影印件、工程图纸（按规定要求折叠装订）、软盘等。
三、毕业论文（设计）撰写的内容与要求一份完整的毕业设计（论文）应包括以下几个方面：（一）封面按广东工业大学高等教育自学考试毕业论文（设计）规定的格式打印。
（二）标题标题应简短、明确，主标题不宜超过20字；可以设副标题。
（三）论文摘要或设计总说明论文摘要应能概括研究课题的内容和主要观点，中文摘要在400字左右，并翻译英文。
设计总说明介绍设计任务来源、设计标准、设计原则及主要技术资料，中文字数以1000－1500字为宜。
（四）目录目录按三级标题编写（即：1……、1.1……、1.1.1……），要求标题层次清晰。
目录中的标题应与正文中的标题一致。
（五）正文毕业论文（设计）正文包括绪论、正文主体与结论。
其内容分别如下：绪论应说明本课题的目的、意义、研究范围及要达到的技术要求；简述本课题在国内外的发展概况及存在的问题；说明本课题的指导思想；阐述本课题应解决的主要问题。
正文主体是对研究工作的详细表述，其内容包括：问题的提出，研究工作的基本前提、假设和条件；模型的建立，实验方案的拟定；基本概念和理论基础；设计计算的主要方法和内容；实验方法、内容及其分析；理论论证，理论在课题中的应用，课题得出的结果，以及对结果的讨论等。
