計算機專業(yè)畢業(yè)論文外文翻譯--數據類型和值域

1、<p><b>　　附錄1</b></p><p><b>　　外文翻譯</b></p><p><b>　　數據類型和值域</b></p><p>　　任何一個曾經編過程的人都習慣了這樣一個事實：你不得不告訴計算機信息是一個整數，實數，字符串，布爾值或其它的值。大多數計算機由一個整數加法電

2、路，又有一個實數加法電路，而且，通常字符串相加當然沒有任何意義。因為在內存中的比特資料可以被解釋成任何一種形式，計算機必須被告訴去做什么。這就是我們熟知的類型。定義資料對象為一個特定的類型對事物內部代表的定義有影響。舉例來說，在大多數現代計算機框架內部整數表示為32位比特數的形式。在外部，整數表現為從0到9的數字符串的形式，可能帶有負號。當一個資料對象被定義為整數類型時，所有標準的算術和邏輯運算都要做合適的解釋。在定義一個數據類型為整形

3、時，定義它的整理系統(tǒng)的事件也同樣如此（可能不是如此明顯）。那就是說，要定義相對復雜的操作，如排序，是如何進行的。內部表示和外部表示的轉換算法也是必須的。</p><p><b>　　關鍵詞</b></p><p>　　所有的屬性都描述實體的某一方面。一些屬性扮演附加的角色：從所有其它同一類型的實體事例中區(qū)分某一特定實例。舉個例子，如果我們注意不用一個雇員后標記一個以上

4、的雇員，我們可知一個雇員的雇員號足以固定雇員的其它屬性值。能確保每個實體都有唯一值的屬性叫做關鍵詞。</p><p>　　有時可能不只一個屬性唯一的確定每個實體。舉個例子，如果人事紀錄包含社會安全號（而且認為足以控制社會安全號的重復），那幺雇員號和社會安全號都可作為確定雇員的關鍵詞。關鍵詞在計算機系統(tǒng)中管理資料的所有物理有效方法中是最基本的。當有多余一個的可用關鍵詞時，可供選者的為候選關鍵詞。通常，我們選出一個作

5、為主關鍵詞，并決定紀錄的位置。其它便于檢索的候選關鍵詞被稱為副關鍵詞。</p><p><b>　　數據庫模式</b></p><p>　　用于描述存儲數據庫中的數據和明確記載數據中的數據包括什么元素，即這些元素通過怎樣的訪問路徑被訪問。它也包含了安全設置出完整限制之外，與概念模式由幾分相似。但對數據的描述將更加真實，一些真實反映由數據庫中的數據所描述，筆記上，并不能

6、明確記載數據庫中的數據是如何被存儲及訪問路徑如何被提供。（理想的它是不會參考文件、記錄、設置或其他同類的東西）它是，因此獨立描述及為這結論作為邏輯模式作為參考。</p><p>　　最終用戶或最終用戶組對數據庫中的某部分模式特別感興趣被稱為數據庫代替-模式，理想的，代替-模式將利用字符明確記載數據存放位置與最適合的位置，數據庫代替-模式有以下幾種功能：（1）它們能利用應用程序，使它們所感興趣的內容被訪問的路徑可

7、見。（2）同樣的，它們可以在最終用戶的使用報告程序發(fā)電機和使用一種查詢語言等等被體現。（3）它們能被用于劃分數據單位為按去勸秘密的說明書。例如，代替模式中規(guī)定，每類級別上的用戶可進行那些操作，并僅僅指定少數用戶有修改更新的權利。</p><p><b>　　物理模式</b></p><p>　　物理模式是以物理的結構描述數據庫，如果，例如傳統(tǒng)的編入索引的-順序的文件存

8、于數據庫中，它將在物理模式中進行說明。它將包含詳細的有按可查格式、塊因素等等物理的模式，這部分構造作為設計所必須的部分進行處理。它也可使用作為完整的部分，它進行操作的部分在以后進行說明。物理的模式有時成內部模式。</p><p><b>　　物理的存儲結構</b></p><p>　　數據庫中的結構以被事先在物理結構中定義了存儲結構，它包含幾個典型組件：盤文件，幫起文

9、件，組存儲文件，索引文件及程序操縱等。</p><p><b>　　支援和恢復系統(tǒng)</b></p><p>　　支援和恢復系統(tǒng)是指在軟件和硬件發(fā)生故障時重建數據庫系統(tǒng)。</p><p><b>　　理解應用任務</b></p><p>　　在建造軟件方面經常忽略的步驟之一就是真正理解終端用戶的任務－

10、計算機自動化準備去支持的任務。</p><p>　　偶爾，這是由于應用本身是專門的；更經常，它是由于傾向于面向數據的設計方法。經常地，這些是在分析中主要的問題：</p><p>　　■什么數據應該被獲取？</p><p>　　■數據怎樣被處理？</p><p>　　■數據怎樣被匯報？</p><p>　　這些問題

11、擴展成一系列子問題，并且包括諸如輸入報表，代碼，屏幕布局，計算，存儲容量，處理循環(huán)，報表格式化，分布和維護。這些是所有極其重要的部分。然而一個困難是，他們都單獨集中于數據。</p><p>　　人們使用數據，但他們做任務。一個可能的爭論是這或許是專業(yè)的工作人員，有權利的人員僅僅將數據從輸入報表轉移到鍵盤；他們的任務是非常面向數據的。這是今天這些工作的一個清楚地描繪。但這是一個真正要去做的工作的結果，還是計算機應用

12、設計的征兆？使用人類作為輸入設備，特別是大容量的，格式一致的（如報表），并在一個有限可變形范圍內的數據，是昂貴和廢棄的，更別說失去人性，獲取數據的方法。</p><p>　　這或許聽起來像哲學，但它實際上以應用設計方式輸入。人們使用數據，并且他們不通過一次完成來做任務。他們互相做好幾項任務的子集或交集，并且他們并行第一次做完。</p><p>　　設計者允許此觀念指導一項應用的分析和創(chuàng)造，

13、而不是集中于很多年獨領風騷的面向數據，就是這種努力的本性有了驚人的改變。為什么Windowsing環(huán)境如此成功？因為他們允許用戶在小的任務間迅速切換，使它們都存在而不必關閉并退出一個來開始另一個。Windowing環(huán)境更近地映象人們真正的思維和工作方式而不是老一套的“一次做一件事”的方法。這一課不應被丟掉，他應被建立。</p><p>　　理解應用任務意味著遠遠高于識別數據元素，使之標準化，創(chuàng)建屏幕，處理數據，并

14、且匯報。他意味著真正理解用戶做什么并且他們的任務是什么，并設計響應這些任務的應用，不光是獲取他們關聯(lián)的數據。事實上，當面向與數據時，結果設計會不可避免地歪曲用戶的任務而不是支持他們。</p><p>　　你怎樣設計一個應用與任務而不是數據？最大的障礙是簡單理解集中于必要的任務。這允許你從一個新鮮的角度接近事物的分析。</p><p><b>　　附錄2</b><

15、/p><p><b>　　外文原文</b></p><p>　　DATA TYPES AND VALUE SETS</p><p>　　Anyone who has ever programmed a computer is accustomed to the fact that you usually have to tell the compu

16、ter whether the information stored in a particular location is an integer, a real number, a character string, a Boolean va1ue, or whatever. Most computers have one electronic circuit for adding two integers and another f

17、or adding two real numbers, and, of course, addition does not make any sense at all, in general, for character strings. Because the pattern of bits in at storage location ca</p><p><b>　　KEYS</b>&

18、lt;/p><p>　　All attributes describe some aspect of an entity. Some attributes perform the additional role of distinguishing one particular entity occurrence from all others of the same type. For example, if car

19、e is taken not to assign any employee number to more than one person, then knowing an individual's employee number should be sufficient to locate all of the other attribute values for that individual. An attribut

20、e that can be guaranteed to have a unique value for each entity is called a key.Someti</p><p>　　DATABASE SCHEMA</p><p>　　This is a description of the data which is stored in the database and spe

21、cifies what data elements are store and what access paths are provided between these elements. The database schema also contains specifications of privacy as well as integrity constraints. It is somewhat similar to the c

22、onceptual schema, but is a description of data rather than of reality. Some aspects of reality which are described by data in the database schema. Note, however, that the database schema does not specify how</p>&

23、lt;p>　　That part of the database schema which is of interest to a particular end-user or group of end –users is called a database sub-schema. Ideally, a sub-schema should be specified using a notation which is most ap

24、propriate for the use to which it is being put. Database sub-schemas have several use : (ⅰ) they can be referred to by application programmers to see what access paths are available in that part of the database in which

25、they are interested, (ⅱ) similarly, they can be referred to by the end</p><p>　　PHYSICAL SCHEMA</p><p>　　The physical schema is a description of the physical structure of the database. If, for e

26、xample, conventional indexed-sequential files are used to store the database, then this will be stated in the physical schema. It will also contain details of record formats, blocking factors etc. The physical schema is

27、constructed as an essential part of the design process. However, it may also be used as an integeral part of he operational database system as discussed below. The physical schema is sometime</p><p>　　PHYSIC

28、AL STORAGE STRUCTURE</p><p>　　The structure in which the database actually resides is termed the physical storage structure. It typically consists of disc files, tapes, mainstore, indices and programs to man

29、ipulate these components.</p><p>　　BACK-UP AND RECOVERY SYSTEM</p><p>　　The back-up and recovery system is the module which rebuilds the database after corruption due to hardware or software fai

30、lure.</p><p>　　Understanding the Application Tasks</p><p>　　One of the often-neglected steps on building software is really understanding the end user’s job-the that computer automation is inten

31、ded to support.</p><p>　　Occasionally, this is because the application itself is quite specialized; more often, it is because the approach to design tends to be data-oriented. Frequently, these are the major

32、 question asked in the analysis:</p><p>　　■What data should be captured?</p><p>　　■How should the data be processed?</p><p>　　■How should the data be reported?</p><p&g

33、t;　　These question expand into a series of sub question ,and include issues such as input forms, Codes, screen layouts, computations, postings, corrections, audit trails, retention, storage volumes, processing cycles, re

34、port formatting, distribution, and maintenance. there are all vitally important areas. One difficulty, however, is that they all focus solely on data. </p><p>　　People use data, but they do tasks. One

35、 might argue that while this may be true of professional workers. Key-entry clerks really only transfer data from an input form to a keyboard; their tasks are very data-oriented. This is a fair portrayal of their jobs to

36、day, but is this a consequence of the real job that need to get done, or is it a symptom of the computer application? Using humans as input devices, particularly for data that is voluminous, consistent in format (as on f

37、orms), and in a limit</p><p>　　This may sound like so much philosophy, but it has practical import in the way application design is done. People use data, but they do tasks. And they don’t do tasks through o

38、 completion one at a time. They do several tasks that are subset of or in intersection with each other, and they so them all at once, in parallel.</p><p>　　When designers allow this idea to direct the analys

39、is and creation of an Application, rather than focusing on the data orientation that has been historically dominant, the very nature of the effort changes significantly. Why have windowing environments been so successful

40、? Because they allow a user to shut down and exit one in order to begin another. The windowing environment comes closer to mapping the way people really think and work than the old “one thing at a time “approach ever did

41、. This le</p><p>　　Understanding the application tasks means going far beyond identifying the data elements, normalizing them, and creating screens, processing programs, and reports. It means really understa

42、nding what the users do and what their tasks are, and designing the application to be responsive to those tasks, not just to capture the data, associated with them. In fact, when the orientation is toward the data, the r

43、esulting design will inevitably distort the user’s tasks rather than support them.</p><p>　　How do you design an application that is responsive to tasks rather than data? The biggest hurdle is simply underst