【正文】 工作系統(tǒng)。在此圖中我們包含了注釋，概略地描述了每個原型法階段的數(shù)據(jù)庫開發(fā)活動。一般來說，當(dāng)信息系統(tǒng)的問題被確定時，僅僅粗略地嘗試概念數(shù)據(jù)建模。在開發(fā)最初的原型時，設(shè)計用戶想要的顯示和報表，同時理解任何新的數(shù)據(jù)庫需求并定義一個用語原型的數(shù)據(jù)庫。這通常是一個新的數(shù)據(jù)庫，它復(fù)制現(xiàn)存系統(tǒng)的一部分，還可能增加了一些新的內(nèi)容。當(dāng)需要新的內(nèi)容時，這些內(nèi)容通常來自外部數(shù)據(jù)源，如市場研究數(shù)據(jù)、一般的經(jīng)濟(jì)指標(biāo)或行業(yè)標(biāo)準(zhǔn)。 當(dāng)產(chǎn) 生原型新的版本時重復(fù)數(shù)據(jù)庫的實(shí)現(xiàn)和維護(hù)活動。通常僅進(jìn)行最低限度的安全性和完整性控制，因?yàn)榇藭r的重點(diǎn)是盡可能快地產(chǎn)生可以使用的原型版本。而且文檔管理也延遲到項(xiàng)目的最后，在交付使用時才進(jìn)行用戶培訓(xùn)。最后，一旦構(gòu)建了一個可接受的原型，開發(fā)者和用戶將決定最后的原型和數(shù)據(jù)庫是否能交付使用。如果系統(tǒng)（包括數(shù)據(jù)庫）效率很低，那么系統(tǒng)和數(shù)據(jù)庫將被重新編程和重新組織以達(dá)到期望的性能。 隨著可視化編程工具（如 Visual Basic、 Java、 Visual C++和第四代語言）越來越流行，利用可視化編程工具可以很方便地修改用戶 與系統(tǒng)間的界面，原型法正成為可供選擇的系統(tǒng)開發(fā)方法。使用原型法改變用戶報表和顯示的內(nèi)容和布局是相當(dāng)容易的。在這個過程中，新的數(shù)據(jù)庫需求被確定，因此被發(fā)展中的應(yīng)用使用的現(xiàn)存的數(shù)據(jù)庫應(yīng)該進(jìn)行修改。甚至有可能為一個需要新的數(shù)據(jù)庫的系統(tǒng)使用原型法，在這種情況下，當(dāng)系統(tǒng)需求在迭代的開發(fā)過程中不斷變化時需要獲取樣本數(shù)據(jù)以建造或重建數(shù)據(jù)庫原型。 database development process Based on information engineering information systems planning 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 management, or a more accurate sales forecast. However, many more database development project is the bottomup approach emerging, such as information system user needs specific information to plete their work, thus beginning a project request, and as other information systems experts found that organizations need to improve data management and begin new projects. Bottomup even in the circumstances, to set up an enterprise data model is also necessary to understand the existing database can provide the necessary data, otherwise, the new database, data entities and attributes can be added to the current data resources to the organization. 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, design and implementation of a database, as a followup to the basis of the development of information systems. However, in most cases, the database and associated information processing function as a plete information systems development project was part of the development. System Development Life Cycle Guide management 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 system posed 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 next step, that is, the information system is a specification developed by a piece of land, every piece of the output is under an input. However shown in the figure, these steps are not purely linear, each of the steps overlap in time (and thus can manage parallel steps), but when the need to reconsider previous decisions, but also to roll back some steps ahead. (And therefore water can be put back in the waterfall!) The system development life cycle including each stage and database developmentrelated activities, therefore, the question of database management systems throughout the entire development process. In Figure 5 we repeat of the system development life cycle stage of the seven, and outlines the mon database at each stage of development activities. Please note that the systems development life cycle stages and database development steps exists between the relationship between the concept of modeling data in both systems development life cycle stages betwee