齒輪油泵的生產管理系統(tǒng)設計

齒輪油泵的生產管理系統(tǒng)設計,齒輪,油泵,生產管理,系統(tǒng),設計 編號 無錫太湖學院 畢業(yè)設計（論文） 相關資料 題目： 機械零件的管理系統(tǒng)設計 齒輪油泵的生產管理系統(tǒng)設計 信機 系 機械工程及自動化專業(yè) 學 號： 　　　 0923026　　　　 學生姓名： 侍 潔 指導教師： 王士同（職稱：教 授） （職稱： ） 2013年5月25日 目 錄 一、畢業(yè)設計（論文）開題報告 二、畢業(yè)設計（論文）外文資料翻譯及原文 三、學生“畢業(yè)論文（論文）計劃、進度、檢查及落實表” 四、實習鑒定表 無錫太湖學院 畢業(yè)設計（論文） 開題報告 題目： 機械零件的管理系統(tǒng)設計 齒輪油泵的生產管理系統(tǒng)設計 信機 系 機械工程及其自動化 專業(yè) 學 號： 　　0923026 　　　 學生姓名： 侍 潔 指導教師： 　 王士同（職稱：教　授 ） （職稱： ） 2012年11月14日 課題來源 車間零件的管理對每個企業(yè)單位都是十分重要的，課題以齒輪油泵生產車間為應用背景，通過研究當前車間零件的管理現狀、存在問題以及現實需求，設計一個針對零件管理工作的管理信息系統(tǒng)。該系統(tǒng)能夠提供較為完備的功能，對于提高工作效率、加快車間零件管理的自動化具有較為重要的意義。 科學依據（包括課題的科學意義；國內外研究概況、水平和發(fā)展趨勢；應用前景等） （1）課題科學意義 在現如今計算機飛速發(fā)展的時代，信息技術日新月異的發(fā)展，這給車間零件的管理業(yè)帶來了巨大的影響。為了加快車間零件管理自動化的步伐，提高車間零件的管理業(yè)務處理效率，建立零件管理系統(tǒng)，盡可能地減少零件管理的重復性和低效性，已變得十分必要。 隨著科學技術的不斷提高，計算機科學日漸成熟，其強大的功能已為人們深刻認識， 人們對生活質量及工作環(huán)境的要求也越來越高，它已進入人類社會的各個領域并發(fā)揮著越來越重要的作用。作為計算機應用的一部分，使用計算機對信息進行管理，具有與手工管理所無法比擬的優(yōu)點.例如:檢索迅速、查找方便、可靠性高、存儲量大、保密性好、壽命長、成本低等。這些優(yōu)點能夠極大地提高零件管理的效率，也是企業(yè)的科學化、正規(guī)化管理，與世界接軌的重要條件。 眾所周知，車間零件管理是很繁瑣的，生產鏈上車間各種零件種類很多，組裝、加工車間里的零件進進出出給給車漸漸地管理人員的統(tǒng)計帶來了很大的不便。計算機應用技術的發(fā)展，計算機硬件性能的不斷改進，為零件管理系統(tǒng)的開發(fā)提供了技術支持和經濟可行性。管理系統(tǒng)的應用，可以將工作者從煩雜的勞動中解脫出來，極大提高工作效率，有著較好的營運可行性。 研究內容 ① 調查研究、查閱文獻和搜集資料； ② 閱讀和翻譯與研究內容有關的外文資料； ③ 撰寫開題報告或文獻綜述，確定設計方案或研究方案； ④ 掌握visual studio等可視化編程工具； ⑤ 詳細設計方法（包括控制流程圖、功能模塊、數據流圖、程序框圖、開發(fā)關鍵技術等）或研究方法 ； ⑥ 設計或有關計算的源程序（或論點的證明或驗證）； ⑦ 撰寫畢業(yè)設計（論文）； 擬采取的研究方法、技術路線、實驗方案及可行性分析 （1） 實驗方案 本課題的是根據一個車間的零件實際情況開發(fā)工作的，開發(fā)一個試用與此車間零件的信息管理系統(tǒng)。基于B/S結構的網絡版零件信息管理系統(tǒng)已經時零件管理模式的主流。本系統(tǒng)采用動態(tài)網頁編程的最新技術——JSP技術開發(fā)基于B/S結構的零件信息管理系統(tǒng)，在功能上力求滿足該車間日常管理的需求，通過各種功能模塊的設計完成了企業(yè)利用Internet實現對零件信息進行管理的要求。通過建立基于B/S結構的零件信息管理系統(tǒng)，實現管理人員對零件信息管理的高效率和低成本，提高車間生產的工作效率，達到人、財、物盡其用，開源節(jié)流的目的。 （2） 研究方法 本課題的主要工作通過采用基于c語言的JSP技術構造動態(tài)網頁，充分發(fā)揮c語言所獨有的易用性、跨平臺性和安全性，運行效率高、安全可靠、使用性廣的員工信息管理系統(tǒng)。 研究計劃及預期成果 研究計劃： 2012年11月14日-201年12月23日：按照任務書要求查閱論文相關參考資料，填寫畢業(yè)設計開題報告書。 2013年1月11日-2013年3月5日：填寫畢業(yè)實習報告。 2013年3月6日-2013年3月12日：按照要求修改畢業(yè)設計開題報告。 2013年3月13日-2013年3月20日：學習并翻譯一篇與畢業(yè)設計相關的英文材料。 2013年3月21日-2013年4月10日：visual studio程序設計。 2013年4月11日-2013年4月24日：數據庫設計。 2013年4月25日-2013年5月21日：畢業(yè)論文撰寫和修改工作。 預期成果： 利用所開發(fā)的系統(tǒng)對車間零件的信息實施控制與管理 特色或創(chuàng)新之處 ① 可簡單的操作機械企業(yè)信息的管理（增、刪、改、查詢）。 ② 對企業(yè)信息的管理實現了網絡化、信息化、圖形化和自動化。 已具備的條件和尚需解決的問題 ① 解決在信息管理各個環(huán)結互不相通所造成的各種問題。 ② 系統(tǒng)還需要完善界面的美觀，一些功能的完善，還需要算法的優(yōu)化。 指導教師意見 指導教師簽名： 年 月 日 教研室（學科組、研究所）意見 教研室主任簽名： 年 月 日 系意見 主管領導簽名： 年 月 日 英文原文 Introducing C# C#-pronounced “See Sharp”-is a programming language designed for Microsoft’s .NET platform. Since its first release in 2002, C# has found many roles. It is widely used on the server side of websites, and also on both the client and server in line-of-business Windows desktop applications. You can write smartphone user interfaces and Xbox 360 games in C#. More recently, Microsoft’s Silverlight platform has made C# an option for writing Rich Internet Applications that run in a web browser. But what kind of language is C#? To understand a language well enough to use it effectively, it’s not enough to focus purely on the details and mechanisms, although we’ll be spending plenty of time on those in this book. It is equally important to understand the thinking behind the details. So in this chapter, we’ll look at what problems C# was built to solve. Then we’ll explore the style of the language, through aspects that distinguish it from other languages. And we’ll finish the chapter with a look at the latest step in the evolution of C#, its fourth version. Why C#? Why .NET? Programming languages exist to help developers be more productive. Many successful languages simplify or automate tedious tasks that previously had to be done by hand. Some offer new techniques that allow old problems to be tackled more effectively, or on a larger scale than before. How much difference C# can make to you will depend on your programming background, of course, so it’s worth considering what sorts of people the language designers had in mind when they created C#. C# is aimed at developers working on the Windows platform, and its syntax is instantly familiar to users of C or C++, or other languages that draw from the same tradition, such as JavaScript and Java. Fundamental language elements such as statements, expressions, function declarations, and flow control are modeled as closely as possible on their equivalents in C family languages. A familiar syntax is not enough of a reason to pick a language, of course, so C# offers productivity-enhancing features not found in some of its predecessors. Garbage collection frees developers from the tyranny of common memory management problems such as memory leaks and circular references. Verifiable type safety of compiled code rules out a wide range of bugs and potential security flaws. While C or C++ Windows developers may not be accustomed to those features, they will seem old hat to Java veterans, but Java has nothing to compete with the “LINQ” features C# offers for working with collections of information, whether in object models, XML documents, or databases. Integrating code from external components is remarkably painless, even those written in other languages. C# also incorporates support for functional programming, a powerful feature previously most commonly seen in academic languages. Many of the most useful features available to C# developers come from the .NET Framework, which provides the runtime environment and libraries for C#, and all other .NET languages, such as VB.NET. C# was designed for .NET, and one of the main benefits of its close relationship with the .NET Framework is that working with framework features such as the class library feels very natural. The .NET Framework Class Library Working in C# means more than using just the language-the classes offered by the .NET Framework are an extremely important part of the C# developer’s everyday experience (and they account for a lot of this book’s content). Most of the library functionality falls into one of three categories: utility features written in .NET, wrappers around Windows functionality, and frameworks. The first group comprises utility types such as dictionaries, lists, and other collection classes, as well as string manipulation facilities such as a regular expression engine. There are also features that operate on a slightly larger scale, such as the object models for representing XML documents. Some library features are wrappers around underlying OS functionality. For example, there are classes for accessing the filesystem, and for using network features such as sockets. And there are classes for writing output to the console, which we can illustrate with the obligatory first example of any programming language book, shown in Example 1-1. Example 1-1. The inevitable “Hello, world” example class Program { static void Main(){ System.Console.WriteLine("Hello, world");} } We’ll examine all the pieces shown here in due course, but for now, note that even this simplest of examples depends on a class from the library-the System.Console class in this case-to do its job. Finally, the class library offers whole frameworks to support building certain kinds of applications. For example, Windows Presentation Foundation (WPF) is a framework for building Windows desktop software; ASP.NET (which is not an acronym, despite appearances) is a framework for building web applications. Not all frameworks are about user interfaces-Windows Communication Foundation (WCF) is designed for building services accessed over the network by other computer systems, for instance. These three categories are not strict, as quite a few classes fit into two. For example, the parts of the class library that provide access to the filesystem are not just thin wrappers around existing Win32 APIs. They add new object-oriented abstractions, providing significant functionality beyond the basic file I/O services, so these types fit into both the first and second categories. Likewise, frameworks usually need to integrate with underlying services to some extent—for example, although the Windows Forms UI framework has a distinctive API of its own, a lot of the underlying functionality is provided by Win32 components. So the three categories here are not strict. They just offer a useful idea of what sorts of things you can find in the class libraries. Language Style C# is not the only language that runs on the .NET Framework. Indeed, support for multiple languages has always been a key feature of .NET, reflected in the name of its runtime engine, the CLR or Common Language Runtime. As this name implies, .NET is not just for one language—numerous languages have access to the services of the .NET Framework class library. Why might you choose C# over the others? We already mentioned one important reason: C# was designed specifically for .NET. If you are working with .NET technologies such as WPF or ASP.NET, you’ll be speaking their language if you work in C#. Compare this with C++, which supports .NET through extensions to the original language. The extensions are carefully thought out and work well, but code that uses .NET libraries just looks different from normal C++, so programs that bridge the worlds of .NET and standard C++ never feel completely coherent. And the dual personality often presents dilemmas-should you use standard C++ collection classes or the ones in the .NET class library, for example? In native .NET languages such as C#, such questions do not emerge. F# is the odd one out here. It’s a functional programming language, heavily influenced by a language called ML. Back in 1991, when your authors were first-year students, our university’s computer science course chose ML for the first programming language lectures in part because it was so academic that none of the students would previously have come across anything like it. F# is still at the academic end of the spectrum despite having climbed far enough down the ivory tower to be a standard part of a mainstream development environment. It excels at complicated calculations and algorithms, and has some characteristics that can help with parallel execution. However, as with many functional languages, the cost of making some hard problems easier is that a lot of things that are easy in more traditional languages are remarkably hard in F#- functional languages are adept at complex problems, but can be clumsy with simple ones. It seems likely that F# will mostly be used in scientific or financial applications where the complexity of the computation to be performed dwarfs the complexity of the code that needs to act on the results of those calculations. Managed Code The .NET Framework provides more than just a class library. It also provides services in subtler ways that are not accessed explicitly through library calls. For example, earlier we mentioned that C# can automate some aspects of memory management, a notorious source of bugs in C++ code. Abandoning heap-allocated objects once you’re done with them is a coding error in C++, but it’s the normal way to free them in .NET. This service is provided by the CLR-the .NET Framework’s runtime environment. Although the C# compiler works closely with the runtime to make this possible, providing the necessary information about how your code uses objects and data, it’s ultimately the runtime that does the work of garbage collection. Depending on what sorts of languages you may have worked with before, the idea that the language depends heavily on the runtime might seem either completely natural or somewhat disconcerting. It’s certainly different from how C and C++ work-with those languages, the compiler’s output can be executed directly by the computer, and although those languages have some runtime services, it’s possible to write code that can run without them. But C# code cannot even execute without the help of the runtime. Code that depends entirely on the runtime is called managed code. Managed compilers do not produce raw executable code. Instead, they produce an intermediate form of code called IL, the Intermediate Language. The runtime decides exactly how to convert it into something executable. One practical upshot of managed code is that a compiled C# program can run on both 32-bit and 64-bit systems without modification, and can even run on different processor architectures-it’s often possible for code that runs on an ARM-based handheld device to run unmodified on Intel-based PCs, or on the PowerPC architecture found in the Xbox 360 game console. If you’re a Java developer, all of this will sound rather familiar—just substitute bytecode for IL and the story is very similar. Indeed, a popular but somewhat ignorant “joke” among the less thoughtful members of the Java community is to describe C# as a poor imitation of Java. When the first version of C# appeared, the differences were subtle, but the fact that Java went on to copy several features from C# illustrates that C# was always more than a mere clone. The languages have grown more obviously different with each new version, but one difference, present from the start, is particularly important for Windows developers: C# has always made it easy to get at the features of the underlying Windows platform. Continuity and the Windows Ecosystem Software development platforms do not succeed purely on their own merits-context matters. For example, widespread availability of third-party components and tools can make a platform significantly more compelling. Windows is perhaps the most striking example of this phenomenon. Any new programming system attempting to gain acceptance has a considerable advantage if it can plug into some existing ecosystem, and one of the biggest differences between C# and Java is that C# and the .NET Framework positively embrace the Windows platform, while Java goes out of its way to insulate developers from the underlying OS. While .NET offers features to ease integration with the underlying platform, there is still support for non-Windows systems. Microsoft’s Silverlight can run C# and VB.NET code on Mac OS X as well as Windows. There’s an open source project called Mono which enables .NET code to run on Linux, and the related Moonlight project is an open source version of Silverlight. So the presence of local platform integration features doesn’t stop C# from being useful on multiple platforms-if you want to target multiple operating systems, you would just choose not to use any platform-specific features. So the biggest philosophical difference between C# and Java is that C# provides equal support for direct use of operating-system-specific features and for platform independence. Java makes the former disproportionately harder than the latter. The latest version of C# contains features that enhance this capability further. Several of the new C# 4.0 features make it easier to interact with Office and other Windows applications that use COM automation-this was a weak spot in C# 3.0. The relative ease with which developers can reach outside the boundaries of managed code makes C# an attractive choice-it offers all the benefits of managed execution, but retains the ability to work with any code in the Windows environment, managed or not. Database Design Needs analysis to investigate and analyze the user's business activities and the use of data and clarify the data type, scope, quantity, and exchange their business activities, and determine the requirements of the users of the database system and a variety of constraints, formation user needs Statute. The conceptual design of the user asked to describe the real world (which may be a factory, a shopping mall or a school, etc.), at which various classification, aggregation and generalization, an abstract conceptual data model. This conceptual model should reflect the various departments of the real world information structure, the flow of information, information of mutual restraint relations and various departments of information storage, query and processing requirements. That the model should avoid specific implementation details of the database on the computer, represented an abstract form. Expansion entity - contact model (ER model), for example, the first step is explicitly contained in the real world entities and their attributes, the links between the entities and information constraints, which gives each partial description of the information department referred to as a partial view of the user (in the database). Fragmentary view of a plurality of users previously obtained in the second step and then integrated into a global view of the real world, i.e. the user to be described the conceptual data model. The logical design work is a conceptual data model of the real-world design into a logical database model that is adapted to a particular database management system supported by the logical data model. At the same time, may be needed for a variety of data processing applications to produce the corresponding logical sub-mode. The result of this step designed the so-called "logical database. Physical design Selected the most suitable for the specific application tasks according to the specific database management system provides a variety of storage structures and access methods depends on the physical design measures for a specific computer architecture, the physical storage structure (including the file type, the index structure and data storage order bit logic), access method and access path. The result of this step the design is called "physical database. Verify the design On the basis of the design, data collection and the establishment of a specific database, run some typical application tasks to verify the correctness and rationality of the database design. In general, a large database design process often need to go through multiple cycles repeated. When a step of the design problem is found, you may need to return to the front to be modified. Therefore, the database design should consider the possibility and convenience to modify the design in the future. Operation and maintenance of design The database system was put into operation process, must constantly adjust and modify it. So far, database design, a lot of work still needs to do manually, in addition to a relational database has a set of more complete data the paradigm theory can be used to partially guide the database design, lack of a comprehensive database design theory, methods and tools, database design, automated or semi-automated design interactive. Database design future research direction is to study the theory of database design, seeking to more effectively express the semantic relationship data model to provide automatic or semi-automatic design tools and integrated development environment, the design of the various stages of the database design engineering, more standardized and more convenient and easy, so fully embodies the advanced ideas and methods of software engineering in the design of the database. Forming process Requirements analysis phase: the application requirements of individual users Conceptual design phase: the formation of machine-independent features, independent of the various DBMS products conceptual model (ER diagram) Logic design stage: First convert the ER diagram specific database products support data model, such as the relational model, a database logical pattern; based on user requirements, safety considerations, on the basis of the basic table and then create the necessary View (View), the formation of the