本科毕业设计-逻辑数据库设计--外文翻译.doc

《本科毕业设计-逻辑数据库设计--外文翻译.doc》由会员分享，可在线阅读，更多相关《本科毕业设计-逻辑数据库设计--外文翻译.doc（11页珍藏版）》请在淘文阁 - 分享文档赚钱的网站上搜索。

1、附录4 外文译文外文原文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 organizations information system planning process, it aims to help organizatio

2、ns 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

3、. 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 companys enterpris

4、e 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 organizations information system blueprint. In the information system planning, you can build an enterprise data model as a whole

5、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

6、 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 info

7、rmation 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 d

8、isplay, 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

9、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 v

10、ery 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 mer

11、ging 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

12、 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. Th

13、e 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

14、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

15、 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 companys ke

16、y 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 orga

17、nization 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 syste

18、ms 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,

19、 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. Informa

20、tion System data set processing software applications and support procedures.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 ne

21、eds 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

22、, 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

23、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 concentrat

24、ed 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 dev

25、elopment. 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

26、 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 th

27、e 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

28、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

29、 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一一对应exists between the re

30、lationship between the concept of modeling data in both systems development life cycle stages between.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.

31、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

32、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-

33、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, s

34、uch 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 mi

35、stakes. 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

36、 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, state

37、ments, 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

38、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 in

39、dependently 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.

40、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

41、 and determine the rules, the combination, the data after consultation specifications or converted into basic atomic element. Most of todays 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 no

42、t 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.附录5 外文翻译在许多组织中，数据库开发是从企业数据建模开始的，企业数据建模确定了组织数据库

43、的范围和一般内容。这一步骤通常发生在一个组织进行信息系统规划的过程中，它的目的是为组织数据创建一个整体的描述或解释，而不是设计一个特定的数据库。一个特定的数据库为一个或多个信息系统提供数据，而企业数据模型（可能包含许多数据库）描述了由组织维护的数据的范围。在企业数据建模时，你审查当前的系统，分析需要支持的业务领域的本质，描述需要进一步抽象的数据，并且规划一个或多个数据库开发项目。图1显示松谷家具公司的企业数据模型的一个部分。1.1 信息系统体系结构如图1所示，高级的数据模型仅仅是总体信息系统体系结构(ISA)一个部分或一个组织信息系统的蓝图。在信息系统规划期间，你可以建立一个企业数据模型作为整

44、个信息系统体系结构的一部分。根据Zachman(1987)、Sowa和Zachman（1992）的观点，一个信息系统体系结构由以下6个关键部分组成:数据（如图1所示，但是也有其他的表示方法）。 操纵数据的处理（着系可以用数据流图、带方法的对象模型或者其他符号表示）。 网络，它在组织内并在组织与它的主要业务伙伴之间传输数据（它可以通过网络连接和拓扑图来显示）。 人，人执行处理并且是数据和信息的来源和接收者（人在过程模型中显示为数据的发送者和接收者）。 执行过程的事件和时间点（它们可以用状态转换图和其他的方式来显示）。 事件的原因和数据处理的规则（经常以文本形式显示，但是也存在一些用于规划的图表工

45、具，如决策表）。 1.2 信息工程信息系统的规划者按照信息系统规划的特定方法开发出信息系统的体系结构。信息工程是一种正式的和流行的方法。信息工程是一种面向数据的创建和维护信息系统的方法。因为信息工程是面向数据的，所以当你开始理解数据库是怎样被标识和定义时，信息工程的一种简洁的解释是非常有帮助的。信息工程遵循自顶向下规划 的方法，其中，特定的信息系统从对信息需求的广泛理解中推导出来（例如，我们需要关于顾客、产品、供应商、销售员和加工中心的数据），而不是合并许多详尽的信息请求（如一个订单输入屏幕或按照地域报告的销售汇总）。自顶向下规划可使开发人员更全面地规划信息系统，提供一种考虑系统组件集成的方法

46、，增进对信息系统与业务目标的关系的理解，加深对信息系统在整个组织中的影响的理解。信息工程包括四个步骤:规划、分析、设计和实现。信息工程的规划阶段产生信息系统体系结构，包括企业数据模型。1.3 信息系统规划信息系统规划的目标是使信息技术与组织的业务策略紧密结合，这种结合对于从信息系统和技术的投资中获取最大利益是非常重要的。正如表1所描述的那样，信息工程方法的规划阶段包括3个步骤，我们在后续的3个小节中讨论它们。1.确定关键性的规划因素关键性的规划因素是指组织目标、关键的成功因素和问题领域。确定这些因素的目的是建立规划的环境并且将信息系统规划与战略业务规划联系起来。表2显示了松谷家具公司的一些可能

47、的关键规划因素，这些因素有助于信息系统的管理者为新的信息系统和数据库社顶优先级以处理需求。例如，考虑到不精确的销售预测这个问题领域，信息系统的管理者可能在组织数据库中存放额外的历史销售数据、新的市场研究数据和新产品的测试数据。2.确定组织的规划对象组织规划对象定义了业务范围，业务范围会限制后来的系统分析和信息系统可能发生改变的地方。五个关键的规划对象如下所示:组织单元组织中的各种部门。组织地点业务操作的发生地。业务功能支持组织使命的业务处理的相关组。业务功能不同于组织单元，事实上一个功能可以分配给多个组织单元（例如，产品开发功能可能是销售部和生产部共同的责任）。实体类型 关于组织所管理的人，地

48、点和事物的数据的主要类别。信息系统处理数据集的应用软件和支持程序。2数据库开发过程基于信息工程的信息系统规划是数据库开发项目的一个来源。这些开发新数据库的项目通常是为了满足组织的战略需求，例如改善客户支持、提高产品和库存管理或进行更精确的销售预测。然而许多数据库开发项目更多的是以自底向上的方式出现的，例如信息系统的用户需要特定的信息来完成他们的工作，从而请求开始一个项目，又如其他信息系统的专家发现组织需要改进数据管理而开始新的项目。即使在自底向上的情况下，建立企业数据模型也是必须的，以便理解现有的数据库是否可以提供所需的数据，否则，新的数据库、数据实体和属性都应该加到当前的组织数据资源中去。无

49、论是战略需求还是操作信息的需求，每个数据库开发项目通常集中在一个数据库上。一些数据库项目仅仅集中在定义、设计和实现一个数据库，以作为后续信息系统开发的基础。然而在大多数情况下，数据库及其相关信息处理功能是作为一个完整的信息系统开发项目的一部分而被开发的。2.1 系统开发生命周期指导管理信息系统开发项目的传统过程是系统开发生命周期(SDLC)。系统开发生命周期是指一个组织中由数据库设计人员和程序员组成的信息系统专家小组详细说明、开发、维护和替换信息系统的全部步骤。这个过程比作瀑布是因为每一步都流到相邻的下一步，即信息系统的规格说明是一块一块地开发出来的，每一块的输出是下一块的输入。然而如图所示，这些步骤并不是纯线性的，每个步骤在时间上有所重叠（因此可以并行地管理步骤），而且当需要重新考虑先前的决策时，还可以回滚到前面某些步骤。（因而水可以在瀑布中倒流！）图4对系统开发生命周期每一阶段的目的和可交付