软件测试管理中英文对照外文翻译文献

中英文资料外文翻译

基于价值的软件测试管理

摘要:根据研究表明测试已经成为软件开发过程中一个很重要的环节，它占据了整个软件开发成本的百分之三十到五十。测试通常不是用来组织商业价值的最大化，也不是肩负着项目的使命。路径测试、分支测试、指导测试、变换测试、场景测试以及需求测试等对于软件的所有方面都是同等重要的。然而在实践中百分之八十的价值往往来自百分之二十的软件。为了从软件测试中得到最大的投资回报，测试管理需要最大化它的价值贡献。在本章，我们将更加促进对基于价值的测试的需要，描述支持基于价值的测试管理的实践，勾画出基于价值的测试管理的框架，并举例说明该框架。关键词: 基于价值的软件测试,基于价值的测试,测试成本,测试利益,测试管理

11.1 前言

测试是软件质量保证过程中最重要和最广泛使用的方法。校验和验证旨在通过综合分析, 测试软件确保其正确运行功能，确保软件的质量和软件的可靠性。在IEEE610.12(1990)中,测试被定义为在规定条件下对执行的系统或者组件进行观察和记录,并对系统或者组件进行评价的活动。

测试在实践过程中被广泛的使用，在保证质量策略的诸多组织中扮演着重要的角色。软件影响着成千上万人的日常生活，担负着艰巨的任务。因此软件在不久的将来将显得尤其的重要。研究表明，测试通常消耗软件开发成本的30%至50%。对于安全危急系统，甚至更高的比例也不足为奇。因此软件测试具有挑战的就是寻找更多的有效途径进行有效的测试。

软件测试管理的价值在于努力减少测试成本和满足需求。有价值的测试管理对于项目目标和商业价值也能有很好的向导。在第一章，Boehm 列举了很多方面的潜在测试成本。该例子说明了利用客户结账类型的7%的成本来完成50%的软件测试利益。尽管百分百测试是一个不太切实际的目标, 然而通过调整测试方法, 仍有很大的空间来改进和节省达到预期的价值。基于软件工程的价值动力在于目前软件工程的实践研

究都是把需求, 测试案例, 测试对象和产品缺陷看的同等重要。这对测试显然是正确的，它对产品价值间接的做出贡献。开发和测试的分离使得这问题显得更为突出。测试往往是一个纯粹的技术问题，将使得测试和商业决策之间曾解链的关系变的更加紧密。本章主要描述了提高基于价值的测试管理的需求, 解释其基本要素, 讨论现有的实例来支持基于价值的测试, 以及基于价值的测试管理的基本框架。本章接下来部分的基本结构如下：11.2节讨论测试管理的贡献价值； 11.3节讨论已测案例对于测试管理的支持； 11.4节用例子描述基于价值的测试管理的框架。本章最后将对具体的再作更进一步的研究。

11.2基于价值测试的描述

基于价值的校验和验证的目标被定义为确保软件的实施能够满足其预期的目标价值利益。如果我们从价值的角度去考虑，那么测试的贡献应该在哪呢？从根本上来说, 可以从两个方面来考虑: 内部方面包括测试成本以及测试效益, 外部方面强调未来系统的威胁以及机遇。对于基于价值的测试，其关键就是要把这两个方面结合起来,也就是说通过客户和市场需求调整内部测试的过程。

为了使内部和外部两方面因素相结合，只专注于技术方面的测试显然是不恰当的。相反，测试管理需要有个全局的把握。

例41描述了测试管理内外双方面之间的依赖关系。内部方面的就如同测试经理对整个项目的控制。这方面的费用主要来自于软件测试实践以及短期长期的测试。而外部方面被认为是测试主管所能控制以外的一些利益和参数数据.基于价值的软件测试管理使得测试能够满足以利益为重的价值主张，以及使整个小组聚焦在有价值的测试方向上。

对于软件测试的外部观点的首要问题是“我们如何确保软件系统的价值目标？”这目标就是通过协调价值主张来测试软件集中的有价值部分，最重要的品质以及项目风险的及时调整等.回答这样的问题包括市场机遇，项目的价值主张以及成本效益。参考第一章关于机遇和风险的详细介绍以及参考第七章的价值主张的引出与调和。

内部观点是建立在价值主张的利益之上，以及测试的预算代表着整个项目的一个大概水平。这主要的问题就是如何把测试作为一项投资活动。为了能够高效迅速的测试及降低开发预算。适当的内外部交流协调能够满足测试的利益价值。

测试的价值贡献

测试与其他的开发环节诸如代码和用户界面设计相比，它不能立即对产品创造价值。然而测试提供和支持软件开发过程中产生的有价值的任务活动。理解测试贡献价值的关键点在于测试的贡献效应。测试的贡献建立了测试与最终产品价值利益之间的关系。

最直接的客户是直接与测试小组有密切联系的程序开发者和项目主管。在基于价值的软件工程测试过程中的集中力量是顾客和用户（见第七章）。顾客和用户通过设定语境和范围来进行测试达到测试的价值目标。

测试的客户

开发人员,项目主管,质量主管,顾客,分析者,最终用户或者维修人员们都得益于软件系统的分析,依靠反馈来检测问题,降低其不确定性,做出相关的决定来加快产品进程。

下面的例子显示了不同组对于测试需求的反馈信息：

?顾客和用户关于多大程度上需求一致是否满意以及在多大程度上满足软件的价值利益.测试还对项目的进程提供可见性和洞察力.通过测试的结果可以了解已通过的测试案例.当验收测试时出现不实用的或者失败的显示在实际环境中才能出现的问题，α和β测试提供了一个更加坚实的基础来验证结果。

?销售和产品主管从测试计划、定价、促销和分配方面获取相关的信息。产品实际的质量与顾客和用户所期望的质量之间的差异很容易会导致误解和错误的设想以至于降低或者阻止了真正价值的实现。为了能够成功地达到这些期望以及满足个人或组织的目标，通过客户需求来调整产品设计满足某些功能。

?对于项目主管，测试支持了风险管理和项目进程的估计。重点是识别和排除潜在的价值破坏和抑制价值功绩的风险。早期的大幅降低项目绩效的严重缺陷,是一个主要的目的。测试降低了不确定性和帮助项目主管对于清除缺陷、系统稳定性以及产品更新发布能够作出更好、更明智的决定。

?质量主管对于问题的识别以及对特定问题的动态趋势较为感兴趣。测试结果对于项目评估、对于质量策略的保证以及进程的改进提供了帮助。Rosenberg讨论了测试如何对确保质量作出贡献并展示了测试问题如何验证如何修正以此来提升项目进程。开发者和用户了解相关问题的当前状态，并且提供相关数据来衡量及预测软件的质量和可靠性。

?开发人员通常需要获取反馈信息来验证测试实施是否完整，是否符合标准，是否满足质量要求。为了保证稳定性，测试提供了相关缺陷的详细信息，提示测试失败的原因。除此之外，测试对于项目缺陷的改进作出反馈。例如，通过相关的修改以后需要测试其是否随着相关的改动使原先的功能有所改动或者出现衰退的情况，这些都是需要注意的。

?对于需求工程师来说，测试对于验证和确认需求是很有价值的。Weinberg曾指出“最有效的方法之一就是通过测试案例就象测试一个完整的系统来形成测试需求”。黑盒测试通过其需求帮助能够保证它们的完整性，准确性，透明性及简明性等。因此测试能够提升要求且向着测试驱动的方向发展。

简言之，测试能够通过降低计划的不确定性和风险性来提升利益，作出相关的决定，努力控制把不必要的消耗减少到最低程度(内部原因)。尤为重要的是，它有助于实现预期的价值利益。这些利益的得来也并不是免费的，测试的代价通常也是有意义的(外部原因).测试可以被理解为购买信息，也可被认为降低成本风险，减少不确定性的投资活动。在成本和利益的投资上需要对测试需求作出相关的决定。因此接下来的两个问题是：什么是测试成本？什么是价值活动的测试利益？

Value-Based Management of Software Testing

Abstract:Testing is one of the most resource-intensive activities in software development and consumes between 30 and 50% of total development costs according to many studies. Testing is however often not organized to maximize business value and not aligned with a project’s miss ion. Path, branch, instruction, mutation, scenario, or requirement testing usually treat all aspects of software as equally important, while in practice 80% of the value often comes from 20% of the software. In order to maximize the return of investment gained from software testing, the management of testing needs to maximize its value contribution. In this chapter we motivate the need for value-based testing, describe practices supporting the management of value-based testing, outline a framework for value-based test management, and illustrate the framework with an example.

Keywords: Value-based software engineering, value-based testing, cost of testing, benefits of testing, test management.

11.1 Introduction

Testing is one of the most important and most widely used approaches for validation and verification (V&V). V&V aims at comprehensively analyzing and testing software to determine that it performs the intended functions correctly, to ensure that it performs no unintended functions, and to measure its quality and reliability (Wallace and Fujii, 1989). According to IEEE 610.12 (1990) testing is defined as “an activity in which a system or component is executed under specified conditions, the results are observed or recorded, and an evaluation is made of some aspect of the system or component.”

Testing is widely used in practice and plays a central role in the quality assurance strategies of many organizations. As software pervades more and more

critical tasks and affects everyday life, security, and well being of millions of people (Ferscha and Mattern, 2004), the importance of testing will increase in the future. Studies show that testing already consumes between 30 and 50% of software development costs (Beizer, 1990). Even higher percentages are not uncommon for safety-critical systems. Finding more efficient ways to perform effective testing is therefore a key challenge in testing (Harrold, 2000).

Managing software testing based on value considerations promises to tackle increasing testing costs and required effort. Value-based test management could also provide guidance to better align testing investments with project objectives and business value. In Chapter 1, Boehm presents an impressive example of potential test cost savings (on project level as well as on global scale) by focusing testing on the most valuable aspects. The example illustrates that with an investment-oriented focus on testing 7% of the customer billing types (1 in 15) achieved 50% of the benefits of testing the software. Completely testing the system requires a constantly increasing effort and, due to decreasing marginal benefits, results in a negative return on investment. Although a “100% tested” status is not a practica l goal, there is still room for a considerable amount of improvement and savings by better adjusting testing to its value contribution.

The motivation for value-based software engineering comes from the fact that “much of current software engineering practice and research is done in a value neutral setting, in which every requirement, use case, object, and defect is treated as equally important” (Boehm, 2003). This is especially true for testing, where its indirect contribution to product value leads to a value-neutral perception of testing. The common separation of concerns between development and testing exacerbates the problem. Testing is often reduced to a purely technical issue leaving the close relationship between testing and business decisions unlinked and the potential value contribution of testing unexploited.

The objectives of this chapter are to motivate the need for value-based management of testing, to explain its underlying elements, to discuss existing practices that support value-based testing, and to outline a general framework for value-based test management. The remainder of this chapter is thus structured as follows. In Section 11.2 we discuss test management under the light of its value contribution. In Section 11.3 we describe existing practices that support value-based testing. Section 11.4 depicts a value-based test management framework using an example for illustration. An outlook on further research directions closes the chapter.

11.2 Taking a Value-Based Perspective on Testing

The objectives of value-based verification and validation are defined as “ensur ing that a software solution satisfies its value objectives” and organizing V&V tasks to operate as an investment activity” (Boehm and Huang, 2003). What are the contributions of testing if we look at it from a value-based perspective? Fundamentally, we can consider two dimensions: The internal dimension of testing covers costs and benefits of testing. The external dimension emphasizes the opportunities and risks of the future system that have to be addressed. The key challenge in value-based testing is to integrate these two dimensions, i.e., align the internal test process with the value objectives coming from the customers and the market.

It becomes clear that a pure focus on the technical aspects of testing (e.g., the testing methods and tools) is inappropriate to align the internal and external dimensions. Instead, test management activities need to adopt a value-based perspective.

Figure 41 illustrates the external and internal dimensions of test management and their interdependencies. The internal dimension is similar to the scope of control of the test manager in the project. This dimension addresses costs from software testing practice as well as short-term and long-term benefits of testing. The external dimension considers stakeholders

and parameters outside the scope of control of the test manager. Value-based test management organizes testing to satisfy value propositions of the stakeholders and to focus the team on the most worthwhile testing targets.

The key question coming from the external view of software testing is: “How can we ensure the value objectives of the software system?” The goal is to reconcile stakeholder value propositions by focusing testing efforts on the most worthwhile parts of the software, the most important quality characteristics, and the most urgent symptoms of risks that threaten the value contribution of the project. Answering this question involves market opportunities and threats, project-specific customer value propositions, as well as costs and benefits. Please refer to Chapter 1 for details about opportunities and risks and to Chapter 7 for elicitation and reconciliation of stakeholder value propositions.

The internal view builds on the stakeholder value propositions and the test budget that represents the possible level of testing effort in a project. The key question in this view is: “How can we organize testing as an investment activity?”The goal is to achieve effective and efficient testing considering changes in development and budget reductions. Internal project stakeholders consider how plans for software development and associated testing activities can contribute to stakeholder value propositions by supplying system functionality and performance, but also by limiting the impact of project-relevant risks.

Appropriate communication is necessary to balance the external and internal dimensions of testing to assure the consistency of testing objectives with stakeholder value propositions.

Value Contribution of Testing

Compared to other development activities such as coding or user interface design, testing does not create immediate product value. Instead, testing informs and supports other value generating tasks in software development.

A key to understanding the value contribution of testing is the contribution chain of testing (see the benefits realization approach described in Chapter 1). The contribution chain establishes the relation of testing to the final product that ultimately creates value for the stakeholders. Usually, the contribution chain of testing is complex and involves several different “clients,” who benefit from testing.

Direct clients of testing are developers and project managers, who directly interact with the testing team (representing the internal dimension). However, in the spirit of value-based software engineering important parties for testing are customers and users (representing the external view). Customers and users are the source of value objectives (see Chapter 7), which set the context and scope of testing. Within this context testing informs developers and project managers to what extent value objectives are met and where improvement is required.

Clients of Testing

Developers, project managers, quality managers, customers, analysts, end users, or maintenance staff benefit from a thorough analysis of the software system and rely on feedback for detecting problems, reducing uncertainty, making decisions, or improving products and processes. The following examples show the kind of feedback from testing required by different groups: Customers and users get information as to what extent mutually agreed requirements are satisfied and to what extent the software meets their value propositions. Testing also provides visibility and insights about project progress. Passed tests reduce the odds of misbehavior and acceptance decisions are thus frequently based on the results of tests.

When acceptance tests are impractical or fail to reveal hidden problems that become visible only in real-world conditions, alpha and beta testing provide a more solid foundation for acceptance decisions.

?Marketing and product managers require information from testing for planning releases, pricing, promotion, and distribution. A gap between the actual quality and the quality expected by customers and users most certainly leads to misleading expectations and wrong assumptions that diminish or prevent value realization (Boehm, 2000b). In order to successfully manage these expectations and to satisfy individual and organizational objectives, reconciling customer needs with product design has to consider quality in addition to functionality.

?For project managers testing supports risk management and progress estimation. The focus is on identifying and eliminating risks that are potential value breakers and inhibit value achievements. Early detection of severe defects that significantly reduce project performance is a major objective. Ideally, testing reduces uncertainty and helps project managers to take better, more informed decisions, e.g., for defect removal, system stabilization, and release decisions.

?Quality managers are interested in the identification of problems and in particular problem trends. Results from testing are the input for the assessment of development performance and provide the basis for quality assurance strategies and process improvement. Rosenberg (2003) discusses how testing contributes to quality assurance and shows that problems need to be documented, corrected, and can then be used for process improvement; after assessing problem reports for their validity corrective actions are implemented in accordance with customer-approved solutions; developers and users are informed about the problem status; and data for measuring and predicting software quality and reliability is provided.

?Developers require feedback from testing to gain confidence that the implementation is complete and correct, conforming to standards, and satisfying quality requirements. For stabilization, testing provides

details about defects and their estimated severity, information for reproducing defects, and support for revealing the cause of the failures.

Besides, testing provides feedback for improvement and learning from defects. For example, throughout maintenance a detailed and reproducible description of problems contributes to the efficient implementation of changes and regression tests ensuring that these changes do not break existing functionality.

For requirements engineers, testing is valuable to validate and verify requirements. Gause and Weinberg (1989) point out that “… one of the most effective ways of testing requirements is with test cases very much like those for testing a complete system.” Deriving black-box tests from requirements helps to assure their completeness, accuracy, clarity, and conciseness early on. Tests thus enhance requirements and enable development in a test-driven manner.

To summarize, testing helps to realize benefits by reducing planning uncertainty, mitigating risks, making more informed decisions, controlling efforts, and minimizing downstream costs (the internal dimension).More importantly, it helps to realize the expected stakeholder value propositions (the external dimension).

These benefits, however, do not come for free and the costs of testing are often significant. Testing can be perceived as buying information and can be considered as an investment activity as it reduces the costs of risks, uncertainties, and the reward of taking risks. Making sound decisions about the investment in testing requires understanding their implications on both costs and benefits. The underlying questions therefore are: What are the costs of testing, and what are the benefits of testing for value generating activities?

英文文献及中文翻译

毕业设计说明书 英文文献及中文翻译 学院：专 2011年6月 电子与计算机科学技术软件工程

https://www.sodocs.net/doc/e817132847.html, Overview https://www.sodocs.net/doc/e817132847.html, is a unified Web development model that includes the services necessary for you to build enterprise-class Web applications with a minimum of https://www.sodocs.net/doc/e817132847.html, is part of https://www.sodocs.net/doc/e817132847.html, Framework,and when coding https://www.sodocs.net/doc/e817132847.html, applications you have access to classes in https://www.sodocs.net/doc/e817132847.html, Framework.You can code your applications in any language compatible with the common language runtime(CLR), including Microsoft Visual Basic and C#.These languages enable you to develop https://www.sodocs.net/doc/e817132847.html, applications that benefit from the common language runtime,type safety, inheritance,and so on. If you want to try https://www.sodocs.net/doc/e817132847.html,,you can install Visual Web Developer Express using the Microsoft Web Platform Installer,which is a free tool that makes it simple to download,install,and service components of the Microsoft Web Platform.These components include Visual Web Developer Express,Internet Information Services (IIS),SQL Server Express,and https://www.sodocs.net/doc/e817132847.html, Framework.All of these are tools that you use to create https://www.sodocs.net/doc/e817132847.html, Web applications.You can also use the Microsoft Web Platform Installer to install open-source https://www.sodocs.net/doc/e817132847.html, and PHP Web applications. Visual Web Developer Visual Web Developer is a full-featured development environment for creating https://www.sodocs.net/doc/e817132847.html, Web applications.Visual Web Developer provides an ideal environment in which to build Web sites and then publish them to a hosting https://www.sodocs.net/doc/e817132847.html,ing the development tools in Visual Web Developer,you can develop https://www.sodocs.net/doc/e817132847.html, Web pages on your own computer.Visual Web Developer includes a local Web server that provides all the features you need to test and debug https://www.sodocs.net/doc/e817132847.html, Web pages,without requiring Internet Information Services(IIS)to be installed. Visual Web Developer provides an ideal environment in which to build Web sites and then publish them to a hosting https://www.sodocs.net/doc/e817132847.html,ing the development tools in Visual Web Developer,you can develop https://www.sodocs.net/doc/e817132847.html, Web pages on your own computer.

企业创新战略外文翻译文献

企业创新战略外文翻译文献(文档含中英文对照即英文原文和中文翻译) 翻译之一： Choosing an innovation strategy: theory and practice Author：Joseph T. Gilbert Nationality：America Derivation：Business Horizons, Nov-Dec, 1994 Innovations come as both inventions and adoptions. They come in many types and vary greatly in complexity and scope. Companies attempting to

make a profit cannot continue for long periods without innovating. If they try, their customers will leave them for firms with more up-to-date products or services. It is an observed fact that different companies take different approaches to the use of innovation in attempting to improve their performance. Both academic and practitioner publications in recent years have contained a great deal of writing about innovation, the subjects of which have ranged from comparisons of national patterns of innovation to studies of individual innovations. However, little has been published regarding one issue of both theoretical and practical importance: the innovation policy or strategy of individual firms. Business strategy as a field of study is concerned with how a company competes in its chosen business. It deals with the analysis of a firm's strengths and weaknesses and the opportunities and threats presented by the firm's environment. Strategy looks toward consistent execution of broad plans to achieve certain levels of performance. Innovation strategy determines to what degree and in what way a firm attempts to use innovation to execute its business strategy and improve its performance. To choose an innovation strategy, managers might logically start by thinking about various kinds of innovations and their requirements. We shall discuss three major features of innovation, and analyze each in terms of distinct opposites, even though innovations found in the real world more often appear at various points between these opposites. Innovation is sometimes used in a limited sense to refer only to inventions (products, services, or administrative procedures that no other firm has introduced). More often, however, it applies in a more general sense that includes both invention as described above and imitation (adoption by a firm of a product, service, or administrative procedure that is not an invention but is new to that firm). We use the term in this second sense. Innovations can be characterized in a variety of ways. In the following

酒店服务质量管理外文文献翻译

文献出处：Borkar S, Koranne S. Study of Service Quality Management in Hotel Industry [J]. Pacific Business Review International, 2014, 6(9): 21-25. 原文 Study of Service Quality Management in Hotel Industry Borkar; Sameer Abstract It is an attempt to understand the role of quality improvement process in hospitality industry and effectiveness in making it sustainable business enterprise. It is a survey of the presently adopted quality management tools which are making the hotels operations better focused and reliable and meet the customer expectations. Descriptive research design is used to know the parameters of service quality management in hospitality industry. Exploratory research design is undertaken to dig out the service quality management practices and its effectiveness. Data analysis is done and presented; hypothesis is tested against the collected data. Since the industry continuously tries to improve upon their services to meet the levels of customer satisfaction; Study presents tools for continuous improvement process and how it benefits all the stake holders. It can be inferred from the study that the hotel implement continuous improvement process and quality management tools to remain competitive in the market. The study involves hotels of highly competitive market with limited number of respondents. This limits the study to hotel industry and has scope of including other hospitality service providers as well. Keywords:Customer Satisfaction, Perception, Performance Measurement, Continuous, Improvement Process. Introduction It has brought paradigm shifts in the operations of hospitality industry. The overall perspective of the industry is changed due to introduction of new techniques

软件工程专业BIOS资料外文翻译文献

软件工程专业BIOS资料外文翻译文献 What is the Basic Input Output System (BIOS)? BIOS is an acronym for Basic Input Output System. It is the program that stores configuration details about your computer hardware and enables your computer to boot up. Every time your computer is switched on the BIOS loads configuration data into main memory, performs a routine diagnostic test on your hardware, then loads the operating system. The BIOS resides in a ROM (Read-Only memory) chip, which is mounted on the motherboard, usually in a socket so it is removable. To the right is an example of what a BIOS chip may look like in your motherboard. This is a PLCC 32 pin type BIOS chip. It is a very common type. Every computer has BIOS. There are many types but the most common type of BIOS 's come from: AMI, Award and Phoenix. Motherboard manufacturers buy or lease the BIOS source code from these companies. The BIOS tells the operating system in your computer how to boot up, where to load everything, what to load, what memory and CPU are present and much more. A good comparison to further understand the

中小型企业人才流失开题报告

重庆大学网络教育学院 学生毕业设计（论文）开题报告 一、课题的目的及意义（含国内外的研究状况分析）： 近年来，随着国民经济的发展，市场竞争日益加大，再加上中国加入世贸组织，国 门逐渐打开，越来越多的国外企业在中国的市场上发展壮大，抢夺市场占有份额，对国内企业 造成了很大的冲击，特别是中小企业更难立足和发展，因此提高我们企业的竞争力迫在眉睫。 我们都是知道人才对于企业的生存和发展都有着重要的意义，并起着越来越重要的作用， 尤其对于我国的中小企业而言，由于其财力、物力有限，不可能与大企业比资金、比实力，因 而人才，尤其是优秀的人才对我国的中小企业的生存与发展就有着决定性的作用。但是，由于 社会、历史和自身等诸多因素的影响，人才在我国的中小企业中往往难以发挥自己的才能，人 才流失现象相当严重，往往自己培养的核心员工成为别人的得意助手，给企业带来了不可估量 的损失。中小企业如果想要获得长足发展必须在人才方面下功夫，应该将人才战略作为整个 企业发展战略的核心，但是中小企业在人才引进、聘用、培育、留守方面存在着种种的不利和 弊端，这些直接导致了企业请进了人才而又留不住人才的尴尬局面的出现。因此如何留住人才， 如何解决人才流失这一问题就显得尤为必要。 二、课题任务、重点研究内容、实现途径、条件： 本文主要利用文献研究方法，通过多种途径收集有关中小企业人才流失现状及对策的文献 资料。主要包括相关著作、期刊杂志以及相关网站查找资料，收集数据等多个关于人才流失的 的相关著作及论文，收集我国关于中小企业相关的文献资料及法律法规等。通过搜集和整理大 量的与中小企业人才流失相关的资料，在指导老师的指导和帮助下，分析中小企业在人力资源 管理中的人才流失问题，找出原因，并结合自己所学的知识、收集的资料并整理消化写成论文。 通过新颖的论点和想法来提出自己论文的创新点，并运用所学习的知识来补充和加工。本文 先阐述课题背景和目的，从而引出人才流失的研究现状，结合现状并运用课题的研究方法来分

营销策略外文翻译文献

营销策略外文翻译文献 (文档含中英文对照即英文原文和中文翻译)

译文: 营销策略 内容提要：为了组织的销售能是成功的，它需要根据一个营销策略计划来帮助保证其努力的目标和宗旨与市场的需要想吻合。营销策略审查市场以确定潜在顾客的需要，竞争者的战略和市场地位，并且尝试制定出一套能使组织在市场上获取或维护竞争优势的相关战略。有一些因素会对营销策略计划的发展造成冲击性的影响，它包括内部因素例如组织的财产、技能和组织文化，外在因素例如各种各样的市场驱动者、市场或产业运作方式、战略窗口和竞争的本质。一个优选的营销策略计划也需具备一套意外情况防备策略以应对市场治理及组织生产能力的不确定性。 关键词：竞争优势竞争策略市场地位市场份额营销销售计划组织文化营销策略 营销策略简述 无论组织的产品或服务多么好，除非它们的价值能被传达给潜在的顾客，否则组织依然无法实现它的使命。这种传达和交流是组织内市场营销功能的职责。根据美国市场协会，营销是“一个组织效能和一套创造过程、交流和传达产品价值给顾客、处理与顾客关系的有益于组织和它的利益共享者的方式”。营销作用包括相辅相成的两方面。营销策略在市场上审查市场来确定潜在顾客和竞争者本质的需要，并且试图开发

出在市场上将使组织获取或维护竞争优势的战略。操作的营销被建立在营销策略作用和贯彻各种各样的计划和策略(包括适当的混合营销的发展)吸引顾客和促进顾客忠实的基础之上的。 产品和服务营销的方法 有很多的方式能用来销售你的产品或服务包括做广告，直接响应、推销活动和宣传。然而，除非你能了解顾客、市场和产业的需要并且竞争的优势和劣势，否则这些方法是不太可能成功的。营销策略帮助一个组织尖化它的焦点和在市场顺利地竞争。营销策略与二个组分有关：目标市场和用最佳的方式传达你的产品价值或服务到那个市场。一个可实行的销售方针的发展取决于几个关键维度。首先，与组织之内的所有全球性战略一样，一个成功的销售方针需要由在组织之内的最高管理层签名。销售方针本质上也具有政治性的色彩：在组织之内的强有力的单位在最佳的销售方针也许不同意，并且协议也许需要谈判达成。销售方针也许受组织文化的也影响，并且那得假定这发生。例如，如果组织总是销售它的装饰物给商业主管，它也许就看不到组织之内的低层人员甚至是成人或少年的个人消费潜力。 实施战略销售计划发展的因素 存在一些能冲击战略销售计划发展的因素，这些因素首先包括组织已经拥有或它可能欣然获取的财产和技能。例如，如果组织拥有一个重大编程的部门，就为它能做和销售应用软件提供了可行性的条件。然而，如果这些人员已经在其他工作介入并且不能自由研究一个新的软件项目，并且组织没能力聘用另外的程序员，起始一条新的软件线是不妥当

供应商质量管理文献翻译(外文翻译-中英对照)

互利共赢的供应商质量控制 前言 近年来，随着对供应链的重视，供应商管理正逐渐成为企业和学术界的关注对象，IS0９000族标准以及QS 9０00标准都对供应商的管理提出了相应的要求，与供应商管理有关的研究成果正逐渐增多，一些软件巨头也推出了供应商关系管理的软件，但是在这些研究成果和应用软件中，涉及到的供应商质量控制的内容只是一些最基本的要求，而供应商质量控制恰恰是供应商管理的最基本、最重要的内容。另一方而，质量管理界对质量控制的研究取得了大量的成果，遗憾的是这些成果大多依然局限于企业的内部控制，仅仅研究从企业内部各环节如何改善产品的质量，而基于供应链的角度来研究质量控制的成果尚不多见。因此，系统地研究经济全球化形势下供应商质量控制的理论与方法，将有助于推动我国企业产品质量的快速提高和供应链竞争优势的形成与巩固。 1、质量与企业共存 质量一直是一个随着时代的变化而不断变化的概念,人们对质量的认识也往往因关注点不同而有所不同。如，早在1908年，通用汽车公司的工程师们在皇家汽车俱乐部会员们的面前拆解了3辆凯迪拉克轿车，并把这些零件混在一起,而后从中选择零件重新组装成车，然后驾车绝尘而去。这令在场的会员极为震惊，认为凯迪拉克车质量之高令人惊叹。显然在当时，汽车零件具有互换性是一种了不起的质量特性,这也是福特公司的Ｎ型车和T型车取得辉煌成功的重要原因.时至今日，即使农用三轮车的零部件也具有极高的互换性，零部件的标准化和互换性已经是理所当然的事情，不再是吸引顾客的重要质量特性.可见质量的内涵是不断变化的.那么究竟什么是质量呢？ （１)市场竟争就是企业间对“顾客”的争夺，在日益激烈的“顾客"争夺战中，质量、价格、交付（交付日期、方式和手段）和服务是企业常用的四个法宝，其中质量是根本，离开质量其他三项将变得毫无意义，因此可以说质量己成为市场竞争的焦点.它反映了产品是否能够反映顾客需求、能否满足顾客需求，从面决定了产品的市场前途。有鉴于此，质量己成为一项全球性运动,世界上所有优秀企业无一不把质量作为企业战略的关键内容，从战略的角度来规划质量。 （2）对于企业经营者来说,认识到质量对企业的重要意义只是经营企业的第一步,重要的是如何利用科学的方法来保证产品和服务的质量，使顾客满意，来保证过程和工作的质量来获互利共炭的供应商质量控制得良好的业绩。 众所周知,企业管理是社会生产力发展到一定程度的历史产物,质量管理作为企业管理的组成部分,同样也是社会发展的客观要求，特别是顾客处于主导地位的今天,要使顾客满意，就必须有过硬的产品质量和服务质量，这就要求企业积极推行先进的质量管理理论与方法，不断进行质量管理创新. ２、企业与供应商质量控制 随着生产社会化的不断发展，企业的生产活动分工越来越细,专业化程度越来越强，促使生产技术水平越来越高,产品质量得到大幅度改善。通常，某一产品不可能由一个企业从最初的原材料开始加工直至形成顾客最终使用的产品，往往是通过多个企业分工协作来完成.另外，先进生产方式的广泛应用,如准时生产、敏捷制造、零库存等，使企业与供应商的关系愈加紧密，企业与供应商的关系也由单纯的买卖关系向互利共底的合作关系演变。 ISO 900０族标准自1987年诞生以来受到了世界各国的一致追捧,全球约５0多万家企业通过ISO90０1质量管理体系认证足以说明这套管理标准在引领国际管理潮流方面的巨大成功。在备受企业欢迎的新版标准ＩSO9000：2０00中，互利的供应商关系被作为八项质量管理原则之一，充分体现了供应商关系管理在企业经营实践中的作用和价值。企业要贯彻这一原则,就必须

软件工程中英文对照外文翻译文献

中英文对照外文翻译 (文档含英文原文和中文翻译) Application Fundamentals Android applications are written in the Java programming language. The compiled Java code — along with any data and resource files required by the application — is bundled by the aapt tool into an Android package, an archive file marked by an .apk suffix. This file is the vehicle for distributing the application and installing it on mobile devices; it's the file users download to their devices. All the code in a single .apk file is considered to be one application. In many ways, each Android application lives in its own world: 1. By default, every application runs in its own Linux process. Android starts the process when any of the application's code needs to be executed, and shuts down the process when it's no longer needed and system resources are required by other applications. 2. Each process has its own virtual machine (VM), so application code runs in isolation from the code of all other applications. 3. By default, each application is assigned a unique Linux user ID. Permissions are set so that the application's files are visible only to that user and only to the application itself — although there are ways to export them to other applications as well. It's possible to arrange for two applications to share the same user ID, in which case they will be able to see each other's files. To conserve system resources, applications with the same ID can also arrange to run in the same Linux process, sharing the same

文献翻译 (2)

对行销售人员激励机制分析 1激励机制的描述 1.1激励理论主要是研究激发人们行为动机的各种因素。由于人类行为 的原动力是需要，因此这种理论实际上就是围绕着人们的各种需要来进行研究。主要包括马斯洛的赫茨伯格的双因素理论、奥尔德弗的“ERG”理论、需要层次理论和麦克利兰的成就需要激励理论。 1.2 过程型激励理论重点研究人从动机产生到采取行动的心理过程。 包括亚当斯的公平理论、佛隆的期望理论和斯金纳的强化理论。 二对行销售人员激励机制分析 美国心理学家佛隆在1964年首先提出期望理论，人之所以能够完成某项工作并达成组织目标，因为这些组织目标和工作会帮助他们达成自己的目标。根据期望理论，某一活动对某人的激发力量取决于他所能得到的结果的全部预期价值乘以他认为达成该结果的期望概率。这就要求要处理好三个方面的关系：绩效与奖励的关系、努力与绩效的关系、奖励与个人需要的关系，任何一个环节都不能出现问题，否则都会导致无效激励。 从以期望理论为代表的过程型激励理论与内容型激励理论的观点来看，激励过程的科学性和合理性、激励手段对销售人员个性化需求的满足程度构成了激励的两要素。由此看出，销售人员的激励机制确实有改进的必要。 三销售人员激励体制中不足原因 3.1激励方式单一，过分依靠货币等物质激励手段而忽视精神激励的重要作用，销售人员没有归属感，缺少团队凝聚力。即使在物质激励方面，也是“佣金制”和“提成制”的天下，收入的多少完全依据销售额或利润额的多少，无视死去差异和个人实际努力程度，激励不公现象十分普遍。 3.2晋升制度僵硬，论资排辈，讲资历而忽视能力，讲关系而忽视业务水平，人浮于事，优秀人才流失严重，已不再适应市场竞争的需要。 3.3多数企业没有完整的培训激励机制，企业只注重“挖人”而非培养，因而满足不了销售人员自我发展的需要。

战略管理参考文献

战略管理研究参考文献 （总目录） 项保华2003-5-31 重要说明：本目录经过多届博士生的共同努力，于2003年5月整理完成，主要提供本人指导的战略管理研究方向的博士生学习参考之用。可以认为，只要通读了本目录的大部分文献，必将能够对战略管理领域的当前及经典理论、方法有比较系统的把握。若能在此基础上潜心感悟，加强与同行的交流探索，定可具备解决具体战略理论与实践问题的创新思路与实用技能，从而顺利完成博士学位论文的选题与撰写。作为战略管理研究方向博士生培养的业务目标定位为，通过对战略理论与实践的系统学习，达到胜任国内重点高等院校战略领域的教学、研究、咨询工作之要求。所以，对于硕士生以及非战略管理研究方向的博士生而言，不作全面通读本目录文献之要求，各位可以根据自己的兴趣，从本目录中选取部分文献阅读，以作为参与战略课程学习之补充。 学习建议：以具体老师为师的范围终有限，而以文献为师则可延请古今中外名家赐教，广泛借鉴吸收多方面的见解。多读、多思、多写，书山无路勤为径，以学为乐恒则成！谨以此与各位共勉！ 1、中文部分 为人经世 ?孔子, 论语（网上下载） ?老子, 道德经（网上下载） ?孙子, 孙子兵法（网上下载） ?马基雅维里（1469-1527）, 君主论, 中国社会出版社, 1999 ?葛拉西安（1601-1658）, 智慧书——永恒的处世经典（网上下载） ?何兆武, 西方哲学精神, 清华大学出版社, 2002 ?墨顿·亨特, 心理学的故事, 海南人民出版社, 1999 ?维克托·E.弗兰克尔, 人生的真谛, 中国对外翻译出版公司, 1994

? E. 迈尔, 生物学思想发展的历史, 四川教育人民出版社, 1990（网上下载） ?威尔逊, 新的综合：社会生物学（李昆峰编译）, 四川人民出版社, 1985（网上下载） 战略总论 ?项保华, 战略管理——艺术与实务（第3版）, 华夏出版社, 2003 ?明茨伯格等, 战略历程：纵览战略管理学派, 机械工业出版社, 2002 ?拜瑞·J·内勒巴夫；亚当·M·布兰登勃格, 合作竞争（Co-Opetition）, 安徽人民出版社, 2000 ?迈克尔·波特, 竞争战略（原著1980年出版）, 华夏出版社, 2003 ?迈克尔·波特, 竞争优势（原著1985年出版）, 华夏出版社, 2003 ?迈克尔·波特, 国家竞争优势（原著1990年出版）, 华夏出版社, 2002 ?迈克尔·波特等, 未来的战略, 四川人民出版社, 2000 ?格里·约翰逊；凯万·斯科尔斯, 公司战略教程, 华夏出版社, 1998 ?小乔治·斯托尔克等, 企业成长战略, 中国人民大学出版社、哈佛商学院出版社, 1999 专题探讨 ?保罗·索尔曼、托马斯·弗利德曼, 企业竞争战略, 中国友谊出版公司, 1985 ?罗伯特·艾克斯罗德, 对策中的制胜之道：合作的进化, 上海人民出版社, 1996 ?约瑟夫·巴达拉克, 界定时刻——两难境地的选择, 经济日报出版社、哈佛商学院出版社, 1998 ?芝加哥大学商学院、欧洲管理学院、密歇根大学商学院、牛津大学赛德商学院, 把握战略：MBA战略精要, 北京大学出版社, 2003 ?哈默尔、普拉哈拉德, 竞争大未来, 昆仑出版社, 1998 ?尼尔·瑞克曼, 合作竞争大未来, 经济管理出版社, 1998 ?卡尔·W.斯特恩、小乔治·斯托克, 公司战略透视, 上海远东出版社, 1999 ?乔尔·布利克、戴维·厄恩斯特, 协作型竞争, 中国大百科全书出版社, 1998

质量管理文献综述

关于企业质量管理文献综述 摘要：随着新世纪的到来，特别是我国加入WTO后，中国将进一步融入世界经济的主流，质量将成为我国广大企业抓住机遇、迎接严峻挑战的关键。要拓展海外市场，必须靠有竞争力的质量；要保护国内的市场，不再有高关税和政府的过渡保护，也要靠质量的较量。随着科学技术的进步，质量管理的理论和方法有了更大发展。本文综合了质量管理的发展历程，并简要评价，提出看法，以便为企业的质量管理和理论研究提供参考。 关键词：质量管理、管理改进 21世纪是质量的世纪”。随着经济全球化和信息革命的迅猛发展，竞争日益加剧。在“数量”问题已解决的今天，人们将越来越追求和依赖于高质量的产品和服务，而且质量的领域不断拓宽，生活的质量、环境的质量、文化的质量、经济增长的质量更加受到全社会的关注。质量已成为竞争的焦点，不仅关系到企业的生存发展，而且影响到国家经济实力的增强和民族的形象。质量已成为全球经济发展战略的核心问题。 一、质量管理理论的回顾 （一）、质量管理的发展阶段 （1）质量检验阶段（20世纪20-30年代） 生产力迅猛发展，生产过程分工细化、日益复杂，许多美国企业按照泰勒的管理模式，纷纷设立检验部门，使检验与生产分离开来，其最大特点为“事后把关”。（2）统计质量阶段（20世纪40-50年代） 早在20世纪20年代，美国贝尔实验室工程师休哈特就提出“控制与预防缺陷”的概念。主要是利用数理统计原理，预防产生废品并检验产品质量，在方式上由专业质量控制工程师和技术人员承担。但这种方法只是保证生产过程中的产品质量，而不能提高产品本身的质量。 （3）全面质量管理阶段（20世纪60年代至今） 美国的费根堡姆提出，“全面质量是为了能够在最经济的水平上，并考虑到充分满足顾客要求的条件下进行生产和提供服务，将企业各部门研制质量、维持质量和提高质量的活动构成为一体的一种有效体系”。 （二）、质量管理的理论流派 1、事后检验 20世纪，美国工程师泰勒提出“科学管理理论”，1911 年泰勒出版了专

软件工程论文参考文献

软件工程论文参考文献 [1] 杜献峰 . 基于三层 B/S 结构的档案管理系统开发 [J]. 中原工学院学报，2009:19-25 [2]林鹏，李田养. 数字档案馆电子文件接收管理系统研究及建设[J].兰台世界，2008:23-25 [3]汤星群.基于数字档案馆建设的两点思考[J].档案时空，2005:23-28 [4]张华丽.基于 J2EE 的档案管理系统设计与实现[J].现代商贸工业. 2010:14-17 [5] 纪新.转型期大型企业集团档案管理模式研究[D].天津师范大学，2008：46-57. [6] 周玉玲.纸质与电子档案共存及网络环境电子档案管理模式[J].中国科技博览，2009：44-46. [7] 张寅玮.甘肃省电子档案管理研究[D]. 兰州大学，2011:30-42 [8] 惠宏伟.面向数字化校园的档案信息管理系统的研究与实现[D]. 电子科技大学，2006:19-33 [9] 刘冬立.基于 Web 的企业档案管理系统的设计与实现[D].同济大学，2007:14-23 [10]钟瑛.浅议电子文件管理系统的功能要素[J]. 档案学通讯，2006:11-20 [11] 刘洪峰，陈江波.网络开发技术大全[M].人民邮电出版社，2005：119-143. [12] 程成，陈霞.软件工程[M].机械工业出版社，2003：46-80. [13] 舒红平.Web 数据库编程-Java[M].西安电子科技大学出版社，2005：97-143. [14] 徐拥军.从档案收集到知识积累[M].是由工业出版社，2008：6-24. [15]Gary P Johnston，David V. Bowen.he benefits of electronic recordsmanagement systems: a general review of published and some unpublishedcases. RecordsManagement Journal，2005:44-52 [16]Keith Gregory.Implementing an electronic records management system: Apublic sector case study. Records Management Journal，2005:17-21 [17]Duranti Luciana.Concepts，Principles，and Methods for the Management of Electronic RecordsR[J].Information Society，2001：57-60.

第三方物流问题战略外文翻译文献

第三方物流问题战略外文翻译文献 (文档含英文原文和中文翻译) 我国第三方物流中存在的问题、原因及战略选择 【摘要】我国物流业发展刚刚起步，第三方物流的理论和实践等方面都比较薄弱。本文指出我国第三方物流存在的问题在于国内外第三方物流企业差距、物流效率不高、缺乏系统性管理、物流平台构筑滞后、物流管理观念落后等。分析了产生上述问题的原因，并提出了精益物流、中小型第三方物流企业价值链联盟、大型第三方物流企业虚拟化战等三种可供选择的第三方物流企业发展战略。【关键词】第三方物流；精益物流战略；价值链联盟；虚拟化战略 1引言 长期以来，我国国内企业对采购、运输、仓储、代理、包装、加工、配送等

环节控制能力不强，在“采购黑洞”、“物流陷井”中造成的损失浪费难以计算。因此，对第三方物流的研究，对于促进我国经济整体效益的提高有着非常重要的理论和实践意义。本文试图对我国策三方物流存在的问题及原因进行分析探讨，并提出第三方物流几种可行的战略选择。 2 我国第三方物流业存在的主要问题 (一)我国策三方物流企业与国外第三方物流企业的差距较大，具体表现在以下几个方面： 1、规模经济及资本差距明显。由于国外的大型第三方物流企业从全球经营的战略出发，其规模和资本优势是毫无疑问的，尤其初创时期的我国策三方物流业，本身的规模就很小，国外巨头雄厚的资本令国内企业相形见绌。 2、我国策三方物流业企业提供的物流服务水准及质量控制远不如国外同行。当国内一些企业还在把物流理解成“卡车加仓库“的时候，国外的物流企业早已完成了一系列标准化的改造。同时，国外的物流组织能力非常强大，例如德国一家第三方物流公司，公司各方面的物流专家遍布欧洲各地。如果有客户的货物需要经达不同的国家，那么欧洲各地的这些专家就在网上设计出一个最佳的物流解决方案。这种提供解决方案的能力就是这第三方物流公司的核心能力，而不像国内公司号称拥有多少条船，多少辆车。 3、我国加入 WTO 后物流产业的门槛降低。在物流服务业方面：我国承诺所有的服务行业，在经过合理过渡期后，取消大部分外国股权限制，不限制外国服务供应商进入目前的市场，不限制所有服务行业的现有市场准入和活动。同时在辅助分销的服务方面也作出了类似的承诺。这些方面的限制将在以后 3—4 年内逐步取消，在此期间，国外的服务供应商可以建立百分之百的全资拥有的分支机构或经营机构，国内物流服务业将直面国际竞争。 (二)资源浪费严重，第三方物流效率不高。 从微观上看，由于受计划经济体制的影响，长期以来许多企业，尤其是国有企业走的是“大而全”、“小而全”的路子，它们拥有自己的仓库、车队、甚至远洋船队，造成物流过程的大量浪费，具体表现为仓库的闲置，物流业经营分散，组织化程度低，横向联合薄弱。而能够提供一体化、现代化、专业化、准时化、高效服务的第三方物流企业则很少。从宏观上看第三方物流未能跟上经

外文翻译--《软件工程-实践者的研究方法》

附录 Software Engineering-A PRACTITIONER’S APPROACH Written by Roger S. Pressman, Ph.D. （P.340-P.343） 13.3DESIGN PRINCIPLES Software design is both a process and a model. The design process is a sequence ofsteps that enable the designer to describe all aspects of the software to be built. It is important to note, however, that the design process is not simply a cookbook. Creative skill, past experience, a sense of what makes “good” software, and an overallcommitment to quality are critical success factors for a competent design. The design model is the equivalent of an architect’s plans for a house. It begins by representing the totality of the thing to be built (e.g., a three-dimensional renderingof the house) and slowly refines the thing to provide guidance for constructing eachdetail (e.g., the plumbing layout). Similarly, the design model that is created for softwareprovides a variety of different views of the computer software. Basic design principles enable the software engineer to navigate the design process.Davis suggests a setof principles for software design, which have beenadapted and extended in the following list: ? The design process should not suffer from “tunnel vision.” A gooddesigner should consider alternative approaches, judging each based on therequirements of the the resources available to do the job, and thedesign concepts presented in Section ? The design should be traceable to the analysis model. Because a singleelement of the design model often traces to multiple requirements, it is necessaryto have a means for tracking how requirements have been satisfied bythe design model. ? The design should not reinvent the wheel. Systems are constructed usinga set of design patterns, many of which have likely been encountered before.These patterns should always be chosen as an alternative to reinvention.Time is short and resources are limited! Design time should be invested inrepresenting truly new ideas and integrating those patterns that already exist. ? The design should “minimize the intellectual distance” between the software and the problem as it exists in the real world.That is, the structure of the software design should (whenever possible)mimic the structure of the problem domain.