齿轮油泵的生产管理系统设计
齿轮油泵的生产管理系统设计,齿轮,油泵,生产管理,系统,设计
编号无锡太湖学院毕业设计(论文)相关资料题目: 机械零件的管理系统设计 齿轮油泵的生产管理系统设计 信机 系 机械工程及自动化专业学 号: 0923026学生姓名: 侍 洁 指导教师: 王士同(职称:教 授) (职称: )2013年5月25日目 录一、毕业设计(论文)开题报告二、毕业设计(论文)外文资料翻译及原文三、学生“毕业论文(论文)计划、进度、检查及落实表”四、实习鉴定表无锡太湖学院毕业设计(论文)开题报告题目: 机械零件的管理系统设计 齿轮油泵的生产管理系统设计 信机 系 机械工程及其自动化 专业学 号: 0923026 学生姓名: 侍 洁 指导教师: 王士同(职称:教授 ) (职称: ) 2012年11月14日课题来源车间零件的管理对每个企业单位都是十分重要的,课题以齿轮油泵生产车间为应用背景,通过研究当前车间零件的管理现状、存在问题以及现实需求,设计一个针对零件管理工作的管理信息系统。该系统能够提供较为完备的功能,对于提高工作效率、加快车间零件管理的自动化具有较为重要的意义。科学依据(包括课题的科学意义;国内外研究概况、水平和发展趋势;应用前景等)(1)课题科学意义在现如今计算机飞速发展的时代,信息技术日新月异的发展,这给车间零件的管理业带来了巨大的影响。为了加快车间零件管理自动化的步伐,提高车间零件的管理业务处理效率,建立零件管理系统,尽可能地减少零件管理的重复性和低效性,已变得十分必要。随着科学技术的不断提高,计算机科学日渐成熟,其强大的功能已为人们深刻认识, 人们对生活质量及工作环境的要求也越来越高,它已进入人类社会的各个领域并发挥着越来越重要的作用。作为计算机应用的一部分,使用计算机对信息进行管理,具有与手工管理所无法比拟的优点.例如:检索迅速、查找方便、可靠性高、存储量大、保密性好、寿命长、成本低等。这些优点能够极大地提高零件管理的效率,也是企业的科学化、正规化管理,与世界接轨的重要条件。众所周知,车间零件管理是很繁琐的,生产链上车间各种零件种类很多,组装、加工车间里的零件进进出出给给车渐渐地管理人员的统计带来了很大的不便。计算机应用技术的发展,计算机硬件性能的不断改进,为零件管理系统的开发提供了技术支持和经济可行性。管理系统的应用,可以将工作者从烦杂的劳动中解脱出来,极大提高工作效率,有着较好的营运可行性。 研究内容 调查研究、查阅文献和搜集资料; 阅读和翻译与研究内容有关的外文资料; 撰写开题报告或文献综述,确定设计方案或研究方案; 掌握visual studio等可视化编程工具; 详细设计方法(包括控制流程图、功能模块、数据流图、程序框图、开发关键技术等)或研究方法 ; 设计或有关计算的源程序(或论点的证明或验证); 撰写毕业设计(论文);拟采取的研究方法、技术路线、实验方案及可行性分析(1) 实验方案本课题的是根据一个车间的零件实际情况开发工作的,开发一个试用与此车间零件的信息管理系统。基于B/S结构的网络版零件信息管理系统已经时零件管理模式的主流。本系统采用动态网页编程的最新技术JSP技术开发基于B/S结构的零件信息管理系统,在功能上力求满足该车间日常管理的需求,通过各种功能模块的设计完成了企业利用Internet实现对零件信息进行管理的要求。通过建立基于B/S结构的零件信息管理系统,实现管理人员对零件信息管理的高效率和低成本,提高车间生产的工作效率,达到人、财、物尽其用,开源节流的目的。(2) 研究方法本课题的主要工作通过采用基于c语言的JSP技术构造动态网页,充分发挥c语言所独有的易用性、跨平台性和安全性,运行效率高、安全可靠、使用性广的员工信息管理系统。研究计划及预期成果研究计划:2012年11月14日-201年12月23日:按照任务书要求查阅论文相关参考资料,填写毕业设计开题报告书。2013年1月11日-2013年3月5日:填写毕业实习报告。2013年3月6日-2013年3月12日:按照要求修改毕业设计开题报告。2013年3月13日-2013年3月20日:学习并翻译一篇与毕业设计相关的英文材料。2013年3月21日-2013年4月10日:visual studio程序设计。2013年4月11日-2013年4月24日:数据库设计。2013年4月25日-2013年5月21日:毕业论文撰写和修改工作。预期成果:利用所开发的系统对车间零件的信息实施控制与管理特色或创新之处 可简单的操作机械企业信息的管理(增、删、改、查询)。 对企业信息的管理实现了网络化、信息化、图形化和自动化。已具备的条件和尚需解决的问题 解决在信息管理各个环结互不相通所造成的各种问题。 系统还需要完善界面的美观,一些功能的完善,还需要算法的优化。指导教师意见 指导教师签名:年 月 日教研室(学科组、研究所)意见 教研室主任签名: 年 月 日系意见 主管领导签名: 年 月 日英文原文Introducing C# C#-pronounced “See Sharp”-is a programming language designed for Microsofts .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, Microsofts 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, its not enough to focus purely on the details and mechanisms, although well 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, well look at what problems C# was built to solve. Then well explore the style of the language, through aspects that distinguish it from other languages. And well 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 its 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 LibraryWorking in C# means more than using just the language-the classes offered by the .NET Framework are an extremely important part of the C# developers everyday experience (and they account for a lot of this books 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” exampleclass Programstatic void Main()System.Console.WriteLine(Hello, world);Well 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 extentfor 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 StyleC# 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 languagenumerous 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, youll 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. Its a functional programming language, heavily influenced by a language called ML. Back in 1991, when your authors were first-year students, our universitys 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 CodeThe .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 youre done with them is a coding error in C+, but its the normal way to free them in .NET. This service is provided by the CLR-the .NET Frameworks 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, its 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. Its certainly different from how C and C+ work-with those languages, the compilers output can be executed directly by the computer, and although those languages have some runtime services, its 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-its 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 youre a Java developer, all of this will sound rather familiarjust 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 EcosystemSoftware 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. Microsofts Silverlight can run C# and VB.NET code on Mac OS X as well as Windows. Theres 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 doesnt 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 DesignNeeds analysis to investigate and analyze the users 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 designSelected 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 designOn 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 designThe 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 processRequirements analysis phase: the application requirements of individual usersConceptual 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
收藏