带你一起游微博系统毕业设计(本科论文).doc

大连交通大学信息工程学院
毕业设计(论文)任务书

题 目 带你一起游微博系统

任务及要求：　
1.设计（研究）内容和要求
任务：
1、调查数码相册管理系统及jsp技术的发展近况，完成调研报告字数不少于3000第三周交给指导教师；
2、结合自己实际情况，安排进度，填写进度计划表，第二周完成，交给指导教师签字，并严格执行；
3、按照软件工程的思想，独立完成系统的设计和程序的开发，完成代码估计2000行左右。
4、实现功能模块：
l 用户管理模块：主要完成用户注册、登录、信息更新、分类查询等
l 足迹管理模块：主要完成旅游记忆添加、更新、删除、分类查询等
l 好友社区管理：完成好友的添加、更新、分类查询等
l 用户评价管理：评价的发布、更新、删除等.
5、完成数据库设计。
6、程序简洁，算法可行，运行情况良好。
要求：
1、每周要和指导老师至少见面两次，汇报课题进展情况，接受老师的询问。
2、接到任务书后找到与题目相关的外文资料进行翻译，要求不少于10000外文字
符或译出3000汉字，于第四周交给指导教师审阅。
3、 毕业设计第13周完成设计论文的装订，交由指导教师评阅。论文要求10000
字以上，包括综述、系统总体设计、系统实现、性能分析、结论等。
4、 毕业设计第12周左右经教研室组织进行软件验收，验收时要提供软件使用说
明书。
5、于第13周提出毕业答辩申请，签字。
6、第14周答辩，要求制作PPT。

2.原始依据
通过大学几年的学习，已经学习了诸如软件工程、数据库原理及应用、数据结构、C++、Visual Basic、JAVA等多门程序设计语言和网络等基础知识和专业知识，学生有能力而且可以独立完成小中型项目的设计与开发。学校现有设备和环境可以提供给学生实习和上机，而且具有专业老师可以指导学生。
3.参考文献
[1] 杨丰盛.Android应用开发揭秘[M].北京：机械工业出版社.2010
[2] 李刚.疯狂Android讲义[M].北京：电子工业出版社.2011
[3] 吴亚峰，苏亚光.Android应用案例开发大全[M].北京：人民邮电出版社.2011
[4] 田俊静,张波等.Android基础教程[M].北京：人民邮电出版社.2010
[5] 杨越.精通Android[M].北京:人民邮电出版社.2011
[6] 盖索林.Android开发入门指南[M].北京: 人民邮电出版社.2011
[7] 斩岩，姚尚郎.移动开发权平台解决方案[M].北京:海洋出版社.2011
[8] 张利国等.Android移动开发入门与进阶[M].北京: 人民邮电出版社.2009
[9] 寒超，Android开发原理及开发要点详解[M].北京：电子工业出版社.2010
[10] 孙更新.Android从入门到精通[M].北京：电子工业出版社.2011
[11] 王向辉，张国印.Android应用程序开发[M].北京.清华大学出版社.2010
[12] 汪永辉.Android平台开发之旅[M].北京：机械工业出版社.2011
[13] James Goodwill. Pure Java Server Pages[M].Indianapolis Ind: Sams.2000
[14] Andy Rubin.Android-sdk Developers[M].Application Resources.2007

　 指导教师签字：
教研室主任签字：
　　　　　　　　　　　　　　　　　　　　　　 年 月 日
大连交通大学信息工程学院
毕业设计(论文)进度计划与考核表
学生姓名
刘昌健
专业班级
软件工程
08-3班
指导教师
阎树昕
刘瑞杰
本课题其他人员
无
题　目
带你一起游微博系统
日　期
计划完成内容
完成情况
指导老师检查签字
第1周
接受设计任务书，确定毕业设计题目收集资料考虑毕业设计的总体进度。

第2周
收集资料，完成详细进度计划表的填写工作、进行毕业设计项目相关的调研。了解毕业设计的业务流程。

第3周
查阅课题相关资料以及参考文献并提交调研报告，查找相关的外文文献，确定外文文献的题目。

第4周
进一步查阅课题相关的外文资料以及参考文献并完成外文文献翻译工作 ，学习项目开发用到的技术。

第5周
对毕业设计进行概要设计，首先进行功能模块的划分。

第6周
进一步完善概要设计即数据库的设计数据库当中表的组织结构，画出E-R图，考虑所用到的开发工具。

第7周
对毕业设计进行概要设计，包括实现每个模块的数据结构以及每个模块的主要算法，画出流程图。

第8周
进一步完善详细设计即，完成数据库的后台设计及实现。

第9周
基于详细设计开始毕业设计的编码工作，实现部分模块的功能。

第10周
进一步对代码进行调试，完成所有功能模块的编码实现，进行整体测试，开始撰写论文。

第11周
对系统进行最后的完善，迎接软件验收，继续撰写论文。

第12周
进行软件验收，完成论文初稿。

第13周
对论文进行修改，定稿，排版，打印并装订，准备答辩。

第14周
制作答辩PPT，参加毕业设计答辩。

指导教师签字：　　　　　　　　　　　 　 　年　 　月　 　日

注：“计划完成内容”由学生本人认真填写，其它由指导教师考核时填写。

大连交通大学信息工程学院
毕业设计(论文)外文翻译

学生姓名 刘昌健 专业班级 软件工程08-3班
指导教师 阎树昕 刘瑞杰 职 称 高工 讲师
所在单位 　信息科学系软件工程教研室
教研室主任 　 刘瑞杰

完成日期 2012 年 4 月 13 日

Application Resources

Android applications are written in the Java programming language. The Android SDK tools compile the code—along with any data and resource files—into an Android package, an archive file with an.apk suffix. All the code in a single .apk file is considered to be one application and is the file that Android-powered devices use to install the application.
Once installed on a device, each Android application lives in its own security sandbox: The Android operating system is a multi-user Linux system in which each application is a different user
By default, every application runs in its own Linux process. Android starts the process when any of the application's components need to be executed, then shuts down the process when it's no longer needed or when the system must recover memory for other applications.
In this way, the Android system implements the principle of least privilege. That is, each application, by default, has access only to the components that it requires to do its work and no more. This creates a very secure environment in which an application cannot access parts of the system for which it is not given permission.However, there are ways for an application to share data with other applications and for an application to access system services:It's possible to arrange for two applications to share the same Linux user ID, in which case they are able to access each other's files. To conserve system resources, applications with the same user ID can also arrange to run in the same Linux process and share the same VM (the applications must also be signed with the same certificate).
An application can request permission to access device data such as the user's contacts, SMS messages, the mountable storage (SD card), camera, Bluetooth, and more. All application permissions must be granted by the user at install time.That covers the basics regarding how an Android application exists within the system. The rest of this document introduces you to:The core framework components that define your application. The manifest file in which you declare components and required device features
for your application. Resources that are separate from the application code and allow your application to gracefully optimize its behavior for a variety of device configurations
Application Components
Application components are the essential building blocks of an Android application. Each component is a different point through which the system can enter your application. Not all components are actual entry points for the user and some depend on each other, but each one exists as its own entity and plays a specific role—each one is a unique building block that helps define your application's overall behavior.
There are four different types of application components. Each type serves a distinct purpose and has a distinct lifecycle that defines how the component is created and destroyed. Activities
An activity represents a single screen with a user interface. For example, an email application might have one activity that shows a list of new emails, another activity to compose an email, and another activity for reading emails. Although the activities work together to form a cohesive user experience in the email application, each one is independent of the others. As such, a different application can start any one of these activities (if the email application allows it). For example, a camera application can start the activity in the email application that composes new mail, in order for the user to share a picture. An activity is implemented as a subclass of ACTIVITY and you can learn more about it in the Activities developer guide.
Services
A service is a component that runs in the background to perform long-running operations or to perform work for remote processes. A service does not provide a user interface. For example, a service might play music in the background while the user is in a different application, or it might fetch data over the network without blocking user interaction with an activity. Another component, such as an activity, can start the service and let it run or bind to it in order to interact with it.
A service is implemented as a subclass of Service and you can learn more about it in the Service developer guide.
Content providers
A content provider manages a shared set of application data. You can store the data in the file system, an SQLite database, on the web, or any other persistent storage location your application can access. Through the content provider, other applications can query or even modify the data (if the content provider allows it). For example, the Android system provides a content provider that manages the user's contact information. As such, any application with the proper permissions can query part of the content provider (such as ContactsContact.data) to read and write information about a particular person.
Content providers are also useful for reading and writing data that is private to your application and not shared. For example, theNote Pad sample application uses a content provider to save notes.
A content provider is implemented as a subclass of ContenProvider and must implement a standard set of APIs that enable other applications to perform transactions. For more information, see the ContenProvider developer guide.
Broadcast receivers
A broadcast receiver is a component that responds to system-wide broadcast announcements. Many broadcasts originate from the system—for example, a broadcast announcing that the screen has turned off, the battery is low, or a picture was captured. Applications can also initiate broadcasts—for example, to let other applications know that some data has been downloaded to the device and is available for them to use. Although broadcast receivers don't display a user interface, they may create a status bar notification to alert the user when a broadcast event occurs. More commonly, though, a broadcast receiver is just a "gateway" to other components and is intended to do a very minimal amount of work. For instance, it might initiate a service to perform some work based on the event.
A broadcast receiver is implemented as a subclass of BroadcastReceiver and each broadcast is delivered as an Intent object. For more information, see the BroadcastReceiver class.
A unique aspect of the Android system design is that any application can start another application’s component. For example, if you want the user to capture a photo with the device camera, there's probably another application that does that and your application can use it, instead of developing an activity to capture a photo yourself. You don't need to incorporate or even link to the code from the camera application. Instead, you can simply start the activity in the camera application that captures a photo. When complete, the photo is even returned to your application so you can use it. To the user, it seems as if the camera is actually a part of your application.
When the system starts a component, it starts the process for that application (if it's not already running) and instantiates the classes needed for the component. For example, if your application starts the activity in the camera application that captures a photo, that activity runs in the process that belongs to the camera application, not in your application's process. Therefore, unlike applications on most other systems, Android applications don't have a single entry point (there's no main() function, for example).
Because the system runs each application in a separate process with file permissions that restrict access to other applications, your application cannot directly activate a component from another application. The Android system, however, can. So, to activate a component in another application, you must deliver a message to the system that specifies your intent to start a particular component. The system then activates the component for you.
The Manifest File
Before the Android system can start an application component, the system must know that the component exists by reading the application's AndroidManifest.xml file (the "manifest" file). Your application must declare all its components in this file, which must be at the root of the application project directory.The manifest does a number of things in addition to declaring the application's components, such as:
Identify any user permissions the application requires, such as Internet access or read-access to the user's contacts.
Declare the minimum APILevel required by the application, based on which APIs the application uses.
Declare hardware and software features used or required by the application, such as a camera, bluetooth services, or a multitouch screen.
API libraries the application needs to be linked against (other than the Android framework APIs), such as the Google Mapa library. Activities, services, and content providers that you include in your source but do not declare in the manifest are not visible to the system and, consequently, can never run. However, broadcast receivers can be either declared in the manifest or created dynamically in code (as BroadcastReceiver objects) and registered with the system by calling regusterReceuver().For more about how to structure the manifest file for your application, see the The AndroidManifest.xml.documentation.
Declaring application requirements
There are a variety of devices powered by Android and not all of them provide the same features and capabilities. In order to prevent your application from being installed on devices that lack features needed by your application, it's important that you clearly define a profile for the types of devices your application supports by declaring device and software requirements in your manifest file. Most of these declarations are informational only and the system does not read them, but external services such as Android Market do read them in order to provide filtering for users when they search for applications from their device.
However, you can also declare that your applicaiton uses the camera, but does not require it. In that case, your application must perform a check at runtime to determine if the device has a camera and disable any features that use the camera if one is not available.
Here are some of the important device characteristics that you should consider as you design and develop your application:
Screen size and density
In order to categorize devices by their screen type, Android defines two characteristics for each device: screen size (the physical dimensions of the screen) and screen density (the physical density of the pixels on the screen, or dpi—dots per inch). To simplify all the different types of screen configurations, the Android system generalizes them into select groups that make them easier to target.
The screen sizes are: small, normal, large, and extra large.
The screen densities are: low density, medium density, high density, and extra high density.
By default, your application is compatible with all screen sizes and densities, because the Android system makes the appropriate adjustments to your UI layout and image resources. However, you should create specialized layouts for certain screen sizes and provide specialized images for certain densities, using alternative layout resources, and by declaring in your manifest exactly which screen sizes your application supports with the element.
There are many hardware and software features that may or may not exist on a given Android-powered device, such as a camera, a light sensor, bluetooth, a certain version of OpenGL, or the fidelity of the touchscreen. You should never assume that a certain feature is available on all Android-powered devices (other than the availability of the standard Android library), so you should declare any features used by your application with the element.
Application Resources
An Android application is composed of more than just code—it requires resources that are separate from the source code