计算机专业毕业论文外文翻译2篇.doc

武汉理工大学本科生毕业设计（论文）英文翻译毕业设计题目：会务管理系统的设计与实现学院（系）： 信息工程学院 专业班级： 电信0601班 学生姓名： 肖 曼 指导教师： 王 琳 1 professional c# third edition simon robinson, christian nagel, jay glynn, morgan skinner, karli watson, bill evjen. wiley publishing, inc. 2006英文原文：where c# fits inin one sense, c# can be seen as being the same thing to programming languages as .net is to the windows environment. just as microsoft has been adding more and more features to windows and the windows api over the past decade, visual basic and c+ have undergone expansion. although visual basic and c+ have ended up as hugely powerful languages as a result of this, both languages also suffer from problems due to the legacies of how they have evolved.in the case of visual basic 6 and earlier, the main strength of the language was the fact that it was simple to understand and didnt make many programming tasks easy, largely hiding the details of the windows api and the com component infrastructure from the developer. the downside to this was that visual basic was never truly object-oriented, so that large applications quickly become disorganized and hard to maintain. as well as this, because visual basics syntax was inherited from early versions of basic (which, in turn, was designed to be intuitively simple for beginning programmers to understand, rather than to write large commercial applications), it didnt really lend itself to well-structured or object-oriented programs.c+, on the other hand, has its roots in the ansi c+ language definition. it isnt completely ansi compliant for the simple reason that microsoft first wrote its c+ compiler before the ansi definition had become official, but it comes close. unfortunately, this has led to two problems. first, ansi c+ has its roots in a decade-old state of technology, and this shows up in a lack of support for modern concepts (such as unicode strings and generating xml documentation), and in some archaic syntax structures designed for the compilers of yesteryear (such as the separation of declaration from definition of member functions). second, microsoft has been simultaneously trying to evolve c+ into a language that is designed for high-performance tasks on windows, and in order to achieve that theyve been forced to add a huge number of microsoft-specific keywords as well as various libraries to the language. the result is that on windows, the language has become a complete mess. just ask c+ developers how many definitions for a string they can think of: char*, lptstr, string, cstring (mfc version), cstring (wtl version), wchar_t*, olechar*, and so on.now enter .neta completely new environment that is going to involve new extensions to both languages. microsoft has gotten around this by adding yet more microsoft-specific keywords to c+, and by completely revamping visual basic into visual basic .net, a language that retains some of the basic vb syntax but that is so different in design that we can consider it to be, for all practical purposes, a new language. its in this context that microsoft has decided to give developers an alternativea language designed specifically for .net, and designed with a clean slate. visual c# .net is the result. officially, microsoft describes c# as a “simple, modern, object-oriented, and type-safe programming language derived from c and c+.” most independent observers would probably change that to “derived from c, c+, and java.” such descriptions are technically accurate but do little to convey the beauty or elegance of the language. syntactically, c# is very similar to both c+ and java, to such an extent that many keywords are the same, and c# also shares the same block structure with braces () to mark blocks of code, and semicolons to separate statements. the first impression of a piece of c# code is that it looks quite like c+ or java code. behind that initial similarity, however, c# is a lot easier to learn than c+, and of comparable difficulty to java. its design is more in tune with modern developer tools than both of those other languages, and it has been designed to give us, simultaneously, the ease of use of visual basic, and the high performance, low-level memory access of c+ if required. some of the features of c# are: full support for classes and object-oriented programming, including both interface and implementation inheritance, virtual functions, and operator overloading. a consistent and well-defined set of basic types. built-in support for automatic generation of xml documentation. automatic cleanup of dynamically allocated memory. the facility to mark classes or methods with user-defined attributes. this can be useful for documentation and can have some effects on compilation (for example, marking methods to be compiled only in debug builds). full access to the .net base class library, as well as easy access to the windows api (if you really need it, which wont be all that often). pointers and direct memory access are available if required, but the language has been designed in such a way that you can work without them in almost all cases. support for properties and events in the style of visual basic. just by changing the compiler options, you can compile either to an executable or to a library of .net components that can be called up by other code in the same way as activex controls (com components). c# can be used to write asp.net dynamic web pages and xmlweb services.most of the above statements, it should be pointed out, do also apply to visual basic .net and managed c+. the fact that c# is designed from the start to work with .net, however, means that its support for the features of .net is both more complete, and offered within the context of a more suitable syntax than for those other languages. while the c# language itself is very similar to java, there are some improvements: in particular, java is not designed to work with the .net environment.before we leave the subject, we should point out a couple of limitations of c#. the one area the language is not designed for is time-critical or extremely high performance codethe kind where you really are worried about whether a loop takes 1,000 or 1,050 machine cycles to run through, and you need to clean up your resources the millisecond they are no longer needed. c+ is likely to continue to reign supreme among low-level languages in this area. c# lacks certain key facilities needed for extremely high performance apps, including the ability to specify inline functions and destructors that are guaranteed to run at particular points in the code. however, the proportions of applications that fall into this category are very low.中文：c#的优点c#在某种程度上可以看作是.net面向windows环境的一种编程语言。在过去的十几年里，microsoft给windows和 windows api添加了许多功能，vb和c+也经历了许多变化。虽然vb和c+最终已成为非常强大的语言，但这两种语言也存在问题，因为它们保留了原来的一些内容。对于visual basic来说，它的主要优点是很容易理解，许多编程工作都很容易完成，基本上隐藏了windows api和com组件结构的内涵。其缺点是visual basic从来没有实现真正意义上的面向对象，所以大型应用程序很难分解和维护。另外，因为vb的语法继承于basic的早期版本(basic主要是为了让初学者更容易理解，而不是为了编写大型商业应用程序)，所以不能真正成为结构化或面向对象的编程语言。另一方面，c+在ansi c+语言定义中有其自己的根。它与ansi不完全兼容，因为microsoft是在ansi定义标准化之前编写c+编译器的，但已经相当接近了。遗憾的是，这导致了两个问题。其一，ansi c+是在十几年前的技术条件下开发的，因此不支持现在的概念(例如unicode字符串和生成xml文档)，某些古老的语法结构是为以前的编译器设计的(例如成员函数的声明和定义是分开的)。其二，microsoft同时还试图把c+演变为一种用于在windows上执行高性能任务的语言 在语言中避免添加大量microsoft专用的关键字和各种库。其结果是在windows中，该语言成为了一种非常杂乱的语言。让一个c+开发人员说说字符串有多少个定义方式就可以说明这一点：char*、lptstr、string、cstring (mfc 版本)、cstring (wtl 版本)、wchar_t*和 olechar*等。现在进入.net时代 一种全新的环境，它对这两种语言都进行了新的扩展。microsoft给c+添加了许多microsoft专用的关键字，并把vb演变为vb.net，保留了一些基本的vb语法，但在设计上完全不同，从实际应用的角度来看，vb.net是一种新语言。在这里，microsoft决定给开发人员另一个选择 专门用于.net、具有新起点的语言， 即visual c# .net。microsoft在正式场合把c#描述为一种简单、现代、面向对象、类型非常安全、派生于c和c+的编程语言。大多数独立的评论员对其说法是“派生于c、 c+ 和java”。这种描述在技术上是非常准确的，但没有涉及到该语言的真正优点。从语法上看，c#非常类似于c+和java，许多关键字都是相同的，c#也使用类似于c+和java的块结构，并用括号()来标记代码块，用分号分隔各行语句。对c#代码的第一印象是它非常类似于c+或java代码。但在这些表面上的类似性后面，c#学习起来要比c+容易得多，但比java难一些。其设计与现代开发工具的适应性要比其他语言更高，它同时具有visual basic的易用性、高性能以及c+的低级内存访问性。c#包括以下一些特性： 完全支持类和面向对象编程，包括接口和继承、虚函数和运算符重载的处理。 定义完整、一致的基本类型集。 对自动生成xml文档说明的内置支持。 自动清理动态分配的内存。 可以用用户定义的特性来标记类或方法。这可以用于文档说明，对编译有一定的影响(例如，把方法标记为只在调试时编译)。 对.net基类库的完全访问权，并易于访问windows api。 可以使用指针和直接内存访问，但c#语言可以在没有它们的条件下访问内存。 以vb的风格支持属性和事件。 改变编译器选项，可以把程序编译为可执行文件或.net组件库，该组件库可以用与activex控件(com组件)相同的方式由其他代码调用。 c#可以用于编写asp.net动态web页面和xml web服务。应该指出，对于上述大多数特性，vb.net和managed c+也具备。但c#从一开始就使用.net，对.net特性的支持不仅是完整的，而且提供了比其他语言更合适的语法。c#语言本身非常类似于java，但其中有一些改进，因为java并不是为应用于.net环境而设计的。在结束这个主题前，还要指出c#的两个局限性。其一是该语言不适用于编写时间急迫或性能非常高的代码，例如一个要运行1000或1050次的循环，并在不需要这些循环时，立即清理它们所占用的资源。在这方面，c+可能仍是所有低级语言中的佼佼者。其二是c#缺乏性能极高的应用程序所需要的关键功能，包括保证在代码的特定地方运行的内联函数和析构函数。但这类应用程序非常少。2 dba survivor：become a rock star dba by thomas larock , published by apress . 2010英文原文：you know that a database is a collection of logically related data elements that may be structured in various ways to meet the multiple processing and retrieval needs of organizations and individuals. there s nothing new about databasesearly ones were chiseled in stone, penned on scrolls, and written on index cards. but now databases are commonly recorded on magnetizable media, and computer programs are required to perform the necessary storage and retrieval operations.youll see in the following pages that complex data relationships and linkages may be found in all but the simplest databases. the system software package that handles the difficult tasks associated with creating, accessing, and maintaining database records is called a database management system（dbms）.the programs in a dbms package establish an interface between the database itself and the users of the database.（these users may be applications programmers,managers and others with information needs, and various os programs.）a dbms can organize, process, and present selected data elements from the database. this capability enables decision makers to search, probe, and query database contents in order to extract answers to nonrecurring and unplanned questions that arent available in regular reports. these questions might initially be vague and / or poorly defined, but people can “browse” through the database until they have the needed information. in short, the dbms will “manage” the stored data items and assemble the needed items from the common database in response to the queries of those who arent programmers. in a file-oriented system, users needing special information may communicate their needs to a programmer, who, when time permits, will write one or more programs to extract the data and prepare the information4.the availability of a dbms, however, offers users a much faster alternative communications path.if the dbms provides a way to interactively and update the database, as well as interrogate it capability allows for managing personal data-aces however, it does not automatically leave an audit trail of actions and does not provide the kinds of control a necessary in a multiuser organization. these-controls are only available when a set of application programs are customized for each data entry and updating function. software for personal computers which perform me of the dbms functions have been very popular. personal computers were intended for use by individuals for personal information storage and process- these machines have also been used extensively small enterprises, professionals like doctors, acrylics, engineers, lawyers and so on .by the nature of intended usage, database systems on these machines except from several of the requirements of full doge database systems. since data sharing is not tended, concurrent operations even less so, the fewer can be less complex. security and integrity maintenance are de-emphasized or absent. as data limes will be small, performance efficiency is also important. in fact, the only aspect of a database system that is important is data independence. data-dependence, as stated earlier, means that applicant programs and user queries need not recognizant physical organization of data on secondary storage. the importance of this aspect, particularly for the personal computer user, is that this greatly simplifies database usage. the user can store, access and manipulate data at a high level (close to the application) and be totally shielded from the low level (close to the machine) details of data organization. we will not discuss details of specific pc dbms software packages here. let us summarize in the following the strengths and weaknesses of personal computer data-base software systems： the most obvious positive factor is the user friendliness of the software. a user with no prior computer background would be able to use the system to store personal and professional data, retrieve and perform relayed processing. the user should, of course, satiety himself about the quality of software and the freedom from errors (bugs) so that invest-merits in data arc protected. for the programmer implementing applications with them, the advantage lies in the support for applications development in terms of input screen generations, output report generation etc. offered by theses stems. the main negative point concerns absence of data protection features. unless encrypted, data cane accessed by whoever has access to the machine data can be destroyed through mistakes or malicious intent. the second weakness of many of the pc-based systems is that of performance. if data volumes grow up to a few thousands of records, performance could be a bottleneck. for organization where growth in data volumes is expected, availability of, the same or compatible software on large machines should be considered.this is one of the most common misconceptions about database management systems that are used in personal computers. thoroughly comprehensive and sophisticated business systems can be developed in dbase, paradox and other dbmss. however, they are created by experienced programmers using the dbmss own programming language. that is not the same as users who create and manage personal files that are not part of the mainstream company system. transaction management of databasethe objective of long-duration transactions is to model long-duration, interactive database access sessions in application environments. the fundamental assumption about short-duration of transactions that underlies the traditional model of transactions is inappropriate for long-duration transactions. the implementation of the traditional model of transactions may cause intolerably long waits when transactions aleph to acquire locks before accessing data, and may also cause a large amount of work to be lost when transactions are backed out in response to user-initiated aborts or system failure situations. the objective of a transaction model is to pro-vide a rigorous basis for automatically enforcing criterion for database consistency for a set of multiple concurrent read and write accesses to the database in the presence of potential system failure situations. the consistency criterion adopted for traditional transactions is the notion of scrializability. scrializa-bility is enforced in conventional database systems through the use of locking for automatic concurrency control, and logging for automatic recovery from system failure situations. a “transaction” that doesnt provide a basis for automatically enforcing data-base consistency is not really a transaction. to be sure, a long-duration transaction need not adopt seri-alizability as its consistency criterion. however, there must be some consistcricy criterion.version system management of database despite a large number of proposals on version support in the context of computer aided design and software engineering, the absence of a consensus on version semantics has been a key impediment to version support in database systems. because of the differences between files and databases, it is intuitively clear that the model of versions in database systems cannot be as simple as that adopted in file systems to support software engineering.for data-bases, it may be necessary to manage not only versions of single objects (e.g. a software module, document, but also versions of a collection of objects (e.g. a compound document, a user manual, etc. and perhaps even versions of the schema of database (c.g. a table or a class, a collection of tables or classes). broadly, there are three directions of research and development in versioning. first is the notion of a parameterized versioning, that is, designing and implementing a versioning system whose behavior may be tailored by adjusting system parameters this may be the only viable approach, in view of the fact that there are various plausible choices for virtually every single aspect of versioning.the second is to revisit these plausible choices for every aspect of versioning, with the view to discarding some of themes either impractical or flawed. the third is the investigation into the semantics and implementation of versioning collections of objects and of versioning the database. there is no consensus of the definition of the term “management information system”. some writers prefer alternative terminology such as “information processing system”, “information and decision system”, “organizational information system”, or simply “information system” to refer to the computer-based information processing system which supports the operations, management, and decision-making functions of an organization. this text uses “mis” because it is descriptive and generally understood; it also frequently uses “information system” instead of “mis” to refer to an organizational information system.a definition of a management information system, as the term is generally understood, is an integrated, user-machine system for provi