齿轮油泵的生产管理系统设计[含CAD图纸和说明书等资料]
收藏
资源目录
压缩包内文档预览：(预览前20页/共55页)
编号：21897384
类型：共享资源
大小：2.10MB
格式：ZIP
上传时间：2019-09-09
上传人：好资料QQ****51605
认证信息
个人认证
孙**（实名认证）
江苏
IP属地：江苏
50
积分
- 关 键 词：
-
含CAD图纸和说明书等资料
齿轮
油泵
生产管理
系统
设计
cad
图纸
以及
说明书
仿单
资料
- 资源描述：
-
【温馨提示】 dwg后缀的文件为CAD图，可编辑，无水印，高清图，压缩包内含CAD图的预览图片，仅用于预览，压缩包内文档可直接点开预览，需要原稿请自助充值下载，请见压缩包内的文件及预览，所见才能所得，请细心查看有疑问可以咨询QQ：414951605或1304139763
- 内容简介：
-
binDebugCHEXC.exebinDebugCHEXC.pdbobjDebugResolveAssemblyReference.cacheobjDebugCHEXC.frmDataBack.resourcesobjDebugCHEXC.frmDataReole.resourcesobjDebugCHEXC.frmMain.resourcesobjDebugCHEXC.frmCompanyInfo.resourcesobjDebugCHEXC.frmEmpInfo.resourcesobjDebugCHEXC.frmFindGood.resourcesobjDebugCHEXC.frmGonYingShang.resourcesobjDebugCHEXC.frmGoodID.resourcesobjDebugCHEXC.frmJhGoodsInfo.resourcesobjDebugCHEXC.frmKcGoodFind.resourcesobjDebugCHEXC.frmKcGoods.resourcesobjDebugCHEXC.frmLogin.resourcesobjDebugCHEXC.frmSellGoodInfo.resourcesobjDebugCHEXC.frmSellGoods.resourcesobjDebugCHEXC.frmThGoodsInfo.resourcesobjDebugCHEXC.Properties.Resources.resourcesobjDebugCHEXC.csproj.GenerateResource.CacheobjDebugCHEXC.exeobjDebugCHEXC.pdbbinDebugCHEXC.exe.configE:downcodeCHEXCCHEXCobjDebugCHEXC.exeE:downcodeCHEXCCHEXCobjDebugCHEXC.pdbE:downcodeCHEXCCHEXCbinDebugCHEXC.exeE:downcodeCHEXCCHEXCbinDebugCHEXC.pdbE:downcodeCHEXCCHEXCobjDebugResolveAssemblyReference.cacheE:downcodeCHEXCCHEXCobjDebugCHEXC.frmDataBack.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmDataReole.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmMain.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmCompanyInfo.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmEmpInfo.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmFindGood.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmGonYingShang.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmGoodID.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmJhGoodsInfo.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmKcGoodFind.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmKcGoods.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmLogin.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmSellGoodInfo.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmSellGoods.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.frmThGoodsInfo.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.Properties.Resources.resourcesE:downcodeCHEXCCHEXCobjDebugCHEXC.csproj.GenerateResource.CacheE:WinformCode超市进销存CHEXCobjDebugCHEXC.exeE:WinformCode超市进销存CHEXCobjDebugCHEXC.pdbE:WinformCode超市进销存objDebugCHEXC.exeE:WinformCode超市进销存objDebugCHEXC.pdbE:WinformCode超市进销存binDebugCHEXC.exeE:WinformCode超市进销存binDebugCHEXC.pdbE:WinformCode超市进销存objDebugResolveAssemblyReference.cacheE:WinformCode超市进销存objDebugCHEXC.frmDataBack.resourcesE:WinformCode超市进销存objDebugCHEXC.frmDataReole.resourcesE:WinformCode超市进销存objDebugCHEXC.frmMain.resourcesE:WinformCode超市进销存objDebugCHEXC.frmCompanyInfo.resourcesE:WinformCode超市进销存objDebugCHEXC.frmEmpInfo.resourcesE:WinformCode超市进销存objDebugCHEXC.frmFindGood.resourcesE:WinformCode超市进销存objDebugCHEXC.frmGonYingShang.resourcesE:WinformCode超市进销存objDebugCHEXC.frmGoodID.resourcesE:WinformCode超市进销存objDebugCHEXC.frmJhGoodsInfo.resourcesE:WinformCode超市进销存objDebugCHEXC.frmKcGoodFind.resourcesE:WinformCode超市进销存objDebugCHEXC.frmKcGoods.resourcesE:WinformCode超市进销存objDebugCHEXC.frmLogin.resourcesE:WinformCode超市进销存objDebugCHEXC.frmSellGoodInfo.resourcesE:WinformCode超市进销存objDebugCHEXC.frmSellGoods.resourcesE:WinformCode超市进销存objDebugCHEXC.frmThGoodsInfo.resourcesE:WinformCode超市进销存objDebugCHEXC.Properties.Resources.resourcesE:WinformCode超市进销存objDebugCHEXC.csproj.GenerateResource.CacheC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）binDebugCHEXC.exe.configC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.exeC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.pdbC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）binDebugCHEXC.exeC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）binDebugCHEXC.pdbC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugResolveAssemblyReference.cacheC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmDataBack.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmDataReole.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmMain.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmCompanyInfo.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmEmpInfo.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmFindGood.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmGonYingShang.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmGoodID.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmJhGoodsInfo.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmKcGoodFind.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmKcGoods.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmLogin.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmSellGoodInfo.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmSellGoods.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.frmThGoodsInfo.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.Properties.Resources.resourcesC:Documents and SettingsAdministrator桌面侍洁论文shijie（sys）objDebugCHEXC.csproj.GenerateResource.Cache编号无锡太湖学院毕业设计（论文）相关资料题目： 机械零件的管理系统设计 齿轮油泵的生产管理系统设计 信机 系 机械工程及自动化专业学 号： 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 outer mode of the dataPhysical design phase: physical storage arrangement according to the DBMS characteristics and processing requirements, indexing, and database mode is formed.Systems AnalysisSystems Analysis (Systems Analysis) The term was first used in the 1930s, was based on management problems as the main application object, a major in management information systems and critical stage, a key figure in this stage is responsible for systems analysts, The key question is to complete this stage of the task communication between developers and users. In the 1940s, due to the success of its application, has been further developed. Decades later, is the study of large-scale systems, or to create a complex system, widely used system analysis method.TaskSystematic analysis of the main task is to get detailed investigation of the system documentation focused, analysis of the organization within the overall management status and information processing. It focuses on the analysis of the whole process from the business point of view. The main contents of the analysis are: business and data flow is smooth, is reasonable; relationship between data, business processes and implementation of management functions; reform of the old system management mode and the management of the new system implementation of the method is feasible. Systems aim of the analysis is to determine the needs of users and their solutions down results include: the need to determine the understanding of the development of the existing organization and management; demand of the users of the information systems function; data and business processes; management capabilities and management data index system; system and the proposed changes and new management model. The content is determined by analysis of the system implemented on the basis of system design, system in the future.中文译文介绍C#C#,读作“see sharp”是专门为.NET平台设计的编程语言。从2002年首次发布以来，C#创建了许多角色。它广泛的应用于网站服务器端以及windows桌面应用程序的客户端和服务器上。你可以用C#编写智能手机的用户界面和Xbox 360游戏。最近，微软的Sliverlight平台使得可以用C#编写可以在网页浏览器上运行的Internet应用程序。但是什么样的语言是C#？为了很好的了解一种语言并且有效的应用，仅仅专注于细节和机制是不够的，虽然在这本书中我们也将花费大量的时间来了解这些东西，但是同样重要的是了解这些细节之后的东西。因此，在本章中，我们将要了解C#建立一个什么样的问题解决机制。因此，我们将探讨这种语言的风格，并且通过各个方面来区别C#与其他语言。并且我们将在了解C#的最新演变第四个版本。 编程语言的存在，可以让开发人员的开发工作更加的有效率。许多成功的编程语言都简化或者自动化了以前要靠繁琐的步骤才能完成的任务。有些提供新技术，使得老问题可以比以前更加有效或者在更大的规模上得到解决。当然，C#可以给你带来多大的差异取决于你的编程背景，所以这值得考虑，语言设计人员在开发C#的时候考虑了哪些种类的人。C#是针对windows平台上的开发的，并且其语法跟使用C、C+或者其他编程语言的编程人员的编程传统相似，如JavaScript和Java绘制。基本语言元素如语句、表达式、函数声明和流量控制，尽量与C家族语言接近。当然，一个熟悉的语法这个理由并不足够来选择一个语法，所以C#提供了一个生产增强特性，这个特性在它之前的语言中并没有。垃圾回收机制把开发人员从常见的内存管理问题的暴政中解救出来，如内存泄漏和循环引用。编译代码可验证类型安全机制规则了广泛的错误和潜在的安全漏洞。但是C或C+的windows开发人员可能不习惯这些功能，他们觉得这是Java淘汰下来的旧帽子，但是无论在对象模型，XML或者数据库中，Java都没有任何东西能够媲美C#为搜集信息工作所提供的“LINQ”功能。即使用其他语言编写，从外部原件集成代码也是非常痛苦的。C#中还采用了功能编程的支持，这是以前学术语言中的一个非常强大的功能。C#开发人员中使用的大多数有用的功能，许多都来自于.NET框架，它为C#提供运行环境、C#库以及所有其他.NET语言，就像VB.NET。C#是为.NET设计的，他们之间关系如此密切的一个主要好处是与框架功能的合作，就像类库一样感觉很自然。.NET Framwork 类库在C#中工作是指比语言用到的更多.NET Framwork提供的类是开发人员日常经验（他们占了这本书很大一部分内容）的一个极其重要的组成部分。大多数的库的功能分为一下三类：编写实用的功能、.NET包装windows功能和框架。第一组包括的实用工具如字典、列表和其他集合类，以及字符串处理工具如正规表达引擎。也有一些处理稍大规模的功能，例如对象模型，代表XML文档。一些类的功能的特点是围绕底层的OS的包装，例如有用于访问文件系统的类，并使用网络功能如接口。也有书面向控制台输出的类，我们可以用在任何书上都可以看到的第一个例子说明，如示例1-1所示。示例1-1。“Hello，world”示例class Programstatic void Main()System.Console.WriteLine(Hello, world);我们将在适当的时候检查所有组件，但现在，即使是这个最简单的例子也需要调用库中的类（这个例子中的System.Console类）来做这个工作。最后，类库提供整个框架以支持建设的某些种类应用。例如Windows Presentation Foundation (WPF)是建立windows桌面软件的框架；ASP.NET(这不是一个缩写，尽管出现)是一种用于构建WEB应用程序的框架。并不是所有框架都是关于用户界面的，例如Windows Communication Foundation (WCF)是专为在网络上访问其他计算机系统建立服务而设计的。这三类划分并不严格，不少类适合一分为二。例如，类库提供访问文件系统的部分不只是薄的包装围绕现有的Win32 API。他们添加新的面向对象的抽象，提供超出了基本的文件I / O服务的重要功能，所以这些类型的融入第一类和第二类。同样，框架通常需要整合与相关服务为例，虽然在一定程度上的Windows窗体UI框架有其自身独特的API，很多的基本功能是所提供的Win32组件。因此，这里的三个类别是不严格。他们只是提供了一个什么东西，你可以在类库中找到各种有用的想法。语言风格C#并不是唯一一个在.NET Framwork上运行的语言。事实上，支持多种语言一直是.NET Framwork的一个主要特点，这体现在它运行环境引擎的名字上CLR或者叫通用语言运行环境。顾名思义，.NET Framwork不只是支持一种编程语言，而是支持多种语言服务的.NET框架类库。你为什么会选择除了C#的其他语言呢？我们已经提到了一个重要的原因：C是专门为.NET设计的。如果您在C#工作中正在使用以.NET技术为基础的工具，如WPF或ASP.NET，那你就会说话他们的语言。与C+相比，它支持原始语言的.NET的扩展。扩展是经过深思熟虑的并且工作的很好，但是所调用.NET库的代码与C+并不相同。但是从正常使用，所以建立的贯通C#与标准化的C+之间的桥梁从来没有贯通过。同时这个犹如一把双刃剑，也面临着困境。比如说你能用标准的C+集合一个或者多个.NET类库中的类么？在本地.NET语言中，这些问题并不会出现。但C在这方面并不是独树一帜的。Visual Studio 2010为.NET设计了三种语言：NET的C，VB.NET和F。（虽然VB.NET从其如下非.NETVisual Basic的前辈，这是在一些重要方面截然不同。它是原生的。NET语言像VB的语法，而不是VB 6中。NET功能螺栓）。这些语言之间的选择归结到什么风格的需要的语言。虽然F的感觉明显等，VB.NET和C有很多相似之处。最在选择之间的这些明显的因素是，VB.NET有人更容易学习熟悉Visual Basic语法，而C将是一个熟悉的人更容易C类语言。然而，有微妙的区别在于：在语言哲学超越语法。托管代码.NET Framework提供更多的不仅仅是一个类库。它还以一种微妙的方式不直接访问调用类库而提供服务。例如，早期我们提到，C可以自动内存管理的某些方面，一个臭名昭著的C + +代码中的错误源。一旦你放弃堆分配对象他们是在C + +的，但它是正常的方式释放他们。NET编码错误。这CLR的。NET Framework的运行时环境提供服务。虽然C编译器紧密合作，使这成为可能的运行，提供您的代码如何使用对象和数据的必要的信息，这是最终运行垃圾收集工作。托管编译器不产生原始的可执行代码。相反，它们产生中间形式的代码称为白细胞介素，中间语言运行时决定。究竟如何转换成可执行的东西。一个实际结果的管理代码是一个已编译的C程序可以运行32位和64位系统不修改，甚至可以运行在不同的处理器架构，它往往可能VB.NET支持XML文本代码上运行一个基于ARM的手持设备的运行在基于Intel的未修改个人电脑，或在Xbox360游戏机的PowerPC架构。如CPU的独立有趣的可能是在实践中，最有用的方面的管理代码和IL。NET运行时，可以提供有用的服务，这都很难传统的编译系统要贯彻落实好。换句话说，这一点是使开发人员的生产力。只是前面提到的内存管理其中一个例子。其他包括安全模型，考虑到代码的起源而不是仅仅发生运行代码的用户的身份;灵活装载了强大的支持服务和版本的共享组件的机制;如何在实践中使用的代码正在运行时代码优化的基础上而不是编译器猜测它可能被使用;已经提到，符合CLR的能力，以验证该代码输入安全规则，在执行前，裁决了整体的安全和稳定的错误类。如果你是一个Java开发人员，这一切听起来相当熟悉，刚刚替补字节码IL和故事非常相似。事实上，一个受欢迎的，但有些无知的“笑话”欠周到的Java社区成员之间形容为一个贫穷的C仿爪哇。当第一个版本的C出现，差异有微妙的，但事实上，Java的去复制几个特点，从C说明的C总是比只克隆。语言变得更加明显不同每个新版本，但一个区别，目前，从一开始就显得尤为重要Windows开发C一直很容易得到的功能底层的Windows平台。连续性和windows生态系统没有成功的软件开发平台纯粹是对自己的优点上下文事项。例如，第三方组件和工具的广泛可用性平台明显更具吸引力。Windows是也许最引人注目的这种现象的例子。任何试图获得认可的新的编程系统有相当大的优势，如果它可以插入一些现有的生态系统，C和Java之间最大的区别之一是，C和。NET框架积极拥抱Windows平台上，而Java超出其隔离方式从底层的操作系统的开发。如果你正在编写一个特定的操作系统上运行的代码，它不是特别有用语言独特的工具和组件的削减你到您选择平台。而不是要求开发商与过去决裂NET提供的连续性它可能是内置的组件和服务直接或Windows内置。大多数时候，你不会需要使用这个类库提供了很多底层平台的功能的包装。然而，如果你需要使用一个第三方组件或功能的操作系统目前还没有。NET包装，工作能力等非托管功能直接从托管代码是无价的。虽然.NET中提供的功能一体化的基础平台，仍然有支持非Windows系统。微软的Silverlight可以运行的Mac OS X以及Windows的C和VB.NET代码。还有一个开源项目称为单使。NET代码在Linux上运行，以及相关的Moonlight项目是一个开源版本的Silverlight。因此，本地平台整合功能如果你不停止从多个有用的C平台要针对多个操作系统，你
- 温馨提示:
1: 本站所有资源如无特殊说明，都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
2: 本站的文档不包含任何第三方提供的附件图纸等，如果需要附件，请联系上传者。文件的所有权益归上传用户所有。
3.本站RAR压缩包中若带图纸，网页内容里面会有图纸预览，若没有图纸预览就没有图纸。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 人人文库网仅提供信息存储空间，仅对用户上传内容的表现方式做保护处理，对用户上传分享的文档内容本身不做任何修改或编辑，并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容，请与我们联系，我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。
人人文库网所有资源均是用户自行上传分享，仅供网友学习交流，未经上传用户书面授权，请勿作他用。
川公网安备: 51019002004831号