外文翻譯--信息系統(tǒng)開發(fā)和數(shù)據(jù)庫開發(fā)_第1頁
已閱讀1頁,還剩9頁未讀, 繼續(xù)免費閱讀

下載本文檔

版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進行舉報或認領(lǐng)

文檔簡介

1、<p><b>  英文原文:</b></p><p>  Information System Development and Database Development </p><p>  In many organizations, database development from the beginning of enterprise data m

2、odeling, data modeling enterprises determine the scope of the database and the general content. This step usually occurs in an organization's information system planning process, it aims to help organizations create

3、an overall data description or explanation, and not the design of a specific database. A specific database for one or more information systems provide data and the corporate data model (which may invol</p><p&g

4、t;  1.1 Information System Architecture </p><p>  As shown in figure 1, senior data model is only general information system architecture (ISA) or a part of an organization's information system blueprin

5、t. In the information system planning, you can build an enterprise data model as a whole information system architecture part. According to Zachman (1987), Sowa and Zachman (1992) views of an information system architect

6、ure consists of the following six key components: </p><p>  Data (Figure 1 shows, but there are other methods that). </p><p>  Manipulation of data processing (of a data flow diagram can be us

7、ed, with the object model methods, or other symbols that). </p><p>  Networks, which organizations and in organizations with its main transmission of data between business partners (it can connect through t

8、he network topology map and to demonstrate). </p><p>  People who deal with the implementation of data and information and is the source and receiver (in the process model for the data shows that the sender

9、 and the receiver). </p><p>  Implementation of the events and time points (they can use state transition diagram and other means.) </p><p>  The reasons for the incident and data processing r

10、ules (often in the form of text display, but there are also a number of charts for the planning tools such as decision tables). </p><p>  1.2 Information Engineering </p><p>  Information syst

11、ems planners in accordance with the specific information system planning methods developed information system architecture. Information engineering is a popular and formal methods. Information engineering is a data-orien

12、ted creation and maintenance of the information system. Information engineering is because the data-oriented, so when you begin to understand how the database is defined by the logo and when information engineering a con

13、cise explanation is very helpful. Informatio</p><p>  Information Engineering includes four steps: planning, analysis, design and implementation. The planning stage of project information generated informati

14、on system architecture, including enterprise data model. </p><p>  1.3 Information System Planning Information systems planning objective is to enable IT organizations and the business strategy closely in

15、tegrated, such integration for the information systems and technology to make the most of the investment interest is very important. As the table as a description, information engineering approach the planning stage incl

16、ude three steps, we in the follow-up of three sections they discussed. </p><p>  1. Critical factors determining the planning Planning is the key factor that organizational objectives, critical success fac

17、tors and problem areas. These factors determine the purpose of the establishment of planning and environment planning and information systems linked to strategic business planning. Table 2 shows the Pine Valley furniture

18、 company's key planning a number of possible factors, these factors contribute to the information systems manager for the new information systems and datab</p><p>  2. The planning organizations set targ

19、ets </p><p>  Organizations planning targets defined scope of business, and business scope will limit the subsequent analysis and information systems may change places. Five key planning targets as follows:

20、 </p><p>  ● organizational units in the various sectors. </p><p>  ● organizations location of the place of business operations. </p><p>  ● functions of the business support or

21、ganizations handling mission of the relevant group. Unlike business organizations function modules, in fact a function can be assigned to various organizations modules (for example, product development function is the pr

22、oduction and sale of the common responsibility of the Ministry). </p><p>  ● types of entities managed by the organization on the people, places and things of the major types of data. </p><p>

23、  ● Information System data set processing software applications and support procedures. </p><p>  3. To set up a business model </p><p>  A comprehensive business model including the function

24、s of each enterprise functional decomposition model, the enterprise data model and the various planning matrix. Functional decomposition is the function of the organization for a more detailed decomposition process, the

25、functional decomposition is to simplify the analysis of the issue, distracted and identify components and the use of the classical approach. Pine Valley furniture company in order to function in the functional decomposit

26、ion exa</p><p>  The use of specific enterprise data model to describe the symbol. Apart from the graphical description of this type of entity, a complete enterprise data model should also include a descript

27、ion of each entity type description of business operations and a summary of that business rules. Business rules determine the validity of the data. </p><p>  An enterprise data model includes not only the t

28、ypes of entities, including the link between the data entities, as well as various other objects planning links. Showed that the linkage between planning targets a common form of matrix. Because of planning matrix need n

29、ot be explicit modeling database can be clearly described business needs, planning matrix is an important function. Regular planning matrix derived from the operational rules, it will help social development activities t

30、hat top prio</p><p>  ● locations - features show business function in which the implementation of operational locations. </p><p>  ● unit - functions which showed that business function or bus

31、iness unit responsible for implementation. </p><p>  ● Information System - data entities to explain how each information system interact with each data entity (for example, whether or not each system in ea

32、ch entity have the data to create, retrieve, update and delete). </p><p>  ● support functions - data in each functional entities in the data set for the acquisition, use, update and delete. </p>&l

33、t;p>  ● Information System - target indication for each information system to support business objectives. </p><p>  Figure 3 illustrate a possible functions - data entities matrix. Such a matrix can be

34、 used for a variety of purposes, including the following three objectives: </p><p>  1) identify gaps in the data entities to indicate the types of entities not use any function or functions which do not us

35、e any entity. </p><p>  2) found that the loss of each functional entities involved in the inspection staff through the matrix to identify any possible loss of the entity. </p><p>  3) The dis

36、tinction between development activities if the priority to the top of a system development function for a high-priority (probably because it important organizational objectives related), then this area used by entities i

37、n the development of the database has a high priority. Hoffer, George and Valacich (2002) are the works of the matrix on how to use the planning and completion of the Information Engineering </p><p> 

38、 The planning system more complete description. </p><p>  2 database development process </p><p>  Based on information engineering information systems planning database is a source of develop

39、ment 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 management, or a more accurate sa

40、les 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 b</p><p>  Guide mana

41、gement information system development projects is the traditional process of system development life cycle (SDLC). System development life cycle is an organization of the database designers and programmers information sy

42、stem composed of the Panel of Experts detailed description, development, maintenance and replacement of the entire information system steps. This process is because Waterfall than for every step into the adjacent the nex

43、t step, that is, the information system is a speci</p><p>  Figure 4 on the system development life cycle and the purpose of each stage of the product can be delivered concise notes. The system development l

44、ife 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 of the system developmen

45、t life cycle stage of the seven, and outlines the common database at each stage of development activities. Please note that the syste</p><p>  Enterprise Modeling </p><p>  Database development

46、 process from the enterprise modeling (system development life cycle stage of the project feasibility studies, and to choose a part), Organizations set the scope and general database content. Enterprise modeling in infor

47、mation systems planning and other activities, these 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 cur

48、rent database and information systems, d</p><p>  Conceptual Data Modeling </p><p>  One has already begun on the Information System project, the concept of data modeling phase of the informati

49、on systems needs of all the data. It is divided into two stages. First, it began the project in the planning stage and the establishment of a plan similar to Figure 1. At the same time outlining the establishment of othe

50、r documents to the existing database without considering the circumstances specific development projects in the scope of the required data. This category only includes high</p><p>  3. Logical Database Desig

51、n Logical database design from two perspectives database development. First, the concept of data model transform into relational database theory based on the criteria that means - between. Then, as the design of informa

52、tion systems, every computer procedures (including procedures for the input and output format), database support services, statements, and inquiries revealed that a detailed examination. In this so-called Bottom-up analy

53、sis, accurate verification of the n</p><p>  For each separate statements, services, and so on the analysis must take into account a specific, limited but complete database view. When statements, services, a

54、nd other analysis might be necessary to change the concept of data model. Especially in large-scale projects, the different analytical systems development staff and the team can work independently in different procedures

55、 or in a centralized, the details of their work until all the logic design stage may be displayed. In these circumstan</p><p>  Logical database design is based on the final step for the formation of good da

56、ta specifications and determine the rules, the combination, the data after consultation specifications or converted into basic atomic element. Most of today's database, these rules from the relational database theory

57、 and the process known as standardization. This step is the result of management of these data have not cited any database management system for a complete description of the database map. Logical database</p><

58、;p>  4. Physical 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 t

59、he library management 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 ef

60、fective and safe management of all data-processing database, the physical database design to closely integrate the information systems </p><p>  5. Database Implementation </p><p>  The databas

61、e prepared by the realization 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 l

62、anguages (such as SQL), 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 als

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

64、s 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 af

65、fect or damage the database may also be reconstruction. This step usually is the longest in the database development process step, a</p><p>  信息系統(tǒng)開發(fā)和數(shù)據(jù)庫開發(fā)</p><p>  在許多組織中,從企業(yè)數(shù)據(jù)建模開始的數(shù)據(jù)庫開發(fā),企業(yè)數(shù)據(jù)建模確

66、定數(shù)據(jù)庫的范圍和一般內(nèi)容。這一步驟通常發(fā)生在一個組織的信息系統(tǒng)規(guī)劃的過程中,它的目的是幫助組織數(shù)據(jù)創(chuàng)建一個整體的描述或解釋,而不是一個特定的數(shù)據(jù)庫設(shè)計。一個或多個信息系統(tǒng)提供數(shù)據(jù)和企業(yè)數(shù)據(jù)模型的一個特定的數(shù)據(jù)庫(可能包含許多數(shù)據(jù)庫)組織所保持的數(shù)據(jù)的范圍描述。在企業(yè)數(shù)據(jù)建模,你審查當(dāng)前的系統(tǒng),需要支持的業(yè)務(wù)領(lǐng)域的性質(zhì)分析,用于描述需要進一步抽象的數(shù)據(jù),并且規(guī)劃一個或多個數(shù)據(jù)庫開發(fā)項目。圖1顯示一個部分松谷家具公司的企業(yè)數(shù)據(jù)模型。<

67、/p><p>  1.1信息系統(tǒng)體系結(jié)構(gòu)</p><p>  如圖1所示,高級的數(shù)據(jù)模型僅僅是一般的信息系統(tǒng)體系結(jié)構(gòu)(ISA)一個部分或一個組織信息系統(tǒng)的藍圖。在信息系統(tǒng)規(guī)劃,你可以建立一個企業(yè)數(shù)據(jù)模型作為整個信息系統(tǒng)體系結(jié)構(gòu)的一部分。根據(jù)Zachman框架(1987),索瓦和Zachman框架(1992)的信息系統(tǒng)體系結(jié)構(gòu)視圖包含以下六個關(guān)鍵組件:</p><p> 

68、 數(shù)據(jù)(如圖1所示,但還有其他的方法)。</p><p>  數(shù)據(jù)處理操作(一個數(shù)據(jù)流圖可以使用,與對象模型的方法,或其他符號)。</p><p>  網(wǎng)絡(luò)組織,并在組織與它的主要業(yè)務(wù)伙伴之間傳輸數(shù)據(jù)(它可以通過網(wǎng)絡(luò)連接的拓撲結(jié)構(gòu)圖和說明)。</p><p>  人們處理數(shù)據(jù)和信息的實現(xiàn),源和接收器(在過程模型中的數(shù)據(jù)表明,發(fā)送方和接收方)。</p>

69、<p>  事件和時間點執(zhí)行(他們可以使用狀態(tài)轉(zhuǎn)換圖和其他手段。)</p><p>  事件發(fā)生的原因和處理數(shù)據(jù)的規(guī)則(通常以文本的形式顯示,但也有規(guī)劃工具,如決策表的一些圖表)。</p><p><b>  1.2信息工程</b></p><p>  信息系統(tǒng)的規(guī)劃者按照特定的信息系統(tǒng)規(guī)劃方法開發(fā)的信息系統(tǒng)體系結(jié)構(gòu)。信息工程是一種流

70、行的和正式的方法。信息工程是一個面向數(shù)據(jù)的創(chuàng)建和維護信息系統(tǒng)。因為信息工程是面向數(shù)據(jù)的,所以當(dāng)你開始理解數(shù)據(jù)庫是怎樣被標識和定義時,信息工程的一種簡潔的解釋是非常有幫助的。信息工程遵循自上而下的規(guī)劃方法,在特定的信息系統(tǒng)從一個廣泛的信息需要從認識(例如,我們需要對客戶,產(chǎn)品,供應(yīng)商,銷售和數(shù)據(jù)中心處理),而不是合并許多詳細的信息請求(訂單,如屏幕或按照地理的銷售總結(jié)報告進口)。自上而下的規(guī)劃將使開發(fā)人員更全面地規(guī)劃信息系統(tǒng),考慮系統(tǒng)組件

71、提供了提高信息系統(tǒng)的理解和業(yè)務(wù)目標之間的關(guān)系的一種綜合方法,加深對信息系統(tǒng)在整個組織中的影響的理解。</p><p>  信息工程包括四個步驟:規(guī)劃,分析,設(shè)計與實現(xiàn)。信息工程的規(guī)劃階段產(chǎn)生的信息系統(tǒng)體系結(jié)構(gòu),包括企業(yè)數(shù)據(jù)模型。</p><p>  1.3信息系統(tǒng)規(guī)劃信息系統(tǒng)規(guī)劃的目標是使它的組織和企業(yè)戰(zhàn)略緊密結(jié)合,使大部分的投資興趣的信息系統(tǒng)和技術(shù)的整合是非常重要的。如表1所描述的那樣,

72、信息工程方法的規(guī)劃階段包括三個步驟,我們在三節(jié)他們討論后續(xù)。</p><p>  1。確定規(guī)劃規(guī)劃的關(guān)鍵因素是組織目標的關(guān)鍵因素,關(guān)鍵成功因素和問題領(lǐng)域。這些因素確定的規(guī)劃和環(huán)境規(guī)劃與信息系統(tǒng)與業(yè)務(wù)戰(zhàn)略規(guī)劃的建立。表2顯示松谷家具公司的一些可能的關(guān)鍵規(guī)劃因素,這些因素有助于信息系統(tǒng)的經(jīng)理為新的信息系統(tǒng)和數(shù)據(jù)庫的俱樂部優(yōu)先處理的需求。例如,考慮到不精確的銷售預(yù)測這個問題領(lǐng)域,信息系統(tǒng)管理者在組織可以存儲在數(shù)據(jù)庫中的

73、額外的歷史銷售數(shù)據(jù),新的市場研究數(shù)據(jù)和新產(chǎn)品的測試數(shù)據(jù)。</p><p>  2。規(guī)劃組織確定目標</p><p>  組織規(guī)劃對象定義了業(yè)務(wù)范圍,業(yè)務(wù)范圍會限制后續(xù)的分析和信息系統(tǒng)可能發(fā)生改變的地方。五個主要規(guī)劃指標如下:</p><p>  ●組織單位在各部門。</p><p>  ●組織經(jīng)營地點的位置。所支持的業(yè)務(wù)組織處理相關(guān)集團的使命

74、</p><p>  ●功能。不同的企業(yè)組織功能模塊,事實上一個函數(shù)可以被分配到各模塊(例如,產(chǎn)品開發(fā)功能部共同負責(zé)生產(chǎn)和銷售)。</p><p>  ●類型對人組織的管理實體,地方和數(shù)據(jù)類型主要的東西。</p><p>  ●信息系統(tǒng)數(shù)據(jù)處理的應(yīng)用軟件和支持程序。</p><p><b>  3。建立企業(yè)模型</b>&

75、lt;/p><p>  包括每個企業(yè)功能分解模型的功能全面的商業(yè)模式,企業(yè)數(shù)據(jù)模型和各種規(guī)劃矩陣。功能分解是一個更詳細的分解過程組織的功能,功能分解,簡化問題的分析,分散注意力和確定組件和使用的經(jīng)典方法。松谷家具公司為函數(shù)的功能分解的例子如圖2所示。在處理的全套,多個數(shù)據(jù)庫的業(yè)務(wù)功能和支持功能,是一個特定的數(shù)據(jù)庫,因此可能只支持功能必不可少的(如圖2所示)的一個子集提供支持。為了減少數(shù)據(jù)冗余,使數(shù)據(jù)更有意義,擁有完整

76、的,高層次的業(yè)務(wù)視圖是非常有幫助的。</p><p>  企業(yè)數(shù)據(jù)模型使用特定的符號來描述。除了這類實體的圖形化描述,一個完整的企業(yè)數(shù)據(jù)模型還應(yīng)包括業(yè)務(wù)運營的每個實體類型的描述和總結(jié),業(yè)務(wù)規(guī)則。業(yè)務(wù)規(guī)則決定數(shù)據(jù)的有效性。</p><p>  企業(yè)數(shù)據(jù)模型不僅包括實體類型,還包括數(shù)據(jù)實體之間的聯(lián)系,以及其他各種規(guī)劃對象鏈接。顯示規(guī)劃對象間聯(lián)系的一種常見形式的矩陣。由于規(guī)劃矩陣不需要顯式建模的

77、數(shù)據(jù)庫可以明確描述業(yè)務(wù)需求,規(guī)劃矩陣是一個重要的功能。定期規(guī)劃矩陣推導(dǎo)出從操作規(guī)則,這將有助于最高優(yōu)先排序和發(fā)展活動的自上而下的視角下進行這些活動的發(fā)展,社會發(fā)展活動的企業(yè)范圍的方法。有許多類型的規(guī)劃矩陣是可用的,他們的共同點:</p><p>  ●位置特征顯示業(yè)務(wù)功能,操作地點實施。</p><p>  ●單元功能顯示業(yè)務(wù)功能或業(yè)務(wù)單元負責(zé)實施。</p><p>

78、;  ●信息系統(tǒng)-數(shù)據(jù)實體來解釋每個信息系統(tǒng)與每個數(shù)據(jù)實體(例如,是否在每個實體的每個系統(tǒng)已經(jīng)創(chuàng)建,檢索,更新和刪除數(shù)據(jù))。</p><p>  ●支持功能集的采集,使用數(shù)據(jù)在各個功能實體的數(shù)據(jù),更新和刪除。</p><p>  ●信息系統(tǒng)為每個信息系統(tǒng)支持的業(yè)務(wù)目標,目標指示。</p><p>  圖3說明了一個可能的功能-數(shù)據(jù)單位矩陣。這樣一個矩陣可用于多種用途

79、,包括以下三個目標:</p><p>  1)確定數(shù)據(jù)的空白實體顯示實體類型不使用任何功能或不使用任何實體功能。</p><p>  2)發(fā)現(xiàn)各個功能實體參與檢驗人員通過矩陣來確定實體的任何可能的損失的損失。</p><p>  3)區(qū)分開發(fā)活動如果一個高優(yōu)先級的系統(tǒng)開發(fā)功能的優(yōu)先(可能因為它與重要的組織目標相關(guān)的),然后通過實體在數(shù)據(jù)庫開發(fā)應(yīng)用具有高優(yōu)先級?;舾?,

80、喬治和瓦拉季奇(2002)是基質(zhì)的如何利用信息工程的規(guī)劃和完成</p><p>  更完整的描述的規(guī)劃系統(tǒng)。</p><p><b>  2數(shù)據(jù)庫開發(fā)過程</b></p><p>  基于信息工程的信息系統(tǒng)規(guī)劃是數(shù)據(jù)庫開發(fā)項目的一個源碼。這些新的數(shù)據(jù)庫開發(fā)項目通常是為了滿足組織的戰(zhàn)略需求,如改善客戶支持,提高產(chǎn)品和庫存管理,或更準確的銷售預(yù)測。

81、然而,許多數(shù)據(jù)庫開發(fā)項目更多的是以自底向上的方式出現(xiàn)的,例如信息系統(tǒng)的用戶需要特定的信息來完成他們的工作,從而開始一個項目的要求,與其他信息系統(tǒng)的專家發(fā)現(xiàn)組織需要提高數(shù)據(jù)管理而開始新的項目。即使在情況上下,建立企業(yè)數(shù)據(jù)模型也有必要了解現(xiàn)有的數(shù)據(jù)庫,可以提供所需的數(shù)據(jù),否則,新的數(shù)據(jù)庫,數(shù)據(jù)實體和屬性可以添加到現(xiàn)有的數(shù)據(jù)資源的組織。雙方的戰(zhàn)略需要,或操作的每個數(shù)據(jù)庫開發(fā)項目通常集中在一個數(shù)據(jù)庫中的信息需求。有些項目只集中在數(shù)據(jù)庫中的定義,

82、設(shè)計和實現(xiàn)一個數(shù)據(jù)庫,以作為后續(xù)信息系統(tǒng)開發(fā)的基礎(chǔ)。然而,在大多數(shù)情況下,數(shù)據(jù)庫和相關(guān)的信息處理功能是作為一個完整的信息系統(tǒng)開發(fā)項目是發(fā)展計劃的一部分。</p><p>  2.1系統(tǒng)開發(fā)生命周期</p><p>  指導(dǎo)管理信息系統(tǒng)開發(fā)項目是系統(tǒng)開發(fā)生命周期(SDLC)傳統(tǒng)工藝。系統(tǒng)開發(fā)生命周期是一個數(shù)據(jù)庫設(shè)計人員和程序員組成的信息系統(tǒng)專家小組開發(fā)的詳細描述,組織,維護和替換信息系統(tǒng)的全

83、部步驟。這個過程是因為瀑布比每一步到相鄰的下一步,那就是,信息系統(tǒng)是一個規(guī)范的一塊土地開發(fā),每一塊的輸出是下一塊的輸入。然而如圖所示,這些步驟并不是純線性的,每個步驟在時間上重疊(因此可以并行地管理步驟),而且當(dāng)需要重新考慮先前的決定,但也可以回滾到前面某些步驟。(所以水可以放回在瀑布?。?lt;/p><p>  圖4在系統(tǒng)開發(fā)生命周期的每個階段和產(chǎn)品的目的,可提供簡明的注釋。系統(tǒng)開發(fā)生命周期的各個階段,包括數(shù)據(jù)庫開

84、發(fā)相關(guān)的活動,因此,在整個開發(fā)過程中的數(shù)據(jù)庫管理系統(tǒng)的問題。我們在圖5中重復(fù)的七系統(tǒng)開發(fā)生命周期階段,并概述了常見的數(shù)據(jù)庫開發(fā)活動的各個階段。請注意,系統(tǒng)開發(fā)生命周期的階段和數(shù)據(jù)庫開發(fā)步驟一一對應(yīng)建模數(shù)據(jù)在系統(tǒng)開發(fā)生命周期的各個階段之間的關(guān)系之間存在的概念。</p><p><b>  企業(yè)建模</b></p><p>  從企業(yè)建模數(shù)據(jù)庫開發(fā)過程(該項目的可行性研究

85、,系統(tǒng)開發(fā)生命周期的階段和選擇的一部分),組織數(shù)據(jù)庫的范圍和一般內(nèi)容。在信息系統(tǒng)規(guī)劃和其他活動,企業(yè)建模,這些活動確定信息系統(tǒng)的哪個部分需要改變和加強整個組織的輪廓數(shù)據(jù)的范圍。在這一步,檢查當(dāng)前數(shù)據(jù)庫和信息系統(tǒng),該項目的開發(fā),為公司的業(yè)務(wù)性質(zhì)的主要領(lǐng)域,在信息系統(tǒng)開發(fā)中非常一般的術(shù)語描述每個時所需要的數(shù)據(jù)。每個項目只有當(dāng)它達到組織的預(yù)期目標時才可以進行下一步。</p><p><b>  概念數(shù)據(jù)建模&

86、lt;/b></p><p>  對一個已經(jīng)開始的信息系統(tǒng)項目,數(shù)據(jù)建模的所有信息系統(tǒng)數(shù)據(jù)階段需要的概念。它分為兩個階段。首先,它開始在規(guī)劃階段的項目和計劃類似于圖1的建立。同時建立其他文檔來概述現(xiàn)有的數(shù)據(jù)庫,而不考慮環(huán)境的具體開發(fā)項目中所需的數(shù)據(jù)范圍。這僅僅包括高層類別的數(shù)據(jù)(實體),和主要的接觸。然后在系統(tǒng)開發(fā)生命周期的分析階段,必須有一個管理信息系統(tǒng)的所有數(shù)據(jù)屬性的數(shù)據(jù)模型定義整個組織的細節(jié),列出所有

87、的數(shù)據(jù)實體間的業(yè)務(wù)聯(lián)系的所有數(shù)據(jù)類型,定義數(shù)據(jù)完整性規(guī)則的描述。在分析階段,而且檢查概念數(shù)據(jù)模型(也被稱為模型背后的概念),用來解釋的模型類別的一致性等方面的信息系統(tǒng)的目標,如加工步驟,規(guī)則和時序數(shù)據(jù)的處理時間。然而,即使是這樣詳細的概念數(shù)據(jù)模型僅僅是初步的,因為在服務(wù),報表設(shè)計后續(xù)信息系統(tǒng)生命周期活動,顯示和查詢時可能會發(fā)現(xiàn)遺漏的元素或錯誤。因此,數(shù)據(jù)經(jīng)常表示,建模是一個自上而下的方式的概念,它由業(yè)務(wù)領(lǐng)域的一般理解所驅(qū)動,而不是特定的

88、信息處理活動所驅(qū)動。</p><p>  3。數(shù)據(jù)庫邏輯設(shè)計邏輯數(shù)據(jù)庫設(shè)計從兩個角度進行數(shù)據(jù)庫開發(fā)。首先,將概念數(shù)據(jù)模型轉(zhuǎn)換成基于關(guān)系數(shù)據(jù)庫理論意味著之間的標準。然后,作為信息系統(tǒng)的設(shè)計,每一個計算機程序(包括程序的輸入和輸出格式),數(shù)據(jù)庫服務(wù)支持,報表,查詢和顯示一個詳細的檢查。在這個所謂的自底向上的分析,需要保持在每個事務(wù)數(shù)據(jù)庫和數(shù)據(jù)準確的驗證,報表等的數(shù)據(jù)的性質(zhì)的需要。</p><p&g

89、t;  對于每個單獨的報表,服務(wù),所以在分析必須考慮到一個特定的,有限的,完整的數(shù)據(jù)庫視圖。當(dāng)報表,服務(wù),和其他的分析可能需要改變概念數(shù)據(jù)模型。尤其在大型的項目中,不同的分析人員和系統(tǒng)開發(fā)者團隊可以在不同的程序或程序集中的獨立工作,他們的工作細節(jié),直到所有的邏輯設(shè)計階段可以顯示。在這種情況下,邏輯數(shù)據(jù)庫設(shè)計階段必須將原始的概念數(shù)據(jù)模型和這些獨立的用戶視圖或合并為一個綜合設(shè)計。在邏輯信息系統(tǒng)設(shè)計時也可以確定額外的信息處理需求,此時這些新的

90、需求必須集成到前面確定的邏輯在數(shù)據(jù)庫設(shè)計。</p><p>  邏輯數(shù)據(jù)庫設(shè)計是基于良好的數(shù)據(jù)規(guī)范形成的最后一步,確定的規(guī)則,結(jié)合,經(jīng)過協(xié)商規(guī)范或轉(zhuǎn)換成基本的原子元素的數(shù)據(jù)。今天大多數(shù)的數(shù)據(jù)庫,這些規(guī)則來自關(guān)系數(shù)據(jù)庫理論和過程稱為標準化。這一步是對這些數(shù)據(jù)的管理的結(jié)果沒有被引用的數(shù)據(jù)庫映射一個完整的描述的任何數(shù)據(jù)庫管理系統(tǒng)。邏輯數(shù)據(jù)庫設(shè)計完成后,我們開始了詳細的計算機程序的邏輯和維護標識,用于查詢數(shù)據(jù)庫的報告內(nèi)容

91、。</p><p>  4。物理數(shù)據(jù)庫設(shè)計和定義</p><p>  物理數(shù)據(jù)庫設(shè)計和定義階段決定計算機存儲器(通常是磁盤)中數(shù)據(jù)庫的組織,定義數(shù)據(jù)庫管理系統(tǒng)的物理結(jié)構(gòu),概述處理事務(wù)的程序,產(chǎn)生所需的信息管理與決策支持報表。本階段的目標是設(shè)計的所有數(shù)據(jù)處理的數(shù)據(jù)庫安全和有效的管理,物理數(shù)據(jù)庫設(shè)計的設(shè)計,其他物理方面的信息系統(tǒng)緊密結(jié)合起來,包括程序,計算機硬件,操作系統(tǒng)和數(shù)據(jù)通信網(wǎng)絡(luò)。<

92、;/p><p><b>  5。數(shù)據(jù)庫的實現(xiàn)</b></p><p>  通過數(shù)據(jù)庫實現(xiàn)階段編寫,測試和安裝處理數(shù)據(jù)庫的程序。設(shè)計人員可以使用標準的編程語言(如COBOL,C或Visual Basic),專用的數(shù)據(jù)庫處理語言(如SQL),以產(chǎn)生固定格式的報表或非獨家的語言編程的過程中為了,結(jié)果將顯示,可能還包括圖表。在實現(xiàn)階段,還可以完成對所有數(shù)據(jù)庫文件,信息系統(tǒng)培訓(xùn)的用

93、戶(數(shù)據(jù)庫)的用戶安裝的程序。當(dāng)損壞或影響數(shù)據(jù)庫恢復(fù)數(shù)據(jù)庫。</p><p>  6。在數(shù)據(jù)庫維護數(shù)據(jù)庫在數(shù)據(jù)庫維護逐步發(fā)展。在這一步,為了滿足變化的業(yè)務(wù)條件,為了正確的數(shù)據(jù)庫設(shè)計的錯誤,或數(shù)據(jù)庫應(yīng)用的處理速度的增加,刪除或改變數(shù)據(jù)庫的結(jié)構(gòu)。當(dāng)計算機數(shù)據(jù)庫程序或失效的影響或破壞數(shù)據(jù)庫也可以重建。這一步通常是數(shù)據(jù)庫開發(fā)過程中最長的一步,因為它持續(xù)數(shù)據(jù)庫及相關(guān)應(yīng)用的整個生命周期,每個數(shù)據(jù)庫的發(fā)展可以被看作是一個簡單的

溫馨提示

  • 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 眾賞文庫僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負責(zé)。
  • 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準確性、安全性和完整性, 同時也不承擔(dān)用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。

評論

0/150

提交評論