計(jì)算機(jī)外文資料翻譯

1、.畢業(yè)設(shè)計(jì)(論文)外文資料翻譯院 系計(jì)算機(jī)科學(xué)與工程學(xué)院專業(yè)計(jì)算機(jī)科學(xué)與技術(shù)學(xué)生姓名班級(jí)學(xué)號(hào)外文出處Russ Basiura,Mike BatongbacalProfessional ASP.NET Web ServicesMatt WeisfeldThe Object-Oriented Thought ProcessJeffrey PutzMaximizing ASP.NET:Real World,Object-Oriented Development附件：1.外文資料翻譯譯文； 2.外文資料原文；指導(dǎo)教師評(píng)語：指導(dǎo)教師簽名：年月日附件1：外文資料翻譯譯文1 利用面向?qū)ο髮?shí)現(xiàn)設(shè)計(jì)一般來說，一

2、個(gè)可靠的面向?qū)ο蟮臄?shù)額及過程往往包含以下步驟：(1)完成適當(dāng)?shù)姆治觯?2)建立一份描述系統(tǒng)的工作陳述；(3)從上述的工作陳述中收集需求；(4)開發(fā)一個(gè)用戶界面模型；(5)明確類；(6)確定各個(gè)類的職責(zé)；(7)確定各個(gè)類是如何相互交互的；(8)創(chuàng)建一個(gè)工程模型來描述要構(gòu)建的系統(tǒng)；系統(tǒng)（或?qū)ο竽Ｐ停┯深悎D和類交互構(gòu)成。這個(gè)模型應(yīng)當(dāng)真實(shí)地表示系統(tǒng)，而且要易于理解和修改。2 類到底是什么簡(jiǎn)而言之，類似對(duì)象的一個(gè)藍(lán)圖。當(dāng)你在實(shí)例化一個(gè)對(duì)象時(shí)，就是使用一個(gè)類作為構(gòu)建這個(gè)對(duì)象的基礎(chǔ)。實(shí)際上，解釋類和對(duì)象時(shí)確實(shí)存在“先有雞還是先有蛋”的問題。要描述類很難不使用對(duì)象這個(gè)詞，反過來，描述對(duì)象時(shí)又少不了類。例如，一

3、輛自行車是一個(gè)對(duì)象。不過，必須有人創(chuàng)建了自行車的藍(lán)圖（也就是類）。在面向?qū)ο蟮能浖O(shè)計(jì)中就不存在這樣的問題，我們確實(shí)知道哪一個(gè)在前應(yīng)該是先有類。如果沒有類，對(duì)象就無法實(shí)例化。要解釋類和方法，即一個(gè)關(guān)系數(shù)據(jù)庫領(lǐng)域的例子會(huì)很有幫助的。在一個(gè)數(shù)據(jù)庫表中，表的自身的定義（字段、描述和所用的數(shù)據(jù)類型）就是一個(gè)類（元數(shù)據(jù)），對(duì)象則是表中的行（數(shù)據(jù)）。3 建立用戶界面模型作為面向?qū)ο笤O(shè)計(jì)過程的最后一步，必須創(chuàng)建用戶界面的一個(gè)原型。這個(gè)原型將提供很有價(jià)值的信息來幫助指導(dǎo)迭代完成設(shè)計(jì)過程。在Object-Oriented Design in Java一書中，Gilbert和McCarty就曾指出“對(duì)于一個(gè)系統(tǒng)用

4、戶來說，用戶界面就是系統(tǒng)”。這種說法非常貼切。創(chuàng)建用戶界面原型有很多不同的方法?？梢栽诩埳匣蛘咴诎装迳袭嫵鲇脩艚缑?，可以使用一種專門的原型工具甚至一個(gè)語言環(huán)境（如Visual Basic，它常用于建立快速模型），也可以使用你最喜歡的開發(fā)工具的集成開發(fā)環(huán)境來創(chuàng)建原型。不論你用哪種方式來開發(fā)用戶模型界面，都需要確保用戶能夠?qū)缑娴耐庥^做最后的評(píng)判。4 繼承面向?qū)ο蟪绦蛟O(shè)計(jì)中最強(qiáng)大的一個(gè)特性可能是代碼的重用。結(jié)構(gòu)化設(shè)計(jì)在某種程度上提供了代碼重用你可以編寫 一個(gè)過程，然后根據(jù)需要使用多次。然而，面向?qū)ο笤O(shè)計(jì)者更進(jìn)一步，允許通過組織類并且抽取各個(gè)類之間的共性來定義類之間的關(guān)系，這不僅有利于代碼的重用，而

5、且還可以實(shí)現(xiàn)過了更好的整體設(shè)計(jì)。集成是體重這種功能的一個(gè)主要途徑。繼承允許類繼承另一個(gè)類的屬性和方法。這就允許通過抽取共同的屬性和方法來創(chuàng)建全新的類。5 使用對(duì)象持久性對(duì)象持久性也還是許多面向?qū)ο笙到y(tǒng)必須解決的一個(gè)問題。持久性概念是指維護(hù)對(duì)象的狀態(tài)。運(yùn)行程序是，如果沒有以某種方式保存對(duì)象，對(duì)象就會(huì)死亡，永遠(yuǎn)不能恢復(fù)。這些臨時(shí)性對(duì)象在某些應(yīng)用中可能適用，但是在大多數(shù)商業(yè)系統(tǒng)中，必須保存對(duì)象的狀態(tài)以備以后使用?？梢酝ㄟ^將對(duì)象串行化并寫至一個(gè)平面文件來持久保存對(duì)象，這是最簡(jiǎn)單的方法?，F(xiàn)在的最新技術(shù)是基于XML的。盡管從理論上來講，對(duì)象只要沒有被撤銷就能在內(nèi)存中持久保存，但是我們所要強(qiáng)調(diào)的是將持久對(duì)象

6、保存到某種存儲(chǔ)設(shè)備上。可以考慮以下3種主要的存儲(chǔ)設(shè)備。.平面文件系統(tǒng)可以通過串行化對(duì)象來將對(duì)象保存在一個(gè)平面文件中。這種用法很有限。.關(guān)系數(shù)據(jù)庫必須使用某種中間件將對(duì)象轉(zhuǎn)化為關(guān)系模型。.面向?qū)ο髷?shù)據(jù)庫這是保證對(duì)象持久性最合理的方法，但是大多數(shù)公司都已經(jīng)將數(shù)據(jù)存儲(chǔ)在遺留系統(tǒng)中，而且只是剛開始研究對(duì)象數(shù)據(jù)庫。通常，及時(shí)是全新的面向?qū)ο髴?yīng)用也必須與遺留數(shù)據(jù)交互。6 什么是UML？顧名思義，UML是一種建模語言。UML用戶指南將UML定義為“一種用戶可視化表示、指定、構(gòu)造和描述軟件密集系統(tǒng)中部件的圖形化語言”。UML為編寫系統(tǒng)藍(lán)圖提供了一種標(biāo)準(zhǔn)方法。簡(jiǎn)單的說，UML提供了一種以圖形化方式表示和管理面向

7、對(duì)象軟件系統(tǒng)的發(fā)那個(gè)發(fā)。它不僅是系統(tǒng)設(shè)計(jì)的表示，而且是一種有助于完成系統(tǒng)設(shè)計(jì)的工具。7 ASP.NET 概述ASP.NET 是一個(gè)統(tǒng)一的 Web 開發(fā)模型，它包括您使用盡可能少的代碼生成企業(yè)級(jí) Web 應(yīng)用程序所必需的各種服務(wù)。ASP.NET 作為 .NET Framework 的一部分提供。當(dāng)您編寫 ASP.NET 應(yīng)用程序的代碼時(shí)，可以訪問 .NET Framework 中的類。您可以使用與公共語言運(yùn)行庫 (CLR) 兼容的任何語言來編寫應(yīng)用程序的代碼，這些語言包括 Microsoft Visual Basic、C#、JScript .NET 和 J#。使用這些語言，可以開發(fā)利用公共語言運(yùn)

8、行庫、類型安全、繼承等方面的優(yōu)點(diǎn)的 ASP.NET 應(yīng)用程序。8 Web服務(wù)也是一種對(duì)象Web服務(wù)通過使用XML來提供一種與平臺(tái)無關(guān)的數(shù)據(jù)交換方式。而簡(jiǎn)單對(duì)象訪問協(xié)議（SOAP）這是作為一種標(biāo)準(zhǔn)來序列化和傳遞對(duì)象數(shù)據(jù)。ASP.NET致力于讓程序員和XML分離，以便使他們能夠用自己熟知的面向?qū)ο蟮脑O(shè)計(jì)理念來實(shí)現(xiàn)所需的功能。雖然你可以用面向?qū)ο蟮脑O(shè)計(jì)方式來模擬Web服務(wù)的設(shè)計(jì)，但是我們應(yīng)該盡量把Web服務(wù)看成數(shù)據(jù)交換的一個(gè)終端，類似于你調(diào)用本地類的靜態(tài)方法，你也可以在容器類里包裝數(shù)據(jù)。但是你要充分考慮到這種Web服務(wù)設(shè)計(jì)帶來的性能影響，并且這種設(shè)計(jì)的伸縮性也不好。在VS中使用Web服務(wù)僅僅需要給W

9、eb服務(wù)添加應(yīng)用。在一個(gè)Web項(xiàng)目里，Web服務(wù)的應(yīng)用是動(dòng)態(tài)生成的，而在類庫項(xiàng)目里這是創(chuàng)建了一個(gè)物理代理類。在這兩種情況下，你都能對(duì)這些對(duì)象進(jìn)行編程，就好象這些對(duì)象是位于你本地系統(tǒng)一樣，這樣說帶來的好處就是不需要關(guān)注數(shù)據(jù)是怎么與遠(yuǎn)程系統(tǒng)進(jìn)行交換的。9 IIS和WEB應(yīng)用程序的具體細(xì)節(jié)IIS（Internet Information Services）是Windows操作系統(tǒng)的組成部分之一，它服務(wù)與對(duì)Web站點(diǎn)的請(qǐng)求。IIS管理器用樹形結(jié)構(gòu)顯示W(wǎng)eb站點(diǎn)的集群，每個(gè)站點(diǎn)都被設(shè)置成通過IP地址，端口，和一個(gè)主機(jī)頭接受請(qǐng)求。其中主機(jī)頭使得一個(gè)IP地址，根據(jù)不同的域名，能訪問多個(gè)站點(diǎn)。當(dāng)一個(gè)HTTP請(qǐng)

10、求達(dá)到服務(wù)器是，IIS根據(jù)請(qǐng)求的文件的擴(kuò)展名判斷由哪個(gè)應(yīng)用程序來處理請(qǐng)求，如果沒有找到匹配的擴(kuò)展名，被請(qǐng)求的文件將不經(jīng)過任何處理直接發(fā)送給客戶端。IIS首先獲取請(qǐng)求并判斷由哪一個(gè)ISAPI（網(wǎng)絡(luò)服務(wù)應(yīng)用程序接口）程序來處理。以ASP.NET為例，它將請(qǐng)求交由aspnet_isapi.dll處理。ASP.NET把以多個(gè)不同物理文件形式存在的頁面編譯成一個(gè)程序集并緩存起來供其他請(qǐng)求使用。在多種可能的編碼模型中，inline編碼和code-beside是最簡(jiǎn)單也是最實(shí)用的代碼編寫及維護(hù)形式。由發(fā)布程序執(zhí)行的預(yù)編譯可以通過隱藏代碼、預(yù)先檢查錯(cuò)誤和防止在第一次請(qǐng)求是執(zhí)行編譯等方式來緩解部署應(yīng)用程序的壓力

11、。10 測(cè)試、測(cè)試、再測(cè)試以我個(gè)人的觀點(diǎn)來看，測(cè)試在了解需求階段就已經(jīng)考試了。任何開發(fā)人員在Visual Studio里面敲入“Public Class”之前，就必須對(duì)你的軟件所要實(shí)現(xiàn)的功能有一個(gè)非常清晰的認(rèn)識(shí)，這就要求每一個(gè)項(xiàng)目相關(guān)人員（最終用戶、業(yè)務(wù)專家、數(shù)據(jù)庫管理員、硬件人員等）都必須介入到軟件的開發(fā)過程中，這些人員必須參與開發(fā)的整個(gè)過程。把開發(fā)看成一個(gè)漸進(jìn)的過程要比你在項(xiàng)目一開始的時(shí)候就確定你將要交付給客戶的一個(gè)什么樣的產(chǎn)品容易得多。如果使用測(cè)試驅(qū)動(dòng)的開發(fā)方法，在實(shí)際編碼前應(yīng)先寫好相應(yīng)的測(cè)試代碼。一般來說，這些測(cè)試的代碼應(yīng)該盡量以能夠讓需求分析員（也許就是你自己）能讀懂這些代碼并測(cè)試這

12、些代碼實(shí)都能夠滿足預(yù)期的使用目的。 測(cè)試是伴隨整個(gè)開發(fā)過程的，如果一個(gè)或多個(gè)測(cè)試失敗，您將不得不修改自己的代碼來確保測(cè)試順利通過，而絕不是等寫完了所有代碼之后才去測(cè)試。所有代碼接近完工的時(shí)候，你的傳統(tǒng)測(cè)試就可以開始了，這個(gè)時(shí)候你可以讓測(cè)試人員去檢查那些用戶接口部分還有哪些不合理的地方（可以使用類似ACT的自動(dòng)化工具）。因?yàn)樵谡麄€(gè)開發(fā)過程中，你一直在測(cè)試，所以這個(gè)時(shí)候系統(tǒng)底層的業(yè)務(wù)邏輯應(yīng)該已經(jīng)可以很好的工作。從項(xiàng)目的理想到軟件的最終發(fā)布，你的項(xiàng)目的所有相關(guān)人員都必須參與到開發(fā)的整個(gè)過程中一確保你的軟件能夠滿足預(yù)期的使用需求。十一 訪問關(guān)系數(shù)據(jù)庫所有數(shù)據(jù)庫應(yīng)用都有以下結(jié)構(gòu)：.數(shù)據(jù)庫客戶.數(shù)據(jù)庫服務(wù)

13、器.數(shù)據(jù)庫數(shù)據(jù)庫客戶是為系統(tǒng)提供界面的用戶應(yīng)用。通常這是一個(gè)GUI應(yīng)用，允許用戶查詢和更新數(shù)據(jù)庫。SQLSQL是指結(jié)構(gòu)化查詢語言（Structured Query Language）。只是數(shù)據(jù)庫客戶與實(shí)現(xiàn)了這個(gè)標(biāo)準(zhǔn)的不同廠商的數(shù)據(jù)庫系統(tǒng)哦你之間進(jìn)行通信所采用的一種標(biāo)準(zhǔn)方法。數(shù)據(jù)庫客戶要通過SQL語句與數(shù)據(jù)庫服務(wù)器進(jìn)行通信。圖12-5顯示了數(shù)據(jù)庫客戶/服務(wù)器模型的一般解決方案。用戶數(shù)據(jù)庫客戶數(shù)據(jù)庫服務(wù)器數(shù)據(jù)庫SQL驅(qū)動(dòng)程序附件2：外文原文1 Designing with ObjectsGenerally, a solid OO design process will generally incl

14、ude the following steps:1. Doing the proper analysis2. Developing a statement of work that describes the system3. Gathering the requirements from this statement of work4. Developing a prototype for the user interface5. Identifying the classes6. Determining the responsibilities of each class7. Determ

15、ining how the various classes interact with each other8. Creating a high-level model that describes the system to be builtThe system, or object model, is made up of class diagrams and class interactions.This model should represent the system faithfully and be easy to understand and modify.2 What Exa

16、ctly Is a Class?In short, a class is a blueprint for an object.When you instantiate an object, you use a class as the basis for how the object is built. In fact, trying to explain classes and objects is really a chicken-and-egg dilemma. It is difficult to describe a class without using the term obje

17、ct and visa versa. For example, a specific individual bike is an object. However, someone had to have created the blueprints (that is, the class) to build the bike. In OO software, unlike the chicken-and-egg dilemma,we do know what comes firstthe class.An object cannot be instantiated without a clas

18、s.To explain classes and methods, its helpful to use an example from the relational database world. In a database table, the definition of the table itself (fields, description, and data types used) would be a class (metadata), and the objects would be the rows of the table (data).3 Prototyping the

19、User InterfaceAs our final step in the OO design process,we must create a prototype of our user interface.This prototype will provide invaluable information to help navigate through the iterations of the design process.As Gilbert and McCarty in Object-Oriented Design in Java aptly point out,“to a sy

20、stem user, the user interface is the system.”There are several ways to create a user interface prototype.You can sketch the user interface by simply drawing it on paper or a whiteboard.You can use a special prototyping tool or even a language environment like Visual Basic, which is often used for ra

21、pid prototyping. Or you can use the IDE from your favorite development tool to create the prototype.However you develop the user interface prototype, make sure that the users have the final say on the look and feel.4 InheritanceOne of the most powerful features of OO programming is, perhaps, code re

22、use. Structured design provides code reuse to a certain extentyou can write a procedure and then use it as many times as you want. However, OO design goes an important step further, allowing you to define relationships between classes that facilitate not only code reuse, but also better overall desi

23、gn, by organizing classes and factoring in commonalties of various classes. Inheritance is a primary means of providing this functionality. Inheritance allows a class to inherit the attributes and methods of another class.This allows creation of brand new classes by abstracting out common attributes

24、 and behaviors.One of the major design issues in OO programming is to factor out commonality of the various classes.5 Using Object PersistenceObject persistence is another issue that must be addressed in many OO systems. Persistence is the concept of maintaining the state of an object.When you run a

25、 program, if you dont save the object in some manner, the object simply dies, never to be recovered.These transient objects might work in some applications, but in most business systems, the state of the object must be saved for later use.In its simplest form, an object can persist by being serializ

26、ed and written to a flat file.The state-of-the-art technology is now XML-based.Although it is true that an object theoretically can persist in memory as long as it is not destroyed,we will concentrate on storing persistent objects on some sort of storage device.There are three primary storage device

27、s to consider:. Flat file systemYou can store an object in a flat file by serializing the object.This has very limited use. Relational databaseSome sort of middleware is necessary to convert an object to a relational model.OO databaseThis is the logical way to make objects persistent, but most compa

28、nies have all their data in legacy systems and are just starting to explore object databases. Even brand-new OO applications must usually interface with legacy data.6 What Is UML?UML, as its name implies, is a modeling language.The UML User Guide defines UML as “a graphical language for visualizing,

29、 specifying, constructing and documenting the artifacts of a software-intensive system.”UML gives you a standard way to write the systems blueprints. In a nutshell,UML offers a way to graphically represent and manipulate an object-oriented (OO) software system. It is not only the representation of t

30、he design of a system, but a tool to assist in this design.7 ASP.NET OverviewASP.NET is a unified Web development model that includes the services necessary for you to build enterprise-class Web applications with a minimum of coding. ASP.NET is part of the .NET Framework, and when coding ASP.NET app

31、lications you have access to classes in the .NET Framework. You can code your applications in any language compatible with the common language runtime (CLR), including Microsoft Visual Basic, C#, JScript .NET, and J#. These languages enable you to develop ASP.NET applications that benefit from

32、the common language runtime, type safety, inheritance, and so on.8 Web Services as ObjectsWeb services provide a platform-neutral means of exchanging data between two systems over the Web using XML. Simple Object Access Protocol (SOAP) is a standard used to serialize and transfer object data between

33、 these systems. ASP.NET goes a long way to isolate programmers from the actual XML and allows them to concentrate on the implementation in the familiar realm of object-oriented code.Although it's possible to simulate full object orientation in the design of Web services, consideration should be

34、given to make them act as endpoints for the exchange of data, similarly to the way you'd call a static method from a local class. You can also package data in container classes. It's important to consider the performance implications of a Web service that needs to make many calls back and fo

35、rth to arrive at an end result, as this kind of solution would not scale well.Consuming a Web service from Visual Studio 2005 requires little more than adding a reference to the Web service. In a Web project, this reference is created dynamically, while a class library creates a physical proxy class

36、. In both scenarios, you can code against these objects as if they were locally in your own system, releasing you from the details of how the data is exchanged with the remote system.9 The Nuts and Bolts of IIS and Web ApplicationsInternet Information Services is the part of the Windows operating sy

37、stem that services requests to your Web site. The IIS Manager shows a tree of sites grouped under the Web Sites group. Each site is set to take requests by IP address, port (normally port 80), and a host header value, which allows one IP to be used for several sites.When an HTTP request arrives at t

38、he machine, IIS determines which application will handle the request based on the file extension of the request. If no matching extension is found, the requested file is served straight, the file is served without any processing. These applications that handle the various file types are known as ISA

39、PI applications (Internet Server Application Program Interface).IIS first gets the request and figures out which ISAPI program will process the page. In the case of ASP.NET, it makes its way to aspnet_isapi.dll and is processed.ASP.NET compiles pages in one of several different physical file schemes

40、 and caches that code for execution in other requests. Of the different schemes possible, inline code and code-beside are the easiest and most practical means of writing and maintaining code.The pre-compilation performed by the publishing utility can ease deployment by hiding your code, checking for

41、 errors, and avoiding the first-run compilation process on the first request.10 Test, Test, and Retest with All StakeholdersIn my frequently less-than-humble opinion, testing actually begins with the development of specifications and requirements. Before any developer types "public class"

42、in Visual Studio, an extensive discovery process must take place to flesh out exactly what your application is supposed to do. This requires involvement from every stakeholder in the process. End-users, subject matter experts (generally the "business people"), DBAs, hardware peopleeveryone

43、. What's more, these people should stay involved throughout the entire process. It's easier to view development as an evolutionary process than getting a sign-off at the start of the project and delivering what you think they wanted.Using test-driven development (TDD) principles (more on tha

44、t in a moment), you'll write tests before the actual code. These tests are frequently simple enough that requirements analysts (yeah, that might be the same person as you) can read the code to understand what's going on and determine whether they match the stated goals or use cases of the ap