毕业设计(论文)外文资料翻译〔含原文〕

合集下载

毕业论文(设计)外文文献翻译及原文

金融体制、融资约束与投资——来自OECD的实证分析R．SemenovDepartment of Economics，University of Nijmegen，Nijmegen（荷兰内梅亨大学，经济学院）这篇论文考查了OECD的11个国家中现金流量对企业投资的影响.我们发现不同国家之间投资对企业内部可获取资金的敏感性具有显著差异,并且银企之间具有明显的紧密关系的国家的敏感性比银企之间具有公平关系的国家的低.同时，我们发现融资约束与整体金融发展指标不存在关系.我们的结论与资本市场信息和激励问题对企业投资具有重要作用这种观点一致，并且紧密的银企关系会减少这些问题从而增加企业获取外部融资的渠道。

一、引言各个国家的企业在显著不同的金融体制下运行。

金融发展水平的差别(例如，相对GDP的信用额度和相对GDP的相应股票市场的资本化程度），在所有者和管理者关系、企业和债权人的模式中，企业控制的市场活动水平可以很好地被记录.在完美资本市场,对于具有正的净现值投资机会的企业将一直获得资金。

然而，经济理论表明市场摩擦，诸如信息不对称和激励问题会使获得外部资本更加昂贵，并且具有盈利投资机会的企业不一定能够获取所需资本.这表明融资要素，例如内部产生资金数量、新债务和权益的可得性，共同决定了企业的投资决策.现今已经有大量考查外部资金可得性对投资决策的影响的实证资料（可参考，例如Fazzari（1998）、 Hoshi(1991)、 Chapman（1996）、Samuel(1998））.大多数研究结果表明金融变量例如现金流量有助于解释企业的投资水平。

这项研究结果解释表明企业投资受限于外部资金的可得性。

很多模型强调运行正常的金融中介和金融市场有助于改善信息不对称和交易成本，减缓不对称问题,从而促使储蓄资金投着长期和高回报的项目,并且提高资源的有效配置（参看Levine（1997)的评论文章）。

因而我们预期用于更加发达的金融体制的国家的企业将更容易获得外部融资.几位学者已经指出建立企业和金融中介机构可进一步缓解金融市场摩擦。

毕业设计外文翻译译文

1 工程概论1.1 工程专业1.2 工业和技术1.3 现代制造业工程专业1 工程行业是历史上最古老的行业之一。

如果没有在广阔工程领域中应用的那些技术，我们现在的文明绝不会前进。

第一位把岩石凿削成箭和矛的工具匠是现代机械工程师的鼻祖。

那些发现地球上的金属并找到冶炼和使用金属的方法的工匠们是采矿和冶金工程师的先祖。

那些发明了灌溉系统并建造了远古世纪非凡的建筑物的技师是他们那个时代的土木工程师。

2 工程一般被定义为理论科学的实际应用，例如物理和数学。

许多早期的工程设计分支不是基于科学而是经验信息，这些经验信息取决于观察和经历，而不是理论知识。

这是一个倾斜面实际应用的例子，虽然这个概念没有被确切的理解，但是它可以被量化或者数字化的表达出来。

3 从16、17世纪当代初期，量化就已经成为科学知识大爆炸的首要原因之一。

另外一个重要因素是实验法验证理论的发展。

量化包含了把来源于实验的数据和信息转变成确切的数学术语。

这更加强调了数学是现代工程学的语言。

4 从19世纪开始，它的结果的实际而科学的应用已经逐步上升。

机械工程师现在有精确的能力去计算来源于许多不同机构之间错综复杂的相互作用的机械优势。

他拥有能一起工作的既新型又强硬的材料和巨大的新能源。

工业革命开始于使用水和蒸汽一起工作。

从此使用电、汽油和其他能源作动力的机器变得如此广泛以至于它们承担了世界上很大比例的工作。

5 科学知识迅速膨胀的结果之一就是科学和工程专业的数量的增加。

到19世纪末不仅机械、土木、矿业、冶金工程被建立而且更新的化学和电气工程专业出现了。

这种膨胀现象一直持续到现在。

我们现在拥有了核能、石油、航天航空空间以及电气工程等。

每种工程领域之内都有细分。

6 例如，土木工程自身领域之内有如下细分：涉及永久性结构的建筑工程、涉及水或其他液体流动与控制系统的水利工程、涉及供水、净化、排水系统的研究的环境工程。

机械工程主要的细分是工业工程，它涉及的是错综复杂的机械系统，这些系统是工业上的，而非单独的机器。

毕业论文外文翻译(中英文)

译文交通拥堵和城市交通系统的可持续发展摘要:城市化和机动化的快速增长,通常有助于城市交通系统的发展，是经济性，环境性和社会可持续性的体现,但其结果是交通量无情增加，导致交通拥挤。

道路拥挤定价已经提出了很多次，作为一个经济措施缓解城市交通拥挤，但还没有见过在实践中广泛使用，因为道路收费的一些潜在的影响仍然不明。

本文首先回顾可持续运输系统的概念,它应该满足集体经济发展,环境保护和社会正义的目标.然后,根据可持续交通系统的特点，使拥挤收费能够促进经济增长，环境保护和社会正义。

研究结果表明,交通拥堵收费是一个切实有效的方式，可以促进城市交通系统的可持续发展。

一、介绍城市交通是一个在世界各地的大城市迫切关注的话题。

随着中国的城市化和机动化的快速发展,交通拥堵已成为一个越来越严重的问题,造成较大的时间延迟,增加能源消耗和空气污染，减少了道路网络的可靠性．在许多城市,交通挤塞情况被看作是经济发展的障碍.我们可以使用多种方法来解决交通挤塞,包括新的基础设施建设，改善基础设施的维护和操作,并利用现有的基础设施,通过需求管理策略,包括定价机制,更有效地减少运输密度.交通拥堵收费在很久以前就已提出，作为一种有效的措施,来缓解的交通挤塞情况。

交通拥堵收费的原则与目标是通过对选择在高峰拥挤时段的设施的使用实施附加收费,以纾缓拥堵情况．转移非高峰期一些出行路线,远离拥挤的设施或高占用车辆，或完全阻止一些出行,交通拥堵收费计划将在节省时间和降低经营成本的基础上,改善空气中的质量，减少能源消耗和改善过境生产力。

此计划在世界很多国家和地方都有成功的应用。

继在2０世纪70年代初和8０年代中期挪威与新加坡实行收费环,在20０３年2月伦敦金融城推出了面积收费；直至现在,它都是已经开始实施拥挤收费的大都市圈中一个最知名的例子。

然而,交通拥堵收费由于理论和政治的原因未能在实践中广泛使用。

道路收费的一些潜在的影响尚不清楚,和城市发展的拥塞定价可持续性,需要进一步研究。

本科毕业设计外文翻译(中文)

本科生毕业设计（论文）外文翻译外文原文题目：Real-time interactive optical micromanipulation of a mixture of high- and low-index particles中文翻译题目：高低折射率微粒混合物的实时交互式光学微操作毕业设计（论文）题目：阵列光镊软件控制系统设计姓名：任有健学院：生命学院班级：06210501指导教师：李勤高低折射率微粒混合物的实时交互式光学微操作Peter John Rodrigo Vincent Ricardo Daria Jesper Glückstad丹麦罗斯基勒DK-4000号，Risø国家实验室光学和等离子研究系jesper.gluckstad@risoe.dkhttp://www.risoe.dk/ofd/competence/ppo.htm摘要：本文论证一种对于胶体的实时交互式光学微操作的方法，胶体中包含两种折射率的微粒，与悬浮介质（0n ）相比，分别低于（0L n n <）、高于（0H n n >）悬浮介质的折射率。

球形的高低折射率微粒在横平板上被一批捕获激光束生成的约束光势能捕获，捕获激光束的横剖面可以分为“礼帽形”和“圆环形”两种光强剖面。

这种应用方法在光学捕获的空间分布和个体几何学方面提供了广泛的可重构性。

我们以实验为基础证实了同时捕获又独立操作悬浮于水（0 1.33n =）中不同尺寸的球形碳酸钠微壳（ 1.2L n ≈）和聚苯乙烯微珠（ 1.57H n =）的独特性质。

1 引言光带有动量和角动量。

伴随于光与物质相互作用的动量转移为我们提供了在介观量级捕获和操作微粒的方法。

过去数十年中的巨大发展已经导致了在生物和物理领域常规光学捕获的各种应用以及下一代光学微操作体系的出现[1-5]。

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

毕业设计(论文）外文文献翻译院系：财务与会计学院年级专业：201＊级财务管理姓名:学号：132148*＊*附件: 财务风险管理【Abstract】Although financial risk has increased significantly in recent years risk and risk management are not contemporary issues。

The result of increasingly global markets is that risk may originate with events thousands of miles away that have nothing to do with the domestic market。

Information is available instantaneously which means that change and subsequent market reactions occur very quickly。

The economic climate and markets can be affected very quickly by changes in exchange rates interest rates and commodity prices。

Counterparties can rapidly become problematic。

As a result it is important to ensure financial risks are identified and managed appropriately. Preparation is a key component of risk management。

【Key Words】Financial risk，Risk management，YieldsI. Financial risks arising1.1What Is Risk1.1.1The concept of riskRisk provides the basis for opportunity. The terms risk and exposure have subtle differences in their meaning. Risk refers to the probability of loss while exposure is the possibility of loss although they are often used interchangeably。

毕业设计(论文)外文资料翻译(学生用)

毕业设计外文资料翻译学院：信息科学与工程学院专业：软件工程姓名： XXXXX学号： XXXXXXXXX外文出处： Think In Java (用外文写)附件： 1.外文资料翻译译文；2.外文原文。

附件1：外文资料翻译译文网络编程历史上的网络编程都倾向于困难、复杂，而且极易出错。

程序员必须掌握与网络有关的大量细节，有时甚至要对硬件有深刻的认识。

一般地，我们需要理解连网协议中不同的“层”（Layer）。

而且对于每个连网库，一般都包含了数量众多的函数，分别涉及信息块的连接、打包和拆包；这些块的来回运输；以及握手等等。

这是一项令人痛苦的工作。

但是，连网本身的概念并不是很难。

我们想获得位于其他地方某台机器上的信息，并把它们移到这儿；或者相反。

这与读写文件非常相似，只是文件存在于远程机器上，而且远程机器有权决定如何处理我们请求或者发送的数据。

Java最出色的一个地方就是它的“无痛苦连网”概念。

有关连网的基层细节已被尽可能地提取出去，并隐藏在JVM以及Java的本机安装系统里进行控制。

我们使用的编程模型是一个文件的模型；事实上，网络连接（一个“套接字”）已被封装到系统对象里，所以可象对其他数据流那样采用同样的方法调用。

除此以外，在我们处理另一个连网问题——同时控制多个网络连接——的时候，Java内建的多线程机制也是十分方便的。

本章将用一系列易懂的例子解释Java的连网支持。

15.1 机器的标识当然，为了分辨来自别处的一台机器，以及为了保证自己连接的是希望的那台机器，必须有一种机制能独一无二地标识出网络内的每台机器。

早期网络只解决了如何在本地网络环境中为机器提供唯一的名字。

但Java面向的是整个因特网，这要求用一种机制对来自世界各地的机器进行标识。

为达到这个目的，我们采用了IP（互联网地址）的概念。

IP以两种形式存在着：(1) 大家最熟悉的DNS（域名服务）形式。

我自己的域名是。

所以假定我在自己的域内有一台名为Opus的计算机，它的域名就可以是。

毕设外文文献+翻译1

外文翻译外文原文CHANGING ROLES OF THE CLIENTS、ARCHITECTSAND CONTRACTORS THROUGH BIMAbstract:Purpose –This paper aims to present a general review of the practical implications of building information modelling (BIM) based on literature and case studies. It seeks to address the necessity for applying BIM and re-organising the processes and roles in hospital building projects. This type of project is complex due to complicated functional and technical requirements, decision making involving a large number of stakeholders, and long-term development processes.Design/methodology/approach–Through desk research and referring to the ongoing European research project InPro, the framework for integrated collaboration and the use of BIM are analysed.Findings –One of the main findings is the identification of the main factors for a successful collaboration using BIM, which can be recognised as “POWER”: product information sharing (P),organisational roles synergy (O), work processes coordination (W), environment for teamwork (E), and reference data consolidation (R).Originality/value –This paper contributes to the actual discussion in science and practice on the changing roles and processes that are required to develop and operate sustainable buildings with the support of integrated ICT frameworks and tools. It presents the state-of-the-art of European research projects and some of the first real cases of BIM application in hospital building projects.Keywords:Europe, Hospitals, The Netherlands, Construction works, Response flexibility, Project planningPaper type :General review1. IntroductionHospital building projects, are of key importance, and involve significant investment, and usually take a long-term development period. Hospital building projects are also very complex due to the complicated requirements regarding hygiene, safety, special equipments, and handling of a large amount of data. The building process is very dynamic and comprises iterative phases and intermediate changes. Many actors with shifting agendas, roles and responsibilities are actively involved, such as: the healthcare institutions, national and local governments, project developers, financial institutions, architects, contractors, advisors, facility managers, and equipment manufacturers and suppliers. Such building projects are very much influenced, by the healthcare policy, which changes rapidly in response to the medical, societal and technological developments, and varies greatly between countries (World Health Organization, 2000). In The Netherlands, for example, the way a building project in the healthcare sector is organised is undergoing a major reform due to a fundamental change in the Dutch health policy that was introduced in 2008.The rapidly changing context posts a need for a building with flexibility over its lifecycle. In order to incorporate life-cycle considerations in the building design, construction technique, and facility management strategy, a multidisciplinary collaboration is required. Despite the attempt for establishing integrated collaboration, healthcare building projects still faces serious problems in practice, such as: budget overrun, delay, and sub-optimal quality in terms of flexibility, end-user’s dissatisfaction, and energy inefficiency. It is evident that the lack of communication and coordination between the actors involved in the different phases of a building project is among the most important reasons behind these problems. The communication between different stakeholders becomes critical, as each stakeholder possesses different setof skills. As a result, the processes for extraction, interpretation, and communication of complex design information from drawings and documents are often time-consuming and difficult. Advanced visualisation technologies, like 4D planning have tremendous potential to increase the communication efficiency and interpretation ability of the project team members. However, their use as an effective communication tool is still limited and not fully explored. There are also other barriers in the information transfer and integration, for instance: many existing ICT systems do not support the openness of the data and structure that is prerequisite for an effective collaboration between different building actors or disciplines.Building information modelling (BIM) offers an integrated solution to the previously mentioned problems. Therefore, BIM is increasingly used as an ICT support in complex building projects. An effective multidisciplinary collaboration supported by an optimal use of BIM require changing roles of the clients, architects, and contractors; new contractual relationships; and re-organised collaborative processes. Unfortunately, there are still gaps in the practical knowledge on how to manage the building actors to collaborate effectively in their changing roles, and to develop and utilise BIM as an optimal ICT support of the collaboration.This paper presents a general review of the practical implications of building information modelling (BIM) based on literature review and case studies. In the next sections, based on literature and recent findings from European research project InPro, the framework for integrated collaboration and the use of BIM are analysed. Subsequently, through the observation of two ongoing pilot projects in The Netherlands, the changing roles of clients, architects, and contractors through BIM application are investigated. In conclusion, the critical success factors as well as the main barriers of a successful integrated collaboration using BIM are identified.2. Changing roles through integrated collaboration and life-cycle design approachesA hospital building project involves various actors, roles, and knowledge domains. In The Netherlands, the changing roles of clients, architects, and contractors in hospital building projects are inevitable due the new healthcare policy. Previously under the Healthcare Institutions Act (WTZi), healthcare institutions were required to obtain both a license and a building permit for new construction projects and major renovations. The permit was issued by the Dutch Ministry of Health. The healthcare institutions were then eligible to receive financial support from the government. Since 2008, new legislation on the management of hospital building projects and real estate has come into force. In this new legislation, a permit for hospital building project under the WTZi is no longer obligatory, nor obtainable (Dutch Ministry of Health, Welfare and Sport, 2008). This change allows more freedom from the state-directed policy, and respectively, allocates more responsibilities to the healthcare organisations to deal with the financing and management of their real estate. The new policy implies that the healthcare institutions are fully responsible to man age and finance their building projects and real estate. The government’s support for the costs of healthcare facilities will no longer be given separately, but will be included in the fee for healthcare services. This means that healthcare institutions must earn back their investment on real estate through their services. This new policy intends to stimulate sustainable innovations in the design, procurement and management of healthcare buildings, which will contribute to effective and efficient primary healthcare services.The new strategy for building projects and real estate management endorses an integrated collaboration approach. In order to assure the sustainability during construction, use, and maintenance, the end-users, facility managers, contractors and specialist contractors need to be involved in the planning and design processes. The implications of the new strategy are reflected in the changing roles of the building actors and in the new procurement method.In the traditional procurement method, the design, and its details, are developed by the architect, and design engineers. Then, the client (the healthcare institution) sends an application to the Ministry of Healthto obtain an approval on the building permit and the financial support from the government. Following this, a contractor is selected through a tender process that emphasises the search for the lowest-price bidder. During the construction period, changes often take place due to constructability problems of the design and new requirements from the client. Because of the high level of technical complexity, and moreover, decision-making complexities, the whole process from initiation until delivery of a hospital building project can take up to ten years time. After the delivery, the healthcare institution is fully in charge of the operation of the facilities. Redesigns and changes also take place in the use phase to cope with new functions and developments in the medical world.The integrated procurement pictures a new contractual relationship between the parties involved in a building project. Instead of a relationship between the client and architect for design, and the client and contractor for construction, in an integrated procurement the client only holds a contractual relationship with the main party that is responsible for both design and construction. The traditional borders between tasks and occupational groups become blurred since architects, consulting firms, contractors, subcontractors, and suppliers all stand on the supply side in the building process while the client on the demand side. Such configuration puts the architect, engineer and contractor in a very different position that influences not only their roles, but also their responsibilities, tasks and communication with the client, the users, the team and other stakeholders.The transition from traditional to integrated procurement method requires a shift of mindset of the parties on both the demand and supply sides. It is essential for the client and contractor to have a fair and open collaboration in which both can optimally use their competencies. The effectiveness of integrated collaboration is also determined by the client’s capacity and strategy to organize innovative tendering procedures.A new challenge emerges in case of positioning an architect in a partnership with the contractor instead of with the client. In case of the architect enters a partnership with the contractor, an important issues is how to ensure the realisation of the architectural values as well as innovative engineering through an efficient construction process. In another case, the architect can stand at the client’s side in a strategic advisory role instead of being the designer. In this case, the architect’s responsibility is translating client’s requirements and wishes into the architectural values to be included in the design specification, and evaluating the contractor’s proposal against this. In any of this new role, the architect holds the responsibilities as stakeholder interest facilitator, custodian of customer value and custodian of design models.The transition from traditional to integrated procurement method also brings consequences in the payment schemes. In the traditional building process, the honorarium for the architect is usually based on a percentage of the project costs; this may simply mean that the more expensive the building is, the higher the honorarium will be. The engineer receives the honorarium based on the complexity of the design and the intensity of the assignment. A highly complex building, which takes a number of redesigns, is usually favourable for the engineers in terms of honorarium. A traditional contractor usually receives the commission based on the tender to construct the building at the lowest price by meeting the minimum specifications given by the client. Extra work due to modifications is charged separately to the client. After the delivery, the contractor is no longer responsible for the long-term use of the building. In the traditional procurement method, all risks are placed with the client.In integrated procurement method, the payment is based on the achieved building performance; thus, the payment is non-adversarial. Since the architect, engineer and contractor have a wider responsibility on the quality of the design and the building, the payment is linked to a measurement system of the functional and technical performance of the building over a certain period of time. The honorarium becomes an incentive to achieve the optimal quality. If the building actors succeed to deliver a higher added-value thatexceed the minimum client’s requirements, they will receive a bonus in accordance to the client’s extra gain. The level of transparency is also improved. Open book accounting is an excellent instrument provided that the stakeholders agree on the information to be shared and to its level of detail (InPro, 2009).Next to the adoption of integrated procurement method, the new real estate strategy for hospital building projects addresses an innovative product development and life-cycle design approaches. A sustainable business case for the investment and exploitation of hospital buildings relies on dynamic life-cycle management that includes considerations and analysis of the market development over time next to the building life-cycle costs (investment/initial cost, operational cost, and logistic cost). Compared to the conventional life-cycle costing method, the dynamic life-cycle management encompasses a shift from focusing only on minimizing the costs to focusing on maximizing the total benefit that can be gained. One of the determining factors for a successful implementation of dynamic life-cycle management is the sustainable design of the building and building components, which means that the design carries sufficient flexibility to accommodate possible changes in the long term (Prins, 1992).Designing based on the principles of life-cycle management affects the role of the architect, as he needs to be well informed about the usage scenarios and related financial arrangements, the changing social and physical environments, and new technologies. Design needs to integrate people activities and business strategies over time. In this context, the architect is required to align the design strategies with the organisational, local and global policies on finance, business operations, health and safety, environment, etc.The combination of process and product innovation, and the changing roles of the building actors can be accommodated by integrated project delivery or IPD (AIA California Council, 2007). IPD is an approach that integrates people, systems, business structures and practices into a process that collaboratively harnesses the talents and insights of all participants to reduce waste and optimize efficiency through all phases of design, fabrication and construction. IPD principles can be applied to a variety of contractual arrangements. IPD teams will usually include members well beyond the basic triad of client, architect, and contractor. At a minimum, though, an Integrated Project should include a tight collaboration between the client, the architect, and the main contractor ultimately responsible for construction of the project, from the early design until the project handover. The key to a successful IPD is assembling a team that is committed to collaborative processes and is capable of working together effectively. IPD is built on collaboration. As a result, it can only be successful if the participants share and apply common values and goals.3. Changing roles through BIM applicationBuilding information model (BIM) comprises ICT frameworks and tools that can support the integrated collaboration based on life-cycle design approach. BIM is a digital representation of physical and functional characteristics of a facility. As such it serves as a shared knowledge resource for information about a facility forming a reliable basis for decisions during its lifecycle from inception onward (National Institute of Building Sciences NIBS, 2007). BIM facilitates time and place independent collaborative working. A basic premise of BIM is collaboration by different stakeholders at different phases of the life cycle of a facility to insert, extract, update or modify information in the BIM to support and reflect the roles of that stakeholder. BIM in its ultimate form, as a shared digital representation founded on open standards for interoperability, can become a virtual information model to be handed from the design team to the contractor and subcontractors and then to the client.BIM is not the same as the earlier known computer aided design (CAD). BIM goes further than an application to generate digital (2D or 3D) drawings. BIM is an integrated model in which all process and product information is combined, stored, elaborated, and interactively distributed to all relevant building actors. As a central model for all involved actors throughout the project lifecycle, BIM develops andevolves as the project progresses. Using BIM, the proposed design and engineering solutions can be measured against the client’s requirements and expected building performance. The functionalities of BIM to support the design process extend to multidimensional (nD), including: three-dimensional visualisation and detailing, clash detection, material schedule, planning, cost estimate, production and logistic information, and as-built documents. During the construction process, BIM can support the communication between the building site, the factory and the design office– which is crucial for an effective and efficient prefabrication and assembly processes as well as to prevent or solve problems related to unforeseen errors or modifications. When the building is in use, BIM can be used in combination with the intelligent building systems to provide and maintain up-to-date information of the building performance, including the life-cycle cost.To unleash the full potential of more efficient information exchange in the AEC/FM industry in collaborative working using BIM, both high quality open international standards and high quality implementations of these standards must be in place. The IFC open standard is generally agreed to be of high quality and is widely implemented in software. Unfortunately, the certification process allows poor quality implementations to be certified and essentially renders the certified software useless for any practical usage with IFC. IFC compliant BIM is actually used less than manual drafting for architects and contractors, and show about the same usage for engineers. A recent survey shows that CAD (as a closed-system) is still the major form of technique used in design work (over 60 per cent) while BIM is used in around 20 percent of projects for architects and in around 10 per cent of projects for engineers and contractors.The application of BIM to support an optimal cross-disciplinary and cross-phase collaboration opens a new dimension in the roles and relationships between the building actors. Several most relevant issues are: the new role of a model manager; the agreement on the access right and Intellectual Property Right (IPR); the liability and payment arrangement according to the type of contract and in relation to the integrated procurement; and the use of open international standards.Collaborative working using BIM demands a new expert role of a model manager who possesses ICT as well as construction process know-how (InPro, 2009). The model manager deals with the system as well as with the actors. He provides and maintains technological solutions required for BIM functionalities, manages the information flow, and improves the ICT skills of the stakeholders. The model manager does not take decisions on design and engineering solutions, nor the organisational processes, but his roles in the chain of decision making are focused on:the development of BIM, the definition of the structure and detail level of the model, and the deployment of relevant BIM tools, such as for models checking, merging, and clash detections;the contribution to collaboration methods, especially decision making and communication protocols, task planning, and risk management;and the management of information, in terms of data flow and storage, identification of communication errors, and decision or process (re-)tracking.Regarding the legal and organisational issues, one of the actual questions is: “In what way does the intellectual property right (IPR) in collaborative working using BIM differ from the IPR in a traditional teamwork?”. In terms of combined work, the IPR of each element is at tached to its creator. Although it seems to be a fully integrated design, BIM actually resulted from a combination of works/elements; for instance: the outline of the building design, is created by the architect, the design for the electrical system, is created by the electrical contractor, etc. Thus, in case of BIM as a combined work, the IPR is similar to traditional teamwork. Working with BIM with authorship registration functionalities may actually make it easier to keep track of the IPR.How does collaborative working, using BIM, effect the contractual relationship? On the one hand,collaborative working using BIM does not necessarily change the liability position in the contract nor does it obligate an alliance contract. The General Principles of BIM A ddendum confirms: ‘This does not effectuate or require a restructuring of contractual relationships or shifting of risks between or among the Project Participants other than as specifically required per the Protocol Addendum and its Attachments’ (ConsensusDOCS, 2008). On the other hand, changes in terms of payment schemes can be anticipated. Collaborative processes using BIM will lead to the shifting of activities from to the early design phase. Much, if not all, activities in the detailed engineering and specification phase will be done in the earlier phases. It means that significant payment for the engineering phase, which may count up to 40 per cent of the design cost, can no longer be expected. As engineering work is done concurrently with the design, a new proportion of the payment in the early design phase is necessary.4. Review of ongoing hospital building projects using BIMIn The Netherlands, the changing roles in hospital building projects are part of the strategy, which aims at achieving a sustainable real estate in response to the changing healthcare policy. Referring to literature and previous research, the main factors that influence the success of the changing roles can be concluded as: the implementation of an integrated procurement method and a life-cycle design approach for a sustainable collaborative process; the agreement on the BIM structure and the intellectual rights; and the integration of the role of a model manager. The preceding sections have discussed the conceptual thinking on how to deal with these factors effectively. This current section observes two actual projects and compares the actual practice with the conceptual view respectively.The main issues, which are observed in the case studies, are:the selected procurement method and the roles of the involved parties within this method;the implementation of the life-cycle design approach;the type, structure, and functionalities of BIM used in the project;the openness in data sharing and transfer of the model, and the intended use of BIM in the future; and the roles and tasks of the model manager.The pilot experience of hospital building projects using BIM in the Netherlands can be observed at University Medical Centre St Radboud (further referred as UMC) and Maxima Medical Centre (further referred as MMC). At UMC, the new building project for the Faculty of Dentistry in the city of Nijmegen has been dedicated as a BIM pilot project. At MMC, BIM is used in designing new buildings for Medical Simulation and Mother-and-Child Centre in the city of Veldhoven.The first case is a project at the University Medical Centre (UMC) St Radboud. UMC is more than just a hospital. UMC combines medical services, education and research. More than 8500 staff and 3000 students work at UMC. As a part of the innovative real estate strategy, UMC has considered to use BIM for its building projects. The new development of the Faculty of Dentistry and the surrounding buildings on the Kapittelweg in Nijmegen has been chosen as a pilot project to gather practical knowledge and experience on collaborative processes with BIM support.The main ambition to be achieved through the use of BIM in the building projects at UMC can be summarised as follows:using 3D visualisation to enhance the coordination and communication among the building actors, and the user participation in design;integrating the architectural design with structural analysis, energy analysis, cost estimation, and planning;interactively evaluating the design solutions against the programme of requirements and specifications;reducing redesign/remake costs through clash detection during the design process; andoptimising the management of the facility through the registration of medical installations andequipments, fixed and flexible furniture, product and output specifications, and operational data.The second case is a project at the Maxima Medical Centre (MMC). MMC is a large hospital resulted from a merger between the Diaconessenhuis in Eindhoven and St Joseph Hospital in Veldhoven. Annually the 3,400 staff of MMC provides medical services to more than 450,000 visitors and patients. A large-scaled extension project of the hospital in Veldhoven is a part of its real estate strategy. A medical simulation centre and a women-and-children medical centre are among the most important new facilities within this extension project. The design has been developed using 3D modelling with several functionalities of BIM.The findings from both cases and the analysis are as follows. Both UMC and MMC opted for a traditional procurement method in which the client directly contracted an architect, a structural engineer, and a mechanical, electrical and plumbing (MEP) consultant in the design team. Once the design and detailed specifications are finished, a tender procedure will follow to select a contractor. Despite the choice for this traditional method, many attempts have been made for a closer and more effective multidisciplinary collaboration. UMC dedicated a relatively long preparation phase with the architect, structural engineer and MEP consultant before the design commenced. This preparation phase was aimed at creating a common vision on the optimal way for collaboration using BIM as an ICT support. Some results of this preparation phase are: a document that defines the common ambition for the project and the collaborative working process and a semi-formal agreement that states the commitment of the building actors for collaboration. Other than UMC, MMC selected an architecture firm with an in-house engineering department. Thus, the collaboration between the architect and structural engineer can take place within the same firm using the same software application.Regarding the life-cycle design approach, the main attention is given on life-cycle costs, maintenance needs, and facility management. Using BIM, both hospitals intend to get a much better insight in these aspects over the life-cycle period. The life-cycle sustainability criteria are included in the assignments for the design teams. Multidisciplinary designers and engineers are asked to collaborate more closely and to interact with the end-users to address life-cycle requirements. However, ensuring the building actors to engage in an integrated collaboration to generate sustainable design solutions that meet the life-cycle performance expectations is still difficult. These actors are contracted through a traditional procurement method. Their tasks are specific, their involvement is rather short-term in a certain project phase, their responsibilities and liabilities are limited, and there is no tangible incentive for integrated collaboration.From the current progress of both projects, it can be observed that the type and structure of BIM relies heavily on the choice for BIM software applications. Revit Architecture and Revit Structure by Autodesk are selected based on the argument that it has been widely used internationally and it is compatible with AutoCAD, a widely known product of the same software manufacturer. The compatibility with AutoCAD is a key consideration at MMC since the drawings of the existing buildings were created with this application. These 2D drawings were then used as the basis to generate a 3D model with the BIM software application. The architectural model generated with Revit Architecture and the structural model generated by Revit Structure can be linked directly. In case of a change in the architectural model, a message will be sent to the structural engineer. He can then adjust the structural model, or propose a change in return to the architect, so that the structural model is always consistent with the architectural one.Despite the attempt of the design team to agree on using the same software application, the MEP consultant is still not capable to use Revit; and therefore, a conversion of the model from and to Revit is still required. Another weakness of this “closed approach”, which is dependent to the use of the same software applications, may appear in the near future when the project further progresses into the construction phase. If the contractor uses another software application, considerable extra work will be needed to make the model creted during the design phase to be compatible for use in the construction phase.。

计算机科学与技术毕业设计(论文)外文翻译

本科毕业设计(论文) 外文翻译（附外文原文）系 ( 院 )：信息科学与工程学院课题名称：学生信息管理系统专业(方向)：计算机科学与技术（应用）7.1 Enter ActionMappingsThe Model 2 architecture (see chapter 1) encourages us to use servlets and Java- Server Pages in the same application. Under Model 2, we start by calling a servlet.The servlet handles the business logic and directs control to the appropriate pageto complete the response.The web application deployment descriptor (web.xml) lets us map a URL patternto a servlet. This can be a general pattern, like *.do, or a specific path, like saveRecord.do.Some applications implement Model 2 by mapping a servlet to each business operation. This approach works, but many applications involve dozens or hundredsof business operations. Since servlets are multithreaded, instantiating so manyservlets is not the best use of server resources. Servlets are designed to handle anynumber of parallel requests. There is no performance benefit in simply creatingmore and more servlets.The servlet’s primary job is to interact with the container and HTTP. Handlinga business operation is something that a servlet could delegate to another component. Struts does this by having the ActionServlet delegate the business operationto an object. Using a servlet to receive a request and route it to a handler is knownas the Front Controller pattern [Go3].Of course, simply delegating the business operation to another componentdoes not solve the problem of mapping URIs [W3C, URI] to business operations.Our only way of communicating with a web browser is through HTTP requests and URIs. Arranging for a URI to trigger a business operation is an essential part of developing a web application.Meanwhile, in practice many business operations are handled in similar ways.Since Java is multithreaded, we could get better use of our server resources if wecould use the same Action object to handle similar operations. But for this towork, we might need to pass the object a set of configuration parameters to usewith each operation.So what’s the bottom line? To implement Model 2 in an efficient and flexibleway, we need to:Enter ActionMappings 195♉ Route requests for our business operations to a single servlet♉ Determine which business operation is related to the request♉ Load a multithreaded helper object to handle the business operation♉ Pass the helper object the specifics of each request along with any configuration detail used by this operationThis is where ActionMappings come in.7.1.1 The ActionMapping beanAn ActionMapping (org.apache.struts.action.ActionMapping) describes howthe framework handles each discrete business operation (or action). In Struts,each ActionMapping is associated with a specific URI through its path property. When a request comes in, the ActionServlet uses the path property to select the corresponding ActionMapping. The set of ActionMapping objects is kept in an ActionMappings collection (org.apache.struts.action.ActionMappings). Originally, the ActionMapping object was used to extend the Action objectrather than the Action class. When used with an Action, a mapping gives a specific Action object additional responsibilities and new functionality. So, it was essentiallyan Action decorator [Go4]. Along the way, the ActionMapping evolved into anobject in its own right and can be used with or without an Action.DEFINITION The intent of the decorator pattern is to attach additional responsibilities to an object dynamically. Decorators provide a flexible alternative to subclassingfor extending functionality [Go4].The ActionMappings are usually created through the Struts configuration file.For more about this file, see chapter 4.7.1.2 The ActionMappings catalogThe ActionMappings catalog the business logic available to a Struts application.When a request comes in, the servlet finds its entry in the ActionMappings catalogand pulls the corresponding bean.The ActionServlet uses the ActionMapping bean to decide what to do next. Itmay need to forward control off to another resource. Or it may need to populateand validate an ActionForm bean. At some point, it may have to pass control to an Action object, and when the Action returns, it may have to look up an Action-Forward associated with this mapping.196 CHAPTER 7Designing with ActionMappingsThe ActionMapping works like a routing slip for the servlet. Depending onhow the mapping is filled out, the request could go just about anywhere.The ActionMappings represent the core design of a Struts application. If youwant to figure out how a Struts application works, start with the ActionMappings. Ifyou want to figure out how to write a new Struts application, start with the Action- Mappings. The mappings are at the absolute center of every Struts application.In this chapter, we take a close look at the ActionMapping properties andexplore how they help you design the flow of a Struts application.1.0 vs 1.1 In Struts 1.1, ActionMapping subclasses ActionConfig (org.apache. struts.config.ActionConfig) and adds API methods required forbackward compatibility. ActionMapping is not deprecated, and how thehierarchy will be handled in future releases has not been determined.For now, we refer to the ActionMapping class, but you should note thatin Struts 1.1 all of the action properties are actually defined by the ActionConfigsuper class. The ActionMapping class otherwise works thesame way in both versions.7.2 ActionMapping propertiesTable 7.1 describes the base ActionMapping properties. As with other configuration components, developers may extend ActionMapping to provide additionalproperties.Table 7.1 The base ActionMapping propertiesProperty Descriptionpath The URI path from the request used to select this mapping. (API command) forward The context-relative path of the resource that should serve this request via a forward.Exactly one of the forward, include, or type properties must be specified.orinclude The context-relative path of the resource that should serve this request via aninclude. Exactly one of the forward, include, or type properties must be specified.ortype Optionally specifies a subclass oforg.apache.struts.action.ActionMappingthat should be used when instantiating this mapping.className The fully qualified name of the Action class used by this mapping. SinceStruts 1.1ActionMapping properties 197In the sections that follow, we take a look at each of these properties.7.2.1 The path propertyThe ActionMapping URI, or path, will look to the user like just another file onthe web server. But it does not represent a file. It is a virtual reference to our ActionMapping.Because it is exposed to other systems, the path is not really a logical name, likethose we use with ActionForward. The path can include slashes and an extension—as if it referred to a file system—but they are all just part of a single name.The ActionMappings themselves are a “flat” namespace with no type of internalhierarchy whatsoever. They just happen to use the same characters that we areused to seeing in hierarchical file systems.name The name of the form bean, if any, associated with this action. This is not the classname. It is the logical name used in the form bean configuration.roles The list of security roles that may access this mapping.scope The identifier of the scope (request or session) within which the form bean, if any,associated with this mapping will be created.validate Set to true if the validate method of the form bean (if any) associated with thismapping should be called.input Context-relative path of the input form to which control should be returned ifa validationerror is encountered. This can be any URI: HTML, JSP, VM, or another Action- Mapping.parameter General-purpose configuration parameter that can be used to pass extra informationto the Action selected by this ActionMapping.attribute Name of the request-scope or session-scope attribute under which our form bean isaccessed, if it is other than the bean's specified name.prefix Prefix used to match request parameter names to form bean property names, if any.suffix Suffix used to match request parameter names when populating the properties ofour ActionForm bean, if any.unknown Can be set to true if this mapping should be configured as the default for this application(to handle all requests not handled by another mapping). Only one mappingcan be defined as the default unknown mapping within an application.forwards(s) Block of ActionForwards for this mapping to use, if any.exception(s) Block of ExceptionHandlers for this mapping to use, if any.Table 7.1 The base ActionMapping properties (continued)Property DescriptionSinceStruts 1.1SinceStruts 1.1198 CHAPTER 7Designing with ActionMappingsOf course, it can still be useful to treat your ActionMappings as if they werepart of a hierarchy and group related commands under the same "folder." Theonly restriction is that the names must match whatever pattern is used in the application’s deployment description (web.xml) for the ActionServlet. This is usuallyeither /do/* or *.do, but any similar pattern can be used.If you are working in a team environment, different team members can begiven different ActionMapping namespaces to use. Some people may be workingwith the /customer ActionMappings, others may be working with the /vendor ActionMappings. This may also relate to the Java package hierarchy the team isusing. Since the ActionMapping URIs are logical constructs, they can be organizedin any way that suits your project.With Struts 1.1, these types of namespaces can be promoted to applicationmodules. Each team can work independently on its own module, with its own setof configuration files and presentation pages. Configuring your application to use multiple modules is covered in chapter 4.DEFINITION The web runs on URIs, and most URIs map to physical files. If you want to change the resource, you change the corresponding file. Some URIs, likeStruts actions, are virtual references. They do not have a correspondingfile but are handled by a programming component. To change the resource,we change how the component is programmed. But since thepath is a URI and interacts with other systems outside our control, thepath is not a true logical reference—the name of an ActionForward, forinstance. We can change the name of an ActionForward without consultingother systems. It’s an internal, logical reference. If we change thepath to an ActionMapping, we might need to update other systems thatrefer to the ActionMapping through its public URI.7.2.2 The forward propertyWhen the forward property is specified, the servlet will not pass the request to an Action class but will make a call to RequestDispatcher.forward. Since the operationdoes not use an Action class, it can be used to integrate Struts with otherresources and to prototype systems. The forward, include, and type propertiesare mutually exclusive. (See chapter 6 for more information.)7.2.3 The include propertyWhen the include property is specified, the servlet will not pass the request to an Action class but will make a call to RequestDispatcher.include. The operationActionMapping properties 199does not use an Action class and can be used to integrate Struts with other components. The forward, include, and type properties are mutually exclusive. (Seechapter 6 for more information.)7.2.4 The type propertyMost mappings will specify an Action class type rather than a forward or include.An Action class may be used by more than one mapping. The mappings may specifyform beans, parameters, forwards, or exceptions. The forward, include, andtype properties are mutually exclusive.7.2.5 The className propertyWhen specified, className is the fully qualified Java classname of the ActionMapping subclass that should be used for this object. This allows you to use your own ActionMapping subclass with specialized methods and properties. See alsosection 7.4.7.2.6 The name propertyThis property specifies the logical name for the form bean, as given in the formbean segment of the Struts configuration file. By default, this is also the name tobe used when placing the form bean in the request or session context. Use theattribute property of this class to specify a different attribute key.7.2.7 The roles propertyThis property is a comma-delimited list of the security role names that are allowed access to this ActionMapping object. By default, the same system that is used with standard container-based security is applied to the list of roles given here. Thismeans you can use action-based security in lieu of specifying URL patterns in the deployment descriptor, or you can use both together.The security check is handled by the processRoles method of the Request- Processor (org.apache.struts.action.RequestProcessor). By subclassing RequestProcessor, you can also use the roles property with application-based security. See chapter 9 for more about subclassing RequestProcessor.7.2.8 The scope propertyThe ActionForm bean can be stored in the current request or in the session scope (where it will be available to additional requests). While most developers userequest scope for the ActionForm, the framework default is session scope. Tomake request the default, see section 7.4.SinceStruts 1.1SinceStruts 1.1200 CHAPTER 7Designing with ActionMappings7.2.9 The validate propertyAn important step in the lifecycle of an ActionForm is to validate its data before offering it to the business layer. When the validate property for a mapping is true, the ActionServlet will call the ActionForm’s validate method. If validate returns false, the request is forwarded to the resource given by the input property.Often, developers will create a pair of mappings for each data entry form. Onemapping will have validate set to false, so you can create an empty form. Theother has validate set to true and is used to submit the completed form.NOTE Whether or not the ActionForm validate method is called does not relateto the ActionServlet’s validating property. That switch controlshow the Struts configuration file is processed.7.2.10 The input propertyWhen validate is set to true, it is important that a valid path for input be provided. This is where control will pass should the ActionForm validate methodreturn false. Often, this is the address for a presentation page. Sometimes it willbe another Action path (with validate set to false) that is required to generatedata objects needed by the page.NOTE The input path often leads back to the page that submitted the request.While it seems natural for the framework to return the request to whereit originated, this is not a simple task in a web application. A request is oftenpassed from component to component before a response is sent backto the browser. The browser only knows the path it used to retrieve theinput page, which may or may not also be the correct path to use for theinput property. While it may be possible to try and generate a default inputpage based on the HTTP referrer attribute, the Struts designersdeemed that approach unreliable.inputForwardIn Struts 1.0, the ActionMapping input property is always a literal URI. InStruts 1.1, it may optionally be the name of an ActionForward instead. The ActionForward is retrieved and its path property is used as the input property.This can be a global or local ActionForward.To use ActionForwards here instead of literal paths, set the inputForwardattribute on the <controller> element for this module to true:SinceStruts 1.1ActionMapping properties 201<controller inputForward="true">For more about configuring Struts, see chapter 4. For more about ActionForwards,see chapter 6.7.2.11 The parameter propertyThe generic parameter property allows Actions to be configured at runtime. Severalof the standard Struts Actions make use of this property, and the standardScaffold Actions often use it, too. The parameter property may contain a URI, the name of a method, the name of a class, or any other bit of information an Actionmay need at runtime. This flexibility allows some Actions to do double and tripleduty, slashing the number of distinct Action classes an application needs on hand.Within an Action class, the parameter property is retrieved from the mappingpassed to perform:parameter = mapping.getParameter();Multiple parametersWhile multiple parameters are not supported by the standard ActionMappingsclass, there are some easy ways to implement this, including using HttpUtils, a StringTokenizer, or a Properties file (java.util.Properties).HttpUtils. Although deprecated as of the Servlet API 2.3 specification, theHttpUtils package (javax.servlet.http.HttpUtils) provides a static method that parses any string as if it were a query string and returns a Hashtable(java.util.Hashtable):Hashtable parameters = parseQueryString(parameter);The parameter property for your mapping then becomes just another query string, because you might use it elsewhere in the Struts configuration. stringTokenizer. Another simple approach is to delimit the parameters using the token of your choice—such as a comma, colon, or semicolon—and use the StringTokenizer to read them back:StringTokenizer incoming =new StringTokenizer(mapping.getParameter(),";");int i = 0;String[] parameters = new String[incoming.countTokens()]; while (incoming.hasMoreTokens()) {parameters[i++] = incoming.nextToken().trim();}202 CHAPTER 7Designing with ActionMappingsProperties file. While slightly more complicated than the others, another popular approach to providing multiple parameters to an ActionMapping is with a standard Properties files (java.util.Properties). Depending on your needs, the Properties file could be stored in an absolute location in your file system or anywhere on your application’s CLASSPATH.The Commons Scaffold package [ASF, Commons] provides a ResourceUtils package (mons.scaffold.util.ResourceUtils) with methods forloading a Properties file from an absolute location or from your application’s CLASSPATH.7.2.12 The attribute propertyFrom time to time, you may need to store two copies of the same ActionForm inthe same context at the same time. This most often happens when ActionFormsare being stored in the session context as part of a workflow. To keep their names from conflicting, you can use the attribute property to give one ActionForm bean a different name.An alternative approach is to define another ActionForm bean in the configuration, using the same type but under a different name.7.2.13 The prefix and suffix propertiesLike attribute, the prefix and suffix properties can be used to help avoid naming conflicts in your application. When specified, these switches enable aprefix or suffix for the property name, forming an alias when it is populatedfrom the request.If the prefix this was specified, thenthisName=McClanahanbecomes equivalent toname=McClanahanfor the purpose of populating the ActionForm. Either or both parameters would call getName("McClanahan");This does not affect how the properties are written by the tag extensions. It affects how the autopopulation mechanism perceives them in the request.Nested components 2037.2.14 The unknown ActionMappingWhile surfing the Web, most of us have encountered the dreaded 404— page not found message. Most web servers provide some special features for processing requests for unknown pages, so webmasters can steer users in the right direction. Struts offers a similar service for ActionMapping 404s—the unknown ActionMapping. In the Struts configuration file, you can specify one ActionMapping toreceive any requests for an ActionMapping that would not otherwise be matched:<actionname="/debug"forward="/pages/debug.jsp"/>When this option is not set, a request for an ActionMapping that cannot bematched throws400 Invalid path /notHere was requestedNote that by a request for an ActionMapping, we mean a URI that matches the prefix or suffix specified for the servlet (usually /do/* or *.do). Requests for other URI patterns, good or bad, will be handled by other servlets or by the container:/do/notHere (goes to the unknown ActionMapping)/notHere.txt (goes to the container)7.3 Nested componentsThe ActionMapping properties are helpful when it comes to getting an Action torun a business operation. But they tell only part of the story. There is still much todo when the Action returns.An Action may have more than one outcome. We may need to register several ActionForwards so that the Action can take its pick.7.3.1 Local forwardsIn the normal course, an ActionMapping is used to select an Action object to handle the request. The Action returns an ActionForward that indicates which pageshould complete the response.The reason we use ActionForwards is that, in practice, presentation pages areeither often reused or often changed, or both. In either case, it is good practice to encapsulate the page’s location behind a logical name, like “success” or “failure.”The ActionForward object lets us assign a logical name to any given URI.204 CHAPTER 7Designing with ActionMappingsOf course, logical concepts like success or failure are often relative. What represents success to one Action may represent failure to another. Each Action-Mapping can have its own set of local ActionForwards. When the Action asks for a forward (by name), the local set is checked before trying the global forwards. See chapter 6 for more about ActionForwards.Local forwards are usually specified in the Struts configuration file. See chapter4 for details.7.3.2 Local exceptionsMost often, an application’s exception handlers (org.apache.struts.action. ExceptionHandler) can be declared globally. However, if a given ActionMapping needs to handle an exception differently, it can have its own set of local exception handlers that are checked before the global set.Local exceptions are usually specified in the Struts configuration file. Seechapter 4 for details.7.4 Rolling your own ActionMappingWhile ActionMapping provides an impressive array of properties, developers may also provide their own subclass with additional properties or methods. InStruts 1.0, this is configured in the deployment descriptor (web.xml) for the ActionServlet:<init-param><param-name>mapping</param-name><param-value>app.MyActionMapping</param-value></init-param>In Struts 1.1, this is configured in the Struts configuration file as an attribute to the <action-mappings> element:<action-mappings type="app.MyActionMapping">Individual mappings may also be set to use another type through the className attribute:<action className="app.MyActionMapping">For more about configuring Struts, see chapter 4.SinceStruts 1.1Summary 205The framework provides two base ActionMapping classes, shown in table 7.2. They can be selected as the default or used as a base for your own subclasses.The framework default is SessionActionMapping, so scope defaults to session. Subclasses that provide new properties may set them in the Struts configuration using a standard mechanism:<set-property property="myProperty" value="myValue" /> Using this standard mechanism helps developers avoid subclassing the Action- Servlet just to recognize the new properties when it digests the configuration file. This is actually a feature of the Digester that Struts simply inherits.7.5 SummarySun’s Model 2 architecture teaches that servlets and JavaServer Pages should be used together in the same application. The servlets can handle flow control and data acquisition, and the JavaServer Pages can handle the HTML.Struts takes this one step further and delegates much of the flow control anddata acquisition to Action objects. The application then needs only a single servletto act as a traffic cop. All the real work is parceled out to the Actions and theStruts configuration objects.Like servlets, Actions are efficient, multithreaded singletons. A single Actionobject can be handling any number of requests at the same time, optimizing your server’s resources.To get the most use out of your Actions, the ActionMapping object is used as a decorator for the Action object. It gives the Action a URI, or several URIs, and away to pass different configuration settings to an Action depending on which URIis called.In this chapter, we took a close look at the ActionMapping properties andexplained each property’s role in the scheme of things. We also looked at extendingthe standard ActionMapping object with custom properties—just in case yourscheme needs even more things.Table 7.2 The default ActionMapping classesActionMapping Descriptionorg.apache.struts.action.SessionActionMapping Defaults the scope property to sessionorg.apache.struts.action.RequestActionMapping Defaults the scope property to request206 CHAPTER 7Designing with ActionMappingsIn chapter 8, the real fun begins. The configuration objects covered so far aremainly a support system. They help the controller match an incoming requestwith a server-side operation. Now that we have the supporting players, let’s meet the Struts diva: the Action object.7.1 进入ActionMappingModel 2 架构(第1章)鼓励在同一个应用中使用servlet和JSP页面。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

南京理工大学毕业设计(论文)外文资料翻译教学点：南京信息职业技术学院专业：电子信息工程姓名：陈洁学号： 014910253034外文出处：《 Pci System Architecture 》(用外文写)附件： 1.外文资料翻译译文；2.外文原文。

指导教师评语：该生外文翻译没有基本的语法错误，用词准确，没有重要误译，忠实原文；译文通顺，条理清楚，数量与质量上达到了本科水平。

签名：年月日注：请将该封面与附件装订成册。

附件1：外文资料翻译译文64位PCI扩展1.64位数据传送和64位寻址：独立的能力PCI规范给出了允许64位总线主设备与64位目标实现64位数据传送的机理。

在传送的开始，如果回应目标是一个64位或32位设备，64位总线设备会自动识别。

如果它是64位设备，达到8个字节（一个4字）可以在每个数据段中传送。

假定是一串0等待状态数据段。

在33MHz总线速率上可以每秒264兆字节获取（8字节／传送＊33百万传送字／秒），在66MHz总线上可以528M字节／秒获取。

如果回应目标是32位设备，总线主设备会自动识别并且在下部4位数据通道上（AD[31::00]）引导，所以数据指向或来自目标。

规范也定义了64位存储器寻址功能。

此功能只用于寻址驻留在4GB地址边界以上的存储器目标。

32位和64位总线主设备都可以实现64位寻址。

此外，对64位寻址反映的存储器目标（驻留在4GB地址边界上）可以看作32位或64位目标来实现。

注意64位寻址和64位数据传送功能是两种特性，各自独立并且严格区分开来是非常重要的。

一个设备可以支持一种、另一种、都支持或都不支持。

2.64位扩展信号为了支持64位数据传送功能，PCI总线另有39个引脚。

●REQ64#被64位总线主设备有效表明它想执行64位数据传送操作。

REQ64#与FRAME#信号具有相同的时序和间隔。

REQ64#信号必须由系统主板上的上拉电阻来支持。

当32位总线主设备进行传送时，REQ64#不能又漂移。

●ACK64#被目标有效以回应被主设备有效的REQ64#（如果目标支持64位数据传送），ACK64#与DEVSEL#具有相同的时序和间隔（但是直到REQ64#被主设备有效，ACK64#才可被有效）。

像REQ64#一样，ACK64#信号线也必须由系统主板上的上拉电阻来支持。

当32位设备是传送目标时，ACK64#不能漂移。

●AD[64::32]包含上部4位地址／数据通道。

●C/BE#[7::4]包含高4位命令/字节使能信号。

●PAR64是为上部4个AD通道和上部4位C/BE信号线提供偶校验的奇偶校验位。

以下是几小结详细讨论64位数据传送和寻址功能。

3.在32位插入式连接器上的64位卡安装在32位扩展槽上的64位卡只能自动地使用总线的下半部来执行传送，这是事实，因为系统主板的设计者将连接器上的REQ64#输出引脚和ACK64#输入引脚与系统主板上的上拉电阻分别连接而没有其它连接。

当64位总线主设备安装在32位插槽并开始交易时，对于任何目标REQ64#的有效是不可见的。

此外，ACK64#输出总被采样无效（因为它在系统主板上被上拉），这就迫使总线主设备在传送时只能使能总线下部分。

而且，如果交易中被寻址的目标是64位的，它会采样无效的REQ64#（因为它在系统主板上被上拉），这就迫使目标在传送时只能利用总线下部分，并且使ACK64#输出为不可用。

在自身卡上的64位扩展信号线在它们使用时不能有漂移。

如果插卡上的COMS输入接收器出现振动和泄露过量的电流，这就违反了规范的“绿色”原则。

当插卡安装在32位槽时，它不能使用总线的上半部。

插卡检测插槽的类型的方法（在启动开始时采样REQ64#无效）下一节将描述。

4.当未使用时，上拉可防止64位扩展的漂移在未使用时如果允许64位扩展信号（AD[63::32]、C/BE[7::4]和PAR64）漂移，那么插卡上的CMOS输入缓存器将振动并且泄漏过量电流。

当不再使用时,为了防止扩展的漂移，要求系统主板设计者在扩展信号上加上拉电阻来防止漂移，因为这些上拉电阻可保证扩展位不漂移，嵌入在系统板上的64位设备和安装在64位PCI插入式连接器上的64位卡，当它们不使用扩展位位时，不需要采取任何特殊措施防止扩展槽漂移。

64位扩展在以下环境中不使用：1．PCI总线空闲。

2．32位总线组设备正与一个32为目标进行交易。

3．32位总线主设备与一个64位目标进行交易，当在交易的起始检测到REQ64#无效时，目标不用总线的上半部。

4．64位总线主设备寻址一个目标已进行32位数据传送（REQ64#无效），并且目标驻留在低于4GB地址边界以下（在地址段和数据段不使用总线上半部）。

不管目标是32位还是64位，在数据中不使用总线的上半部（因为REQ64#无效）。

5．一个64位总线主设备试图与驻留在4GB边界以下的32位存储器目标进行传送时（REQ64#无效）。

在此情况下，主设备在地址段中只能使用总线的下半部分（因为它仅生成32位地址）。

当它发现当前寻址的目标是32位目标时（当DEVSEL#无效时ACK64#不能有效），主设备在数据段中停止使用总线的下半部。

4.1 32位PCI 连接器上的64位插卡64位卡允许安装在32位卡插卡连接器上。

连接器的主要部分（32位）包括所有32位PCI信号，同时连接器的扩展包含64位信号（除了放置在连接器32位部分的REQ64#和ACK64#）.当64位设备安装在32位扩展槽上时，在AD[63::32]、C/BE[7::4]和PAR64上的系统主板上拉对插入式卡是不可用的。

这就意味着连接到扩展信号号上的插入式输入缓存器将会漂移，震动和泄漏电流。

规范中强调插入卡设计者不能通过在插入卡的扩展线上提供上拉电阻来解决这个问题，当卡安装在64位扩展槽中用此方法会引起一些问题，在这些信号线上会需要2套上拉电阻（一套在插卡上，另一套在系统主板上）。

如果所有设计者都用此方法，若共有多个64位插卡的设备装入连接器上时，将会由多个上拉电阻在扩展信号线上，这就会造成上拉电阻过载。

规范中对一个64位插卡给出了如何在起始时间确定是安装在了32位连接器上还是64位连接器上的方法。

如果插卡检测出被插入了64位连接器上时，系统主板上的上拉电阻可在扩展信号不使用时防止卡上的输入接受不漂移；另一方面，如果64位插卡检测出被插入32位卡连接器上时，卡上的逻辑可防止输入接收器的漂移，规范中列举了近似于以下几种方法：●将输入缓存器关闭。

●不断的驱动输出（因为它们没有连接任何器件）。

4.2 64位插卡如何确定所安装插槽的类型当系统被加电时，复位信号会自动被有效。

在此期间，系统主板上的逻辑必须有效REQ64#、还有RST#。

REQ64#上面有一个上拉电阻与集成在系统主板上的所有64位设备和所有64位PCI扩展槽上的REQ64#引脚相连。

规范指出了每个32位PCI扩展槽上的REQ64#信号线（REQ64#和ACK64#放置在连接器的32位部分），每一个都有自己独立的上拉电阻。

在复位期间，系统主板复位逻辑最初有效PCI RST#信号同时供电电源的POWERGOOD 信号被无效。

在RST#有效过程中，系统主板逻辑有效REQ64#并保持有效直至它消除了RST#信号。

在POWERGOOD被电源逻辑有效时，系统主板复位逻辑会无效PCI RST#信号。

在RST#有效的尾部边沿，要求所有64位设备采样REQ64#信号的状态。

嵌入在系统主板或安装在64位扩展槽上的所有64位设备在RST#的尾沿采样REQ#有效，这就要求它们镰刀系统主板上的扩展上拉电阻上并且当不使用它们时不需要采取特殊措施防止扩展信号漂移。

安装在32位插卡槽上的所有64位设备，在RST#的尾部边沿都可检测到无效的REQ64#，这就告知它们需要连接扩展信号上的系统主板的上拉电阻，插卡逻辑必须对本身的64位卡上的扩展信号线的状态负责。

所以插卡必须使用前一节提过的方法之一，防止卡的输入接受器泄漏过量电流。

附件2：外文原文The 64-bit PCI ExtensionThe 64-bit PCI ExtensionThis chapter describes the 64-bit extension that permits masters and targets to perform eight byte transfers during each data phase. It also describes 64-bit addressing used to address memory targets that reside above the 4GB boundary.1．64-bit Ata Transfers and 64-bit Addressing: Seperate CapabilitiesThe PCI specification provides a mechanism that permits a 64-bit bus master to perform 64-bit data transfers with a 64-bit target. At the beginning of a transaction, the 64-bit bus maser automatically senses if the responding target is a 64-bit or a 32-bit device. If it’s a 64-bit device, up to eight bytes(a quadword) may be transferred during each data phase. Assuming a series of 0-wait state data phases, throughput of 264Mbytes/second can be achieved at a bus speed of 33MHz(8 bytes/transfer x 33 million transfers/second) and 528Mbytes/second at66MHz.If the responding target is a 32-bit device, the bus master automatically senses this and steers all data to or from the target over the lower four data paths(AD[31:0]).The specification also defines 64-bit memory addressing capability. This capability is only used to address memory targets that reside above the 4GB address boundary. Both 32-and 64[bit bus masters can perform 64-bit addressing. In addition, memory target(that reside over the 4GB address boundary) that respond to 64-bit addressing can be implemented as either 32-or 64-bit targets.2．64-Bit Extension SignalsIn order to support the 64-bit data transfer capability, the PCI bus implements an additional thirty-nine pins:●REQ64# is asserted by a 64-bit bus master to indicate that is would like to perform64-bit data transfers.REQ64# has the same timing and duration a s the FRAME# signal.The REQ64# signal line must be supplied with a pull up resistor on the system board.REQ64# cannot be permitted to float when a 32-bit bus master is performing a transaction.●ACK64# is asserted by a target in response to REQ64# assertion by the master (if thetarget supports 64-bit data transfers).ACK64# has the same timing and duration as DEVSEL#(but ACK64# must not be asserted unless REQ64# is asserted by the initiator).Like REQ64#,the AcK64# signal line must also be supplied with a pullup resistor on the system board.ACK64# cannot be permitted to float when a 32-bit device si the target of transaction.●AD [63::32] comprise the upper four address/data paths.●C/BE# [7::4] comprise the upper four command/byte enable signals.●PAR64 is the parity bit that provides even parity for the upper four AD paths and theupper four C/BE signal lines.The following sections provide a detailed discussion of 64-bit data master and addressing capability.3．64-bit Cards in 32-bit Add-in ConnectorsA 64-bit card installed in a 32-bit expansion slot automatically only uses the lower half of the bus to perform transfers. This is true because the system board designer connects theREQ64# output pin and the ACK64# input pin on the connector to individual pull-ups on the system board and to nothing else.When a 64-bit bus master is installed in a 32-bit card slot and it initiates a transaction, its assertion of REQ64# is not visible to any of the target. In addition, its ACK64# input is always sampled deasserted (because it’s pulled up on the system board).This forces the bus master to use only the lower part of the bus during the transfer. Furthermore, if the target addressed in the transaction is a 64-bit target, it samples REQ74# deasserted (because it’s pulled up on the system board),forcing it to only utilize the lower half of the bus during the transaction and to disable its ACK64# output.The 64-bit extension signal lines on the card itself cannot be permitted to float when they are not in use. The CMOS input receives on the card would oscillate and draw excessive current, thus violating the “green” aspect of the specification. hen the card is installed in a 32- bit slot, it cannot use the upper half of the bus. The manner in which the card detects the type of slot (REQ64# sampled deasserted at startup time) is described in the next section.4．Pullups Prevent 64-bit Extension from Floating When Not in UseIf the 64-bit extension signals (AD[63::32],C/BE[7::4]# and PAR64 are permitted to float when not in use, the CMOS input buffers on the card will oscillate and draw excessive current. In order to prevent the extension signals to keep them from floating. Because these pull-ups are guaranteed to keep the extension from floating when not in use, 64-bit devices that are embedded on the system board and 64-bit cards installed in 64-bit PCI add-in connectors don’t need to take any special action to keep the extension from floating when they are not using it.The 64-bit extension is not in use under the following circumstance:1.The PCI bus is idle.2. A 32-bit bus master is performing a transaction with a 32-bit target.3. A 32-bit bus master is performing a transaction with a 64-bit target. Upondetecting REQ64# deasserted at the start of the transaction, the target will notuse the upper half of the bus.4. A 64-bit bus master addresses a target to perform 32-bit data transfers (REQ64#deasserted) and the target resides below the 4GB boundary. In this case, theinitiator only uses the lower half of the bus during the address phase(because it’s only generating a 32-bit address).When it discovers the currently-addressedtarget is a 32-bit target(ACK64# not asserted when DEVSEL# asserted),theinitiator ceases to use the upper half at the bus during the data phases.4.1. a 64-bit Card in a 32-bit PCI ConnectorInstallation of a 64-bit card in a 32-bit card connector is permitted. The main(32-bit) portion of the connector contains all of the 32-bit PCI signals, which an extension to the connector contains the 64-bit extension signal(with the exception of REQ64# and ACK64# which are located on the 32-bit portion of the connector).When a 64-bit device is installed in a 32-bit PCI expansion slot, the system board pull-ups on AD[63::32],C/BE#[7::4] and PAR64 are not available to the add-in card. This means that the add-in card’s input buffers that are connected to the extension signal pins will float, oscillate, and draw excessive current.The specification states that the add-in card designer must not solve the problem by supplying pullup resistors on the extension lines on the add-in card. Using this approach would cause problems when the card is installed in a 64-bit expansion slot. There would then be towsets of pullup resistor on these signal line (the ones on the card plus the ones on the system board).If all designer solved the problem in this manner, a machine with multiple 64-bit cards inserted in 64-bit card connectors would have multiple pull-ups on the extension signal, resulting in pullup current overload.The specification provides a method for a 64-b9it card to determine at startup time whether it’s installed in a 32-bit or a 64-bit connector. If the card detects that it is plugged into a 64-bit connector, the pull-ups on the system board will keep the input receives on the card from floating when the extension is not in use. On the other hand, if a y64-bit card detects that it is a 32-bit card connector, the logic on the card must keep the input receives from switching. The specification states that an approach similar to one of the following should be use:●Biasing the input buffer to turning it off.●Actively driving the outputs continually (since they aren’t connected to anything).4.2.How 64-bit Card Determines Type of Slot installed InWhen the system is powered up, the reset signal is automatically asserted. During this period of time, the logic on the system board must assert the REQ64# signal as well as RST#.REQ64# has a single pullup resistor on it and is connected to the REQ64# pin on all 64-bit devices integrated onto the system board and on all 64-bit PCI expansion slot. The specification states that the REQ64# signal line on each 32-bit PCI expansion slot (REQ64# and ACK64# are located on the 32-bit portion of the connector), however, each has its own independent pullup resistor. During reset time, the system board reset logic initially asserts the PCI RST# signal while the POWERGOOD signal from the power supply is deasserted .During the assertion of RST# signal. When POWERGOOD is asserted by the power supply logic, the system board reset logic deasserts the PCI RST# signal. On the trailing-edge of RST# assertion, all 64-bit devices are required to sample the stated of the REQ64# signal.All 64-bit devices that are embedded on the system board or that they are installed in 64-bit expansion slots sample REQ64# asserted on the trailing-edge of RST#. This informs them that they are connected to the extension pull-ups on the system board and need take no special action to keep the extension from floating when not using it.All 64－bit devices that are installed in 32-bit card slot, however detect REQ64# desserted on the trailing-edge of RST#. This informs them that they are not connected to the system board resident pull-ups on the extension signal. The card logic must therefore take responsibility for the state of its own on-card 64-bit extension signal lines. The card must therefore use one of the methods cited in the previous section to prevent excessive current draw by the card’s input receivers.。