软件工程外文翻译文献
软件工程外文翻译文献
(文档含中英文对照即英文原文和中文翻译)
Software engineering
Software engineering is the study of the use of engineering methods to build and maintain effective, practical and high-quality software disciplines. It involves the programming language, database, software development tools, system platform, standards, design patterns and so on.
In modern society, the software used in many ways. Typical software such as email, embedded systems, human-machine interface, office packages, operating systems, compilers, databases, games. Meanwhile, almost all the various sectors of computer software applications, such as industry, agriculture, banking, aviation and government departments. These applications facilitate the economic and social development,
improve people's working efficiency, while improving the quality of life. Software engineers is to create software applications of people collectively, according to which software engineers can be divided into different areas of system analysts, software designers, system architects, programmers, testers and so on. It is also often used to refer to a variety of software engineers, programmers.
Origin
In view of difficulties encountered in software development, North Atlantic Treaty Organization (NATO) in 1968 organized the first Conference on Software Engineering, and will be presented at the "software engineering" to define the knowledge required for software development, and suggested that "software development the activities of similar projects should be. " Software Engineering has formally proposed since 1968, this time to accumulate a large number of research results, widely lot of technical practice, academia and industry through the joint efforts of software engineering is gradually developing into a professional discipline.
Definition
creation and use of sound engineering principles in order to obtain reliable and economically efficient software.
application of systematic, follow the principle can be measured approach to development, operation and maintenance of software; that is to be
applied to software engineering.
The development, management and updating software products related to theories, methods and tools.
A knowledge or discipline (discipline), aims to produce good quality, punctual delivery, within budget and meet users need software.
the practical application of scientific knowledge in the design, build computer programs, and the accompanying documents produced, and the subsequent operation and maintenance.
Use systematic production and maintenance of software products related to technology and management expertise to enable software development and changes in the limited time and under cost.
Construction team of engineers developed the knowledge of large software systems disciplines.
the software analysis, design, implementation and maintenance of a systematic method.
the systematic application of tools and techniques in the development of computer-based applications.
Software Engineering and Computer Science
Software development in the end is a science or an engineering, this is a question to be debated for a long time. In fact, both the two characteristics of software development. But this does not mean that they can be confused with each other. Many people think that software
engineering, computer science and information science-based as in the traditional sense of the physical and chemical engineering as. In the U.S., about 40% of software engineers with a degree in computer science. Elsewhere in the world, this ratio is also similar. They will not necessarily use every day knowledge of computer science, but every day they use the software engineering knowledge.
For example, Peter McBreen that software "engineering" means higher degree of rigor and proven processes, not suitable for all types of software development stage. Peter McBreen in the book "Software Craftsmanship: The New Imperative" put forward the so-called "craftsmanship" of the argument, consider that a key factor in the success of software development, is to develop the skills, not "manufacturing" software process.
Software engineering and computer programming
Software engineering exists in a variety of applications exist in all aspects of software development. The program design typically include program design and coding of the iterative process, it is a stage of software development.
Software engineering, software project seeks to provide guidance in all aspects, from feasibility analysis software until the software after completion of maintenance work. Software engineering that software development and marketing activities are closely related. Such as
software sales, user training, hardware and software associated with installation. Software engineering methodology that should not be an independent programmer from the team and to develop, and the program of preparation can not be divorced from the software requirements, design, and customer interests.
Software engineering design of industrial development is the embodiment of a computer program.
Software crisis
Software engineering, rooted in the 20th century to the rise of 60,70 and 80 years of software crisis. At that time, many of the software have been a tragic final outcome. Many of the software development time significantly beyond the planned schedule. Some projects led to the loss of property, and even some of the software led to casualties. While software developers have found it increasingly difficult for software development.
OS 360 operating system is considered to be a typical case. Until now, it is still used in the IBM360 series host. This experience for decades, even extremely complex software projects do not have a set of programs included in the original design of work systems. OS 360 is the first large software project, which uses about 1,000 programmers. Fred Brooks in his subsequent masterpiece, "The Mythical Man Month" (The Mythical Man-Month) in the once admitted that in his management of the
project, he made a million dollar mistake.
Property losses: software error may result in significant property damage. European Ariane rocket explosion is one of the most painful lesson.
Casualties: As computer software is widely used, including hospitals and other industries closely related to life. Therefore, the software error might also result in personal injury or death.
Was used extensively in software engineering is the Therac-25 case of accidents. In 1985 between June and January 1987, six known medical errors from the Therac-25 to exceed the dose leads to death or severe radiation burns.
In industry, some embedded systems do not lead to the normal operation of the machine, which will push some people into the woods. Methodology
There are many ways software engineering aspects of meaning. Including project management, analysis, design, program preparation, testing and quality control.
Software design methods can be distinguished as the heavyweight and lightweight methods. Heavyweight methods produce large amounts of official documentation.
Heavyweight development methodologies, including the famous ISO 9000, CMM, and the Unified Process (RUP).
Lightweight development process is not an official document of the large number of requirements. Lightweight methods, including well-known Extreme Programming (XP) and agile process (Agile Processes).
According to the "new methodology" in this article, heavyweight method presented is a "defensive" posture. In the application of the "heavyweight methods" software organizations, due to a software project manager with little or no involvement in program design, can not grasp the item from the details of the progress of the project which will have a "fear", constantly had to ask the programmer to write a lot of "software development documentation." The lightweight methods are presented "aggressive" attitude, which is from the XP method is particularly emphasized four criteria - "communication, simplicity, feedback and courage" to be reflected on. There are some people that the "heavyweight method" is suitable for large software team (dozens or more) use, and "lightweight methods" for small software team (a few people, a dozen people) to use. Of course, on the heavyweight and lightweight method of approach has many advantages and disadvantages of debate, and various methods are constantly evolving.
Some methodologists think that people should be strictly followed in the development and implementation of these methods. But some people do not have the conditions to implement these methods. In fact, the
method by which software development depends on many factors, but subject to environmental constraints.
Software development process
Software development process, with the subsequent development of technology evolution and improvement. From the early waterfall (Waterfall) development model to the subsequent emergence of the spiral iterative (Spiral) development, which recently began the rise of agile development methodologies (Agile), they showed a different era in the development process for software industry different awareness and understanding of different types of projects for the method.
Note distinction between software development process and software process improvement important difference between. Such as ISO 15504, ISO 9000, CMM, CMMI such terms are elaborated in the framework of software process improvement, they provide a series of standards and policies to guide software organizations how to improve the quality of the software development process, the ability of software organizations, and not give a specific definition of the development process.
Development of software engineering
"Agile Development" (Agile Development) is considered an important software engineering development. It stressed that software development should be able to possible future changes and uncertainties
of a comprehensive response.
Agile development is considered a "lightweight" approach. In the lightweight approach should be the most prestigious "Extreme Programming" (Extreme Programming, referred to as XP).Correspond with the lightweight approach is the "heavyweight method" exists. Heavyweight approach emphasizes the development process as the center, rather than people-centered. Examples of methods such as heavyweight CMM / PSP / TSP.
Aspect-oriented programming (Aspect Oriented Programming, referred to as the AOP) is considered to software engineering in recent years, another important development. This aspect refers to the completion of a function of a collection of objects and functions. In this regard the contents related to generic programming (Generic Programming) and templates.
软件工程
软件工程是一门研究用工程化方法构建和维护有效的、实用的和高质量的软件的学科。它涉及到程序设计语言、数据库、软件开发工具、系统平台、标准、设计模式等方面。
在现代社会中，软件应用于多个方面。典型的软件比如有电子邮件、嵌入式系统、人机界面、办公包、操作系统、编译器、数据库、游戏等。同时，各个行业几乎都有计算机软件的应用，比如工业、农业、银行、航空、政府部门等。这些应用促进了经济和社会的发展，提高人们的工作效率，同时提升了生活质量。
软件工程师是对应用软件创造软件的人们的统称，软件工程师按照所处的领域不同可以分为系统分析员、软件设计师、系统架构师、程序员、测试员等等。人们也常常用程序员来泛指各种软件工程师。
由来
鉴于软件开发时所遭遇困境，北大西洋公约组织（NATO）在1968年举办了首次软件工程学术会议，并于会中提出“软件工程”来界定软件开发所需相关知识，并建议“软件开发应该是类似工程的活动”。软件工程自1968年正式提出至今，这段时间累积了大量的研究成果，广泛地进行大量的技术实践，借由学术界和产业界的共同努力，软件工程正逐渐发展成为一门专业学科。
定义
创立与使用健全的工程原则，以便经济地获得可靠且高效率的软件.
应用系统化，遵从原则，可被计量的方法来发展、操作及维护软件；也就是把工程应用到软件上。
与开发、管理及更新软件产品有关的理论、方法及工具。
一种知识或学科（discipline），目标是生产品质良好、准时交货、符合预算，并满足用户所需的软件。
实际应用科学知识在设计、建构电脑程序，与相伴而来所产生的文件，以及后续的操作和维护上。
使用与系统化生产和维护软件产品有关之技术与管理的知识，使软件开发与修改可在有限的时间与费用下进行。
建造由工程师团队所开发之大型软件系统有关的知识学科。
土木工程类专业英文文献及翻译
PA VEMENT PROBLEMS CAUSED BY COLLAPSIBLE SUBGRADES By Sandra L. Houston,1 Associate Member, ASCE (Reviewed by the Highway Division) ABSTRACT: Problem subgrade materials consisting of collapsible soils are com- mon in arid environments, which have climatic conditions and depositional and weathering processes favorable to their formation. Included herein is a discussion of predictive techniques that use commonly available laboratory equipment and testing methods for obtaining reliable estimates of the volume change for these problem soils. A method for predicting relevant stresses and corresponding collapse strains for typical pavement subgrades is presented. Relatively simple methods of evaluating potential volume change, based on results of familiar laboratory tests, are used. INTRODUCTION When a soil is given free access to water, it may decrease in volume, increase in volume, or do nothing. A soil that increases in volume is called a swelling or expansive soil, and a soil that decreases in volume is called a collapsible soil. The amount of volume change that occurs depends on the soil type and structure, the initial soil density, the imposed stress state, and the degree and extent of wetting. Subgrade materials comprised of soils that change volume upon wetting have caused distress to highways since the be- ginning of the professional practice and have cost many millions of dollars in roadway repairs. The prediction of the volume changes that may occur in the field is the first step in making an economic decision for dealing with these problem subgrade materials. Each project will have different design considerations, economic con- straints, and risk factors that will have to be taken into account. However, with a reliable method for making volume change predictions, the best design relative to the subgrade soils becomes a matter of economic comparison, and a much more rational design approach may be made. For example, typical techniques for dealing with expansive clays include: (1) In situ treatments with substances such as lime, cement, or fly-ash; (2) seepage barriers and/ or drainage systems; or (3) a computing of the serviceability loss and a mod- ification of the design to "accept" the anticipated expansion. In order to make the most economical decision, the amount of volume change (especially non- uniform volume change) must be accurately estimated, and the degree of road roughness evaluated from these data. Similarly, alternative design techniques are available for any roadway problem. The emphasis here will be placed on presenting economical and simple methods for: (1) Determining whether the subgrade materials are collapsible; and (2) estimating the amount of volume change that is likely to occur in the 'Asst. Prof., Ctr. for Advanced Res. in Transp., Arizona State Univ., Tempe, AZ 85287. Note. Discussion open until April 1, 1989. To extend the closing date one month,
软件开发概念和设计方法大学毕业论文外文文献翻译及原文
毕业设计（论文）外文文献翻译 文献、资料中文题目：软件开发概念和设计方法文献、资料英文题目： 文献、资料来源： 文献、资料发表（出版）日期： 院（部）： 专业： 班级： 姓名： 学号： 指导教师： 翻译日期： 2017.02.14
外文资料原文 Software Development Concepts and Design Methodologies During the 1960s, ma inframes and higher level programming languages were applied to man y problems including human resource s yste ms,reservation s yste ms, and manufacturing s yste ms. Computers and software were seen as the cure all for man y bu siness issues were some times applied blindly. S yste ms sometimes failed to solve the problem for which the y were designed for man y reasons including: ?Inability to sufficiently understand complex problems ?Not sufficiently taking into account end-u ser needs, the organizational environ ment, and performance tradeoffs ?Inability to accurately estimate development time and operational costs ?Lack of framework for consistent and regular customer communications At this time, the concept of structured programming, top-down design, stepwise refinement，and modularity e merged. Structured programming is still the most dominant approach to software engineering and is still evo lving. These failures led to the concept of "software engineering" based upon the idea that an engineering-like discipl ine could be applied to software design and develop ment. Software design is a process where the software designer applies techniques and principles to produce a conceptual model that de scribes and defines a solution to a problem. In the beginning, this des ign process has not been well structured and the model does not alwa ys accurately represent the problem of software development. However,design methodologies have been evolving to accommo date changes in technolog y coupled with our increased understanding of development processes. Whereas early desig n methods addressed specific aspects of the
英文文献及中文翻译
毕业设计说明书 英文文献及中文翻译 学院：专 2011年6月 电子与计算机科学技术软件工程
https://www.360docs.net/doc/7614452257.html, Overview https://www.360docs.net/doc/7614452257.html, is a unified Web development model that includes the services necessary for you to build enterprise-class Web applications with a minimum of https://www.360docs.net/doc/7614452257.html, is part of https://www.360docs.net/doc/7614452257.html, Framework,and when coding https://www.360docs.net/doc/7614452257.html, applications you have access to classes in https://www.360docs.net/doc/7614452257.html, Framework.You can code your applications in any language compatible with the common language runtime(CLR), including Microsoft Visual Basic and C#.These languages enable you to develop https://www.360docs.net/doc/7614452257.html, applications that benefit from the common language runtime,type safety, inheritance,and so on. If you want to try https://www.360docs.net/doc/7614452257.html,,you can install Visual Web Developer Express using the Microsoft Web Platform Installer,which is a free tool that makes it simple to download,install,and service components of the Microsoft Web Platform.These components include Visual Web Developer Express,Internet Information Services (IIS),SQL Server Express,and https://www.360docs.net/doc/7614452257.html, Framework.All of these are tools that you use to create https://www.360docs.net/doc/7614452257.html, Web applications.You can also use the Microsoft Web Platform Installer to install open-source https://www.360docs.net/doc/7614452257.html, and PHP Web applications. Visual Web Developer Visual Web Developer is a full-featured development environment for creating https://www.360docs.net/doc/7614452257.html, Web applications.Visual Web Developer provides an ideal environment in which to build Web sites and then publish them to a hosting https://www.360docs.net/doc/7614452257.html,ing the development tools in Visual Web Developer,you can develop https://www.360docs.net/doc/7614452257.html, Web pages on your own computer.Visual Web Developer includes a local Web server that provides all the features you need to test and debug https://www.360docs.net/doc/7614452257.html, Web pages,without requiring Internet Information Services(IIS)to be installed. Visual Web Developer provides an ideal environment in which to build Web sites and then publish them to a hosting https://www.360docs.net/doc/7614452257.html,ing the development tools in Visual Web Developer,you can develop https://www.360docs.net/doc/7614452257.html, Web pages on your own computer.
土木工程外文翻译
转型衰退时期的土木工程研究 Sergios Lambropoulosa[1], John-Paris Pantouvakisb, Marina Marinellic 摘要 最近的全球经济和金融危机导致许多国家的经济陷入衰退，特别是在欧盟的周边。这些国家目前面临的民用建筑基础设施的公共投资和私人投资显著收缩，导致在民事特别是在民用建筑方向的失业。因此，在所有国家在经济衰退的专业发展对于土木工程应届毕业生来说是努力和资历的不相称的研究，因为他们很少有机会在实践中积累经验和知识，这些逐渐成为过时的经验和知识。在这种情况下，对于技术性大学在国家经济衰退的计划和实施的土木工程研究大纲的一个实质性的改革势在必行。目的是使毕业生拓宽他们的专业活动的范围，提高他们的就业能力。 在本文中，提出了土木工程研究课程的不断扩大，特别是在发展的光毕业生的潜在的项目，计划和投资组合管理。在这个方向上，一个全面的文献回顾，包括ASCE体为第二十一世纪，IPMA的能力的基础知识，建议在其他：显著增加所提供的模块和项目管理在战略管理中添加新的模块，领导行为，配送管理，组织和环境等；提供足够的专业训练五年的大学的研究；并由专业机构促进应届大学生认证。建议通过改革教学大纲为土木工程研究目前由国家技术提供了例证雅典大学。 1引言 土木工程研究（CES）蓬勃发展，是在第二次世界大战后。土木工程师的出现最初是由重建被摧毁的巨大需求所致，目的是更多和更好的社会追求。但是很快，这种演变一个长期的趋势，因为政府为了努力实现经济发展，采取了全世界的凯恩斯主义的理论，即公共基础设施投资作为动力。首先积极的结果导致公民为了更好的生活条件（住房，旅游等）和增加私人投资基础设施而创造机会。这些现象再国家的发展中尤为为明显。虽然前景并不明朗（例如，世界石油危机在70年代），在80年代领先的国家采用新自由主义经济的方法（如里根经济政策），这是最近的金融危机及金融危机造成的后果（即收缩的基础设施投资，在技术部门的高失业率），消除发展前途无限的误区。 技术教育的大学所认可的大量研究土木工程部。旧学校拓展专业并且新的学校建成，并招收许多学生。由于高的职业声望，薪酬，吸引高质量的学校的学生。在工程量的增加和科学技术的发展，导致到极强的专业性，无论是在研究还是工作当中。结构工程师，液压工程师，交通工程师等，都属于土木工程。试图在不同的国家采用专业性的权利，不同的解决方案，，从一个统一的大学学历和广泛的专业化的一般职业许可证。这个问题在许多其他行业成为关键。国际专业协会的专家和机构所确定的国家性检查机构，经过考试后，他们证明不仅是行业的新来者，而且专家通过时间来确定进展情况。尽管在很多情况下，这些证书虽然没有国家接受，他们赞赏和公认的世界。 在试图改革大学研究（不仅在土木工程）更接近市场需求的过程中，欧盟确定了1999博洛尼亚宣言，它引入了一个二能级系统。第一级度（例如，一个三年的学士）是进入
软件工程专业BIOS资料外文翻译文献
软件工程专业BIOS资料外文翻译文献 What is the Basic Input Output System (BIOS)? BIOS is an acronym for Basic Input Output System. It is the program that stores configuration details about your computer hardware and enables your computer to boot up. Every time your computer is switched on the BIOS loads configuration data into main memory, performs a routine diagnostic test on your hardware, then loads the operating system. The BIOS resides in a ROM (Read-Only memory) chip, which is mounted on the motherboard, usually in a socket so it is removable. To the right is an example of what a BIOS chip may look like in your motherboard. This is a PLCC 32 pin type BIOS chip. It is a very common type. Every computer has BIOS. There are many types but the most common type of BIOS 's come from: AMI, Award and Phoenix. Motherboard manufacturers buy or lease the BIOS source code from these companies. The BIOS tells the operating system in your computer how to boot up, where to load everything, what to load, what memory and CPU are present and much more. A good comparison to further understand the
土木工程岩土类毕业设计外文翻译
姓名： 学号： 10447425 X X 大学 毕业设计（论文）外文翻译 （2014届） 外文题目Developments in excavation bracing systems 译文题目开挖工程支撑体系的发展 外文出处Tunnelling and Underground Space Technology 31 (2012) 107–116 学生XXX 学院XXXX 专业班级XXXXX 校内指导教师XXX 专业技术职务XXXXX 校外指导老师专业技术职务 二○一三年十二月
开挖工程支撑体系的发展 1.引言 几乎所有土木工程建设项目（如建筑物，道路，隧道，桥梁，污水处理厂，管道，下水道）都涉及泥土挖掘的一些工程量。往往由于由相邻的结构，特性线，或使用权空间的限制，必须要一个土地固定系统，以允许土壤被挖掘到所需的深度。历史上，许多挖掘支撑系统已经开发出来。其中，现在比较常见的几种方法是：板桩，钻孔桩墙，泥浆墙。 土地固定系统的选择是由技术性能要求和施工可行性（例如手段，方法）决定的，包括执行的可靠性，而成本考虑了这些之后，其他问题也得到解决。通常环境后果（用于处理废泥浆和钻井液如监管要求）也非常被关注（邱阳、1998）。 土地固定系统通常是建设项目的较大的一个组成部分。如果不能按时完成项目，将极大地影响总成本。通常首先建造支撑，在许多情况下，临时支撑系统是用于支持在挖掘以允许进行不断施工，直到永久系统被构造。临时系统可以被去除或留在原处。 打桩时，因撞击或振动它们可能会被赶入到位。在一般情况下，振动是最昂贵的方法，但只适合于松散颗粒材料，土壤中具有较高电阻（例如，通过鹅卵石）的不能使用。采用打入桩系统通常是中间的成本和适合于软沉积物（包括粘性和非粘性），只要该矿床是免费的鹅卵石或更大的岩石。 通常，垂直元素（例如桩）的前安装挖掘工程和水平元件（如内部支撑或绑回）被安装为挖掘工程的进行下去，从而限制了跨距长度，以便减少在垂直开发弯矩元素。在填充情况下，桩可先设置，从在斜坡的底部其嵌入悬挑起来，安装作为填充进步水平元素（如搭背或土钉）。如果滞后是用来保持垂直元素之间的土壤中，它被安装为挖掘工程的进行下去，或之前以填补位置。 吉尔- 马丁等人（2010）提供了一个数值计算程序，以获取圆形桩承受轴向载荷和统一标志（如悬臂桩）的单轴弯矩的最佳纵筋。他们开发的两种优化流程：用一个或两个直径为纵向钢筋。优化增强模式允许大量减少的设计要求钢筋的用量，这些减少纵向钢筋可达到50％相对传统的，均匀分布的加固方案。 加固桩集中纵向钢筋最佳的位置在受拉区。除了节约钢筋，所述非对称加强钢筋图案提高抗弯刚度，通过增加转动惯量的转化部分的时刻。这种增加的刚性可能会在一段时间内增加的变形与蠕变相关的费用。评估相对于传统的非对称加强桩的优点，对称，钢筋桩被服务的条件下全面测试来完成的，这种试验是为了验证结构的可行性和取得的变形的原位测量。 基于现场试验中，用于优化的加强图案的优点浇铸钻出孔（CIDH）在巴塞罗那的
外文翻译---硬件软件的设计和开发过程知识讲解
附录 一、英文原文 Hardware/Software Design and Development Process Everett Lumpkin and Michael Gabrick Delphi Corporation, Electronics and Safety Division INTRODUCTION Process and technology advancements in the semiconductor industry have helped to revolutionize automotive and consumer electronics. As Moore’s Law predicted, the increase in complexity and operating frequencies of today’s integrated circuits have enabled the creation of system applications once thought to be impossible. And systems such as camera cell phones, automotive infotainment systems, advanced powertrain controllers and handheld personal computers have been realized as a result. In addition to the increases in process technology, the Electronic Design Automation (EDA) industry has helped to transform the way semiconductor integrated circuits (IC) and subsequent software applications are designed and verified. This transformation has occurred in the form of design abstraction, where the implementation continues to be performed at higher levels through the innovation of design automation tools. An example of this trend is the evolution of software development from the early days of machine-level programming to the C++ and Java software written today. The creation of the assembler allowed the programmer to move a level above machine language, which increased the efficiency of code generation and documentation, but still tied the programmer to the underlying hardware architecture. Likewise, the dawn of C / C++ compilers, debuggers and linkers helped to move the abstraction layer further away from the underlying hardware, making the software completely platform independent, easier to read, easier to debug and more efficient to manage. However, a shift to higher levels of software abstraction has not translated to a reduction in complexity or human resources. On the contrary, as integrated systems have become more feature rich, the complexity of the operating system and corresponding applications have increased rapidly, as have the costs associated with the software implementation and verification activities. Certainly the advancements in embedded software tools such as static code checkers, debuggers and hardware emulators have helped to solve some of the software verification problems, but software verification activities have become more time and resource consuming than the actual software creation. Time-to-market constraints have pushed software verification activities to the system-level, and led to a greater demand for production hardware to be made available earlier in
土木工程外文翻译.doc
项目成本控制 一、引言 项目是企业形象的窗口和效益的源泉。随着市场竞争日趋激烈，工程质量、文明施工要求不断提高，材料价格波动起伏，以及其他种种不确定因素的影响，使得项目运作处于较为严峻的环境之中。由此可见项目的成本控制是贯穿在工程建设自招投标阶段直到竣工验收的全过程，它是企业全面成本管理的重要环节，必须在组织和控制措施上给于高度的重视，以期达到提高企业经济效益的目的。 二、概述 工程施工项目成本控制，指在项目成本在成本发生和形成过程中，对生产经营所消耗的人力资源、物资资源和费用开支，进行指导、监督、调节和限制，及时预防、发现和纠正偏差从而把各项费用控制在计划成本的预定目标之内，以达到保证企业生产经营效益的目的。 三、施工企业成本控制原则 施工企业的成本控制是以施工项目成本控制为中心，施工项目成本控制原则是企业成本管理的基础和核心，施工企业项目经理部在对项目施工过程进行成本控制时，必须遵循以下基本原则。 3.1 成本最低化原则。施工项目成本控制的根本目的，在于通过成本管理的各种手段，促进不断降低施工项目成本，以达到可能实现最低的目标成本的要求。在实行成本最低化原则时，应注意降低成本的可能性和合理的成本最低化。一方面挖掘各种降低成本的能力，使可能性变为现实；另一方面要从实际出发，制定通过主观努力可能达到合理的最低成本水平。 3.2 全面成本控制原则。全面成本管理是全企业、全员和全过程的管理，亦称“三全”管理。项目成本的全员控制有一个系统的实质性内容，包括各部门、各单位的责任网络和班组经济核算等等，应防止成本控制人人有责，人人不管。项目成本的全过程控制要求成本控制工作要随着项目施工进展的各个阶段连续 进行，既不能疏漏，又不能时紧时松，应使施工项目成本自始至终置于有效的控制之下。 3.3 动态控制原则。施工项目是一次性的，成本控制应强调项目的中间控制，即动态控制。因为施工准备阶段的成本控制只是根据施工组织设计的具体内容确
软件工程中英文对照外文翻译文献
中英文对照外文翻译 (文档含英文原文和中文翻译) Application Fundamentals Android applications are written in the Java programming language. The compiled Java code — along with any data and resource files required by the application — is bundled by the aapt tool into an Android package, an archive file marked by an .apk suffix. This file is the vehicle for distributing the application and installing it on mobile devices; it's the file users download to their devices. All the code in a single .apk file is considered to be one application. In many ways, each Android application lives in its own world: 1. By default, every application runs in its own Linux process. Android starts the process when any of the application's code needs to be executed, and shuts down the process when it's no longer needed and system resources are required by other applications. 2. Each process has its own virtual machine (VM), so application code runs in isolation from the code of all other applications. 3. By default, each application is assigned a unique Linux user ID. Permissions are set so that the application's files are visible only to that user and only to the application itself — although there are ways to export them to other applications as well. It's possible to arrange for two applications to share the same user ID, in which case they will be able to see each other's files. To conserve system resources, applications with the same ID can also arrange to run in the same Linux process, sharing the same
土木工程专业外文文献及翻译
（ 二 〇 一 二 年 六 月 外文文献及翻译 题 目： About Buiding on the Structure Design 学生姓名： 学 院：土木工程学院 系 别：建筑工程系 专 业：土木工程(建筑工程方向) 班 级：土木08-4班 指导教师：
英文原文： Building construction concrete crack of prevention and processing Abstract The crack problem of concrete is a widespread existence but again difficult in solve of engineering actual problem, this text carried on a study analysis to a little bit familiar crack problem in the concrete engineering, and aim at concrete the circumstance put forward some prevention, processing measure. Keyword:Concrete crack prevention processing Foreword Concrete's ising 1 kind is anticipate by the freestone bone, cement, water and other mixture but formation of the in addition material of quality brittleness not and all material.Because the concrete construction transform with oneself, control etc. a series problem, harden model of in the concrete existence numerous tiny hole, spirit cave and tiny crack, is exactly because these beginning start blemish of existence just make the concrete present one some not and all the characteristic of quality.The tiny crack is a kind of harmless crack and accept concrete heavy, defend Shen and a little bit other use function not a creation to endanger.But after the concrete be subjected to lotus carry, difference in temperature etc. function, tiny crack would continuously of expand with connect, end formation we can see without the
软件开发外文翻译
软件开发外文翻译本页仅作为文档页封面，使用时可以删除 This document is for reference only-rar21year.March
Requirements Phase The chances of a product being developed on time and within budget are somewhat slim unless the members of the software development team agree on what the software product will do. The first step in achieving this unanimity is to analyze the client’s current situation as precisely as possible. For example, it is inadequate to say, “ They need a computer-aided design system because they claim their manual design system, there is lousy. “ Unless the development team knows exactly what is wrong with the current manual system, there is a high probability that aspects of the new computerized system will be equally “lousy. “ Similarly, if a personal computer manufacturer is contemplating development of a new operating system, the first step is to evaluate the firm’s current operating system and analyze carefully exactly why it is unsatisfactory. To take an extreme example, it is vital to know whether the problem exists only in the mind of the sales manager, who blames the operating system for poor sales, or whether users of the operating system are thoroughly disenchanted with its functionality and reliability. Only after a clear picture of the present situation has been gained can the team attempt to answer the critical question, What must the new product be able to do The process of answering this question is carried out during the requirements phase. A commonly held misconception is that , during the requirements phase, the developers must determine what software the client wants. On the contrary, the real objective of the requirements phase is to determine what software the client needs. The problem is that many clients do not know what they need. Furthermore, even a client who has a good idea of what is needed may have difficulty in accurately conveying these ideas to the developers, because most clients are less computer literate than the members of the development team.