【溫馨提示】 dwg后綴的文件為CAD圖，可編輯，無水印，高清圖，，壓縮包內(nèi)文檔可直接點(diǎn)開預(yù)覽，需要原稿請(qǐng)自助充值下載，請(qǐng)見壓縮包內(nèi)的文件及預(yù)覽，所見才能所得，請(qǐng)細(xì)心查看有疑問可以咨詢QQ：414951605或1304139763
無錫太湖學(xué)院
畢業(yè)設(shè)計(jì)（論文）
開題報(bào)告
題目： 模具企業(yè)粗加工車間設(shè)備信息管理系統(tǒng)設(shè)計(jì)
信機(jī)系 機(jī)械工程及其自動(dòng)化 專業(yè)
學(xué) 號(hào)： 0923020
學(xué)生姓名： 張 偉
指導(dǎo)教師： 王士同 （職稱：教 授 ）
（職稱： ）
2013年3月24日
課題來源
信息管理系統(tǒng)
科學(xué)依據(jù)（包括課題的科學(xué)意義；國內(nèi)外研究概況、水平和發(fā)展趨勢(shì)；應(yīng)用前景等）
（1）課題科學(xué)意義
隨著我國經(jīng)濟(jì)的迅速發(fā)展，各種制造業(yè)迅速崛起。制造業(yè)當(dāng)作本地經(jīng)濟(jì)發(fā)展的重要支柱之一，促進(jìn)了制造行業(yè)的快速發(fā)展。同時(shí)，隨著中小型制造公司的越來越多,競爭的愈來愈激烈。問題也越來越多。其中有不少因?yàn)楣芾聿簧贫飘a(chǎn)者。如何在激烈的競爭中生存發(fā)展，是每一個(gè)制造公司必須面對(duì)的現(xiàn)實(shí)問題。對(duì)公司的經(jīng)營狀況起決定作用的是公司的管理水平。如何利用現(xiàn)代化先進(jìn)的管理手段，提高公司的管理水平，已經(jīng)成為制造業(yè)發(fā)展的當(dāng)務(wù)之急。面對(duì)信息時(shí)代的機(jī)遇和挑戰(zhàn)，利用科技手段提高企業(yè)管理無疑是一條行之有效的途徑。雖然計(jì)算機(jī)管理并不是制造業(yè)管理走向成功的唯一元素，但它可以最大限度的發(fā)揮準(zhǔn)確，快捷，高效等作用，對(duì)公司的協(xié)調(diào)管理提供強(qiáng)有力的支持。因此，采用全新的計(jì)算機(jī)網(wǎng)絡(luò)和信息管理系統(tǒng)，已經(jīng)成為提高公司的管理效率，協(xié)調(diào)公司運(yùn)營的重要手段之一。此系統(tǒng)結(jié)合企業(yè)實(shí)際的信息管理制度，經(jīng)過實(shí)際的需求分析，使用功能強(qiáng)大的C語言開發(fā)的機(jī)械企業(yè)信息管理系統(tǒng)。
（2） 國內(nèi)外研究情況
西方發(fā)達(dá)國家由于信息化建設(shè)工作起步較早，在企業(yè)整體的管理體系中，管理己經(jīng)作為一個(gè)成熟的構(gòu)成部分發(fā)揮著非常重要的作用，而與CRM，SCM等相關(guān)領(lǐng)域內(nèi)容的緊密結(jié)合更大大提高了企業(yè)的整體競爭力，市場(chǎng)上也有許多非常成熟的企業(yè)信息化管理軟件廠商，比如德國的SAp、美國的Orade等公司。
目前,我國計(jì)算掃的裝機(jī)量從1979年的0.35臺(tái)增長到約80萬臺(tái)，,國有大中型骨干全業(yè)計(jì)算機(jī)的普及率達(dá)90%以上,其中約有50%的骨干企業(yè)建立了各類而向企業(yè)局部管理職能的基于計(jì)算機(jī)的信息系統(tǒng),少數(shù)企業(yè)正在建設(shè)而向企業(yè)管理全過程的綜合信息系統(tǒng)。在我國萬個(gè)國有1500萬個(gè)中小企業(yè)、,2000萬個(gè)集體企業(yè)、。1000萬個(gè)私營企業(yè)中，目前也有干分之五走上了計(jì)算機(jī)輔助單項(xiàng)管理職能的道路
（3） 水平和發(fā)展趨勢(shì)
今項(xiàng)開發(fā)多,但水平低,系統(tǒng)集成少。專項(xiàng)開發(fā)多,際準(zhǔn)化、商況匕奪欠件少。現(xiàn)行系統(tǒng)翻版多,引入先進(jìn)管理方法少。不能適應(yīng)急劇變革的企業(yè)外部環(huán)境和內(nèi)部需求,
建設(shè)我國EIMS的對(duì)策研究的目標(biāo)是在現(xiàn)有成果的基礎(chǔ)上,完善和發(fā)展適合我國國情的企業(yè)信息管理系統(tǒng)建設(shè)的理論框架、基本模式和方法體系?；谛畔⑾到y(tǒng)的特性和我國的特點(diǎn),應(yīng)用現(xiàn)有的理論和方法,采用理論與實(shí)踐相結(jié)合的手段,創(chuàng)立符合我國國情的建設(shè)方法和技術(shù)。在優(yōu)化現(xiàn)有企業(yè)管理的科學(xué)技術(shù)從礎(chǔ),建立符合我國企業(yè)主要管理、決策職能的計(jì)算機(jī)需求模型。根據(jù)管理工程學(xué)的理論和方法,采用運(yùn)籌學(xué)等技術(shù),建立建設(shè)我國的管理體系,包括計(jì)劃、組織、成本控制等方而。按科學(xué)管理的要求,根據(jù)結(jié)息系統(tǒng)的特點(diǎn),并結(jié)合我國企業(yè)的特點(diǎn),研究我國企業(yè)有效實(shí)施的原理和辦法
研究內(nèi)容
① 調(diào)查研究、查閱文獻(xiàn)和搜集資料；
② 閱讀和翻譯與研究內(nèi)容有關(guān)的外文資料；
③ 撰寫開題報(bào)告或文獻(xiàn)綜述，確定設(shè)計(jì)方案或研究方案；
④ 掌握visual studio等可視化編程工具；
⑤ 詳細(xì)設(shè)計(jì)方法（包括控制流程圖、功能模塊、數(shù)據(jù)流圖、程序框圖、開發(fā)關(guān)鍵技術(shù)等）或研究方法 ；
⑥ 設(shè)計(jì)或有關(guān)計(jì)算的源程序（或論點(diǎn)的證明或驗(yàn)證）；
⑦ 撰寫畢業(yè)設(shè)計(jì)（論文）；
擬采取的研究方法、技術(shù)路線、實(shí)驗(yàn)方案及可行性分析
（1）實(shí)驗(yàn)方案
本課題的開發(fā)工作是根據(jù)一個(gè)企業(yè)的實(shí)際情況，開發(fā)一個(gè)試用與此企業(yè)車間的信息管理系統(tǒng)。通過各種功能模塊的設(shè)計(jì)完成了企業(yè)利用軟件實(shí)現(xiàn)對(duì)車間信息進(jìn)行管理的要求。通過企業(yè)車間信息管理系統(tǒng)，實(shí)現(xiàn)公司對(duì)企業(yè)信息管理的高效率和低成本，提高公司各部門的工作效率，達(dá)到人、財(cái)、物盡其用，開源節(jié)流的目的。
（2）研究方法
本課題的主要工作通過采用基于c語言的軟件，充分發(fā)揮c語言所獨(dú)有的易用性、跨平臺(tái)性和安全性，運(yùn)行效率高、安全可靠、使用性廣的車間設(shè)備信息管理系統(tǒng)。
研究計(jì)劃及預(yù)期成果
研究計(jì)劃：
2011年10月12日-2009年12月25日：按照任務(wù)書要求查閱論文相關(guān)參考資料，填寫畢業(yè)設(shè)計(jì)開題報(bào)告書。
2012年1月11日-2010年3月5日：填寫畢業(yè)實(shí)習(xí)報(bào)告。
2012年3月8日-2010年3月14日：按照要求修改畢業(yè)設(shè)計(jì)開題報(bào)告。
2012年3月15日-2010年3月21日：學(xué)習(xí)并翻譯一篇與畢業(yè)設(shè)計(jì)相關(guān)的英文材料。
2012年3月22日-2010年4月11日：Microsoft Visual Studio 8程序設(shè)計(jì)。
2012年4月12日-2010年4月25日：數(shù)據(jù)庫設(shè)計(jì)。
2012年4月26日-2010年5月21日： 畢業(yè)論文撰寫和修改工作。
預(yù)期成果：
利用所開發(fā)的系統(tǒng)對(duì)企業(yè)的信息實(shí)施控制與管理。
特色或創(chuàng)新之處
① 可簡單的操作機(jī)械企業(yè)車間信息的管理（增、刪、改、查詢）。
② 對(duì)企業(yè)車間信息的管理實(shí)現(xiàn)了網(wǎng)絡(luò)化、信息化、圖形化和自動(dòng)化。
已具備的條件和尚需解決的問題
① 解決在信息管理各個(gè)環(huán)結(jié)互不相通所造成的各種問題。
② 系統(tǒng)還需要完善一些功能的完善，還需要算法的優(yōu)化。
指導(dǎo)教師意見
指導(dǎo)教師簽名：
年 月 日
教研室（學(xué)科組、研究所）意見
教研室主任簽名：
年 月 日
系意見
主管領(lǐng)導(dǎo)簽名：
年 月 日
存檔編碼： 江南大學(xué)太湖學(xué)院 2013 屆畢業(yè)作業(yè)周次進(jìn)度計(jì)劃、檢查落實(shí)表 系別：機(jī)電系 班級(jí)：機(jī)械91 學(xué)生姓名：張偉 課題（設(shè)計(jì)）名稱：粗加工車間設(shè)備信息管理系統(tǒng) 開始日期：2012年11月14日 周 次 起止日期 工作計(jì)劃、進(jìn)度 每周主要完成內(nèi)容 存在問題、改進(jìn)方法 指導(dǎo)教師意見并簽字 備 注 1-3 2012年11月14日-2010年12月2日教師下達(dá)畢業(yè)設(shè)計(jì)任務(wù)，學(xué)生初步閱讀資料，完成畢業(yè)設(shè)計(jì)開題報(bào)告。 按照任務(wù)書要求查閱論文相關(guān)參考資料，填寫畢業(yè)設(shè)計(jì)開題報(bào)告書 問題：不清楚自己所選課題的現(xiàn)實(shí)意義。改進(jìn)方法：多渠道多方面了解自己所選課題，在實(shí)習(xí)過程中到企業(yè)實(shí)地了解。 4-10 2012年12月3日-2013年1月6日 指導(dǎo)專業(yè)實(shí)訓(xùn) 完成專業(yè)實(shí)訓(xùn)，填寫畢業(yè)設(shè)計(jì)任務(wù)書 問題：實(shí)證研究的題目數(shù)據(jù)較難得到。改進(jìn)方法：可通過企業(yè)調(diào)研得到的實(shí)際數(shù)據(jù)來證明 11-122013年1月7日-1月20日 指導(dǎo)畢業(yè)實(shí)習(xí) 明確自己的論文題目 問題：實(shí)證研究的題目數(shù)據(jù)較難得到。改進(jìn)方法：可通過企業(yè)調(diào)研得到的實(shí)際數(shù)據(jù)來證明 13 2013年1月21日-1月28日 指導(dǎo)畢業(yè)實(shí)習(xí) 學(xué)習(xí)并翻譯一篇與畢業(yè)設(shè)計(jì)相關(guān)的英文材料 對(duì)于自己陌生的課題資料及時(shí)咨詢指導(dǎo)老師或是上網(wǎng)搜尋 14 2013年1月22日-3月3日 填寫開題報(bào)告 所寫課題的來源，科學(xué)依據(jù)，課題在國 內(nèi)外的研究概況，自己論文研究的內(nèi)容， 采取的研究方法和技術(shù)路線 改進(jìn)：研究內(nèi)容根據(jù)所寫論文要全面概括，研究方法可以多 樣化。 15 2013年3月4日-3月10日 修改開題報(bào)告 按照要求修改畢業(yè)設(shè)計(jì)開題報(bào)告 格式嚴(yán)格按照學(xué)校的規(guī)范進(jìn)行修改,完善。避免出現(xiàn)語句上的和細(xì)節(jié)方面的錯(cuò)誤 16 2013年3月18日-3月24日 編寫程序 visual studio程序設(shè)計(jì) 問題：程序中的代碼用法還不是太熟悉，編寫容易出錯(cuò)。改進(jìn)：通過軟件自帶錯(cuò)誤檢索功能來幫助盡量避免錯(cuò)誤編寫。 17 2013年3月25日-3月31日 編寫程序 visual studio程序設(shè)計(jì) 問題：程序中的代碼用法還不是太熟悉，編寫容易出錯(cuò)。改進(jìn)：通過軟件自帶錯(cuò)誤檢索功能來幫助盡量避免錯(cuò)誤編寫。 18 2013年4月1日-4月7日 編寫程序 visual studio程序設(shè)計(jì) 問題：程序中的代碼用法還不是太熟悉，編寫容易出錯(cuò)。改進(jìn)：通過軟件自帶錯(cuò)誤檢索功能來幫助盡量避免錯(cuò)誤編寫。 周 次 起止日期 工作計(jì)劃、進(jìn)度 每周主要完成內(nèi)容 存在問題、改進(jìn)方法 指導(dǎo)教師意見并簽字 備 注 19 2013年4月8日-4月14日 指導(dǎo)論文初稿寫作 撰寫畢業(yè)論文緒論，摘要 對(duì)論文中的相關(guān)原因分析進(jìn)行修改 20 2013年4月15日-4月21日 指導(dǎo)論文初稿寫作 數(shù)據(jù)庫設(shè)計(jì) 可簡單的操作機(jī)械企業(yè)信息的管理（增、刪、改、查詢） 21 2013年4月22日-4月28日 指導(dǎo)論文初稿寫作 完成總結(jié)，參考文獻(xiàn)，完善畢業(yè)論文 對(duì)論文中的相關(guān)原因分析進(jìn)行修改 22 2013年4月29日-5月5日 指導(dǎo)論文二稿寫作、修改 根據(jù)指導(dǎo)老師的意見對(duì)論文進(jìn)行修改，注 重章節(jié)的連貫性，和前后的一致性。圍繞 課題充實(shí)自己的內(nèi)容。 對(duì)論文中的相關(guān)原因分析進(jìn)行修改 23 2013年5月6日-5月12日 指導(dǎo)論文修改、定稿 將整篇文章的脈絡(luò)、細(xì)節(jié)加以完善，用詞準(zhǔn)確，不出現(xiàn)病句等。 改進(jìn)：將文章再復(fù)查一邊，避免出現(xiàn)語句上的和細(xì)節(jié)方面的錯(cuò)誤。 24 2013年5月13日-5月19日 論文打印裝訂 根據(jù)論文打印要求格式，將論文打印裝訂成冊(cè)，將論文相關(guān)資料也打印裝訂起來。 論文格式嚴(yán)格按照學(xué)校的規(guī)范進(jìn)行修改,完善 25 2013年5月20日-5月26日 論文上交 完成論文,做最后的修訂、完善工作 按學(xué)校給定規(guī)范進(jìn)行裝訂 說明： 1、“工作計(jì)劃、進(jìn)度”、“指導(dǎo)教師意見并簽字”由指導(dǎo)教師填寫，“每周主要完成內(nèi)容”，“存在問題、改進(jìn)方法”由學(xué)生填寫。 2、本表由各系妥善歸檔，保存?zhèn)洳椤?英文原文：
Information System Development and Database Development
In many organizations, database development from the beginning of enterprise data modeling, 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 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 involve a number of databases) described by the organization maintaining the scope of the data. Data modeling in the enterprise, you review of the current system, the need to support analysis of the nature of the business areas, the need for further description of the abstract data, and planning one or more database development project. Figure 1 shows Pine Valley furniture company's enterprise data model of a part.
1.1 Information System Architecture
As shown in figure 1, senior data model is only general information system architecture (ISA) or a part of an organization's information system blueprint. 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 architecture consists of the following six key components:
Data (Figure 1 shows, but there are other methods that).
Manipulation of data processing (of a data flow diagram can be used, with the object model methods, or other symbols that).
Networks, which organizations and in organizations with its main transmission of data between business partners (it can connect through the network topology map and to demonstrate).
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 and the receiver).
Implementation of the events and time points (they can use state transition diagram and other means.)
The reasons for the incident and data processing rules (often in the form of text display, but there are also a number of charts for the planning tools such as decision tables).
1.2 Information Engineering
Information systems 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-oriented 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 concise explanation is very helpful. Information Engineering follow top-down planning approach, in which specific information systems from a wide range of information needs in the understanding derived from (for example, we need about customers, products, suppliers, sales and processing of the data center), rather than merging many detailed information requested ( orders such as a screen or in accordance with the importation of geographical sales summary report). Top-down planning will enable developers to plan more comprehensive information system, consider system components provide an integrated approach to enhance the information system and the relationship between the business objectives of the understanding, deepen their understanding of information systems throughout the organization in understanding the impact.
Information Engineering includes four steps: planning, analysis, design and implementation. The planning stage of project information generated information system architecture, including enterprise data model.
1.3 Information System Planning Information systems planning objective is to enable IT organizations and the business strategy closely integrated, 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 include three steps, we in the follow-up of three sections they discussed.
1. Critical factors determining the planning Planning is the key factor that organizational objectives, critical success factors 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 company's key planning a number of possible factors, these factors contribute to the information systems manager for the new information systems and databases clubs top priority to deal with the demand. For example, given the imprecise sales forecasts this problem areas, information systems managers in the organization may be stored in the database additional historical sales data, new market research data and new product test data.
2. The planning organizations set targets
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:
● organizational units in the various sectors.
● organizations location of the place of business operations.
● functions of the business support organizations 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 production and sale of the common responsibility of the Ministry).
● types of entities managed by the organization on the people, places and things of the major types of data.
● Information System data set processing software applications and support procedures.
3. To set up a business model
A comprehensive business model including the functions 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 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 decomposition example in figure 2 below. In dealing with business functions and support functions of the full set, multiple databases, is essential to a specific database therefore likely only to support functions (as shown in Figure 2) provide a subset of support. In order to reduce data redundancy and to make data more meaningful, has a complete, high-level business view is very helpful.
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 description of each entity type description of business operations and a summary of that business rules. Business rules determine the validity of the data.
An enterprise data model includes not only the types 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 not 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 that top priority will be sorting and development activities under the top-down view through an enterprise-wide approach for the development of these activities. There are many types of planning matrix is available, their commonalities are:
● locations - features show business function in which the implementation of operational locations.
● unit - functions which showed that business function or business unit responsible for implementation.
● Information System - data entities to explain how each information system interact with each data entity (for example, whether or not each system in each entity have the data to create, retrieve, update and delete).
● support functions - data in each functional entities in the data set for the acquisition, use, update and delete.
● Information System - target indication for each information system to support business objectives.
Figure 3 illustrate a possible functions - data entities matrix. Such a matrix can be used for a variety of purposes, including the following three objectives:
1) identify gaps in the data entities to indicate the types of entities not use any function or functions which do not use any entity.
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.
3) The distinction 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 in 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
The planning system more complete description.
2 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 bottom-up approach emerging, such as information system user needs specific information to complete 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. Bottom-up 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 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 systems development project was part of the development. 2.1 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 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 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!)
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 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 of 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一一對(duì)應(yīng)exists between the relationship between the concept of modeling data in both systems development life cycle stages between.
Enterprise Modeling
Database development 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 information 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 current database and information systems, development of 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 systems when needed data. Each item only when it achieved the expected goals of organizations can be when the next step.
Conceptual Data Modeling
One has 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 and the establishment of a plan similar to Figure 1. At 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 high-level data (entities), and main contact. Then in the system development life-cycle analysis stage must have a management information system set the entire organization Details of the data model definition of all data attributes, listing all data types that all data inter-entity business linkages, defining description of the full data integrity rules. In the analysis phase, but also the concept of inspection data model (also called the concept behind the model) and the goal of information systems used to explain other aspects of the model of consistency categories, such as processing steps, rules and data processing time of timing. However, even if the concept is such detailed data model is only preliminary, because follow-up information system life cycle activities in the design of services, statements, display and inquiries may find that missing element or mistakes. Therefore, the concept of data often said that modeling is a top-down manner, its areas of operation from the general understanding of the driver, rather than the specific information processing activities by the driver.
3. Logical Database Design 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 information 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 analysis, accurate verification of the need to maintain the database and the data in each affairs, statements and so on the needs of those in the nature of the data.
For each separate statements, services, and so on the analysis must take into account a specific, limited but complete database view. When statements, services, and 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 or in a centralized, the details of their work until all the logic design stage may be displayed. In these circumstances, logic database design stage must be the original concept of data model and user view these independent or merged into a comprehensive design. In logic design information systems also identify additional information processing needs of these new demands at this time must be integrated into the logic of earlier identified in the database design.
Logical database design is based on the final step for the formation of good data 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 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 design completed, we began to identify in detail the logic of the computer program and maintenance, the report contents of the database for inquiries.
4. Physical database design and definition
Physical database design and definition phase decisions computer memory (usually disk) database in the organization, definition of According to the 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 effective and safe management of all data-processing database, the physical database design to closely integrate the information systems of other physical aspects of the design, including procedures, computer hardware, operating systems and data communications networks.
5. Database Implementation
The database 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 languages (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 also the completion of all the database files, training users for information systems (database) user setup program. The final step is to use existing sources of information (documents legacy applications and databases and now needs new data) loading data. Loading data is often the first step in data from existing files and databases to an intermediate format (such as binary or text files) and then to turn intermediate loading data to a new database. Finally, running databases and related applications for the actual user maintenance and retrieval of data. In operation, the regular backup database and the database when damaged or affected resume database.
6. Database maintenance During the database in the progressive development of database maintenance. In this step, in order to meet changing business 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 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 databases and related applications throughout the life cycle, the development of each database can be seen as a brief database development process and data modeling concepts arise, logical and physical database design and database to achieve dealing with the changes.
信息系統(tǒng)開發(fā)和數(shù)據(jù)庫開發(fā)
在許多組織中，從企業(yè)數(shù)據(jù)建模開始的數(shù)據(jù)庫開發(fā)，企業(yè)數(shù)據(jù)建模確定數(shù)據(jù)庫的范圍和一般內(nèi)容。這一步驟通常發(fā)生在一個(gè)組織的信息系統(tǒng)規(guī)劃的過程中，它的目的是幫助組織數(shù)據(jù)創(chuàng)建一個(gè)整體的描述或解釋，而不是一個(gè)特定的數(shù)據(jù)庫設(shè)計(jì)。一個(gè)或多個(gè)信息系統(tǒng)提供數(shù)據(jù)和企業(yè)數(shù)據(jù)模型的一個(gè)特定的數(shù)據(jù)庫（可能包含許多數(shù)據(jù)庫）組織所保持的數(shù)據(jù)的范圍描述。在