手机版
1 2 3 4
首页 > 新闻中心 > 翻译公司资讯 >
翻译公司资讯

世联翻译公司业务技术手册英文翻译

发布时间：2018-02-04 17:21　　点击：

世联翻译公司业务技术手册英文翻译
Instruction for using sections 2-9 of this template is available in WTJA-0090 ELC Architecture Design Guidelines; instruction for using sections 10 on is available in WTJA-0026 ELC Design Guidelines.
1 Introduction
This documentation is intended to capture architecture and design specification for <project name>.
2 Architectural Goals and Constraints
To be completed during Requirements Stage
2.1 Capability Roadmap and Technology Strategies
<Identify the capability roadmap and technology strategies that direct the overall architecture approach.>
2.2 Architecture Constraints
<Identify special constraints that may apply to the design of this solution, including design and implementation strategies, team structure, etc.>
2.3 Architectural Trade-offs and Decisions
<Describe the architecturally significant decisions and trade-offs made.  This section applies to both custom development and COTS development.>
3 Architecture Quality & Alignment
To be completed during Requirements Stage
3.1 Repeatable Patterns
<Provide an overview of how this project adopts technology standards, reference architectures and repeatable solution patterns as part of the solution.>
3.2 SOA Services
<Provide an overview of how this project adopts SOA services as a key technology strategy.>
3.3 Master Data Management
<Provide an overview of how this project adopts SOA services as a key technology strategy.>
3.4 Architecture Exceptions
 <List all of the architecture exceptions that have been identified for this solution. Each exception should be identified by the entry in the Enterprise Issue and Risk Management log. Reference the EA Guide on Issues and Risk Management for more information about exceptions.>
ID Exception Resolution
<Identifier for Enterprise Issue & Risk Management Log> <Brief description of exception including architecture domain/shared service impacted> <Date of resolution & determination>
 
 
4 Logical View 
To be completed during Design Stage
4.1 Architecturally Relevant Use Case Realizations
Table 1  - Architecture impact of key use cases
Use Case ID Use Case Name Architecture Impact
None
 
4.2 Architecturally Significant Design Packages
<Document each design package.>
4.3  Architecturally Significant Collaboration
<Document relevant collaborations.>
4.3.1 Key Objects
<Insert Description of Object>
4.3.2 Key Messages
<Insert Description of Message.  Specification of messages is particularly important to service oriented systems.  A message specification identifies how to move data across service boundaries.  Therefore, a message specification should include at least following aspects:
o Anticipated message exchange & sequencing
o Message format and semantics
o Supported technology channels
o Potential error conditions>
4.3.3 Key Policies
<Insert Description of Key Policies.  Policies define the qualitative requirements, constraints, and capabilities of the component/service>
5 Deployment View 
If a decision is made to land the solution outside of a strategic data center, the team must contact Global Network Services (gNS) to perform a network analysis of the proposed infrastructure.
 
To be completed during Design Stage
 
<At a minimum for each configuration indicate the physical nodes (computers, CPUs) that execute the software and their interconnections (bus, LAN, point-to-point, and so on).>
5.1 <Infrastructure Component Name>
<Insert description of infrastructure component>
5.2 <Infrastructure Component Name>
<Insert description of infrastructure component>
6 Implementation View 
To be completed during Design Stage
6.1 Overview
<Name and define the various layers and their contents, the rules that govern the inclusion to a given layer, and the boundaries between layers. Include a component diagram that shows the relations between layers.>
6.2 Layers
<For each layer, include a subsection with its name, an enumeration of the subsystems located in the layer, and a component diagram.>
6.2.1 Client Tier
<Subsystem – for each subsystem, provide a description of its functionality and interaction with other subsystems and layers>
6.2.2 Presentation Layer
<Subsystem – for each subsystem, provide a description of its functionality and interaction with other subsystems and layers>
6.2.3 Control Layer
<Subsystem – for each subsystem, provide a description of its functionality and interaction with other subsystems and layers>
6.2.4 Business Logic Layer
<Subsystem – for each subsystem, provide a description of its functionality and interaction with other subsystems and layers>
6.2.5 Data Access Layer
<Subsystem – for each subsystem, provide a description of its functionality and interaction with other subsystems and layers>
6.2.6 Enterprise Information Layer
<Subsystem – for each subsystem, provide a description of its functionality and interaction with other subsystems and layers>
 
7 Data Flow View
To be completed during Design Stage
7.1 <Component Name>
<Insert description of data structure>
7.2 <Component Name>
<Insert description of data structure>
 
8 Size and Performance 
8.1 Execution Qualities
<Provide information and architectural assessment of the following areas, where applicable: Performance, Scalability, Availability, Reliability, Adaptability Interoperability, Portability, Configurability, Maintainability, Usability, Security>
8.2 Development Qualities
<Provide information and architectural assessment of the following areas, where applicable: Reusability, Modifiability, Localization, Testability>
8.3 COTS/Tool Assessment
<If vendor solutions are being used as part of the architecture, please provide an overview of how it’s being used, and a brief architectural assessment>
 
<Provide any reference to “RFI/RFP Architecture Assessment and Report” related to this project, with an explanation on how it relates to the overall solution.>
 
 
Instruction for using sections 10-19 is available in WTJA-0026 ELC Design Guidelines
9 System Design
<Enter design and a map to the contents and location of the source code.>
10 Directory Structure
<Provide a reference to the source code repository (e.g., repository name, project ID) or directory structure.  For COTS software, identify the location of installation files and/or media.>
 
The files for the <application name> are located on <server name and number>.  The following table represents all subsequent sub-directories associated with this application.
Sub-directory Directory Description
 
 
11 File Naming Conventions
Design Item Naming Convention Description
 
 
12 Development Technologies
Application Tool, System, Database,
Platform, Etc. Comments
Application Development
Browser
Business Rules
Client Server Architecture
Database
Database Access
Database OS Platform
Security
Software Version Control
 
13 Database Design
Enter the information below or reference a separate document or appendix containing the information.
• Physical Constraints:
• Physical Structure: 
• Logical Structure: 
• Data Model:
 
Table Name Keys Indexes Access Control Volume Expected
 
 
 
• Transaction Design Access Path:
• Volumes: 
• Security and Control:
• Optimization:
• Data Dictionary:  When prepared as a separate project deliverable, use the ELC Data Dictionaries Template and provide reference information to the project deliverable here.
• Character Set
• Record Locking:
• Database Technical Requirements:
Database Requirements
 
<TR id>
<Provide a list of technical requirement statements covering details of the database specifications.>
Database ID <Identify the names or labels by which the database may be uniquely identified.  Specify the code name, tag, or label by which each database table or file may be uniquely identified.>
Database Relationships <Indicate whether the database will supersede or interface with other databases, and specify which one(s).>
Schema Information <Depict overall structure in the schema or other global definition of the database.>
Design <Graphically depict the physical design of the database.>
Database Structure <Depict in a graphic representation the physical structure (partitions, files, indexes, pointers) and the logical components of the database.>
Data Dictionary <Reference the data dictionary.>
Database Software Utilities <List and reference the documentation of any DBMS utility software available to support the use or maintenance of the database.>
14 Conversion Design
Source Databases: 
Source Elements:
Validation Rules: 
Processing Rules:
Conversion Component:
Conversion Contingency Arrangements:
Reporting Controls:
Data Security:
15 System Interface Design
15.1.1 Interface Technical Requirements
Interface Technical Requirements
<Technical Requirements ID> <Provide a list of technical requirement statements covering the interfaces for the system.>
Hardware Interfaces
Hardware Devices <List the actual hardware devices your application will interact with and control.>
Supporting Devices <List the devices which are supported.>
Software Interfaces
Name <List the name of the software product.>
Specification Number <List the specification number.>
Version Number <List the version number.>
Communications Interfaces
Protocols <List the network protocols to directly interact with.>
Data Interfaces
Data processing <List the support functions for data processing.>
Back up and Recovery <List the operation for backup and recovery.>
16 Time Zone Specifications
What time zone will be displayed to the user?
What date/time zone will be used when recording audit trails?
Will there be any time zone conversions? If so provide documentation of conversions.
If the system is global, what time will the user see and which time zone will be captured?
17 Security Design
<Define the overall security features of the proposed solution, including the Authentication and Authorization method.>
18 System Components
18.1 <Technical Subsystem Component #1>
18.1.1 Overview
<Enter overview of subsystem’s functional requirements and graphic overview of associated software scripts>
18.1.2 Minimum Configuration Requirements
<Enter specific minimum configuration requirements associated with this technical subsystem component.>  
18.1.3 Processing
 
File Name Functional Description Location Inputs/Outputs
<Include the name of the actual source file of this algorithm / script.> <Include a description of what system functionality this algorithm/script addresses.> <Include the sub-directory in which this file can be located.> <Provide a summary description of inputs and outputs (optional).>
18.1.4 Outputs
<Provide information on the outputs generated from this technical subsystem component.>
18.1.5 Implications for Business Process/Operations
<List implications for user processes and operations generated from this technical subsystem component.>
18.2 <Technical Subsystem Component #2>
Repeat above for all subsystems.
19 Source Code Compiling and Linking
<Provide sufficient information so that a developer can compile and link the completed source code changes.  Include ‘make’ files as applicable.>
20 Supporting References
List supporting information for this project deliverable.  References made within the body of this deliverable should be listed.  Also reference any other documentation that is useful.  Examples are:
• Published controlled documentation (Do not list draft unpublished documentation)
• Governing Policy documentation
• Operating Procedures, Work Instructions and supporting documentation
• Supporting documentation which is not controlled documentation
• References to vendor, external and other manuals and instructions
 
Record Number Reference Title
 
21 Revision History
Version Author Date Revisions
 
22 Appendices
Enter Appendices in the following index and follow with appendices. 
Appendix Appendix Name
Appendix A Potential Solutions
Appendix A—Potential Solutions
List the technical solutions that were evaluated and how the service measured up against the project requirements and any evaluation/Proof-Of-Concept projects.  Include: 
• < Background >
 
• < Technical Details >
 
• < Product Comparisons >
 
• < Fit to Architecture Strategy >
Evaluate Different Solutions
There are a number of different ways of evaluating the criteria that are used to compare the different solutions.  Here are a few examples: 
Evaluation Description / Example
< Yes/No >  < Either the criteria are met or they are not.  For example: >
• < Criteria: The data must be virus-protected >
• < Measure: Yes or No >
< Ranking > < Rank the solutions in terms of their ability to meet the criteria specified.  For example: > 
• < Criteria: Weight must be less than 1.6Kg >
• < Measure: Rank those solutions which are less than 1.6Kg >
< Low / Medium / High > < Where the importance of the criteria is being considered.  This is sometimes a perceptive measure.  For example: >
< Criteria: What level of competitive advantage does the solution give us >
< Measure: Low/medium/high depending on the perceived advantage gained >
Technical Criteria Based on Evaluation
Strategic Emerging Solutions which could be reconsidered in 12-18 months
• • • •
Architecture Council Principles
Management Vendor
Risk Enabl. Comp. Adv Future needs Strat. Open Well Est. Direct
Low/Med/High Low/Med/High Low/Med/High Low/Med/High Yes/No Yes/No Yes/No Yes/No
 

Unitrans世联翻译公司在您身边,离您近的翻译公司,心贴心的专业服务,专业的全球语言翻译与信息解决方案供应商,专业翻译机构品牌。无论在本地,国内还是海外,我们的专业、星级体贴服务，为您的事业加速！世联翻译公司在北京、上海、深圳等国际交往城市设有翻译基地，业务覆盖全国城市。每天有近百万字节的信息和贸易通过世联走向全球！积累了大量政商用户数据，翻译人才库数据，多语种语料库大数据。世联品牌和服务品质已得到政务防务和国际组织、跨国公司和大中型企业等近万用户的认可。 专业翻译公司,北京翻译公司,上海翻译公司,英文翻译,日文翻译,韩语翻译,翻译公司排行榜,翻译公司收费价格表,翻译公司收费标准,翻译公司北京,翻译公司上海。
收藏  打印

  • “贵司提交的稿件专业词汇用词准确，语言表达流畅，排版规范， 且服务态度好。在贵司的帮助下，我司的编制周期得以缩短，稿件语言的表达质量得到很大提升”

    华东建筑设计研究总院

  • “我单位是一家总部位于丹麦的高科技企业，和世联翻译第一次接触，心中仍有着一定的犹豫，贵司专业的译员与高水准的服务，得到了国外合作伙伴的认可！”

    世万保制动器（上海）有限公司

  • “我公司是一家荷兰驻华分公司，主要致力于行为学研究软件、仪器和集成系统的开发和销售工作，所需翻译的英文说明书专业性强，翻译难度较大，贵司总能提供优质的服务。”

    诺达思（北京）信息技术有限责任公司

  • “为我司在东南亚地区的业务开拓提供小语种翻译服务中，翻译稿件格式美观整洁，能最大程度的还原原文的样式，同时翻译质量和速度也得到我司的肯定和好评！”

    上海大众

  • “在此之前，我们公司和其他翻译公司有过合作，但是翻译质量实在不敢恭维，所以当我认识刘颖洁以后，对她的专业性和贵公司翻译的质量非常满意，随即签署了长期合作合同。”

    银泰资源股份有限公司

  • “我行自2017年与世联翻译合作，合作过程中十分愉快。特别感谢Jasmine Liu, 态度热情亲切，有耐心，对我行提出的要求落实到位，体现了非常高的专业性。”

    南洋商业银行

  • “与我公司对接的世联翻译客服经理，可以及时对我们的要求进行反馈，也会尽量满足我们临时紧急的文件翻译要求。热情周到的服务给我们留下深刻印象！”

    黑龙江飞鹤乳业有限公司

  • “翻译金融行业文件各式各样版式复杂，试译多家翻译公司，后经过比价、比服务、比质量等流程下来，最终敲定了世联翻译。非常感谢你们提供的优质服务。”

    国金证券股份有限公司

  • “我司所需翻译的资料专业性强，涉及面广，翻译难度大，贵司总能提供优质的服务。在一次业主单位对完工资料质量的抽查中，我司因为俄文翻译质量过关而受到了好评。”

    中辰汇通科技有限责任公司

  • “我司在2014年与贵公司建立合作关系，贵公司的翻译服务质量高、速度快、态度好，赢得了我司各部门的一致好评。贵司经理工作认真踏实，特此致以诚挚的感谢！”

    新华联国际置地（马来西亚）有限公司

  • “我们需要的翻译人员，不论是笔译还是口译，都需要具有很强的专业性，贵公司的德文翻译稿件和现场的同声传译都得到了我公司和合作伙伴的充分肯定。”

    西马远东医疗投资管理有限公司

  • “在这5年中，世联翻译公司人员对工作的认真、负责、热情、周到深深的打动了我。不仅译件质量好，交稿时间及时，还能在我司资金周转紧张时给予体谅。”

    华润万东医疗装备股份有限公司

  • “我公司与世联翻译一直保持着长期合作关系，这家公司报价合理，质量可靠，效率又高。他们翻译的译文发到国外公司，对方也很认可。”

    北京世博达科技发展有限公司

  • “贵公司翻译的译文质量很高，语言表达流畅、排版格式规范、专业术语翻译到位、翻译的速度非常快、后期服务热情。我司翻译了大量的专业文件，经过长久合作，名副其实，值得信赖。”

    北京塞特雷特科技有限公司

  • “针对我们农业科研论文写作要求，尽量寻找专业对口的专家为我提供翻译服务，最后又按照学术期刊的要求，提供润色原稿和相关的证明文件。非常感谢世联翻译公司！”

    中国农科院

  • “世联的客服经理态度热情亲切，对我们提出的要求都落实到位，回答我们的问题也非常有耐心。译员十分专业，工作尽职尽责，获得与其共事的公司总部同事们的一致高度认可。”

    格莱姆公司

  • “我公司与马来西亚政府有相关业务往来，急需翻译项目报备材料。在经过对各个翻译公司的服务水平和质量的权衡下，我们选择了世联翻译公司。翻译很成功，公司领导非常满意。”

    北京韬盛科技发展有限公司

  • “客服经理能一贯热情负责的完成每一次翻译工作的组织及沟通。为客户与译员之间搭起顺畅的沟通桥梁。能协助我方建立专业词库，并向译员准确传达落实，准确及高效的完成统一风格。”

    HEURTEY PETROCHEM法国赫锑石化

  • “贵公司与我社对翻译项目进行了几次详细的会谈，期间公司负责人和廖小姐还亲自来我社拜访，对待工作热情，专业度高，我们双方达成了很好的共识。对贵公司的服务给予好评！”

    东华大学出版社

  • “非常感谢世联翻译！我们对此次缅甸语访谈翻译项目非常满意，世联在充分了解我司项目的翻译意图情况下，即高效又保质地完成了译文。”

    上海奥美广告有限公司

  • “在合作过程中，世联翻译保质、保量、及时的完成我们交给的翻译工作。客户经理工作积极，服务热情、周到，能全面的了解客户的需求，在此表示特别的感谢。”

    北京中唐电工程咨询有限公司

  • “我们通过图书翻译项目与你们相识乃至建立友谊，你们报价合理、服务细致、翻译质量可靠。请允许我们借此机会向你们表示衷心的感谢！”

    山东教育出版社

  • “很满意世联的翻译质量，交稿准时，中英互译都比较好，措辞和句式结构都比较地道，译文忠实于原文。TNC是一家国际环保组织，发给我们美国总部的同事后，他们反应也不错。”

    TNC大自然保护协会

  • “原英国首相布莱尔来访，需要非常专业的同声传译服务，因是第一次接触，心中仍有着一定的犹豫，但是贵司专业的译员与高水准的服务，给我们留下了非常深刻的印象。”

    北京师范大学壹基金公益研究院

  • “在与世联翻译合作期间，世联秉承着“上善若水、厚德载物”的文化理念，以上乘的品质和质量，信守对客户的承诺，出色地完成了我公司交予的翻译工作。”

    国科创新（北京）信息咨询中心

  • “由于项目要求时间相当紧凑，所以世联在保证质量的前提下，尽力按照时间完成任务。使我们在世博会俄罗斯馆日活动中准备充足，并受到一致好评。”

    北京华国之窗咨询有限公司

  • “贵公司针对客户需要，挑选优秀的译员承接项目，翻译过程客户随时查看中途稿，并且与客户沟通术语方面的知识，能够更准确的了解到客户的需求，确保稿件高质量。”

    日工建机（北京）国际进出口有限公司

15811068017

15801211926

18801485229
点击添加微信

无需转接等回电