計算機(jī)專業(yè)畢業(yè)論文外文翻譯2篇

1、武漢理工大學(xué)本科生畢業(yè)設(shè)計（論文）英文翻譯畢業(yè)設(shè)計題目：會務(wù)管理系統(tǒng)的設(shè)計與實(shí)現(xiàn)學(xué)院（系）： 信息工程學(xué)院 專業(yè)班級： 電信0601班 學(xué)生姓名： 肖 曼 指導(dǎo)教師： 王 琳 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

2、 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 a

3、s 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

4、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

5、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+ langua

6、ge 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 thi

7、s 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 simul

8、taneously 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 beco

9、me 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. mic

10、rosoft 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

11、 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 lan

12、guage 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 t

13、hat 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 easie

14、r 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 requir

15、ed. 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 docum

16、entation. 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

17、 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 properti

18、es 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 an

19、d 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 o

20、f 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 ar

21、ea 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 con

22、tinue 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 applic

23、ations that fall into this category are very low.中文：c#的優(yōu)點(diǎn)c#在某種程度上可以看作是.net面向windows環(huán)境的一種編程語言。在過去的十幾年里，microsoft給windows和 windows api添加了許多功能，vb和c+也經(jīng)歷了許多變化。雖然vb和c+最終已成為非常強(qiáng)大的語言，但這兩種語言也存在問題，因?yàn)樗鼈儽Ａ袅嗽瓉淼囊恍﹥?nèi)容。對于visual basic來說，它的主要優(yōu)點(diǎn)是很容易理解，許多編程工作都很容易完成，基本上隱藏了windows api和com組件結(jié)構(gòu)的內(nèi)涵。其缺點(diǎn)是visual basic從來沒有實(shí)現(xiàn)真正意義上

24、的面向?qū)ο?，所以大型?yīng)用程序很難分解和維護(hù)。另外，因?yàn)関b的語法繼承于basic的早期版本(basic主要是為了讓初學(xué)者更容易理解，而不是為了編寫大型商業(yè)應(yīng)用程序)，所以不能真正成為結(jié)構(gòu)化或面向?qū)ο蟮木幊陶Z言。另一方面，c+在ansi c+語言定義中有其自己的根。它與ansi不完全兼容，因?yàn)閙icrosoft是在ansi定義標(biāo)準(zhǔn)化之前編寫c+編譯器的，但已經(jīng)相當(dāng)接近了。遺憾的是，這導(dǎo)致了兩個問題。其一，ansi c+是在十幾年前的技術(shù)條件下開發(fā)的，因此不支持現(xiàn)在的概念(例如unicode字符串和生成xml文檔)，某些古老的語法結(jié)構(gòu)是為以前的編譯器設(shè)計的(例如成員函數(shù)的聲明和定義是分開的)。其二

25、，microsoft同時還試圖把c+演變?yōu)橐环N用于在windows上執(zhí)行高性能任務(wù)的語言 在語言中避免添加大量microsoft專用的關(guān)鍵字和各種庫。其結(jié)果是在windows中，該語言成為了一種非常雜亂的語言。讓一個c+開發(fā)人員說說字符串有多少個定義方式就可以說明這一點(diǎn)：char*、lptstr、string、cstring (mfc 版本)、cstring (wtl 版本)、wchar_t*和 olechar*等?，F(xiàn)在進(jìn)入.net時代 一種全新的環(huán)境，它對這兩種語言都進(jìn)行了新的擴(kuò)展。microsoft給c+添加了許多microsoft專用的關(guān)鍵字，并把vb演變?yōu)関b.net，保留了一些基本的

26、vb語法，但在設(shè)計上完全不同，從實(shí)際應(yīng)用的角度來看，vb.net是一種新語言。在這里，microsoft決定給開發(fā)人員另一個選擇 專門用于.net、具有新起點(diǎn)的語言， 即visual c# .net。microsoft在正式場合把c#描述為一種簡單、現(xiàn)代、面向?qū)ο?、類型非常安全、派生于c和c+的編程語言。大多數(shù)獨(dú)立的評論員對其說法是“派生于c、 c+ 和java”。這種描述在技術(shù)上是非常準(zhǔn)確的，但沒有涉及到該語言的真正優(yōu)點(diǎn)。從語法上看，c#非常類似于c+和java，許多關(guān)鍵字都是相同的，c#也使用類似于c+和java的塊結(jié)構(gòu)，并用括號()來標(biāo)記代碼塊，用分號分隔各行語句。對c#代碼的第一印象是

27、它非常類似于c+或java代碼。但在這些表面上的類似性后面，c#學(xué)習(xí)起來要比c+容易得多，但比java難一些。其設(shè)計與現(xiàn)代開發(fā)工具的適應(yīng)性要比其他語言更高，它同時具有visual basic的易用性、高性能以及c+的低級內(nèi)存訪問性。c#包括以下一些特性： 完全支持類和面向?qū)ο缶幊?，包括接口和繼承、虛函數(shù)和運(yùn)算符重載的處理。 定義完整、一致的基本類型集。 對自動生成xml文檔說明的內(nèi)置支持。 自動清理動態(tài)分配的內(nèi)存。 可以用用戶定義的特性來標(biāo)記類或方法。這可以用于文檔說明，對編譯有一定的影響(例如，把方法標(biāo)記為只在調(diào)試時編譯)。 對.net基類庫的完全訪問權(quán)，并易于訪問windows api。

28、可以使用指針和直接內(nèi)存訪問，但c#語言可以在沒有它們的條件下訪問內(nèi)存。 以vb的風(fēng)格支持屬性和事件。 改變編譯器選項(xiàng)，可以把程序編譯為可執(zhí)行文件或.net組件庫，該組件庫可以用與activex控件(com組件)相同的方式由其他代碼調(diào)用。 c#可以用于編寫asp.net動態(tài)web頁面和xml web服務(wù)。應(yīng)該指出，對于上述大多數(shù)特性，vb.net和managed c+也具備。但c#從一開始就使用.net，對.net特性的支持不僅是完整的，而且提供了比其他語言更合適的語法。c#語言本身非常類似于java，但其中有一些改進(jìn)，因?yàn)閖ava并不是為應(yīng)用于.net環(huán)境而設(shè)計的。在結(jié)束這個主題前，還要指出c

29、#的兩個局限性。其一是該語言不適用于編寫時間急迫或性能非常高的代碼，例如一個要運(yùn)行1000或1050次的循環(huán)，并在不需要這些循環(huán)時，立即清理它們所占用的資源。在這方面，c+可能仍是所有低級語言中的佼佼者。其二是c#缺乏性能極高的應(yīng)用程序所需要的關(guān)鍵功能，包括保證在代碼的特定地方運(yùn)行的內(nèi)聯(lián)函數(shù)和析構(gòu)函數(shù)。但這類應(yīng)用程序非常少。2 dba survivor：become a rock star dba by thomas larock , published by apress . 2010英文原文：you know that a database is a collection of logic

30、ally 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

31、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 diff

32、icult 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 oth

33、ers 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 aren

34、t 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 resp

35、onse 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,

36、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 kind

37、s 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

38、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

39、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

40、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 u

41、ser, 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 pack

42、ages 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 profess

43、ional 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

44、 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 mistake

45、s 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

46、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 experi

47、enced 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 data

48、base 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 lo

49、ng 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 a

50、utomatically 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

51、 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

52、 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 eng

53、ineering, 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 syste

54、ms 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

55、. 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 param

56、eters 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 f

57、lawed. 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 proce

58、ssing 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 providing i