JDBCSpring外文翻译
毕业设计（论文）
外文文献翻译
系别：XXXXXXXXXXXX
专业：XXXXXXXXXXXX
班级：XXXXXXXXXXXX
学生姓名：XXX
导师姓名：XXXX职称：XXXX
起止时间：2009年3月2日至2009年6月12 日
英文原文
Spring contains a lot of functionality and features, which are well-organized in seven modules shown in the diagram below. This section discusses each the of modules in turn.
The Core package is the most fundamental part of the framework and provides the Dependency Injection features allowing you to manage bean container functionality. The basic concept here is the BeanFactory, which provides a factory pattern removing the need for programmatic singletons and allowing you to decouple the configuration and specification of dependencies from your actual program logic.
On top of the Core package sits the Context package, providing a way to access beans in a framework-style manner, somewhat resembling a JNDI-registry. The context package inherits its features from the beans package and adds support for text messaging using e.g. resource bundles, event-propagation, resource-loading and transparent creation of contexts by, for example, a servlet container.
The DAO package provides a JDBC-abstraction layer that removes the need to do tedious JDBC coding and parsing of database-vendor specific error codes. Also, the JDBC package provides a way to do programmatic as well as declarative transaction management, not only for classes implementing special interfaces, but for all your POJOs (plain old java objects).
The ORM package provides integration layers for popular object-relational mapping APIs, including JDO, Hibernate and iBatis. Using the ORM package you can use all those O/R-mappers in combination with all the other features Spring offers, like simple declarative transaction management mentioned before.
Spring's AOP package provides an AOP Alliance compliant aspect-oriented programming implementation allowing you to define, for example, method-interceptors and pointcuts to cleanly decouple code implementing functionality that should logically speaking be separated. Using source-level metadata functionality you can incorporate all kinds of behavioral information into your code, a little like .NET attributes.
Spring's Web package provides basic web-oriented integration features, such as multipart functionality, initialization of contexts using servlet listeners and a web-oriented application context. When using Spring together with WebWork or Struts, this is the package to integrate with.
Spring's Web MVC package provides a Model-View-Controller implementation for web-applications. Spring's MVC implementation is not just any implementation, it provides a clean separation between domain model code and web forms and allows you to use all the other features of the Spring Framework like validation.
Spring's web MVC framework is designed around a DispatcherServlet that dispatches requests to handlers, with configurable handler mappings, view resolution, locale and theme resolution as well as support for upload files. The default handler is a very simple Controller interface, just offering a ModelAndView handleRequest(request,response) method. This can already be used for application controllers, but you will prefer the included implementation hierarchy, consisting of, for example AbstractController, AbstractCommandController and SimpleFormController. Application controllers will typically be subclasses of those. Note that you
can choose an appropriate base class: If you don't have a form, you don't need a FormController. This is a major difference to Struts.
You can use any object as a command or form object - there's no need to implement an interface or derive from a base class. Spring's data binding is highly flexible, for example, it treats type mismatches as validation errors that can be evaluated by the application, not as system errors. So you don't need to duplicate your business objects' properties as Strings in your form objects, just to be able to handle invalid submissions, or to convert the Strings properly. Instead, it is often preferable to bind directly to your business objects. This is another major difference to Struts which is built around required base classes like Action and ActionForm - for every type of action.
Compared to WebWork, Spring has more differentiated object roles. It supports the notion of a Controller, an optional command or form object, and a model that gets passed to the view. The model will normally include the command or form object but also arbitrary reference data. Instead, a WebWork Action combines all those roles into one single object. WebWork does allow you to use existing business objects as part of your form, but only by making them bean properties of the respective Action class. Finally, the same Action instance that handles the request is used for evaluation and form population in the view. Thus, reference data needs to be modeled as bean properties of the Action too. These are arguably too many roles for one object.
Spring's view resolution is extremely flexible. A Controller implementation can even write a view directly to the response, returning null as ModelAndView. In the normal case, a ModelAndView instance consists of a view name and a model Map, containing bean names and corresponding objects (like a command or form, containing reference data). View name resolution is highly configurable, either via bean names, via a properties file, or via your own ViewResolver implementation. The abstract model Map allows for complete abstraction of the view technology, without any hassle. Any renderer can be integrated directly, whether JSP, V elocity, or any other rendering technology. The model Map is simply transformed into an appropriate format, such as JSP request attributes or a Velocity template model..
Pluggability of other MVC implementations
There are several reasons why some projects will prefer to use other MVC implementations. Many teams expect to leverage their existing investment in skills and tools. In addition, there is a large body of knowledge and experience avalailable for the Struts framework. Thus, if you can live with Struts' architectural flaws, it can still be a viable choice for the web layer. The same applies to WebWork and other web MVC frameworks.
If you don't want to use Spring's web MVC, but intend to leverage other solutions that Spring offers, you can integrate the web MVC framework of your choice with Spring easily. Simply start up a Spring root application context via its ContextLoaderListener, and access it via its ServletContext attribute (or Spring's respective helper method) from within a Struts or WebWork action. Note that there aren't any "plugins" involved, so no dedicated integration is necessary. From the web layer's point of view, you'll simply use Spring as a library, with the root application context instance as the entry point.
All your registered beans and all of Spring's services can be at your fingertips even without
Spring's web MVC. Spring doesn't compete with Struts or WebWork in this scenario, it just addresses the many areas that the pure web MVC frameworks don't, from bean configuration to data access and transaction handling. So you are able to enrich your application with a Spring middle tier and/or data access tier, even if you just want to use, for example, the transaction abstraction with JDBC or Hibernate.
Features of Spring MVC
Spring's web module provides a wealth of unique web support features, including:
Clear separation of roles - controller, validator, command object, form object, model object, DispatcherServlet, handler mapping, view resolver, etc. Each role can be fulfilled by a specialized object.
Powerful and straightforward configuration of both framework and application classes as JavaBeans, including easy referencing across contexts, such as from web controllers to business objects and validators.
Adaptability, non-intrusiveness. Use whatever controller subclass you need (plain, command, form, wizard, multi-action, or a custom one) for a given scenario instead of deriving from a single controller for everything.
Reusable business code - no need for duplication. You can use existing business objects as command or form objects instead of mirroring them in order to extend a particular framework base class.
Customizable binding and validation - type mismatches as application-level validation errors that keep the offending value, localized date and number binding, etc instead of String-only form objects with manual parsing and conversion to business objects.
Customizable handler mapping and view resolution - handler mapping and view resolution strategies range from simple URL-based configuration, to sophisticated, purpose-built resolution strategies. This is more flexible than some web MVC frameworks which mandate a particular technique.
Flexible model transfer - model transfer via a name/value Map supports easy integration with any view technology.
Customizable locale and theme resolution, support for JSPs with or without Spring tag library, support for JSTL, support for Velocity without the need for extra bridges, etc.
A simple but powerful tag library that avoids HTML generation at any cost, allowing for maximum flexibility in terms of markup code.
Data Access using O/R Mappers
Spring provides integration with Hibernate, JDO, Oracle TopLink, Apache OJB and iBATIS SQL Maps: in terms of resource management, DAO implementation support, and transaction strategies. For example for Hibernate, there is first-class support with lots of IoC convenience features, addressing many typical Hibernate integration issues. All of these support packages for O/R mappers comply with Spring's generic transaction and DAO exception hierarchies. There are usually two integration styles: either using Spring's DAO 'templates' or coding DAOs against plain Hibernate/JDO/TopLink/etc APIs. In both cases, DAOs can be configured through Dependency
Injection and participate in Spring's resource and transaction management.
Spring's adds significant support when using the O/R mapping layer of your choice to create data access applications. First of all, you should know that once you started using Spring's support for O/R mapping, you don't have to go all the way. No matter to what extent, you're invited to review and leverage the Spring approach, before deciding to take the effort and risk of building a similar infrastructure in-house. Much of the O/R mapping support, no matter what technology you're using may be used in a library style, as everything is designed as a set of reusable JavaBeans. Usage inside an ApplicationContext does provide additional benefits in terms of ease of configuration and deployment; as such, most examples in this section show configuration inside an ApplicationContext.
Some of the the benefits of using Spring to create your O/R mapping DAOs include:
Ease of testing. Spring's inversion of control approach makes it easy to swap the implementations and config locations of Hibernate SessionFactory instances, JDBC DataSources, transaction managers, and mapper object implementations (if needed). This makes it much easier to isolate and test each piece of persistence-related code in isolation.
Common data access exceptions.Spring can wrap exceptions from you O/R mapping tool of choice, converting them from proprietary (potentially checked) exceptions to a common runtime DataAccessException hierarchy. This allows you to handle most persistence exceptions, which are non-recoverable, only in the appropriate layers, without annoying boilerplate catches/throws, and exception declarations. You can still trap and handle exceptions anywhere you need to. Remember that JDBC exceptions (including DB specific dialects) are also converted to the same hierarchy, meaning that you can perform some operations with JDBC within a consistent programming model.
General resource management. Spring application contexts can handle the location and configuration of Hibernate SessionFactory instances, JDBC DataSources, iBATIS SQL Maps configuration objects, and other related resources. This makes these values easy to manage and change. Spring offers efficient, easy and safe handling of persistence resources. For example: Related code using Hibernate generally needs to use the same Hibernate Session for efficiency and proper transaction handling. Spring makes it easy to transparently create and bind a Session to the current thread, either by using an explicit 'template' wrapper class at the Java code level or by exposing a current Session through the Hibernate SessionFactory (for DAOs based on plain Hibernate3 API). Thus Spring solves many of the issues that repeatedly arise from typical Hibernate usage, for any transaction environment (local or JTA).
Integrated transaction management. Spring allows you to wrap your O/R mapping code with either a declarative, AOP style method interceptor, or an explicit 'template' wrapper class at the Java code level. In either case, transaction semantics are handled for you, and proper transaction handling (rollback, etc) in case of exceptions is taken care of. As discussed below, you also get the benefit of being able to use and swap various transaction managers, without your Hibernate/JDO related code being affected: for example, between local transactions and JTA, with the same full services (such as declarative transactions) available in both scenarios. As an additional benefit,
JDBC-related code can fully integrate transactionally with the code you use to do O/R mapping. This is useful for data access that's not suitable for O/R mapping, such as batch processing or streaming of BLOBs, which still needs to share common transactions with O/R mapping operations.
To avoid vendor lock-in, and allow mix-and-match implementation strategies. While Hibernate is powerful, flexible, open source and free, it still uses a proprietary API. Furthermore one could argue that iBA TIS is a bit lightweight, although it's excellent for use in application that don't require complex O/R mapping strategies. Given the choice, it's usually desirable to implement major application functionality using standard or abstracted APIs, in case you need to switch to another implementation for reasons of functionality, performance, or any other concerns. For example, Spring's abstraction of Hibernate transactions and exceptions, along with its IoC approach which allows you to easily swap in mapper/DAO objects implementing data access functionality, makes it easy to isolate all Hibernate-specific code in one area of your application, without sacrificing any of the power of Hibernate. Higher level service code dealing with the DAOs has no need to know anything about their implementation. This approach has the additional benefit of making it easy to intentionally implement data access with a mix-and-match approach (i.e. some data access performed using Hibernate, and some using JDBC, others using iBATIS) in a non-intrusive fashion, potentially providing great benefits in terms of continuing to use legacy code or leveraging the strength of each technology.
The Spring transaction abstraction
Spring provides a consistent abstraction for transaction management. This abstraction is one of the most important of Spring's abstractions, and delivers the following benefits: Provides a consistent programming model across different transaction APIs such as JTA, JDBC, Hibernate, iBA TIS Database Layer and JDO.
Provides a simpler, easier to use, API for programmatic transaction management than most of these transaction APIs
Integrates with the Spring data access abstraction
Supports Spring declarative transaction management
Traditionally, J2EE developers have had two choices for transaction management: to use global or local transactions. Global transactions are managed by the application server, using JTA. Local transactions are resource-specific: for example, a transaction associated with a JDBC connection. This choice had profound implications. Global transactions provide the ability to work with multiple transactional resources. (It's worth noting that most applications use a single transaction resource) With local transactions, the application server is not involved in transaction management, and cannot help ensure correctness across multiple resources.
Global transactions have a significant downside. Code needs to use JTA: a cumbersome API to use (partly due to its exception model). Furthermore, a JTA UserTransaction normally needs to be obtained from JNDI: meaning that we need to use both JNDI and JTA to use JTA. Obviously all use of global transactions limits the reusability of application code, as JTA is normally only available in an application server environment.
The preferred way to use global transactions was via EJB CMT (Container Managed Transaction): a form of declarative transaction management (as distinguished from programmatic transaction management). EJB CMT removes the need for transaction-related JNDI lookups--although of course the use of EJB itself necessitates the use of JNDI. It removes most--not all--need to write Java code to control transactions. The significant downside is that CMT is (obviously) tied to JTA and an application server environment; and that it's only available if we choose to implement business logic in EJBs, or at least behind a transactional EJB facade. The negatives around EJB in general are so great that this is not an attractive proposition, when there are alternatives for declarative transaction management.
Local transactions may be easier to use, but also have significant disadvantages: They cannot work across multiple transactional resources, and tend to invade the programming model. For example, code that manages transactions using a JDBC connection cannot run within a global JTA transaction.
Spring resolves these problems. It enables application developers to use a consistent programming model in any environment. You write your code once, and it can benefit from different transaction management strategies in different environments. Spring provides both declarative and programmatic transaction management. Declarative transaction management is preferred by most users, and recommended in most cases.
With programmatic transaction management developers work with the Spring transaction abstraction, which can run over any underlying transaction infrastructure. With the preferred declarative model developers typically write little or no code related to transaction management, and hence don't depend on Spring's or any other transaction API.
中文译文
Core包是框架的最基础部分，并提供依赖注入（Dependency Injection）特性来使你可管理Bean容器功能。这里的基础概念是BeanFactory，它提供Factory模式来消除对程序性单例的需要，并允许你从程序逻辑中分离出依赖关系的配置和描述。
构建于Beans包上Context包，提供了一种框架式的Bean访问方式，有些象JNDI注册。Context包的特性得自Beans包，并添加了文本消息的发送，通过比如资源串，事件传播，资源装载的方式和Context的透明创建，如通过Servlet容器。
DAO包提供了JDBC的抽象层，它可消除冗长的JDBC编码和解析数据库厂商特有的错误代码。该包也提供了一种方法实现编程性和声明性事务管理，不仅仅是针对实现特定接口的类，而且对所有的POJO。
ORM包为流行的关系－对象映射APIs提供了集成层，包括JDO，Hibernate和iBatis。通过ORM包，你可与所有Spring提供的其他特性相结合来使用这些对象/关系映射，如前边提到的简单声明性事务管理。
Spring的AOP包提供与AOP联盟兼容的面向方面编程实现，允许你定义，如方法拦截器和切点，来干净地给从逻辑上说应该被分离的功能实现代码解耦。使用源码级的元数据功能，你可将各种行为信息合并到你的代码中，有点象.Net的attribute。
Spring的Web包提供了基本的面向Web的综合特性，如Multipart功能，使用Servlet 监听器的Context的初始化和面向Web的Applicatin Context。当与WebWork或Struts 一起使用Spring时，这个包使Spring可与其他框架结合。
Spring的Web MVC包提供了面向Web应用的Model-View-Controller实现。 Spring 的MVC实现不仅仅是一种实现，它提供了一种domain model代码和web form的清晰分离，这使你可使用Spring框架的所有其他特性，如校验.
Spring的web框架是围绕分发器（DispatcherServlet）设计的，DispatcherServlet 将请求分发到不同的处理器，框架还包括可配置的处理器映射，视图解析，本地化，主题解析，还支持文件上传。缺省的处理器是一个简单的控制器（Controller）接口，这个接口仅仅定义了ModelAndView handleRequest(request,response)方法。你可以实现这个接口生成应用的控制器，但是使用Spring提供的一系列控制器实现会更好一些，比如AbstractController，AbstractCommandController，和SimpleFormController。应用控制器一般都从它们继承。注意你需要选择正确的基类：如果你没有表单，你就不需要一个FormController。这是和Structs的一个主要区别。
你可以使用任何对象作为命令对象或表单对象：不必实现某个接口或从某个基类继承。Spring的数据绑定相当灵活，例如，它认为类型不匹配这样的错误应该是应用级的验证错误，而不是系统错误。所以你不需要为了处理无效的表单提交，或者正确地转换字符串，在你的表单对象中用字符串类型重复定义你的业务对象属性。你应该直接绑定表单到业务对象
上。这是和Struts的另一个重要不同，Struts是围绕象Action和ActionForm这样的基类构建的，每一种行为都是它们的子类。
和WebWork相比，Spring将对象细分成不同的角色：它支持的概念有控制器（Controller），可选的命令对象（Command Object）或表单对象（Form Object），以及传递到视图的模型（Model）。模型不仅包含命令对象或表单对象，而且也包含任何引用数据。但是，WebWork的Action将所有的这些角色都合并在一个单独的对象里。WebWork允许你在表单中使用现有的业务对象，但是只能把它们定义成不同Action类的bean属性。更重要的是，在运算和表单赋值时，使用的是同一个处理请求的Action实例。因此，引用数据也需要被定义成Action的bean属性。这样在一个对象就承担了太多的角色。
对于视图：Spring的视图解析相当灵活。一个控制器实现甚至可以直接输出一个视图作为响应，这需要使用null返回ModelAndView。在一般的情况下，一个ModelAndView实例包含视图名字和模型映射表，模型映射表提供了bean的名字及其对象（比如命令对象或表单对象，引用数据等等）的对应关系。视图名解析的配置是非常灵活的，可以通过bean 的名字，属性文件或者你自己的ViewResolver来实现。抽象的模型映射表完全抽象了表现层，没有任何限制：JSP，Velocity，或者其它的技术——任何表现层都可以直接和Spring 集成。模型映射表仅仅将数据转换成合适的格式，比如JSP请求属性或者Velocity模版模型。
MVC实现的可扩展性
许多团队努力争取在技术和工具方面能使他们的投入更有价值，无论是现有的项目还是新的项目都是这样。具体地说，Struts 不仅有大量的书籍和工具，而且有许多开发者熟悉它。因此，如果你能忍受Struts的架构性缺陷，它仍然是web层一个很好的选择。WebWork 和其它web框架也是这样。
如果你不想使用Spring的web MVC框架，而仅仅想使用Spring提供的其它功能，你可以很容易地将你选择的web框架和Spring结合起来。只要通过Spring的ContextLoadListener启动一个Spring的根应用上下文，并且通过它的ServletContext属性（或者Spring的各种帮助方法）在Struts或WebWork的Action中访问。注意到现在没有提到任何具体的“plugins”，因此这里也没有提及如何集成：从web层的角度看，你可以仅仅把Spring作为一个库使用，根应用上下文实例作为入口。
所有你注册的bean和Spring的服务可以在没有Spring的web MVC下被访问。Spring 并没有在使用方法上和Struts或WebWork竞争，它只是提供单一web框架所没有的功能，从bean的配置到数据访问和事务处理。所以你可以使用Spring的中间层和（或者）数据访问层来增强你的应用，即使你只是使用象JDBC或Hibernate事务抽象这样的功能。
Spring MVC框架的特点
如果仅仅关注于web方面的支持，Spring有下面一些特点：
清晰的角色划分：控制器，验证器，命令对象，表单对象和模型对象；分发器，处理器映射和视图解析器；等等。
直接将框架类和应用类都作为JavaBean配置，包括通过应用上下文配置中间层引用，例如，从web控制器到业务对象和验证器的引用。
可适应性，但不具有强制性：根据不同的情况，使用任何你需要的控制器子类（普通控制器，命令，表单，向导，多个行为，或者自定义的），而不是要求任何东西都要从Action/ActionForm继承。
可重用的业务代码，而不需要代码重复：你可以使用现有的业务对象作为命令对象或表单对象，而不需要在ActionForm的子类中重复它们的定义。
可定制的绑定和验证：将类型不匹配作为应用级的验证错误，这可以保存错误的值，以及本地化的日期和数字绑定等，而不是只能使用字符串表单对象，手动解析它并转换到业务对象。
可定制的处理器映射，可定制的视图解析：灵活的模型可以根据名字/值映射，处理器映射和视图解析使应用策略从简单过渡到复杂，而不是只有一种单一的方法。
可定制的本地化和主题解析，支持JSP，无论有没有使用Spring标签库，支持JSTL，支持不需要额外过渡的Velocity，等等。
简单而强大的标签库，它尽可能地避免在HTML生成时的开销，提供在标记方面的最大灵活性。
使用ORM工具进行数据访问
Spring在资源管理，DAO实现支持以及实物策略等方面提供了与Hibernate, JDO和iBATIS SQL映射的集成。对Hibernate，Spring使用了很多IoC的方便的特性提供了一流的支持，帮助你处理很多典型的Hibernate整合的问题。所有的这些都遵守Spring通用的事务和DAO异常体系.。
当您选择使用O/R映射来创建数据访问应用程序的时候，Spring的增加部分就会向您提供重要的支持。首先你应该了解的是，一旦你使用了Spring对O/R映射的支持，你不需要亲自作所有的事情。在决定花费力气，冒着风险建造类似的内部底层结构之前，我们都建议您考虑和利用Spring的解决方案。不管你使用的是何种技术，大部分的O/R映射支持都可以以library样式被使用，因为所有的东西都是被设计成一组可重复利用的JavaBeans。在ApplicationContext和BeanFactory中使用更是提供了配置和部署简单的好处，因此，这一章里的大多数例子都是在ApplicationContext中配置。
使用Spring构建你的ORM应用的好处包括:
测试简单. Spring的IoC使得很容易替换掉不同的实现，Hibernate SessionFacotory 的位置，datasource, 事务管理, 映射对象的实现。这样就很容易隔离测试持久化相关代码的各个部分。
成本管理外文文献及翻译
成本管理外文文献 China's Enterprise Cost Management Analysis and Countermeasures Abstract: With the progress and China's traditional Cost Management model difficult to adapt to an increasingly competitive market environment. This paper exists in our country a number of Cost Management and finally put forward to address these issues a number of measures to strengthen Cost Management. Keywords:: Cost Management measures In a market economy conditions, as the global economic integration, the development of increasingly fierce market competition, corporate profit margins shrinking. In this case, the level of high and low business costs directly determines the size of an enterprise profitability and competitive strength. Therefore, strengthen enterprise Cost Management business has become an inevitable choice for the survival and development. First, the reality of China's Enterprise Cost Management Analysis Cost Management in our country after years of development, has made many achievements, but now faces a new environment, China's Cost Management has also exposed some new problems, mainly in the following aspects: (A) Cost Management concept behind the Chinese enterprises lag behind the concept of Cost Management in pervasive phenomenon, mainly in Cost Management of the scope, purpose and means from time to biased. Many enterprises will continue to limit the scope of Cost Management within the enterprise or even only the production process at the expense of other related companies and related fields cost behavior management. We supply side, for example. The supply side of the price of the product cost of doing business, one of the most important motives. As the supply side of the price of the product and its cost plus profit, so the supply side of price in the form of its own costs to the enterprise. However, some enterprises to the supply side too much rock bottom price, as their source of high profits, without considering each other's interests, resulting in supply-side to conceal their true costs, price increase in disguise. This increase in procurement costs, thereby increasing commodity costs, making goods less competitive. The purpose of Cost Management from the point of view, many enterprises confined to lower costs, but less from the perspective of cost-effectiveness of the effectiveness of the means of cost reduction mainly rely on savings, can not be cost-effective. In traditional Cost Management, Cost Management purposes has been reduced to cut costs, saving has become the basic means to reduce costs. From the perspective of Cost Management to analyze the Cost Management of this goal, not difficult to find cost-reduction is conditional and limits, and in some cases, control of costs, could lead to product quality and enterprise efficiency decline. In addition, the vast majority of enterprises in the overall concept of lack of Cost
P2P 金融下的中小企业融资互联网金融外文文献翻译最新译文
文献出处: Waitz M. The small and medium-sized enterprise financing under P2P finance [J]. Journal of Business Research, 2016, 8(6): 81-91. 原文 The small and medium-sized enterprise financing under P2P finance Waitz M Abstract Small and medium-sized enterprise financing difficult is worldwide difficult problem. Article introduces the concept of the Internet financial, mainly summarized the P2P financial in the development of financial innovation and integration of science and technology, a combination of academic research on P2P financial now of the five directions of various views and opinions. Points out the current P2P financial problems in the development of risk control, and analyses the trend of the Internet financial. Keywords: P2P financial; Financial innovation; Risk control 1 Introduction Look from the history of enterprise development, a large enterprise originate from small and medium-sized enterprises. Small and medium-sized enterprises (smes) is the most dynamic part of the national economy, often walk in the forefront of technology development, in the high-tech industry, clean energy, green economy, etc, have good performance, play an important role in the economic transformation. Small and medium-sized enterprise financing difficult is worldwide difficult problem. These small and medium-sized enterprise financing environment and narrow channels, more than 60% are unable to get a bank loan. At present, science and technology enterprises and the characteristics of light assets, financing difficulties, become a huge bottleneck of sustainable development. 2 The concept of the Internet financial In the past two years, the Internet financial show explosive growth, since 2014, the Internet financial sector performance strength. Current economic field exists the phenomenon of two special contradiction, one is the small and medium-sized
试谈提升大学生就业竞争力的培养体系研究
试谈提升大学生就业竞争力的培养体系研究 [摘要]1998年以来，我国高校持续扩招，大学毕业生的就业问题已成为全关注的焦点，我国高等培育机制与社会需求的错位和脱节是造成人才供需矛盾的主要原因。本文剖析了大学生就业竞争力培养体系构建的必要性，基于系统工程和胜任特征理论构建了大学生就业竞争力培养体系的框架模型，以培养大学生化素质为核心，以促进个人职业生涯规划和执行为手段，以提高大学生就业率和就业满意度为目标，从大学生职业能力素质模型、大学生职业能力素质测评系统、大学生就业竞争力培育机制、大学生就业竞争力评价体系等方面构建了四位一体的耦合培养体系，以期提升大学生的就业竞争力。 [关键词]大学生；就业竞争力；培养体系 就业为民生之本。近年来，高校毕业生就业是社会普遍关注的问题，是我国政府面临的重大难题之一，大量的高校毕业生不能及时就业已成为影响社会稳定与的重要因素。国内大多数学者都认为，“就业鸿沟”问题是因为大学生在就业能力方面的缺陷以及用人单位与大学毕业生之间的信息不对称造成的。当前，我国就业体制改革的目标是以市场选择为根本取向，以自主就业为主导模式，以素质能力为竞争之本，形成与经济迥然不同的就业机制。因此，需要让用人单位、学校共同建立新型的大学生就业竞争力培养体系，缓解就业压力、解决培养错位问题。 一、大学生就业竞争力的内涵
就业竞争力包涵着在就业能力和职业发展过程中的多项综合能力，关于其定义有多种解释。国际劳工(ILO)则指出，就业能力是个体获得和保持、在工作中进步以及应对工作生活中出现的变化的能力；英国原教育与就业部(DFEE)把就业能力解释为获得和保持工作的能力，进一步讲，就业能力是在劳动力市场内通过充分的就业机会实现潜能的自信。国外学者Howard认为就业竞争力是指雇员具有劳动力市场和雇主所需要和认为有吸引力的技能的能力；Fuguate认为：就业竞争力是指个体在其职业期间确认和实现在组织内部和外部职业机会的能力。国内学者赵志川认为大学生的就业竞争力是大学生初次进入人力资源市场以及在以后的职业生涯中能够相对于其他竞争对手更加有效地向市场提供自己的智力和服务，从而保证自身持续生存和发展的综合素质和能力；楼锡锦认为大学生就业竞争力是指毕业生在就业市场上，具有战胜竞争对手、找到适合才能发挥和实现自身价值的适当工作岗位的能力，可归结为核心竞争力、基础竞争力和竞争力。 本文所研究的大学生就业竞争力主要是指大学生在校期间通过较为系统的基础知识和专业知识的学习掌握，以及适应社会需要的综合素质的开发培养，在就业竞争和职业发展中所具有的获得和保持工作的职业化能力。 二、构建提升大学生就业竞争力的培养体系的必要性 (一)传统大学生培养模式的错位现象 1．大众化的高等教育与精英就业观的错位
ASP外文翻译原文
https://www.wendangku.net/doc/081721245.html, https://www.wendangku.net/doc/081721245.html, 是一个统一的 Web 开发模型，它包括您使用尽可能少的代码生成企业级 Web 应用程序所必需的各种服务。https://www.wendangku.net/doc/081721245.html, 作为 .NET Framework 的一部分提供。当您编写 https://www.wendangku.net/doc/081721245.html, 应用程序的代码时，可以访问 .NET Framework 中的类。您可以使用与公共语言运行库 (CLR) 兼容的任何语言来编写应用程序的代码，这些语言包括 Microsoft Visual Basic、C#、JScript .NET 和 J#。使用这些语言，可以开发利用公共语言运行库、类型安全、继承等方面的优点的https://www.wendangku.net/doc/081721245.html, 应用程序。 https://www.wendangku.net/doc/081721245.html, 包括： ?页和控件框架 ?https://www.wendangku.net/doc/081721245.html, 编译器 ?安全基础结构 ?状态管理功能 ?应用程序配置 ?运行状况监视和性能功能 ?调试支持 ?XML Web services 框架 ?可扩展的宿主环境和应用程序生命周期管理 ?可扩展的设计器环境 https://www.wendangku.net/doc/081721245.html, 页和控件框架是一种编程框架，它在 Web 服务器上运行，可以动态地生成和呈现 https://www.wendangku.net/doc/081721245.html, 网页。可以从任何浏览器或客户端设备请求 https://www.wendangku.net/doc/081721245.html, 网页，https://www.wendangku.net/doc/081721245.html, 会向请求浏览器呈现标记（例如 HTML）。通常，您可以对多个浏览器使用相同的页，因为 https://www.wendangku.net/doc/081721245.html, 会为发出请求的浏览器呈现适当的标记。但是，您可以针对诸如 Microsoft Internet Explorer 6 的特定浏览器设计https://www.wendangku.net/doc/081721245.html, 网页，并利用该浏览器的功能。https://www.wendangku.net/doc/081721245.html, 支持基于 Web 的设备（如移动电话、手持型计算机和个人数字助理 (PDA)）的移动控件。
毕业设计外文翻译原文.
Optimum blank design of an automobile sub-frame Jong-Yop Kim a ,Naksoo Kim a,*,Man-Sung Huh b a Department of Mechanical Engineering,Sogang University,Shinsu-dong 1,Mapo-ku,Seoul 121-742,South Korea b Hwa-shin Corporation,Young-chun,Kyung-buk,770-140,South Korea Received 17July 1998 Abstract A roll-back method is proposed to predict the optimum initial blank shape in the sheet metal forming process.The method takes the difference between the ?nal deformed shape and the target contour shape into account.Based on the method,a computer program composed of a blank design module,an FE-analysis program and a mesh generation module is developed.The roll-back method is applied to the drawing of a square cup with the ˉange of uniform size around its periphery,to con?rm its validity.Good agreement is recognized between the numerical results and the published results for initial blank shape and thickness strain distribution.The optimum blank shapes for two parts of an automobile sub-frame are designed.Both the thickness distribution and the level of punch load are improved with the designed blank.Also,the method is applied to design the weld line in a tailor-welded blank.It is concluded that the roll-back method is an effective and convenient method for an optimum blank shape design.#2000Elsevier Science S.A.All rights reserved. Keywords:Blank design;Sheet metal forming;Finite element method;Roll-back method
企业成本控制外文翻译文献
企业成本控制外文翻译文献(文档含英文原文和中文翻译)
译文： 在价值链的成本控制下减少费用和获得更多的利润 摘要： 根据基于价值链的成本管理理念和基于价值的重要因素是必要的。首先，必须有足够的资源，必须创造了有利的价值投资，同时还需要基于客户价值活动链，以确定他们的成本管理优势的价值链。其次，消耗的资源必须尽量减少，使最小的运营成本价值链和确保成本优势是基于最大商业价值或利润，这是一种成本控制系统内部整个视图的创建和供应的具实践，它也是一种成本控制制度基于价值链，包括足够的控制和必要的资源投资价值的观点，创建和保持消费的资源到合理的水平，具有价值的观点主要对象的第一个因素是构造有利的价值链，从创造顾客价值开始；第二个因素是加强有利的价值链，从供应或生产客户价值开始。因此它是一个新型的理念，去探索成本控制从整个视图的创建和供应的商品更盈利企业获得可持续的竞争优势。 关键词：成本控制，价值链，收益，支出，收入，成本会计 1、介绍 根据价值链理论，企业的目的是创造最大的顾客价值；和企业的竞争优势在于尽可能提供尽可能多的价值给他们的客户，作为低成本可能的。这要求企业必须首先考虑他们是否能为顾客创造价值，和然后考虑在很长一段时间内如何创造它。然而，竞争一直以“商品”（或“产品”）作为最直接的载体，因此，传统的成本控制方法主要集中在对“产品”和生产流程的过程。很显然，这不能解决企业的问题，企业是否或如何能为客户创造价值。换句话说，这至少不能从根本上解决它。 因此，企业必须首先投入足够的资源，以便他们能够创建客户值取向，然后提供它以最少的资源费用。所以在整个视图中对价值创造和提供整体的观点来控制成本，它可以为客户提供完美的动力和操作运行机制运行成本的控制，也可以从根本上彻底克服了传统的成本控制方法的缺点，解决了无法控制的创造和供应不足的真正价值。基于此，本文试图从创作的整体观讨论成本控制提供价值并探讨实现良性循环的策略，也就是说，“创造价值投资成本供应价值创造价值”。 2、成本及其控制的基于价值链理念 2.1基于价值链的成本观念 根据价值链理论，如果企业是要被客户接受，它必须创造和提供能满足其客户的价值。因此，成本（价值或资源支付费用）这不离为创造和提供顾客价值的活动，其活动的价值链。因此，我们应该从价值链角度看成本的重要。
互联网金融外文翻译银行业是必要的而银行不是,互联网时代的金融中介的未来
译文 银行业是必要的而银行不是，互联网时代的金融中介机构的未来 摘要 本文探讨了互联网时代下金融机构和银行作为特殊的金融机构的未来可能是怎样的问题。由于互联网而导致的交易费用的减少会降低进入金融产品市场的壁垒，因为有可能不再需要运行成本密集型的分支的大型系统。但是，对金融机构的职能研究表明，不是每个人都可以销售和经销金融产品。这是真的，因为金融业务中的信息不对称问题需要一个拥有良好信誉的中介，也因为需要限制大型资本基金转换资产的风险。这两个要求变现了进入金融中介市场的重要壁垒。并不是每一个金融产品会因为互联网的崛起而将面临更多的竞争，只有那些标准化和低风险的产品。此外，那些拥有可观资本和良好声誉的大公司可能被视为银行的新竞争者。 关键字：银行业，银行，金融机构，互联网 1、引言 “银行业是19世纪的钢铁行业。”当谈到关于新的信息技术对银行的影响的谈论时，这句话经常被提起。更一般来说，可能有人会问，新信息技术是如何成功的，特别是互联网的，可能会改变商业和金融机构的市场情况。在互联网的帮助下，人们可以执行所有银行的业务，而不需要银行。这意味着传统银行分支机构的中介。此外，互联网已经使客户直接从网上购买股票而不需要访问当地的分支银行。从更广泛的意义上来说，在互联网的帮助下，金融市场的供给和需求可能通过互联网满足，而不需要金融中介机构。互联网的崛起是否真的是金融中介机构的威胁？在急剧减少的交易成本情况下，商业和竞争将如何变化？本文考察了互联网的成功对金融机构和银行的影响。 2、金融机构的发展 几个世纪以来，许多金融交易需要个人的存在。随着现代信息技术的发展，这些都被改变了。如今，客户可以在不进入当地分支银行的情况下进行任何金融交易。转移支付和支付账单可以通过网络进行，个人金融交易以及关于金融问题的信息咨询业可以通过网络进行。此外，互联网创新类似智能卡或者其他电子支付系统消除了为了得到一些现金而访问分支银行的需要。 但是互联网也会改变咨询活动：在许多情况下，它甚至可能减少个人存在的
中国的对外贸易外文翻译及原文
外文翻译 原文 Foreign T rade o f China Material Source:W anfang Database Author:Hitomi Iizaka 1.Introduction On December11,2001,China officially joined the World T rade Organization(WTO)and be c a me its143rd member.China’s presence in the worl d economy will continue to grow and deepen.The foreign trade sector plays an important andmultifaceted role in China’s economic development.At the same time, China’s expanded role in the world economy is beneficial t o all its trading partners. Regions that trade with China benefit from cheaper and mor e varieties of imported consumer goods,raw materials and intermediate products.China is also a large and growing export market.While the entry of any major trading nation in the global trading system can create a process of adjustment,the o u t c o me is fundamentally a win-win situation.In this p aper we would like t o provide a survey of the various institutions,laws and characteristics of China’s trade.Among some of the findings, we can highlight thefollowing: ?In2001,total trade to gross domestic pr oduct(GDP)ratio in China is44% ?In2001,47%of Chinese trade is processed trade1 ?In2001,51%of Chinese trade is conduct ed by foreign firms in China2 ?In2001,36%of Chinese exports originate from Gu an gdon g province ?In2001,39%of China’s exports go through Hong Kong to be re-exported elsewhere 2.Evolution of China’s Trade Regime Equally remarkable are the changes in the commodity composition of China’s exports and imports.Table2a shows China’s annu al export volumes of primary goods and manufactured goods over time.In1980,primary goods accounted for 50.3%of China’s exports and manufactured goods accounted for49.7%.Although the share of primary good declines slightly during the first half of1980’s,it remains at50.6%in1985.Since then,exports of manufactured goods have grown at a much
成本控制【外文翻译】
外文翻译 原文 Cost Control Material Source:Encyclopedia of business,2 and ed. Author:Anthony, Robet N 1 Cost Control Cost control, also known as cost management or cost containment, is a broad set of cost accounting methods and management techniques with the common goal of improving business cost-efficiency by reducing costs, or at least restricting their rate of growth. Businesses use cost control methods to monitor, evaluate, and ultimately enhance the efficiency of specific areas, such as departments, divisions, or product lines, within their operations. During the 1990s cost control initiatives received paramount attention from corporate America. Often taking the form of corporate restructuring, divestment of peripheral activities, mass layoffs, or outsourcing, cost control strategies were seen as necessary to preserve—or boost—corporate profits and to maintain—or gain—a competitive advantage. The objective was often to be the low-cost producer in a given industry, which would typically allow the company to take a greater profit per unit of sales than its competitors at a given price level. Some cost control proponents believe that such strategic cost-cutting must be planned carefully, as not all cost reduction techniques yield the same benefits. In a notable late 1990s example, chief executive Albert J. Dunlap, nicknamed "Chainsaw Al" because of his penchant for deep cost cutting at the companies he headed, failed to restore the ailing small appliance maker Sunbeam Corporation to profitability despite his drastic cost reduction tactics. Dunlap laid off thousands of workers and sold off business units, but made little contribution to Sunbeam's competitive position or share price in his two years as CEO. Consequently, in 1998 Sunbeam's board fired Dunlap, having lost confidence in his "one-trick" approach to management. A complex business requires frequent information about operations in order to plan for the future, to control present activities, and to evaluate the past performance of managers, employees, and related business segments. To be successful,
互联网金融发展文献综述及外文文献资料P2P金融
本份文档包含：关于该选题的外文文献、文献综述 一、外文文献 标题: Online brokers lead the way for French internet finance 作者: Caffard, Christophe 期刊名称: International Financial Law Review 卷: 20；期: 3；页: 20-24 Online brokers lead the way for French internet finance 1 Regulated brokers Regulated brokers are legal entities which have an investment services licence and are subject to the prudential regulations of the Comite de Reglementation Bancaire et Financiere (CRBF) and the Conseil des Marches Financiers (CMF). * Choice of legal form: regulated brokers are not required to be incorporated in a specific legal form; however, under article 13 of the MAF Law, the CECEI checks whether the legal form of the brokerage company is appropriate for providing investment services. In practice, any type of commercial company is admitted: societes de capitaux (limited companies) or societes de personnes (partnerships). The formalities of share transfer, tax and the scope of liability of a company's management will be relevant factors to the choice of legal form. * Application for an investment services licence from the CECEI: the most important part of the application is the description of the investment services, and a business plan including prospective financial statements for the following three years. The CMF will check whether the business plan is consistent with the investment services licence requested by the broker. The CECEI will ensure that the applicant's own initial funds are consistent with the business plan. The scope of the investment services licence is variable and covers one or more ofthe following investment services: Reception and transmission of orders to another investment services provider on behalf of investors, for execution. This is the core investment service provided by the
就业竞争力
摘要：高职院校大学生的就业问题关系到高职院校的可持续发展。应从提高大学生的就业竞争力入手提升学生的整体就业水平。大学生的就业竞争力可归纳为基本素质、基本工作能力、专业技能、求职技能四个要素。高职院校应分析当前制约毕业生就业竞争力提升的内部因素与外部因素，有针对性地提出提升大学生就业竞争力的有效途径。 关键词：高职院校；学生；就业竞争力 近年来，大学生就业形势日趋严峻，妥善解决好大学生的就业问题，不仅关系到我国高等教育的可持续发展，也直接关系到社会的稳定与和谐，同时还决定着高等院校尤其是高职院校的生存与发展。要做好毕业生就业工作，必须对毕业生的就业竞争力作系统、全面、客观的分析，从提高就业竞争力入手提升大学生的整体就业水平。 就业竞争力的内涵与构成要素 大学生就业竞争力本质上是一种表现力，是大学生综合素质的集中反映和显著标志，是毕业生把握并获取就业机会、赢得欣赏的实际能力和比较优势。概括说来，大学生就业竞争力是指毕业生在就业市场上战胜竞争对手、找到自身才能发挥和实
现自身价值的适当的工作岗位的能力，即满足社会和用人单位对人才需求的能力。从社会对人才的需求来看，笔者认为大学生就业竞争力包含以下四个要素。 （一）基本素质 诚信意识人无信不立，国无信不强。诚信是一个合格公民所必须具备的最基本的思想道德素质，也是市场经济最可靠、最坚实的基石，是维护市场秩序、调整人们社会关系的准则。大学生的诚信状况直接关系到我国市场经济体制建设的成败。社会上的信用缺失，使德才兼备的人才受到用人单位的青睐，有才无德的人是不会受欢迎的。大学生作为未来社会生活的新生力量，应当认真经营好个人信誉这个无形资产。 强烈的责任心责任心是我们这个社会为人处事的基本要求，是一个人能否立足于社会，获得事业发展的至关重要的人格品质，是做人的基本素质。一个人工作能力的大小与他掌握知识的程度和工作方法有很大关系，而一个人的工作态度，即责任心问题则是影响一个人事业成败的关键。从某种意义上说，责任心往往比能力更为重要。大学生一定要树立对自己和他人、对家庭和集体、对国家和社会的责任心，这样才能得到用人单位的青睐。 扎实的科学文化素质科学文化素质主要体现在学生的知识结构、专业水平以及科学精神等方面。一切职业都要求从业者具有相应的知识，因此，在人才竞争日趋激烈的情况下，大学生必须掌握系统的科学知识、扎实的专业知识、广博的社会知识，具有完善而全面的知识结构，才能适应未来工作的需要。 （二）基本工作能力
英文翻译与英文原文.陈--
翻译文献：INVESTIGATION ON DYNAMIC PERFORMANCE OF SLIDE UNIT IN MODULAR MACHINE TOOL （对组合机床滑台动态性能的调查报告） 文献作者：Peter Dransfield, 出处：Peter Dransfield, Hydraulic Control System-Design and Analysis of TheirDynamics, Springer-Verlag, 1981 翻译页数：p139—144 英文译文： 对组合机床滑台动态性能的调查报告 【摘要】这一张纸处理调查利用有束缚力的曲线图和状态空间分析法对组合机床滑台的滑动影响和运动平稳性问题进行分析与研究，从而建立了滑台的液压驱动系统一自调背压调速系统的动态数学模型。通过计算机数字仿真系统，分析了滑台产生滑动影响和运动不平稳的原因及主要影响因素。从那些中可以得出那样的结论，如果能合理地设计液压缸和自调背压调压阀的结构尺寸. 本文中所使用的符号如下： s1-流源，即调速阀出口流量； S el—滑台滑动摩擦力 R一滑台等效粘性摩擦系数： I1—滑台与油缸的质量 12—自调背压阀阀心质量 C1、c2—油缸无杆腔及有杆腔的液容； C2—自调背压阀弹簧柔度； R1, R2自调背压阀阻尼孔液阻， R9—自调背压阀阀口液阻 S e2—自调背压阀弹簧的初始预紧力； I4, I5—管路的等效液感 C5、C6—管路的等效液容： R5, R7-管路的等效液阻； V3, V4—油缸无杆腔及有杆腔内容积； P3, P4—油缸无杆腔及有杆腔的压力 F—滑台承受负载， V—滑台运动速度。本文采用功率键合图和状态空间分折法建立系统的运动数学模型，滑台的动态特性可以能得到显著改善。
污水处理外文翻译(带原文)
提高塔式复合人工湿地处理农村生活污水的 脱氮效率1 摘要： 努力保护水源，尤其是在乡镇地区的饮用水源，是中国污水处理当前面临的主要问题。氮元素在水体富营养化和对水生物的潜在毒害方面的重要作用，目前废水脱氮已成为首要关注的焦点。人工湿地作为一种小型的，处理费用较低的方法被用于处理乡镇生活污水。比起活性炭在脱氮方面显示出的广阔前景，人工湿地系统由于溶解氧的缺乏而在脱氮方面存在一定的制约。为了提高脱氮效率，一种新型三阶段塔式混合湿地结构----人工湿地（thcw）应运而生。它的第一部分和第三部分是水平流矩形湿地结构，第二部分分三层，呈圆形，呈紊流状态。塔式结构中水流由顶层进入第二层及底层，形成瀑布溢流，因此水中溶解氧浓度增加，从而提高了硝化反应效率，反硝化效率也由于有另外的有机物的加入而得到了改善，增加反硝化速率的另一个原因是直接通过旁路进入第二部分的废水中带入的足量有机物。常绿植物池柏（Taxodium ascendens），经济作物蔺草（Schoenoplectus trigueter），野茭白（Zizania aquatica），有装饰性的多花植物睡莲（Nymphaea tetragona），香蒲（Typha angustifolia）被种植在湿地中。该系统对总悬浮物、化学需氧量、氨氮、总氮和总磷的去除率分别为89%、85%、83%、83% 和64%。高水力负荷和低水力负荷（16 cm/d 和32 cm/d）对于塔式复合人工湿地结构的性能没有显著的影响。通过硝化活性和硝化速率的测定，发现硝化和反硝化是湿地脱氮的主要机理。塔式复合人工湿地结构同样具有观赏的价值。 关键词： 人工湿地；硝化作用；反硝化作用；生活污水；脱氮；硝化细菌；反硝化细菌 １. 前言 对于提高水源水质的广泛需求，尤其是提高饮用水水源水质的需求是目前废水深度处理的技术发展指向。在中国的乡镇地区，生活污水是直接排入湖泊、河流、土壤、海洋等水源中。这些缺乏处理的污水排放对于很多水库、湖泊不能达到水质标准是有责任的。许多位于中国的乡镇地区的社区缺乏足够的生活污水处理设备。由于山区地形、人口分散、经济基础差等原因，废水的收集和处理是很成问题的。由于资源短缺，经济欠发达地区所采取的废水处理技术必须低价高效，并且要便于施用，能量输入及维护费用较低，而且要保证出水能达标。建造在城市中基于活性污泥床的废水集中处理厂，对于小乡镇缺乏经济适用性，主要是由于污水收集结构的建造费用高。 1Ecological Engineering，Fen xia ，Ying Li。