《单片机红外汽车测速—-毕业论文设计.doc》由会员分享，可在线阅读，更多相关《单片机红外汽车测速—-毕业论文设计.doc（21页珍藏版）》请在taowenge.com淘文阁网|工程机械CAD图纸|机械工程制图|CAD装配图下载|SolidWorks_CaTia_CAD_UG_PROE_设计图分享下载上搜索。
1、xx大学xx学院毕业设计（论文）相关资料题目： 单片机红外汽车测速 机电 系 电子信息工程 专业学 号： 学生姓名： 指导教师： （职称：讲师 ） （职称： ） XXXX年X月XX日目 录一、毕业设计（论文）开题报告二、毕业设计（论文）外文资料翻译及原文三、学生“毕业论文（论文）计划、进度、检查及落实表”四、实习鉴定表xx大学xx学院毕业设计（论文）开题报告题目： 单片机红外测速设计 机电 系 电子信息工程 专业学 号： 学生姓名： 指导教师： （职称：讲师 ） （职称： ） XXXX年X月XX日课题来源红外线传感器应用相当广，在许多地方你都可以看到它的身影，如红外门禁系统，红外报警系统、红外
2、测距系统，红外遥控系统等等。自从单片机问世以来，在国外，他已广泛应用于自动控制、数据采集和处理、家用电器等各方面，同时也参透到其他各个科技领域。在国内，虽然起步比较晚，但由于单片机物美价廉、功能强、体积小、使用灵活方便，越来越得到发展，尤其在工业过程控制、自动化仪器等领域得到广泛应用。所以本次毕业设计我选择了单片机红外汽车测速这个课题。单片机红外汽车测速精度高，应用广。科学依据（包括课题的科学意义；国内外研究概况、水平和发展趋势；应用前景等）国内外现在都有生产销售类似的汽车测速仪，有些简单的产品就是单单只有测速的功能，比较复杂的产品除了测速功能外，还加入了GPS全球定位，平均速度，时钟，行车时
3、间，车轮转数。未来的发展趋势可能还加入mp3和短信收发功能，使得汽车测速仪更加的人性化，相信会受到更多人的青睐。研究内容 硬件电路的设计 用protel画出硬件原理 软件编程程序框图设计 软件编程实量现汽车速度测拟采取的研究方法、技术路线、实验方案及可行性分析系统硬件电路的详细设计根据系统要求对各部分电路进行细化。设计出具体电路，并根据各单元电路的功能需求选定具体的器件。主要包括各种芯片的选择，元器件的类型，与单片机的各引脚如何连接，各个芯片之间怎么连接等。系统软件的详细设计根据系统软件的结构划分，对各个功能模块进行详细设计，同时画出每个部分的程序框图，最后把单独的程序结合在一起。研究计划及预
4、期成果研究计划：2009年10月12日-2009年12月25日：按照任务书要求查阅论文相关参考资料，并填写毕业设计开题报告书。2010年1月11日-2010年3月5日：进行毕业实习，并填写毕业实习报告。2010年3月8日-2010年3月14日：按照要求修改毕业设计开题报告。2010年3月15日-2010年3月28日：学习并翻译一篇与毕业设计相关的英文材料。2010年3月29日-2010年4月11日：Protel程序设计。2010年4月12日-2010年4月18日：软件设计。2010年4月19日-2009年5月21日：毕业论文撰写和修改工作。预期成果：并熟练掌握Protel的基本操作。训练自己综
5、合运用所学知识的能力，培养自己独立分析和解决问题的能力，启发自己奋发向上的精神。特色或创新之处密度大、体积小、易安装、易操作是它的优点。这些是一般汽车电子产品所没有的，是此系统所具备的优势。已具备的条件和尚需解决的问题已具备的条件：已学过微机原理、单片机两门与本课题相关的课程。在电路图设计和汇编语言方面有较好基础。有过单片机课程设计的经验，并会使用Protel99制作电路图尚需解决的问题：分析电路用protel重新绘制电路原图指导教师意见 指导教师签名：年 月 日教研室（学科组、研究所）意见 教研室主任签名： 年 月 日系意见 主管领导签名： 年 月 日英文原文Agile SCM Patter
6、ns and Software Configuration ManagementAbstractPatterns and pattern languages are tools that you can use to help your team be more effective and more agile. Patterns can lead to robust, effective solutions because the solutions that patterns lead you to take the environment into account, and solve
7、problems in a way that makes the system work better. This article will show you how you can use existing patterns to improve your SCM process. It will also help you to understand where existing patterns and pattern languages have gaps. IntroductionSince this issue of CM Crossroads focuses on Softwar
8、e Configuration Management (SCM) Patterns and two of the contributors of the Agile SCM column are the authors of a book on an SCM Pattern language, it seemed appropriate to focus this months article more on SCM Patterns than on Agile SCM. The themes or agility and patterns are closely related; the a
9、ppropriate use of Patterns and Pattern Languages can help you to be more agile. This month we will provide a quick overview of what Patterns and SCM Patterns are with enough information to get you oriented. Well also provide a list of resources to find to learn more about patterns and pattern langua
10、ges. If you already know what SCM Patterns are about, this article wil provide you with some ideas about how to get your organization to adopt them. If you are new to SCM Patterns (or patterns of any sort), this article wil get you started. This column may start off a bit more theoretical than many
11、of our other columns; if that is not what you prefer, hang on for a bit. There wil be practical advice. When we wrote SCM Patterns we wanted to encourage people to understand what they were trying to accomplish first, and apply practices and tools later. Introducing Patterns and Adding ValueFor “Pat
12、terns” to be useful, you need to think of them as more than just a magic phrase, or silver bul et that everyone will understand and appreciate. By using patterns and pattern languages you can add value to your organization by improving the development process as a whole, rather than simply fixing im
13、mediate problems. Patterns also provide for a common vocabulary for SCM concepts, which wil facilitate communication in your organization. To use “patterns” in your organization, your audience need not be versed in what patterns are, or in the specific patterns that you wish to use for you to levera
14、ge their power. In some organizations the people in a team wil be aware of what patterns are, and they may be familiar with a certain class of patterns. This is not the case in most organizations. As with any attempt on process improvement how, much value you get from patterns depends on how you int
15、roduce the concepts as much as the values of the concepts alone. Often the various aspects of software development such as “coding,” “configuration management,” “testing” to name just a few are treated as separate steps which concern different people. This leads a sense of competition rather than co
16、operation. A pattern approach will help you and your team to understand how SCM practices fit within the development process, thus encouraging everyone to move towards a common goal: higher quality software delivered more effectively. To benefit from SCM patterns you need to introduce them into your
17、 organization in a way that wil have an impact. Walking into in a room and speaking of Patterns wil not get you very far unless the people in the group understand what patterns are and have some clue about the particular patterns that you are discussing. They may hear the word “pattern” and have som
18、e reaction to it (positive or negative) and leave without understanding the real goal: working more effectively, much like the dog in the favorite Gary Larsen Far Side which has a dog hearing “Ginger blah blah blah Ginger” rather than the complete message. This can be frustrating, especialy if you u
19、nderstand how to implement an effective SCM process, and if you have thought a bit about how patterns work with SCM. You are more likely trying to influence people who are so focused on their immediate tasks that may not have even heard of Patterns, much less, SCM Patterns. So if were going to talk
20、about how patterns help you to be more effective and more agile, we may want to consider thinking of how you can use patterns effectively without spending too much time on introducing the concept of patterns. After all, in the end people usually want a better software development process, not an edu
21、cation in patterns or other concepts. (Though through the education, they may be able to better understand how to fix their own process) If you understand the patterns they can provide a framework for helping to explain the value in ways that your audience can grasp. For example, many readers of CM
22、Crossroads know the value of Private Workspaces (for example) and how they fit into the development process, so I hope that the Private Workspace pattern in the book can provide an outline for you to argue why a team should use private workspaces (or anything similar) Patterns, be they from Software
23、 Configuration Management Patterns, or from other sources. Patterns are most effective in the hands of a champion who can interpret the patterns and translate the concepts into a mechanism that works for the existing culture. While there is benefit to adopting the pattern vocabulary, it is more impo
24、rtant to have your organization adopt the principles from the patterns. The “What” of Patterns and SCMPatterns differ from other forms of describing best practices in that patterns make the relationship between practices explicit. Patterns build upon each other, and when they form a coherent unit, t
25、hey form a Pattern Language, which is a guide to building something. Often you are faced with a problem for which a best practice sounds like a solution. You are then faced with questions like: How do I put this practice in place? What are the organizational and process prerequisites for this practi
26、ce to work? What are the implementation considerations specific to my organizations tools and SCM environment? A pattern contains the fol owing basic parts: A name,1 which describes what the pattern helps you build. The name also forms the basic for a common vocabulary. You can talk about a Task Bra
27、nch in an unambiguous way if you al agree that Task Branch is what the pattern Task Branch describes.2 Tools often have their own vocabulary and you may need to translate between the terminology that your organization and tool3 uses. A Context, which describes when it makes sense to build the thing
28、that the pattern describes. Rather than say “Build a task branch” we need to know if the environment is one where a Task Branch will be helpful and useful. In the SCM Pattern language, the Task Branch makes sense in the context of an Active Development Line. In a perfect world, we could express term
29、s of other patterns. In some cases no one has written the pattern and we settle for a prose description of your situation. A description of the problem, both a summary and a detailed description explaining the tradeoffs that you need to consider when solving this problem. A solution, that shows how
30、to use the patterns described to solve your problem, and how the pattern solves your problem. Typical y you wil see a short solution and as well as a longer description with implementation details. Keep in mind throughout this discussion that a prerequisite for a pattern is that it describes a prove
31、n good practice (within the context). The form does not make it a pattern. A pattern col ection or pattern language is a guide to helping you to build a certain kind of thing. Various pattern languages may share some elements, but a pattern language for an Agile SCM environment will be different tha
32、n one for a more control ed environment, and trying to steer an organization in an inappropriate direction will cause problems. The Pattern Language in the book Software Configuration Management Patterns is about building a software CM environment where your want to respond rapidly (agilely) to chan
33、ge. Fortunately, this is a common requirement at the heart of many processes, and the SCM Pattern language addresses how to separate the parts of your codebase that need to change rapidly, from those that need to be stable. Who Can Introduce PatternsProcess Improvement is often thought of as being t
34、he stuff of “initiatives” and “working groups” but most organizations should be trying to improve in smal ways every day. Understanding what patterns should be in an environment is part of that process. When I started out as a software developer I worked with a team of people who taught me that how
35、we do things and why we do things as developers is as important as what we do. In other words: process isnt only the concern of senior developers. Everyone should care about finding ways to work better. Of course, the more influence you have over the team, the more you should care, since youll have
36、a bigger impact on the bottom line, but there are things that everyone can do to make their own work better and perhaps lead by influence.4Perhaps only a few should thing globally. Everyone should act locally. For example, any developer should be able to add tests for their code, independent of the
37、teams global policy. Goals and Intentions of the SCM Pattern LanguagePerhaps the common definition of “SCM Patterns” is the patterns in the book Software Configuration Management Patterns, along with, perhaps, the patterns in Streamed Lines.5 A pattern language guides you along the process of buildi
38、ng a thing, the SCM Pattern language in Software Configuration Management Patterns is not a guide to building every SCM process. The patterns in Software Configuration Management Patterns work best in an agile environment. I could argue that most teams should be more agile than they are now, and cou
39、ld be so without sacrificing anything. Many restrictive (or non-agile) processes seem to have their origins in lack of trust, or an unreasonable fear of risk, rather than reasonable business goals. You are the one who best understands what your team is doing now and how it needs to improve. The Role
40、 of ToolsThe first question I get about SCM is often “What tool should I use?” Like all things, tools influence the way that you work. If you have a tool that makes something easy you may do something one way. Without that tool another approach may be almost as good. My advice, which is not often we
41、ll received, is to understand what your work process is, what you want it to be, what your constraints are, and then pick a tool that supports them. Then you can think about whether you should use different tools. The pattern language in Software Configuration Management Patterns does not care about
42、 tools beyond having some sort of version control system and some sort of build process tool. Of course, some tools make implementing some patterns more transparent than other tools do. Applying the SCM Pattern Language for Process ImprovementA frequent complaint is that teams spend too much time st
43、abilizing their codeline before releases, resulting in developers idling while the team integrate (and thus delays that cascade into subsequent releases). One approach to resolving this situation is creating a release branch and dividing the teams effort into stabilization and new release activity.
44、This does not always work as expected if the release branch takes a long time to reach “release quality.” Time spent waiting for the release to be ready is replaced by time spent on merging release line fixes into the main line. The SCM Pattern Language provides a map to making resolving some of the
45、se issues.6A patterns approach would analyze how the problems relate and provide solutions that build upon each other. If your team has frequent releases you would attempt to focus most of your work on a single Active Development Line, which would have a Codeline Policy that al ows for frequent chec
46、k-ins, but only after they run a suite of Smoke Tests and Unit Tests in their Private Workspaces. Developers wil also be expected to do Private System Builds to provide added assurance that their check-in wil not break the build. Later on an Integration Build will build everything, and perform exten
47、sive Regression Tests. By the time you are ready to start a Release Line, the code should be fairly stable, and you should not need to perform complicated merges between codelines. While having a Release Line (applying a single pattern) relieved some pain, applying the Release Line pattern in context gave you a greater benefit. The Missing PatternsThe SCM Pattern Lang