关 键 词：

含CAD图纸和说明书等资料 车间 零件 管理 系统 cad 图纸 以及 说明书 仿单 资料

资源描述：

【温馨提示】 dwg后缀的文件为CAD图，可编辑，无水印，高清图，压缩包内含CAD图的预览图片，仅用于预览，压缩包内文档可直接点开预览，需要原稿请自助充值下载，请见压缩包内的文件及预览，所见才能所得，请细心查看有疑问可以咨询QQ：414951605或1304139763

内容简介：

编号无锡太湖学院毕业设计（论文）相关资料题目： 磁环车间车间的零件管理系统 信机 系 机械工程及自动化专业学 号： 0923002学生姓名： 常秋阳 指导教师： 王士同 （职称：教授 ） （职称： ）2012年5月25日目 录一、毕业设计（论文）开题报告二、毕业设计（论文）外文资料翻译及原文三、学生“毕业论文（论文）计划、进度、检查及落实表”四、实习鉴定表无锡太湖学院毕业设计（论文）开题报告题目： 磁环生产车间的零件管理 信机 系 机械工程及自动化 专业学 号： 0923002 学生姓名： 常秋阳 指导教师： 王士同 （职称：教授 ） （职称： ）2012年11月25日 课题来源自拟题目科学依据（包括课题的科学意义；国内外研究概况、水平和发展趋势；应用前景等）（1）课题科学意义在现如今计算机飞速发展的时代，信息技术日新月异的发展，这给车间零件的管理业带来了巨大的影响。为了加快车间零件管理自动化的步伐，提高车间零件的管理业务处理效率，建立零件管理系统，尽可能地减少零件管理的重复性和低效性，已变得十分必要。随着科学技术的不断提高，计算机科学日渐成熟，其强大的功能已为人们深刻认识， 人们对生活质量及工作环境的要求也越来越高，它已进入人类社会的各个领域并发挥着越来越重要的作用。作为计算机应用的一部分，使用计算机对信息进行管理，具有与手工管理所无法比拟的优点.例如:检索迅速、查找方便、可靠性高、存储量大、保密性好、寿命长、成本低等。这些优点能够极大地提高零件管理的效率，也是企业的科学化、正规化管理，与世界接轨的重要条件。众所周知，车间零件管理是很繁琐的，生产链上车间各种零件种类很多，组装、加工车间里的零件进进出出给给车渐渐地管理人员的统计带来了很大的不便。计算机应用技术的发展，计算机硬件性能的不断改进，为零件管理系统的开发提供了技术支持和经济可行性。管理系统的应用，可以将工作者从烦杂的劳动中解脱出来，极大提高工作效率，有着较好的营运可行性。 研究内容 调查研究、查阅文献和搜集资料； 阅读和翻译与研究内容有关的外文资料； 撰写开题报告或文献综述，确定设计方案或研究方案； 掌握visual studio等可视化编程工具； 详细设计方法（包括控制流程图、功能模块、数据流图、程序框图、开发关键技术等）或研究方法 ； 设计或有关计算的源程序（或论点的证明或验证）； 撰写毕业设计（论文）；拟采取的研究方法、技术路线、实验方案及可行性分析（1）实验方案本课题的是根据一个车间的零件实际情况开发工作的，开发一个试用与此车间零件的信息管理系统。基于B/S结构的网络版零件信息管理系统已经时零件管理模式的主流。本系统采用动态网页编程的最新技术JSP技术开发基于B/S结构的零件信息管理系统，在功能上力求满足该车间日常管理的需求，通过各种功能模块的设计完成了企业利用Internet实现对零件信息进行管理的要求。通过建立基于B/S结构的零件信息管理系统，实现管理人员对零件信息管理的高效率和低成本，提高车间生产的工作效率，达到人、财、物尽其用，开源节流的目的。（2）研究方法本课题的主要工作通过采用基于c语言的JSP技术构造动态网页，充分发挥C语言所独有的易用性、跨平台性和安全性，运行效率高、安全可靠、使用性广的零件信息管理系统。研究计划及预期成果研究计划：2012年11月12日-201年12月2日：按照任务书要求查阅论文相关参考资料， 填写毕业设计开题报告书。2012年12月3日-2013年3月4日：学习并翻译一篇与毕业设计相关的英文材料。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月19日：毕业论文撰写和修改工作。预期成果：利用所开发的系统对车间零件的信息实施控制与管理。特色或创新之处 可简单的操作机械企业信息的管理（增、删、改、查询）。 对企业信息的管理实现了网络化、信息化、图形化和自动化。已具备的条件和尚需解决的问题 解决在信息管理各个环结互不相通所造成的各种问题。 系统还需要完善界面的美观，一些功能的完善，还需要算法的优化。指导教师意见 指导教师签名：年 月 日教研室（学科组、研究所）意见 教研室主任签名： 年 月 日系意见 主管领导签名： 年 月 日中文译文数据库管理系统1.数据库管理系统数据库管理系统（DBMS）是一组计算机控制、建立、维护和使用数据的程序。它能够使数据库管理员（DBA）和其他专家组织控制数据库开发。一个DBMS是一种系统软件的软件包，帮助综合的收集使用数据记录和文件称为数据库。它允许不同用户的应用程序可以轻松地访问同一个数据库。DBMS可以使用各种各样的数据库模型，如网络模型或关系模型。在大型系统中，DBMS允许用户和其他软件以结构化的方式存储和检索数据。而不必编写计算机程序从中提取信息，用户可以在查询语言中提出简单的问题。因此，许多DBMS软件包提供了第四代编程语言（第四代语言）和其他应用程序开发功能。它有助于指定的数据库，在数据库中访问和使用信息的逻辑组织。它提供了用于控制数据存取的设施，实现数据完整性，并发管理，从备份中恢复数据。一个DBMS还提供了在逻辑上呈现给用户的数据库信息的能力。2.概观一个数据库管理系统是一套软件程序，控制、组织、存储、管理和检索数据库中的数据。DBMS是根据他们的数据结构或类型分类的。DBMS从应用程序接受请求的数据，并指示操作系统进行相应的数据传输。查询和响应必须提交和接收符合一个或多个适用的协议的格式。当一个DBMS使用，信息系统可以更容易地组织的信息需求的变化改变。新的分类的数据可以被添加到数据库中，而不会损坏现有的系统。数据库服务器是有实际的数据库和只运行的数据库管理系统和相关软件的计算机。数据库服务器通常是多处理器计算机上，丰富的内存和RAID磁盘阵列，用于稳定的存储。硬件数据库加速器，经由高速的信道连接到一个或多个服务器，也可用于在大体积的交易处理环境。数据库管理系统被发现在大多数数据库应用程序的心脏。可能会围绕一个自定义的多任务内核，内置网络支持的DBMS，但现代的DBMS通常依赖于一个标准的操作系统来提供这些功能。3.历史数据库从电子计算初期已经投入使用。与现代系统可以适用于广泛的数据库和需求不同，绝大多数旧系统是紧密相连的自定义数据库，以牺牲灵活性为代价获得速度的。最初数据库管理系统被发现仅在的计算机硬件支持大型数据集所需的大型组织中。3.1 20世纪60年代航海DBMS随着计算机的速度和能力的增长，出现了一些通用的数据库系统，由20世纪60年代中期，有一些这样的系统在商业用途。在一个标准的利息开始增长，而这样的产品，集成Data Store数据存储系统（IDS），作者查尔斯巴赫曼，成立了“资料库工作小组”在CODASYL，该集团负责创建和标准化，COBOL。在1971年，他们发表了他们的标准，通常被称为“Codasyl的办法”，很快就有一些商业产品的基础上提供。Codasyl的方法建立在“手册”的导航链接的数据集形成一个大的网络的基础上。第一次打开数据库时，该程序被移交链接到的第一条记录在数据库中，也包含其他的数据的指针。为了找到特定的记录，通过这些指针，程序员必须加强的时间，直到返回所需的记录。简单的查询，如“发现所有的人都在印度”要求的程序走整个数据集，收集的匹配结果。这样，基本上没有概念的“查找”或“搜索”。这可能听起来像今天一个严重的限制，但在这样一个时代数据时最经常被储存在磁带上，这样的运行总之是在太贵了。IBM也有自己的DBMS系统于1968年，被称为IMS。 IMS是一个发展的阿波罗登月计划上的System/360编写的软件。 IMS何Codasyl是大致相同概念的，但其使用严格的层次结构作为数据模型的导航，而不是CODASYL的网络模型。这两个概念后来被称为导航数据库数据的方式访问，巴赫曼1973年的图灵奖颁奖这个程序被作为导航。IMS被归类为一个分层数据库。IMS、IDMS、和CODASYL数据库以及CINCOMs的总数据库都被归类为网络数据库。3.2 20世纪70年代关系数据库管理系统在IBM加利福尼亚州圣何塞市的一个分支办事处工作的科德，他要从事硬盘系统的发展。他不满于Codasyl航海模型的的方法，尤其是缺乏一个变得越来越有用的“搜索”设施。 1970年，他写了一定数量的论文，提出了一个数据库建设新的方法，最终以开创性的关系模型建立大型共享数据银行的。1在本文中，他描述了一个新的存储和处理数据的大型数据库系统。而不是某种被存储在链表的自由形式的记录，在Codasyl的记录，Codd的想法是使用一个固定长度的记录“表”。一个链表存储时，将是非常低效的“稀疏”的数据库中的任何一个记录的数据可以为空。关系模型解决了这个数据分割成一系列规范化的表，可选的元素被移出主表的地方，他们将只在需要时占用空间。例如，一个常见的数据库系统是跟踪用户，他们的名字、登录信息，不同的地址和电话号码的信息。在导航的方法，所有这些数据将被放置在一个单独的记录，并且未使用的项目根本就没有存储在数据库中。在这种关系方法中，数据将被归到一个用户表，地址表和电话号码表（例如）。只有当实际提供的地址或电话号码的记录将建立在这些可选表。链接的信息是该系统的关键。在关系模型中，一些信息的作为“钥匙”使用，唯一定义一个特定的记录。当被收集信息与用户有关，可选的（或相关）表中存储的信息会被发现通过搜索此键。例如，如果一个用户的登录名是独一无二的，地址和电话号码，将被记录作为用户主要的登录名。这种“重新连接”的相关数据备份到一个单一的集合是传统的计算机语言没有设计到的。作为导航的方法，将需要进行循环收集记录，这种方法需要循环收集任何一个信息记录。 Codd的解决方案所需的循环是一个面向集合的语言，一个建议将催生以后无处不在的SQL。使用被称为元组演算的一个数学分支，他证明了这种系统可以支持正常的数据库（插入，更新等），以及提供一个简单的系统查找并返回数据集在一个操作中。 Codd的文章被尤金和迈克尔.斯通布雷克转载。他们启动了一个被称为的项目，使用资金分配的地理数据库，利用学生的程序员生成代码。从1973年开始，INGRES第一次测试的产品在1979年已经可以通常广泛使用了。在此期间，许多人运用这个产品 - 可能多达30人参与该项目，约五人一次。 INGRES在一些方法上类似系统R，包括将一种作为QUEL已知的“语言”的数据访问， QUEL是在事实上关系、是基于Codd的自己的阿尔法语言，但一直以来的被损坏的跟随SQL，从而违反了SQL关系模型本身的相同的概念。IBM自己做了一个实现关系模型的测试，PRTV和一个生产，经营体制12，他们现在都已经停产。霍尼韦尔为Multics做MRDS，现在有两个新的的实现：Alphora Dataphor和REL。其他DBMS实现通常称为关系实际上是SQL DBMS。 1968年开始，美国密歇根大学的微DBMS关系型数据库管理系统的开发。它被用来管理大型数据包括美国劳工部，美国环境保护署和阿尔伯塔大学，密歇根大学和韦恩州立大学（Wayne State University）的研究人员。在密歇根终端系统的电脑主机上运行。该系统在生产保持直到1996年。3.3 70年代末SQL数据库管理系统（DBMS）在20世纪70年代初，IBM开始致力于研发原型系统轻率地地基于Codd的概念和发关系型数据库系统。第一个版本是在1974年到1975年之间完成，然后开始工作多表的系统，在该系统中的数据可以被分割，使得没有一个记录（其中大部分是通常可选的）中的所有的数据要被存储在上一个大的“块”。随后的多用户版本的客户在1978年和1979年进行了测试，而当时一个标准的查询语言SQL已增加。 Codd的想法，建立自己既是可行的，并且优于Codasyl的，推动IBM开发一个真正的系统研发，量产版被称为SQL / DS，并且以后称之为数据库（DB2）。许多参与INGRES的人确信这样的系统会成为未来的商业上的成功，并形成自己的公司进行商业化的运作，除了与SQL接口。 SYBASE，Informix和NonStop SQL，并最终INGRES本身都被出售作为分支在20世纪80年代到原来的INGRES产品。即使是微软的SQL Server版本事实上是Sybase版本的重新构建，都是INGRES。只有拉里埃里森（Larry Ellison）的甲骨文公司开始从不同的链，根据IBM的文件系统研发关系型数据库系统，并击败IBM于1978年向市场推出发布的第一个版本。斯通布雷克从的INGRES发展也就是现在被称为PostgreSQL的一个新的数据库中吸取教训，Postgres通常被称作PostgreSQL，是用于全球关键任务的应用程序（.org和.info域名名称登记使用它作为其主要的数据存储，像许多大公司和金融机构）在瑞典，Codd的文章也读Mimer SQL从70年代中期开始在乌普萨拉大学发展。 1984年，该项目被合并成一个独立的企业。在20世纪80年代初，Mimer介绍了事务处理的高稳定性的应用中，这个想法随后又实施应用于其他大多数DBMS。3.4 20世纪80年代面向对象的数据库20世纪80年代，随着面向对象编程的上升，看到增长的如何在不同的数据库中进行的数据处理。程序员和设计师开始把他们的数据库中的数据对象。这就是说，如果一个人的数据是在一个数据库中，该人的属性，如他们的地址，电话号码，和年龄，现在被认为是属于该人，而不是被多余的数据。这允许数据之间的关系的关系的对象和它们的属性，而不是单独的字段。在20世纪80年代的另一大改变数据库的游戏规则，集中于提高可靠性和访问速度。在1989年，密歇根大学麦迪逊分校，两位教授在ACM相关会议发表了一篇文章，阐述其对提高数据库性能的方法。当时的想法是复制特定的重要的，并经常查询的信息，并将其存储在一个较小的临时数据库这些关键功能反馈到主数据库。这意味着查询可以更快的较小的数据库中搜索，而不是搜索整个数据集。这最终通过这种方式索引，这是几乎所有的操作系统从Windows到苹果的iPod设备的系统都使用的做法。4.DBMS构建模块一个数据库管理系统包括四个主要部分：建模语言，数据结构，数据库查询语言，和交易机制：4.1DBMS的组件DBMS引擎 接受从各种其他DBMS子系统的逻辑请求，将它们转换成物理当量，并实际上访问的，因为它们存在一个存储设备上的数据库和数据字典。数据定义子系统 帮助用户创建和维护的数据字典和定义在一个数据库中的文件的结构。数据处理子系统 可以帮助用户添加，更改和删除数据库中的信息和查询有价值的信息。软件工具内的数据操纵子系统的是最常见的用户和包含在数据库中的信息之间的主要接口。它允许用户指定其逻辑的信息需求。应用程序生成子系统 包含设施，以帮助用户开发的交易密集型应用。它通常要求用户执行一系列详细的任务来处理一个事务。它促进了易于使用的数据输入界面，编程语言和接口。数据管理子系统 帮助用户管理整个数据库环境提供的备份和恢复设施，安全管理，查询优化，并发控制和变更管理。4.2建模语言数据建模语言来定义每个主办的DBMS的数据库的架构，根据DBMS数据库模型。四个最常见的类型的模型：层次模型，网络模型，关系模型，对象模型。倒立的列表和其他的方法也可使用。一个给定的数据库管理系统，可提供的四种模式中的一个或多个。最优的结构依赖于自然的组织应用程序的数据和应用程序的要求（包括成交率（速度），可靠性，可维护性，可扩展性，和成本）。目前使用的主要模式是专案中嵌入SQL，尽管纯粹主义者的反对，他们认为这个模型是一个腐败的关系模型，因为它违反了它的几个基本原则的实用性和性能的缘故。许多数据库管理系统还支持开放式数据库连接API支持程序员以一种标准方式访问的DBMS。之前的数据库管理方法，组织依靠存储文件处理系统到组织，商店和处理数据文件的。加重了最终用户与文件处理，因为数据被存储在许多不同的文件中，并分别以不同的方式组织。每个文件的专业要与一个特定的应用程序使用。不用说，当它来提供所需的数据准确，及时时文件处理是庞大的，昂贵的和非柔软性的，数据冗余是一个问题，因为独立的数据文件产生重复的数据，所以更新时需要将每一个单独的文件需要更新的文件处理系统。另一个问题是缺乏数据集成。数据是依赖于其他的数据组织和存储的。最后，该系统中没有数据的一致性或标准化的文件处理系统，使得难以维护。出于所有这些原因，数据库管理方法畸形的生长。数据库管理系统（DBMS）的设计使用其中的5个数据库结构，提供简单的访问存储在数据库中的信息。五个数据库的结构层次，网络，关系，的多维和面向对象的模型。层次结构使用于早期的大型机数据库管理系统中。记录的关系形成一个树状模型。这种结构是简单的，但非柔软性，因为这种关系仅限于一到多的关系。 IBM公司的IMS系统和RDM的移动是在相同的数据具有多个层级的分层数据库系统的例子。 RDM Mobile是一个新设计的嵌入式移动数据库的计算机系统。层次结构，今天主要用于存储地理信息和文件系统。网络结构有更复杂的关系。与层次结构的不同，它可以涉及许多记录和访问他们的几条路径之一。换句话说，这种结构使许多一对多的关系。关系结构是如今最常用的。它被用于大型机，中型机和微机系统。它使用两维的行和列来存储数据。表中的记录，可连接常见的键值。1970年在为IBM工作时，EF Codd的设计了这种结构。该模型是不容易为最终用户运行查询，因为它可能需要多个表的复杂组合。多维结构与关系模型的是相似的。多维数据集寻找模型的尺寸有相关的数据在每个单元格中的元素。这种结构提供了一个类似电子表格的数据视图。这种结构容易维护，因为记录被存储的基本属性，他们以同样的方式查看和结构是很容易理解的。它的高性能使它成为最流行的数据库结构，当它涉及到可实现在线分析处理（OLAP）。面向对象的结构有能力处理图形，图片，声音和文字，数据类型，没有困难不像其他的数据库结构。这种结构是流行的多媒体基于Web的应用程序。它的目的是与面向对象的编程语言，如Java。4.3数据结构数据结构（字段，记录，文件和对象）优化，以处理存储在永久数据存储装置（这意味着，相对较慢的访问相比，易失性主存储器）的数据量非常大。4.4数据库查询语言数据库查询语言和报告编写允许用户以交互方式的数据库查询，分析其数据，并根据用户权限的数据进行更新。它还控制数据库的安全性。数据安全可以防止未经授权的用户查看或更新数据库。使用密码，用户被允许访问整个数据库或它的子集称为subschemas。例如，一个员工数据库可以包含个别雇员的所有数据，但可以授权一组用户只查看非农就业数据，而另一些则允许访问工作的历史和医疗数据。如果DBMS提供了一种交互的输入和更新数据库，以及审问，此功能允许个人数据库管理。但是，它可能不会留下审计线索的行动，或提供各种必要的控制在一个多用户的组织。这些控件是仅当一套应用程序定制的每一个数据项和更新功能。4.5交易机制理想情况下的数据库事务机构保证ACID属性，尽管并发用户访问的并发控制和故障（容错），以确保数据的完整性。它还保持在数据库中的数据的完整性。 DBMS能保持完整的数据库允许多个用户同时更新相同的记录。 DBMS可以帮助防止重复的记录，通过唯一索引，约束，例如，没有两个客户与同一客户号码（键字段），可以输入到数据库中。 ACID属性的更多信息，（冗余回避）。5.DBMS主题5.1外部逻辑和内部视图数据库管理系统提供了许多不同的用户共享数据和流程资源的能力。但是，可以有很多不同的用户，有许多不同的数据库需要。现在的问题是：如何才能让一个单一的，统一的数据库，满足这么多不同用户的不同的需求？一个DBMS最大限度地减少这些问题提供意见，数据库中的数据的外部视图（或用户视图），逻辑视图（或概念视图）和物理（或内部）视图。用户的视图，一个数据库程序表示中的数据是有意义的给用户，并处理这些数据的软件程序的格式。也就是说，逻辑视图告诉用户，在用户方面，什么是在数据库中。处理实际的，物理的安排和在该直接存取存储设备（DASD）中的数据的位置的物理视图。数据库专家使用的物理视图，使存储和处理资源的高效利用。与逻辑视图用户可以看到它们是如何存储不同的数据，并且他们不想知道的物理存储所有的技术细节。毕竟，企业用户的主要兴趣是在利用这些信息，而不是它是如何存储。一个DBMS的优势之一是，虽然通常只有一个概念（或逻辑）和物理（或内部）的数据视图，但他可以有无数的不同的外部意见。此功能允许用户在更多的业务相关的数据库信息的方式，而不是从技术，处理的观点。因此，逻辑视图引用用户视图的数据，并且物理地存储和处理数据的方式的指的是物理视图.5.2 DBMS的特性和功能另外，特别是在连接的关系模型数据库管理，从一组指定的域中绘制属性之间的关系可以被看作是主要的。例如，数据库可能表明了一辆车，本来是“红”褪色“粉红色”的时候，它的一些特定的“制造”的劣质油漆工作。这种较高的元数的关系提供信息，同时对所有的底层域，没有其他的特权是高于他们的。5.3 DBMS简单的定义数据库管理系统是系统相关的数据存储在一个“高效”，“紧凑型”的方式。在DBMS中存储的数据被访问，在非常快的时间和紧凑的装置，它被存储在数据库管理系统的数据覆盖在计算机的存储器中的空间非常少的有效的手段。在上面的定义中的短语“相关的数据”被使用，这意味着，它被存储在数据库管理系统的数据是关于一些特定主题。纵观近代历史，科学，地理信息，图像，文档存储和类似用途专门的数据库已经存在了。最近开始出现在主流数据库管理系统，以及来自此类应用的功能。然而，至少在商业数据处理市场的目的，存在的主要焦点，仍是重复记录的结构描述的属性。因此，今天推出的DBMS中经常需要的服务或功能的属性管理。通过外等功能的数据库管理系统，应用程序有效地共享代码，彼此都减轻了许多的内部复杂性。通常所提供的数据库管理系统的功能包括：5.3.1查询能力查询是请求属性信息的过程，信息从不同的角度和因素的组合。例如：“多少双门轿车，在得克萨斯州是绿色的吗？”数据库查询语言和报告编写允许用户以交互方式的数据库查询，分析其数据，并根据用户权限的数据进行更新。5.3.2备份和复制主磁盘或其他设备出现故障的情况下，需要进行定期的属性的复制。周期性复制的属性，也可以创建一个遥远的组织，不能轻易访问原始。 DBMS通常只是提供实用程序，以促进这一进程的提取和传播属性集。数据库服务器之间复制数据时，整个数据库系统，使信息保持一致，用户可以不说，甚至不知道他们使用的是在DBMS服务器，该系统被认为具有复制透明度。5.3.3规则通常情况下，一个人想将规则应用到的属性中，使属性变得清洁和可靠的。例如，我们可能有一个规则说，每节车厢只有一个引擎（发动机号确定）。如果有人试图与一个给定的汽车相关联的第二个引擎，我们希望DBMS拒绝这样的请求，并显示一条错误消息。然而，改变模型中的规范，例如，在这个例子中，混合气体的电动车，规则可能需要改变。理想情况下，这些规则应该是可以添加和删除，而不需要显着的数据布局重新设计。5.3.4安全通常情况下，最好是限制谁可以查看或更改的属性或属性组。这可能是直接由个人管理，或由指定的个人和特权的群体，或在最精心制作的模型通过分配角色，然后授予个人和团体权利。5.3.5计算常见的有计算的属性，如计数，求和，平均，排序，分组，交叉引用等，而不是每台计算机上的应用程序从头开始执行这些要求，他们可以依靠的DBMS提供这样的计算。5.3.6更改和访问日志记录通常一个人想知道是谁访问哪些属性，什么是改变，什么时候被改变了。日志服务允许保持记录的访问事件和变化。5.3.7自动优化如果是经常发生的使用模式或要求，有些DBMS可以调整自己，以改善这些交互的速度。在某些情况下，DBMS只是提供工具来监控性能，允许人类专家检验收集的统计数据后进行必要的调整。5.4元数据存储库元数据是描述数据的数据。例如，描述的属性在数据集被允许，这样的属性被称为“元信息”。元数据也被称为关于数据的数据。5.5目前的趋势在1998年，数据库管理需要新的风格数据库，以解决当前的数据库管理上的问题。研究人员发现，旧趋势的数据库管理变得过于复杂和有必要的自动化配置和管理。格哈德Weikum的Michael Stonebraker，Surajit乔德赫瑞的数据库管理系统，极大地影响了思想的先驱。他们认为，数据库管理需要一个更模块化的方法，有这么多的规格为各种用户的需求。由于这种新的数据库管理开发过程中，我们有无限的可能性。数据库管理是不再局限于“铁板一块的实体”。许多解决方案开发，以满足用户的个性化需求。在数据库管理中，众多的数据库选项的发展创造了灵活的解决方案。今天，有几个方面的数据库管理技术已经影响到了世界，因为我们知道它。为组织的发展，目录服务的组织的需求已经成为一个极端的必要性。企业现在都可以使用目录服务，提供及时搜索其公司的资料。移动设备不仅能够存储联系人信息的用户，但已发展到更大的能力。移动技术是能够缓存，用于计算机和较小的设备上显示大量的信息。网络搜索，甚至与数据库管理的影响。搜索引擎的查询能够在万维网定位数据。从数据仓库的发展与零售商也从中受益。这些公司都能够记录客户在他们的业务交易。网上交易已成为非常流行的电子商务世界。消费者和企业在公司网站上能够安全地进行支付。没有这些当前的事态发展将是不可能实现的数据库管理的演变。即使所有的数据库管理的进展和目前的发展趋势，为规范和需求的增长，他们将永远是一个新的发展需要。随着消费者互联网连接的速度增长，数据的可用性和计算变得更加普及，数据库被看着迁移到Web服务。正在使用的基于Web的语言，如XML和PHP来处理数据库的基于网络的服务。这些语言允许数据库住在“云”。与许多其他产品，如谷歌的GMail中，微软办公2010，和无忧的在线备份服务，许多服务都开始向移动网络基础的服务，以提高网络的可靠性，数据存储效率和缺乏需要专门的IT员工管理的硬件。在罗切斯特技术学院的学院发表了一篇文章，关于使用数据库在云计算和状态，他们的学校自己的课程计划增加基于云的数据库计算“他们的信息技术（IT）课程保持在技术的最前沿。英文原文Database management system1.Database management systemA Database Management System (DBMS) is a set of computer programs that controls the creation, maintenance, and the use of a database. It allows organizations to place control of database development in the hands of database administrators (DBAs) and other specialists. A DBMS is a system software package that helps the use of integrated collection of data records and files known as databases. It allows different user application programs to easily access the same database. DBMSs may use any of a variety of database models, such as the network model or relational model. In large systems, a DBMS allows users and other software to store and retrieve data in a structured way. Instead of having to write computer programs to extract information, user can ask simple questions in a query language. Thus, many DBMS packages provide Fourth-generation programming language (4GLs) and other application development features. It helps to specify the logical organization for a database and access and use the information within a database. It provides facilities for controlling data access, enforcing data integrity, managing concurrency, and restoring the database from backups. A DBMS also provides the ability to logically present database information to users.2. OverviewA DBMS is a set of software programs that controls the organization, storage, management, and retrieval of data in a database. DBMSs are categorized according to their data structures or types. The DBMS accepts requests for data from an application program and instructs the operating system to transfer the appropriate data. The queries and responses must be submitted and received according to a format that conforms to one or more applicable protocols. When a DBMS is used, information systems can be changed much more easily as the organizations information requirements change. New categories of data can be added to the database without disruption to the existing system.Database servers are computers that hold the actual databases and run only the DBMS and related software. Database servers are usually multiprocessor computers, with generous memory and RAID disk arrays used for stable storage. Hardware database accelerators, connected to one or more servers via a high-speed channel, are also used in large volume transaction processing environments. DBMSs are found at the heart of most database applications. DBMSs may be built around a custom multitasking kernel with built-in networking support, but modern DBMSs typically rely on a standard operating system to provide these functions.3. HistoryDatabases have been in use since the earliest days of electronic computing. Unlike modern systems which can be applied to widely different databases and needs, the vast majority of older systems were tightly linked to the custom databases in order to gain speed at the expense of flexibility. Originally DBMSs were found only in large organizations with the computer hardware needed to support large data sets.3.1 1960s Navigational DBMSAs computers grew in speed and capability, a number of general-purpose database systems emerged; by the mid-1960s there were a number of such systems in commercial use. Interest in a standard began to grow, and Charles Bachman, author of one such product, Integrated Data Store (IDS), founded the Database Task Group within CODASYL, the group responsible for the creation and standardization of COBOL. In 1971 they delivered their standard, which generally became known as the Codasyl approach, and soon there were a number of commercial products based on it available.The Codasyl approach was based on the manual navigation of a linked data set which was formed into a large network. When the database was first opened, the program was handed back a link to the first record in the database, which also contained pointers to other pieces of data. To find any particular record the programmer had to step through these pointers one at a time until the required record was returned. Simple queries like find all the people in India required the program to walk the entire data set and collect the matching results. There was, essentially, no concept of find or search. This might sound like a serious limitation today, but in an era when the data was most often stored on magnetic tape such operations were too expensive to contemplate anyway.IBM also had their own DBMS system in 1968, known as IMS. IMS was a development of software written for the Apollo program on the System/360. IMS was generally similar in concept to Codasyl, but used a strict hierarchy for its model of data navigation instead of Codasyls network model. Both concepts later became known as navigational databases due to the way data was accessed, and Bachmans 1973 Turing Award award presentation was The Programmer as Navigator. IMS is classified as a hierarchical database. IMS and IDMS, both CODASYL databases, as well as CINCOMs TOTAL database are classified as network databases.3.2 1970s Relational DBMSEdgar Codd worked at IBM in San Jose, California, in one of their offshoot offices that was primarily involved in the development of hard disk systems. He was unhappy with the navigational model of the Codasyl approach, notably the lack of a search facility which was becoming increasingly useful. In 1970, he wrote a number of papers that outlined a new approach to database construction that eventually culminated in the groundbreaking A Relational Model of Data for Large Shared Data Banks.In this paper, he described a new system for storing and working with large databases. Instead of records being stored in some sort of linked list of free-form records as in Codasyl, Codds idea was to use a table of fixed-length records. A linked-list system would be very inefficient when storing sparse databases where some of the data for any one record could be left empty. The relational model solved this by splitting the data into a series of normalized tables, with optional elements being moved out of the main table to where they would take up room only if needed.For instance, a common use of a database system is to track information about users, their name, login information, various addresses and phone numbers. In the navigational approach all of these data would be placed in a single record, and unused items would simply not be placed in the database. In the relational approach, the data would be normalized into a user table, an address table and a phone number table (for instance). Records would be created in these optional tables only if the address or phone numbers were actually provided.Linking the information back together is the key to this system. In the relational model, some bit of information was used as a key, uniquely defining a particular record. When information was being collected about a user, information stored in the optional (or related) tables would be found by searching for this key. For instance, if the login name of a user is unique, addresses and phone numbers for that user would be recorded with the login name as its key. This re-linking of related data back into a single collection is something that traditional computer languages are not designed for.Just as the navigational approach would require programs to loop in order to collect records, the relational approach would require loops to collect information about any one record. Codds solution to the necessary looping was a set-oriented language, a suggestion that would later spawn the ubiquitous SQL. Using a branch of mathematics known as tuple calculus, he demonstrated that such a system could support all the operations of normal databases (inserting, updating etc.) as well as providing a simple system for finding and returning sets of data in a single operation.Codds paper was picked up by two people at the Berkeley, Eugene Wong and Michael Stonebraker. They started a project known as INGRES using funding that had already been allocated for a geographical database project, using student programmers to produce code. Beginning in 1973, INGRES delivered its first test products which were generally ready for widespread use in 1979. During this time, a number of people had moved through the group perhaps as many as 30 people worked on the project, about five at a time. INGRES was similar to System R in a number of ways, including the use of a language for data access, known as QUEL QUEL was in fact relational, having been based on Codds own Alpha language, but has since been corrupted to follow SQL, thus violating much the same concepts of the relational model as SQL itself.IBM itself did one test implementation of the relational model, PRTV, and a production one, Business System 12, both now discontinued. Honeywell did MRDS for Multics, and now there are two new implementations: Alphora Dataphor and Rel. All other DBMS implementations usually called relational are actually SQL DBMSs. In 1968, the University of Michigan began development of the Micro DBMS relational database management system. It was used to manage very large data sets by the US Department of Labor, the Environmental Protection Agency and researchers from University of Alberta, the University of Michigan and Wayne State University. It ran on mainframe computers using Michigan Terminal System. The system remained in production until 1996.3.3 End 1970s SQL DBMSIBM started working on a prototype system loosely based on Codds concepts as System R in the early 1970s. The first version was ready in 1974/5, and work then started on multi-table systems in which the data could be split so that all of the data for a record (much of which is often optional) did not have to be stored in a single large chunk. Subsequent multi-user versions were tested by customers in 1978 and 1979, by which time a standardized query language, SQL, had been added. Codds ideas were establishing themselves as both workable and superior to Codasyl, pushing IBM to develop a true production version of System R, known as SQL/DS, and, later, Database 2 (DB2).Many of the people involved with INGRES became convinced of the future commercial success of such systems, and formed their own companies to commercialize the work but with an SQL interface. Sybase, Informix, NonStop SQL and eventually Ingres itself were all being sold as offshoots to the original INGRES product in the 1980s. Even Microsoft SQL Server is actually a re-built version of Sybase, and thus, INGRES. Only Larry Ellisons Oracle started from a different chain, based on IBMs papers on System R, and beat IBM to market when the first version was released in 1978.Stonebraker went on to apply the lessons from INGRES to develop a new database, Postgres, which is now known as PostgreSQL. PostgreSQL is often used for global mission critical applications (the .org and .info domain name registries use it as their primary data store, as do many large companies and financial institutions).In Sweden, Codds paper was also read and Mimer SQL was developed from the mid-70s at Uppsala University. In 1984, this project was consolidated into an independent enterprise. In the early 1980s, Mimer introduced transaction handling for high robustness in applications, an idea that was subsequently implemented on most other DBMS.3.4 1980s Object Oriented DatabasesThe 1980s, along with a rise in object oriented programming, saw a growth in how data in various databases were handled. Programmers and designers began to treat the data in their databases as objects. That is to say that if a persons data were in a database, that persons attributes, such as their address, phone number, and age, were now considered to belong to that person instead of being extraneous data. This allows for relationships between data to be relation to objects and their attributes and not to individual fields. Another big game changer for databases in the 1980s was the focus on increasing reliability and access speeds. In 1989, two professors from the University of Michigan at Madison, published an article at an ACM associated conference outlining their methods on increasing database performance. The idea was to replicate specific important, and often queried information, and store it in a smaller temporary database that linked these key features back to the main database. This meant that a query could search the smaller database much quicker, rather than search the entire dataset. This eventually leads to the practice of indexing, which is used by almost every operating system from Windows to the system that operates Apple iPod devices.4. DBMS building blocksA DBMS includes four main parts: modeling language, data structure, database query language, and transaction mechanisms:4.1 Components of DBMSDBMS Engine accepts logical request from the various other DBMS subsystems, converts them into physical equivalents, and actually accesses the database and data dictionary as they exist on a storage device. Data Definition Subsystem helps user to create and maintain the data dictionary and define the structure of the files in a database. Data Manipulation Subsystem helps user to add, change, and delete information in a database and query it for valuable information. Software tools within the data manipulation subsystem are most often the primary interface between user and the information contained in a database. It allows user to specify its logical information requirements. Application Generation Subsystem contains facilities to help users to develop transaction-intensive applications. It usually requires that user perform a detailed series of tasks to process a transaction. It facilitates easy-to-use data entry screens, programming languages, and interfaces. Data Administration Subsystem helps users to manage the overall database environment by providing facilities for backup and recovery, security management, query optimization, concurrency control, and change management. 4.2 Modeling languageA data modeling language to define the schema of each database hosted in the DBMS, according to the DBMS database model. The four most common types of models are the:hierarchical model, network model, relational model, and object model. Inverted lists and other methods are also used. A given database management system may provide one or more of the four models. The optimal structure depends on the natural organization of the applications data, and on the applications requirements (which include transaction rate (speed), reliability, maintainability, scalability, and cost).The dominant model in use today is the ad hoc one embedded in SQL, despite the objections of purists who believe this model is a corruption of the relational model, since it violates several of its fundamental principles for the sake of practicality and performance. Many DBMSs also support the Open Database Connectivity API that supports a standard way for programmers to access the DBMS.Before the database management approach, organizations relied on file processing systems to organize, store, and process data files. End users became aggravated with file processing because data is stored in many different files and each organized in a different way. Each file was specialized to be used with a specific application. Needless to say, file processing was bulky, costly and nonflexible when it came to supplying needed data accurately and promptly. Data redundancy is an issue with the file processing system because the independent data files produce duplicate data so when updates were needed each separate file would need to be updated. Another issue is the lack of data integration. The data is dependent on other data to organize and store it. Lastly, there was not any consistency or standardization of the data in a file processing system which makes maintenance difficult. For all these reasons, the database management approach was produced. Database management systems (DBMS) are designed to use one of five database structures to provide simplistic access to information stored in databases. The five database structures are hierarchical, network, relational, multidimensional and object-oriented models.The hierarchical structure was used in early mainframe DBMS. Records relationships form a treelike model. This structure is simple but nonflexible because the relationship is confined to a one-to-many relationship. IBMs IMS system and the RDM Mobile are examples of a hierarchical database system with multiple hierarchies over the same data. RDM Mobile is a newly designed embedded database for a mobile computer system. The hierarchical structure is used primary today for storing geographic information and file systems.The network structure consists of more complex relationships. Unlike the hierarchical structure, it can relate to many records and accesses them by following one of several paths. In other words, this structure allows for many-to-many relationships.The relational structure is the most commonly used today. It is used by mainframe, midrange and microcomputer systems. It uses two-dimensional rows and columns to store data. The tables of records can be connected by common key values. While working for IBM, E.F. Codd designed this structure in 1970. The model is not easy for the end user to run queries with because it may require a complex combination of many tables.The multidimensional structure is similar to the relational model. The dimensions of the cube looking model have data relating to elements in each cell. This structure gives a spreadsheet like view of data. This structure is easy to maintain because records are stored as fundamental attributes, the same way theyre viewed and the structure is easy to understand. Its high performance has made it the most popular database structure when it comes to enabling online analytical processing (OLAP).The object oriented structure has the ability to handle graphics, pictures, voice and text, types of data, without difficultly unlike the other database structures. This structure is popular for multimedia Web-based applications. It was designed to work with object-oriented programming languages such as Java.4.3 Data structureData structures (fields, records, files and objects) optimized to deal with very large amounts of data stored on a permanent data storage device (which implies relatively slow access compared to volatile main memory).4.4 Database query languageA database query language and report writer allows users to interactively interrogate the database, analyze its data and update it according to the users privileges on data. It also controls the security of the database. Data security prevents unauthorized users from viewing or updating the database. Using passwords, users are allowed access to the entire database or subsets of it called subschemas. For example, an employee database can contain all the data about an individual employee, but one group of users may be authorized to view only payroll data, while others are allowed access to only work history and medical data.If the DBMS provides a way to interactively enter and update the database, as well as interrogate it, this capability allows for managing personal databases. However, it may not leave an audit trail of actions or provide the kinds of controls necessary in a multi-user organization. These controls are only available when a set of application programs are customized for each data entry and updating function.4.5 Transaction mechanismA database transaction mechanism ideally guarantees ACID properties in order to ensure data integrity despite concurrent user accesses (concurrency control), and faults (fault tolerance). It also maintains the integrity of the data in the database. The DBMS can maintain the integrity of the database by not allowing more than one user to update the same record at the same time. The DBMS can help prevent duplicate records via unique index constraints; for example, no two customers with the same customer numbers (key fields) can be entered into the database. See ACID properties for more information (Redundancy avoidance).5. DBMS topics5.1 External, Logical and Internal viewA database management system provides the ability for many different users to share data and process resources. But as there can be many different users, there are many different database needs. The question now is: How can a single, unified database meet the differing requirement of so many users?A DBMS minimizes these problems by providing two views of the database data: an external view(or User view), logical view(or conceptual view)and physical(or internal) view. The users view, of a database program represents data in a format that is meaningful to a user and to the software programs that process those data. That is, the logical view tells the user, in user terms, what is in the database. The physical view deals with the actual, physical arrangement and location of data in the direct access storage devices(DASDs). Database specialists use the physical view to make efficient use of storage and processing resources. With the logical view users can see data differently from how they are stored, and they do not want to know all the technical details of physical storage. After all, a business user is primarily interested in using the information, not in how it is stored.One strength of a DBMS is that while there is typically only one conceptual (or logical) and physical (or Internal) view of the data, there can be an endless number of different External views. This feature allows users to see database information in a more business-related way rather than from a technical, processing viewpoint. Thus the logical view refers to the way user views data, and the physical view to the way the data are physically stored and processed.5.2 DBMS features and capabilitiesAlternatively, and especially in connection with the relational model of database management, the relation between attributes drawn from a specified set of domains can be seen as being primary. For instance, the database might indicate that a car that was originally red might fade to pink in time, provided it was of some particular make with an inferior paint job. Such higher arity relationships provide information on all of the underlying domains at the same time, with none of them being privileged above the others.5.3 DBMS simple definitionData base management system is the system in which related data is stored in an efficient and compact manner. Efficient means that the data which is stored in the DBMS is accessed in very quick time and compact means that the data which is stored in DBMS covers very less space in computers memory. In above definition the phrase related data is used which means that the data which is stored in DBMS is about some particular topic.Throughout recent history specialized databases have existed for scientific, geospatial, imaging, document storage and like uses. Functionality drawn from such applications has lately begun appearing in mainstream DBMSs as well. However, the main focus there, at least when aimed at the commercial data processing market, is still on descriptive attributes on repetitive record structures.Thus, the DBMSs of today roll together frequently needed services or features of attribute management. By externalizing such functionality to the DBMS, applications effectively share code with each other and are relieved of much internal complexity. Features commonly offered by database management systems include: 5.3.1 Query ability Querying is the process of requesting attribute information from various perspectives and combinations of factors. Example: How many 2-door cars in Texas are green? A database query language and report writer allow users to interactively interrogate the database, analyze its data and update it according to the users privileges on data. 5.3.2 Backup and replication Copies of attributes need to be made regularly in case primary disks or other equipment fails. A periodic copy of attributes may also be created for a distant organization that cannot readily access the original. DBMS usually provide utilities to facilitate the process of extracting and disseminating attribute sets. When data is replicated between database servers, so that the information remains consistent throughout the database system and users cannot tell or even know which server in the DBMS they are using, the system is said to exhibit replication transparency. 5.3.3 Rule enforcement Often one wants to apply rules to attributes so that the attributes are clean and reliable. For example, we may have a rule that says each car can have only one engine associated with it (identified by Engine Number). If somebody tries to associate a second engine with a given car, we want the DBMS to deny such a request and display an error message. However, with changes in the model specification such as, in this example, hybrid gas-electric cars, rules may need to change. Ideally such rules should be able to be added and removed as needed without significant data layout redesign. 5.3.4 Security Often it is desirable to limit who can see or change which attributes or groups of attributes. This may be managed directly by individual, or by the assignment of individuals and privileges to groups, or (in the most elaborate models) through the assignment of individuals and groups to roles which are then granted entitlements. 5.3.5 Computation There are common computations requeste