計(jì)算機(jī)外文翻譯--- 數(shù)據(jù)庫(kù)開(kāi)發(fā)過(guò)程

1、<p>　　畢業(yè)設(shè)計(jì)(論文)外文資料翻譯</p><p>　　系　　部： 計(jì)算機(jī)科學(xué)與技術(shù) </p><p>　　專(zhuān) 業(yè)： 計(jì)算機(jī)科學(xué)與技術(shù) </p><p>　　姓 名： </p><p>　　學(xué) 號(hào)：

2、 </p><p>　　外文出處： http://www.18lw.com/lwzl_inf- </p><p>　　o.asp?ztId=467&page=1 </p><p>　　附 件： 1.外文資料翻譯譯文；2.外文原文。 </p><p>　　注：請(qǐng)將該封面與附件裝訂

3、成冊(cè)。</p><p>　　附件1：外文資料翻譯譯文</p><p><b>　　數(shù)據(jù)庫(kù)開(kāi)發(fā)過(guò)程</b></p><p>　　基于信息工程的信息系統(tǒng)規(guī)劃是數(shù)據(jù)庫(kù)開(kāi)發(fā)項(xiàng)目的一個(gè)來(lái)源。這些開(kāi)發(fā)新數(shù)據(jù)庫(kù)的項(xiàng)目通常是為了滿足組織的戰(zhàn)略需求，例如改善客戶支持、提高產(chǎn)品和庫(kù)存管理或進(jìn)行更精確的銷(xiāo)售預(yù)測(cè)。然而許多數(shù)據(jù)庫(kù)開(kāi)發(fā)項(xiàng)目更多的是以自底向上的方式出現(xiàn)的，

4、例如信息系統(tǒng)的用戶需要特定的信息來(lái)完成他們的工作，從而請(qǐng)求開(kāi)始一個(gè)項(xiàng)目，又如其他信息系統(tǒng)的專(zhuān)家發(fā)現(xiàn)組織需要改進(jìn)數(shù)據(jù)管理而開(kāi)始新的項(xiàng)目。即使在自底向上的情況下，建立企業(yè)數(shù)據(jù)模型也是必須的，以便理解現(xiàn)有的數(shù)據(jù)庫(kù)是否可以提供所需的數(shù)據(jù)，否則，新的數(shù)據(jù)庫(kù)、數(shù)據(jù)實(shí)體和屬性都應(yīng)該加到當(dāng)前的組織數(shù)據(jù)資源中去。</p><p>　　無(wú)論是戰(zhàn)略需求還是操作信息的需求，每個(gè)數(shù)據(jù)庫(kù)開(kāi)發(fā)項(xiàng)目通常集中在一個(gè)數(shù)據(jù)庫(kù)上。一些數(shù)據(jù)庫(kù)項(xiàng)目?jī)H僅集中

5、在定義、設(shè)計(jì)和實(shí)現(xiàn)一個(gè)數(shù)據(jù)庫(kù)，以作為后續(xù)信息系統(tǒng)開(kāi)發(fā)的基礎(chǔ)。然而在大多數(shù)情況下，數(shù)據(jù)庫(kù)及其相關(guān)信息處理功能是作為一個(gè)完整的信息系統(tǒng)開(kāi)發(fā)項(xiàng)目的一部分而被開(kāi)發(fā)的。</p><p>　　2.1 系統(tǒng)開(kāi)發(fā)生命周期</p><p>　　指導(dǎo)管理信息系統(tǒng)開(kāi)發(fā)項(xiàng)目的傳統(tǒng)過(guò)程是系統(tǒng)開(kāi)發(fā)生命周期(SDLC)。系統(tǒng)開(kāi)發(fā)生命周期是指一個(gè)組織中由數(shù)據(jù)庫(kù)設(shè)計(jì)人員和程序員組成的信息系統(tǒng)專(zhuān)家小組詳細(xì)說(shuō)明、開(kāi)發(fā)、維護(hù)和替

6、換信息系統(tǒng)的全部步驟。這個(gè)過(guò)程比作瀑布是因?yàn)槊恳徊蕉剂鞯较噜彽南乱徊剑葱畔⑾到y(tǒng)的規(guī)格說(shuō)明是一塊一塊地開(kāi)發(fā)出來(lái)的，每一塊的輸出是下一塊的輸入。然而如圖所示，這些步驟并不是純線性的，每個(gè)步驟在時(shí)間上有所重疊（因此可以并行地管理步驟），而且當(dāng)需要重新考慮先前的決策時(shí)，還可以回滾到前面某些步驟。（因而水可以在瀑布中倒流?。┫到y(tǒng)開(kāi)發(fā)生命周期的每一階段都包括與數(shù)據(jù)庫(kù)開(kāi)發(fā)相關(guān)的活動(dòng)，所以，數(shù)據(jù)庫(kù)管理的問(wèn)題遍布整個(gè)系統(tǒng)開(kāi)發(fā)過(guò)程。請(qǐng)注意，系統(tǒng)開(kāi)發(fā)生命周

7、期的階段和數(shù)據(jù)庫(kù)開(kāi)發(fā)步驟之間不存在一一對(duì)應(yīng)的關(guān)系，概念數(shù)據(jù)建模發(fā)生在兩個(gè)系統(tǒng)開(kāi)發(fā)生命周期階段之間。</p><p><b>　　企業(yè)建模 </b></p><p>　　數(shù)據(jù)庫(kù)開(kāi)發(fā)過(guò)程從企業(yè)建模（系統(tǒng)開(kāi)發(fā)生命周期中項(xiàng)目論證和選擇階段的一部分）開(kāi)始，設(shè)定組織數(shù)據(jù)庫(kù)的范圍和一般內(nèi)容。企業(yè)建模發(fā)生在信息系統(tǒng)規(guī)劃和其他活動(dòng)期間，這些活動(dòng)確定信息系統(tǒng)的哪個(gè)部分需要改變和加強(qiáng)并概述

8、出全部組織數(shù)據(jù)的范圍。在這一步中，檢查當(dāng)前數(shù)據(jù)庫(kù)和信息系統(tǒng)，分析作為開(kāi)發(fā)項(xiàng)目主體的業(yè)務(wù)領(lǐng)域的本質(zhì)，用非常一般的術(shù)語(yǔ)描述每個(gè)信息系統(tǒng)在開(kāi)發(fā)時(shí)所需要的數(shù)據(jù)。每個(gè)項(xiàng)目只有當(dāng)它達(dá)到組織的預(yù)期目標(biāo)時(shí)才可以進(jìn)行下一步。</p><p><b>　　概念數(shù)據(jù)建模 </b></p><p>　　對(duì)一個(gè)已經(jīng)開(kāi)始的信息系統(tǒng)項(xiàng)目而言，概念數(shù)據(jù)建模階段分析信息系統(tǒng)的全部數(shù)據(jù)需求。它分為兩個(gè)階

9、段。首先，它在項(xiàng)目開(kāi)始和規(guī)劃階段建立一張圖。同時(shí)建立其他文檔來(lái)概述不考慮現(xiàn)存數(shù)據(jù)庫(kù)的情況下特定開(kāi)發(fā)項(xiàng)目中所需的數(shù)據(jù)范圍。此時(shí)僅僅包括高層類(lèi)別的數(shù)據(jù)（實(shí)體）和主要聯(lián)系。然后在系統(tǒng)開(kāi)發(fā)生命周期的分析階段產(chǎn)生確定信息系統(tǒng)必須管理的全部組織數(shù)據(jù)的詳細(xì)數(shù)據(jù)模型，定義所有數(shù)據(jù)屬性，列出全部數(shù)據(jù)類(lèi)別，表示數(shù)據(jù)實(shí)體間所有的業(yè)務(wù)聯(lián)系，確定描述數(shù)據(jù)完整性的全部規(guī)則。在分析階段，還要檢查概念數(shù)據(jù)模型（在后面也稱(chēng)作概念模式）與用來(lái)解釋目標(biāo)信息系統(tǒng)其他方面的模型

10、類(lèi)別的一致性，例如處理步驟、處理數(shù)據(jù)的規(guī)則以及時(shí)間的時(shí)序。然而，即使是這樣詳細(xì)的概念數(shù)據(jù)模型也只是初步的，因?yàn)楹罄m(xù)的信息系統(tǒng)生命周期中的活動(dòng)在設(shè)計(jì)事務(wù)、報(bào)表、顯示和查詢時(shí)可能會(huì)發(fā)現(xiàn)遺漏的元素或錯(cuò)誤。因此，經(jīng)常說(shuō)到的概念數(shù)據(jù)建模是以一種自頂向下的方式完成的，它由業(yè)務(wù)領(lǐng)域的一般理解所驅(qū)動(dòng)，而不是由特定的信息處理活動(dòng)所驅(qū)動(dòng)。</p><p><b>　　3.邏輯數(shù)據(jù)庫(kù)設(shè)計(jì)</b></p>

11、;<p>　　邏輯數(shù)據(jù)庫(kù)設(shè)計(jì)從兩個(gè)角度進(jìn)行數(shù)據(jù)庫(kù)開(kāi)發(fā)。首先，將概念數(shù)據(jù)模型變換成基于關(guān)系數(shù)據(jù)庫(kù)理論的標(biāo)準(zhǔn)表示方法——關(guān)系。然后像設(shè)計(jì)信息系統(tǒng)的每個(gè)計(jì)算機(jī)程序（包括程序的輸入和輸出格式）那樣，對(duì)數(shù)據(jù)庫(kù)支持的事務(wù)、報(bào)表、顯示和查詢進(jìn)行詳細(xì)的檢查。在這個(gè)所謂的自底向上的分析中，精確地驗(yàn)證數(shù)據(jù)庫(kù)中需要維護(hù)的數(shù)據(jù)和在每個(gè)事務(wù)、報(bào)表等等中需要的那些數(shù)據(jù)的性質(zhì)。</p><p>　　對(duì)于每個(gè)單獨(dú)的報(bào)表、事務(wù)等等的

12、分析都要考慮一個(gè)特定的、有限制的但是完全的數(shù)據(jù)庫(kù)視圖。當(dāng)報(bào)表、事務(wù)等被分析時(shí)有可能根據(jù)需要而改變概念數(shù)據(jù)模型。尤其在大型的項(xiàng)目中，不同的分析人員和系統(tǒng)開(kāi)發(fā)者的團(tuán)隊(duì)可以獨(dú)立地工作在不同的程序或程序集中，他們所有工作的細(xì)節(jié)直到邏輯設(shè)計(jì)階段才可能會(huì)顯示出來(lái)。在這種情況下，邏輯數(shù)據(jù)庫(kù)設(shè)計(jì)階段必須將原始的概念數(shù)據(jù)模型和這些獨(dú)立的用戶視圖合并或集成到一個(gè)全面的設(shè)計(jì)中。在進(jìn)行邏輯信息系統(tǒng)設(shè)計(jì)時(shí)也可以確定額外的信息處理需求，此時(shí)這些新的需求必須集成到前

13、面確定的邏輯數(shù)據(jù)庫(kù)設(shè)計(jì)中。</p><p>　　邏輯數(shù)據(jù)庫(kù)設(shè)計(jì)的最后一步是根據(jù)為生成結(jié)構(gòu)良好的數(shù)據(jù)規(guī)格說(shuō)明而確定的規(guī)則，將組合的、協(xié)商后的數(shù)據(jù)規(guī)格說(shuō)明轉(zhuǎn)換成基本的或原子的元素。對(duì)當(dāng)今的大部分?jǐn)?shù)據(jù)庫(kù)而言，這些規(guī)則來(lái)自關(guān)系數(shù)據(jù)庫(kù)理論和稱(chēng)作規(guī)范化的過(guò)程。這一步的結(jié)果是產(chǎn)生管理這些數(shù)據(jù)的、不引用任何數(shù)據(jù)庫(kù)管理系統(tǒng)的完整的數(shù)據(jù)庫(kù)描述圖。在完成邏輯數(shù)據(jù)庫(kù)設(shè)計(jì)后，開(kāi)始確定詳細(xì)的計(jì)算機(jī)程序的邏輯和維護(hù)、報(bào)告數(shù)據(jù)庫(kù)內(nèi)容所需的查詢。

14、</p><p>　　4.物理數(shù)據(jù)庫(kù)設(shè)計(jì)和定義</p><p>　　物理數(shù)據(jù)庫(kù)設(shè)計(jì)和定義階段決定計(jì)算機(jī)存儲(chǔ)器（通常是磁盤(pán)）中數(shù)據(jù)庫(kù)的組織，定義數(shù)據(jù)庫(kù)管理系統(tǒng)的物理結(jié)構(gòu)，概述處理事務(wù)的程序，產(chǎn)生期望的管理信息和決策支持的報(bào)表。本階段的目標(biāo)是設(shè)計(jì)能夠有效、安全地管理所有數(shù)據(jù)處理的數(shù)據(jù)庫(kù)，因此物理數(shù)據(jù)庫(kù)設(shè)計(jì)需緊密結(jié)合物理信息系統(tǒng)其他方面的設(shè)計(jì)，包括程序、計(jì)算機(jī)硬件、操作系統(tǒng)和數(shù)據(jù)通信網(wǎng)絡(luò)。<

15、;/p><p><b>　　5.數(shù)據(jù)庫(kù)實(shí)現(xiàn)</b></p><p>　　數(shù)據(jù)庫(kù)實(shí)現(xiàn)階段編寫(xiě)、測(cè)試和安裝處理數(shù)據(jù)庫(kù)的程序。設(shè)計(jì)人員可以使用標(biāo)準(zhǔn)的編程語(yǔ)言（如COBOL、C或Visual Basic）、專(zhuān)用的數(shù)據(jù)庫(kù)處理語(yǔ)言（如SQL），或?qū)Ｓ玫姆沁^(guò)程化語(yǔ)言來(lái)編程，以產(chǎn)生固定格式的報(bào)表、顯示結(jié)果，可能還包括圖表。在實(shí)現(xiàn)階段，還要完成所有的數(shù)據(jù)庫(kù)文檔，培訓(xùn)用戶，為信息系統(tǒng)（和數(shù)據(jù)

16、庫(kù)）的用戶安裝程序。最后一步是利用現(xiàn)存的信息源（遺留應(yīng)用中的文件和數(shù)據(jù)庫(kù)以及現(xiàn)在需要的新數(shù)據(jù)）加載數(shù)據(jù)。加載數(shù)據(jù)的第一步經(jīng)常是將數(shù)據(jù)從現(xiàn)存的文件和數(shù)據(jù)庫(kù)中轉(zhuǎn)到一種中間的格式（如二進(jìn)制或文本文件），然后再將這些中間數(shù)據(jù)加載到新的數(shù)據(jù)庫(kù)中。最后，運(yùn)行數(shù)據(jù)庫(kù)以及相關(guān)的應(yīng)用以供實(shí)際的用戶維護(hù)和檢索數(shù)據(jù)。在運(yùn)轉(zhuǎn)期間，定期備份數(shù)據(jù)庫(kù)，并當(dāng)數(shù)據(jù)庫(kù)損壞或受到影響時(shí)恢復(fù)數(shù)據(jù)庫(kù)。</p><p><b>　　6.數(shù)據(jù)庫(kù)維護(hù)

17、</b></p><p>　　數(shù)據(jù)庫(kù)在數(shù)據(jù)庫(kù)維護(hù)期間逐漸發(fā)展。在這一步，為了滿足變化的業(yè)務(wù)條件，為了改正數(shù)據(jù)庫(kù)設(shè)計(jì)的錯(cuò)誤，或數(shù)據(jù)庫(kù)應(yīng)用的處理速度而增加、刪除或改變數(shù)據(jù)庫(kù)的結(jié)構(gòu)特征。當(dāng)一個(gè)程序或計(jì)算機(jī)發(fā)生故障而使數(shù)據(jù)庫(kù)受到影響或損壞時(shí)也可能應(yīng)該重建數(shù)據(jù)庫(kù)。這一步通常是數(shù)據(jù)庫(kù)開(kāi)發(fā)過(guò)程中最長(zhǎng)的一步，因?yàn)樗掷m(xù)數(shù)據(jù)庫(kù)及相關(guān)應(yīng)用的整個(gè)生命周期，每次數(shù)據(jù)庫(kù)的發(fā)展都可看作一個(gè)簡(jiǎn)略的數(shù)據(jù)庫(kù)開(kāi)發(fā)過(guò)程，其中會(huì)出現(xiàn)概念數(shù)據(jù)

18、建模、邏輯和物理數(shù)據(jù)庫(kù)設(shè)計(jì)以及數(shù)據(jù)庫(kù)實(shí)現(xiàn)以處理提出的變化。</p><p>　　2.2 信息系統(tǒng)開(kāi)發(fā)的其他方法</p><p>　　系統(tǒng)開(kāi)發(fā)生命周期法或其稍作變化的變體經(jīng)常用于指導(dǎo)信息系統(tǒng)和數(shù)據(jù)庫(kù)的開(kāi)發(fā)。信息系統(tǒng)生命周期是一種方法學(xué)，它是高度結(jié)構(gòu)化的方法，它包括許多檢查和權(quán)衡以確保每一步產(chǎn)生精確的結(jié)果，而且新的或替代的信息系統(tǒng)與它必須通信的或數(shù)據(jù)定義需要一致的現(xiàn)存系統(tǒng)保持一致。系統(tǒng)開(kāi)發(fā)生命

19、周期法經(jīng)常由于產(chǎn)生一個(gè)工作系統(tǒng)需要很長(zhǎng)的時(shí)間而受到批評(píng)，因?yàn)楣ぷ飨到y(tǒng)僅僅在整個(gè)過(guò)程結(jié)束時(shí)才產(chǎn)生?，F(xiàn)在組織越來(lái)越多的使用快速應(yīng)用開(kāi)發(fā)法，它是一個(gè)包含分析、設(shè)計(jì)和實(shí)現(xiàn)步驟的快速重復(fù)的迭代過(guò)程，直到匯聚到用戶所需的系統(tǒng)為止?？焖賾?yīng)用開(kāi)發(fā)法在所需的數(shù)據(jù)庫(kù)已經(jīng)存在、增強(qiáng)系統(tǒng)主要是為了檢索數(shù)據(jù)的應(yīng)用中適用，而不適用于那些生成和修改數(shù)據(jù)庫(kù)的應(yīng)用。</p><p>　　使用最廣泛的快速應(yīng)用開(kāi)發(fā)法之一是原型法。原型法是一個(gè)系統(tǒng)開(kāi)發(fā)

20、的迭代過(guò)程，通過(guò)分析員和用戶的緊密配合，持續(xù)地修改系統(tǒng)而最終將所有需求轉(zhuǎn)換成一個(gè)工作系統(tǒng)。在此圖中我們包含了注釋?zhuān)怕缘孛枋隽嗣總€(gè)原型法階段的數(shù)據(jù)庫(kù)開(kāi)發(fā)活動(dòng)。一般來(lái)說(shuō)，當(dāng)信息系統(tǒng)的問(wèn)題被確定時(shí)，僅僅粗略地嘗試概念數(shù)據(jù)建模。在開(kāi)發(fā)最初的原型時(shí)，設(shè)計(jì)用戶想要的顯示和報(bào)表，同時(shí)理解任何新的數(shù)據(jù)庫(kù)需求并定義一個(gè)用語(yǔ)原型的數(shù)據(jù)庫(kù)。這通常是一個(gè)新的數(shù)據(jù)庫(kù)，它復(fù)制現(xiàn)存系統(tǒng)的一部分，還可能增加了一些新的內(nèi)容。當(dāng)需要新的內(nèi)容時(shí)，這些內(nèi)容通常來(lái)自外部數(shù)據(jù)源

21、，如市場(chǎng)研究數(shù)據(jù)、一般的經(jīng)濟(jì)指標(biāo)或行業(yè)標(biāo)準(zhǔn)。</p><p>　　當(dāng)產(chǎn)生原型新的版本時(shí)重復(fù)數(shù)據(jù)庫(kù)的實(shí)現(xiàn)和維護(hù)活動(dòng)。通常僅進(jìn)行最低限度的安全性和完整性控制，因?yàn)榇藭r(shí)的重點(diǎn)是盡可能快地產(chǎn)生可以使用的原型版本。而且文檔管理也延遲到項(xiàng)目的最后，在交付使用時(shí)才進(jìn)行用戶培訓(xùn)。最后，一旦構(gòu)建了一個(gè)可接受的原型，開(kāi)發(fā)者和用戶將決定最后的原型和數(shù)據(jù)庫(kù)是否能交付使用。如果系統(tǒng)（包括數(shù)據(jù)庫(kù)）效率很低，那么系統(tǒng)和數(shù)據(jù)庫(kù)將被重新編程和重新

22、組織以達(dá)到期望的性能。</p><p>　　隨著可視化編程工具（如Visual Basic、Java、Visual C++和第四代語(yǔ)言）越來(lái)越流行，利用可視化編程工具可以很方便地修改用戶與系統(tǒng)間的界面，原型法正成為可供選擇的系統(tǒng)開(kāi)發(fā)方法。使用原型法改變用戶報(bào)表和顯示的內(nèi)容和布局是相當(dāng)容易的。在這個(gè)過(guò)程中，新的數(shù)據(jù)庫(kù)需求被確定，因此被發(fā)展中的應(yīng)用使用的現(xiàn)存的數(shù)據(jù)庫(kù)應(yīng)該進(jìn)行修改。甚至有可能為一個(gè)需要新的數(shù)據(jù)庫(kù)的系統(tǒng)使

23、用原型法，在這種情況下，當(dāng)系統(tǒng)需求在迭代的開(kāi)發(fā)過(guò)程中不斷變化時(shí)需要獲取樣本數(shù)據(jù)以建造或重建數(shù)據(jù)庫(kù)原型。</p><p>　　附件2：外文原文（復(fù)印件）</p><p>　　database development process</p><p>　　Based on information engineering information systems planni

24、ng database is a source of development projects. These new database development projects is usually in order to meet the strategic needs of organizations, such as improving customer support, improve product and inventory

25、 management, or a more accurate sales forecast. However, many more database development project is the bottom-up approach emerging, such as information system user needs specific information to complete their work, thus

26、b</p><p>　　Both the strategic needs or operational information needs of each database development projects normally concentrated in a database. Some projects only concentrated in the database definition, des

27、ign and implementation of a database, as a follow-up to the basis of the development of information systems. However, in most cases, the database and associated information processing function as a complete information s

28、ystems development project was part of the development. </p><p>　　2.1 System Development Life Cycle </p><p>　　Guide management information system development projects is the traditional process

29、of system development life cycle (SDLC). System development life cycle is an organization of the database designers and programmers information system composed of the Panel of Experts detailed description, development, m

30、aintenance and replacement of the entire information system steps. This process is because Waterfall than for every step into the adjacent the next step, that is, the information system is a speci</p><p>　　T

31、he system development life cycle including each stage and database development-related activities, therefore, the question of database management systems throughout the entire development process. In Figure 5 we repeat o

32、f the system development life cycle stage of the seven, and outlines the common database at each stage of development activities. Please note that the systems development life cycle stages and database development steps

33、exists between the relationship between the concept of mode</p><p>　　1.Enterprise Modeling </p><p>　　Database development process from the enterprise modeling (system development life cycle stag

34、e of the project feasibility studies, and to choose a part)</p><p>　　Organizations set the scope and general database content. Enterprise modeling in information systems planning and other activities, these

35、activities determine which part of information systems need to change and strengthen the entire organization and outlines the scope of data. In this step, check the current database and information systems, development o

36、f the project as the main areas of the nature of the business, with a very general description of each term in the development of information </p><p>　　2.Conceptual Data Modeling </p><p>　　One h

37、as already begun on the Information System project, the concept of data modeling phase of the information systems needs of all the data. It is divided into two stages. First, it began the project in the planning stage. A

38、t the same time outlining the establishment of other documents to the existing database without considering the circumstances specific development projects in the scope of the required data. This category only includes h

39、igh-level data (entities), and main contact. Then in th</p><p>　　3. Logical Database Design </p><p>　　Logical database design from two perspectives database development. First, the concept of da

40、ta model transform into relational database theory based on the criteria that means - between. Then, as the design of information systems, every computer procedures (including procedures for the input and output format),

41、 database support services, statements, and inquiries revealed that a detailed examination. In this so-called Bottom-up analysis, accurate verification of the need to maintain the database</p><p>　　4. Physic

42、al database design and definition</p><p>　　Physical database design and definition phase decisions computer memory (usually disk) database in the organization, definition of According to the library manageme

43、nt system for physical structure, the procedures outlined processing services, produce the desired management information and decision support statements. The objective of this stage is to design an effective and safe ma

44、nagement of all data-processing database, the physical database design to closely integrate the information systems </p><p>　　5. Database Implementation </p><p>　　The database prepared by the re

45、alization stage, testing and installation procedures for handling databases. Designers can use the standard programming language (such as COBOL, C or Visual Basic), the dedicated database processing languages (such as SQ

46、L), or the process of the non-exclusive language programming in order to produce a statement of the fixed format, the result will be displayed, and may also include charts. In achieving stage, but also the completion of

47、all the database files, train</p><p>　　6. Database maintenance </p><p>　　During the database in the progressive development of database maintenance. In this step, in order to meet changing busin

48、ess conditions, in order to correct the erroneous database design, database applications or processing speed increase, delete or change the structure of the database. When a procedure or failure of the computer database

49、affect or damage the database may also be reconstruction. This step usually is the longest in the database development process step, as it continued to databas</p><p>　　2.2 Information System developed by ot

50、her means </p><p>　　System Development Life Cycle minor changes in law or its variant of the often used to guide information systems and database development. Information System is a life-cycle methodology,

51、it is highly structured approach, which includes many checks and balances to ensure that every step of produce accurate results, and new or alternative information system and it must communications or data definitions co

52、nsistent existing system needs consistency. System development life cycle because of the regu</p><p>　　The most widely used method of rapid application development is one of the prototype. The prototype syst

53、em is a method of iterative development process, analysts and users through close co-operation, continuing to revise the system will eventually convert all the needs of a working system. In this diagram we contains notes

54、, briefly describes each stage of the prototype of the database development activities. Normally, when information systems problems were identified, tried only a rough concept </p><p>　　Along with visual pro

55、gramming tools (such as Visual Basic, Java, Visual C + + and fourth generation language) increasingly popular use of visual programming tools can easily change the user interface with the system, the prototype is becomin

56、g the choice of system development methodology. Customers using the prototype method statements and show changes to the content and layout is quite easy. In the process, the new database needs were identified, so it is t