- 翻譯公司資訊
-
世聯(lián)翻譯公司完成體系結(jié)構(gòu)英文翻譯
發(fā)布時(shí)間：2018-02-04 17:49 點(diǎn)擊：
世聯(lián)翻譯公司完成體系結(jié)構(gòu)英文翻譯
Instruction for using this template is available in WTJA-0624 ELC Requirements Specification Guidelines. In general, enter the requirement #, description and IPRM ID# (for compliance requirements) first and complete the MSC and Scope columns during Requirements Prioritization.1 Business Requirements1.1 Stakeholder Analysis<Reference Stakeholder Analysis created with WTTE-0081 ELC Stakeholder Analysis Template or include here if separate document not necessary>1.2 Current State Process<Include current state business process models (from the enterprise corporate modeler repository or created following WTJA-0018 ELC Business Process Guidelines) or reference separate current state process documentation>1.3 Future State Process<Include future state business process created following WTJA-0018 ELC Business Process Guidelines or reference separate future state process documentation>1.4 Business Process RolesRole Responsibilities As-Is or To-Be1.5 Business Requirements ListReq# Requirement Description BR# MSC ScopeB1.B2.1.6 Business RulesBR# Description Example Source Related RulesBR1.BR2.1.7 Information View and Data Requirements<Include information models (from enterprise corporate modeler repository or created following WTJA-0078 ELC Data Modeling Guidelines) or reference separate information model documentation>Entity Description<List data requirements or reference data dictionary created with WTTE-0027 ELC Data Dictionary Template>2 User RequirementsReq# Requirement Description MSC ScopeU1.U2.2.1 Use Cases2.1.1 Use Case Diagram<Reference Use Case Diagram>2.1.2 Use Case Description<Include use cases (from the enterprise repository or created using WTTE-0026 ELC Use Case Template) or reference separate use cases documentation>3 Functional RequirementsReq# Requirement Description MSC ScopeF1.F2.3.1 Additional Functional Requirements ArtifactsAttach or reference additional Functional Requirements, which can be in the form of Models (such as Wireframes, Storyboards, UI Field Specifications, Prototypes, etc.)4 Quality of Service/Non-Functional Requirements4.1 Infrastructure Hardware RequirementsReq# Requirement Description MSC ScopeIH1.IH2.4.2 Infrastructure Software RequirementsReq# Requirement Description MSC ScopeIS1.IS2.4.3 Specific Software Version Requirements (Internal or External)Req# Requirement Description MSC ScopeSV1.SV2.4.4 Usability and Accessibility RequirementsReq# Requirement Description MSC ScopeUA1.UA2.4.5 Reliability, Stability, Monitoring and Business Continuity RequirementsReq# Requirement Description MSC ScopeRS1.RS2.4.6 Performance RequirementsReq# Requirement Description MSC ScopeP1.P2.4.7 Support and Maintenance RequirementsReq# Requirement Description MSC ScopeSM1.SM2.4.8 Post-Project Application Development Environment RequirementsReq# Requirement Description MSC ScopePPA1.PPA2.4.9 General Environmental RequirementsReq# Requirement Description MSC ScopeE1.E2.4.10 Infrastructure Commissioning RequirementsReq# Requirement Description MSC ScopeIC1.IC2.4.11 Infrastructure Location/Site RequirementsReq# Requirement Description MSC ScopeIL1.IL2.4.12 Licensing and Purchased Components RequirementsReq# Requirement Description MSC ScopeL1.L2.4.13 Interface and Networking RequirementsReq# Requirement Description MSC ScopeIN1.IN2.4.14 Security, Access, Privacy and Records Retention RequirementsReq# Requirement Description MSC ScopeSAP1.SAP2.User accounts:0 Group access accounts (default)0 Individual account based on NT account nameSecurity:0 Standard database services role matrix (default)0 Additional role matrix requirements: <details>0 Other (please specify): <details4.15 User Documentation, Help System and Training RequirementsReq# Requirement Description MSC ScopeT1.T2.5 Compliance RequirementsReq# Requirement Description IPRM ID # MSC ScopeC1.C2.6 Implementation RequirementsReq# Requirement Description MSC ScopeI1.I2.7 Supporting ReferencesList the supporting information for this 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 instructionsRecord Number Reference Title8 Revision HistoryVersion Author Date RevisionsUnitrans世聯(lián)翻譯公司在您身邊,離您近的翻譯公司,心貼心的專業(yè)服務(wù),專業(yè)的全球語言翻譯與信息解決方案供應(yīng)商,專業(yè)翻譯機(jī)構(gòu)品牌。無論在本地,國內(nèi)還是海外,我們的專業(yè)、星級(jí)體貼服務(wù)，為您的事業(yè)加速！世聯(lián)翻譯公司在北京、上海、深圳等國際交往城市設(shè)有翻譯基地，業(yè)務(wù)覆蓋全國城市。每天有近百萬字節(jié)的信息和貿(mào)易通過世聯(lián)走向全球！積累了大量政商用戶數(shù)據(jù)，翻譯人才庫數(shù)據(jù)，多語種語料庫大數(shù)據(jù)。世聯(lián)品牌和服務(wù)品質(zhì)已得到政務(wù)防務(wù)和國際組織、跨國公司和大中型企業(yè)等近萬用戶的認(rèn)可。 專業(yè)翻譯公司,北京翻譯公司,上海翻譯公司,英文翻譯,日文翻譯,韓語翻譯,翻譯公司排行榜,翻譯公司收費(fèi)價(jià)格表,翻譯公司收費(fèi)標(biāo)準(zhǔn),翻譯公司北京,翻譯公司上海。
