Systems-Analysis-and-Design系统的分析与设计大学毕业论文外文文献翻译及原文

毕 业 设 计（论文） 外 文 文 献 翻 译

文献、资料中文题目：系统的分析与设计

文献、资料英文题目：Systems Analysis and Design

文献、资料来源： 文献、资料发表（出版）日期： 院 （部）： 专 业： 班 级： 姓 名： 学 号： 指导教师： 翻译日期： 2017.02.14 引 言 如今的世界，已经是步入了信息化的时代，特别是互联网的迅猛发展，带动了信息进入我们生活的各个领域，也使得信息化建设成为各行业、各领域增强自身管理效率和核心竞争力的重要手段。出版业作为我国社会主义文化产业的一部分，在信息化建设方面相对于其他领域，有成绩是肯定的，但仍然显得滞后，建设水平不够高，离市场需求还有一定距离，还有很大的发展潜力，在我国信息化建设中应该发挥更大的作用。同时要充分利用先进的电子信息技术改造出版业，来加快出版业信息化建设的步伐。 出版社信息化建设是用一种全新的、先进的管理理念，一种全新的机制，一种全新的企业文化来改变以前的管理模式，是一种管理模式的变革。它充分利用信息技术与出版社管理模式的结合，来推动管理水平的提升。面对日益激烈的竞争，出版社必须转变思路，确立全新的经营理念，确立以读者需求为中心，提供专业化的一流服务。信息化建设更是一场管理体制的革命，它要用先进的思想模式和技术手段改变以前的管理模式，用数字化、规范化、程序化、标准化来进行管理，用量化的指标支持奖惩与分配政策，体现激励机制。通过这场改革和革命，最终实现出版社的办公自动化、管理网络化、资源数字化、商务电子化。 而在整个的出版过程中，编务管理是出版行业信息管理系统的重要部分,它将编务人员及图书管理人员从繁重的事务性工作中解放出来,并使管理工作更透明、更科学,此次的系统如果有了良好的分析与设计,不但对编务管理,而且对整个出版行业的管理信息系统的建设都具有十分重要的意义。 本文将以北京科学技术出版社为例，为出版企业编务管理部门的信息化建设提出一个可行性方案，为将来的出版社进行信息化建设打下良好的基础。

附录1 外文翻译(原文) Systems Analysis and Design Working under control of a stored program, a computer processes data into information. Think about that definition for a minute. Any given computer application involves at least three components: hardware, software, and data. Merely writing a program isn't enough; because the program is but one component in a system. A system is a group of components that work together to accomplish an objective. For example, consider a payroll system. Its objective is paying employees. What components are involved? Each day，employees record their hours worked on time cards. At the end of each week, the time cards are collected and delivered to the computer center, where they are read into a payroll program. As it runs, the program accesses data files. Finally, the paychecks are printed and distributed. For the system to work, people, procedures, input and output media, files, hardware, and software must be carefully coordinated. Note that the program is but one component in a system. Computer-based systems are developed because people need information. Those people, called users, generally know what is required, but may lack the expertise to obtain it. Technical professionals, such as programmers, have the expertise, but may lack training in the user's field. To complicate matters, users and programmers often seem to speak different languages, leading to communication problems. A systems analyst is a professional who translates user needs into technical terms, thus serving as a bridge between users and technical professionals. Like an engineer or an architect, a systems analyst solves problems by combining solid technical skills with insight, imagination, and a touch of art. Generally, the analyst follows a well-defined, methodical process that includes at least the following steps; 1.Problem definition 2.Analysis 3.Design 4.Implementation 5.Maintenance At the end of each step, results are documented and shared with both the user and the programmers. The idea is to catch and correct errors and misunderstandings as early as possible. Perhaps the best way to illustrate the process is through example. Picture a small clothing store that purchases merchandise at wholesale, displays this stock, and sells it to customers at retail. On the one hand, too much stock represents an unnecessary expense. On the other hand, a poor selection discourages shoppers. Ideally, a balance can be achieved: enough, but not too much. Complicating matters is the fact that inventory is constantly changing, with customer purchases depleting stock, and returns and reorders adding to it. [1] The owner would like to track inventory levels and reorder and given item just before the store runs out. For a single item, the task is easy-just count the stock-on-hand. Unfortunately, the store has hundreds of different items, and keeping track of each one is impractical. Perhaps a computer might help.

2-1 Problem Definition The first step in the systems analysis and design process is problem definition. The analyst's objective is determining what the user (in this case, the store's owner) needs. Note that, as the process begins, the user possesses the critical information, and the analyst must listen and learn. Few users are technical experts. Most see the computer as a "magic box, "and are not concerned with how it works. At this stage, the analyst has no business even thinking about programs, files, and computer hardware, but must communicate with the user on his or her own term. The idea is to ensure that both the user and the analyst are thinking about the same thing-Thus, a clear, written statement expressing the analyst's understanding of the problem is essential. The user should review and correct this written statement. The time to catch misunderstandings and oversights is now, before time, money and effort are wasted. Often, following a preliminary problem definition, the analyst performs a feasibility study. The study a brief capsule version of the entire systems analysis and design process, attempts to answer three questions: 1.Can the problem be solved? 2.Can it be salved in the user's environment? 3.Can it be solved at a reasonable cost? If the answer to any one of these questions is no, the system should not be developed. Given a good problem definition and a positive feasibility study, the analyst can turn to planning and developing a problem solution.