需求規格說明 的英文怎麼說

中文拼音 [xūqiúguīgéshuōmíng]
需求規格說明 英文
requirements specification,
  • 需 : Ⅰ動詞（需要） need; want; require Ⅱ名詞1. （需用的東西） necessaries; needs 2. （姓氏） a surname
  • 求 : Ⅰ動詞1 （請求; 要求） ask; beg; request; entreat; beseech : 求人幫忙 ask sb a favour; ask a favou...
  • 規 : Ⅰ名詞1 （畫圓形的工具） instrument for drawing circles 2 （規則; 成例） rule; regulation 3 [機械...
  • 格 : 格象聲詞rattle; gurgle
  • 說 : 說動詞（說服別人聽從自己的意見） try to persuade
  • 明 : Ⅰ形容詞1 （明亮） bright; brilliant; light 2 （明白;清楚） clear; distinct 3 （公開;顯露在外;不隱...
  • 需求 : needs; need; demand; requirement
  • 規格 : 1. （產品質量的標準） specifications; norms; standards; specs 2. （泛指規定的要求或條件） standard; format; requirement
  • 說明 : 1 （解釋明白） explain; illustrate; show 2 （解釋意義的話） illustration; instruction; explicatio...
  1. The buyer and the supervisor shall receive from the seller at least thirty ( 30 ) days notice in advance and seven ( 7 ) days definite notice in advance in writing or by fax confirmed in writing, of the time and place of the vessel ? s sea trial as described in the specifications ( hereinafter referred to as " the trial run " ) and the buyer and the supervisor shall promptly acknowledge receipt of such notice

    賣方需分別至少提前三十（ 30 ）天和至少提前七（ 7 ）天向買方及其監造師發出船舶入海試航通知和精確試航通知書（以下稱「試航通知」 ） ，該試航通知應以書面形式或傳真兼書面確認形式製作，其中應載明需求規格說明書中的試航時間和地點。
  2. This paper based on the hj04a railway signal computer system which is developed by the research institute of microcomputer, hefei university of technology. according to requirement of the interlocking software " s reliability and safety. considered with the software requirement analysis, combining the uml and z, we finally design the interlocking software specification which is completeness, consistency, no redundancy, no different meanings and is consistent with the demand of the system

    本論文針對合肥工大微型計算機應用研究所研究開發的hj04a鐵路信號計算機聯鎖系統，根據計算機聯鎖系統聯鎖軟體設計可靠性和安全性要求，從軟體的需求分析著手，綜合uml統一建模語言方法和形式化描述語言z語言的方法，設計出完全的、一致的、無冗餘的、無歧義的、符合系統要求的聯鎖軟體規格說明書。
  3. This tutorial shows how individual change requests are linked and traced back to the original requirements specification, how you manage that information from within your development environment, and how you generate a new specification. in this tutorial

    本教程將說明如何將個別的變更請求連接並追溯到原始的需求規格，如何在開發環境中管理那些信息，以及如何生成一個新的規格說明。
  4. Can a software tester perform white - box testing on a specification

    軟體測試人員可以對《需求規格說明書》做白盒測試嗎？
  5. Although the software specification described using natural language is easy to write and understand, its validity, integrality, non - ambiguity, consistency are hard to guarantee. the process of verification can only be done by manpower which is not normative and not rigorous. and the complexity of a lot of software has made it impossible to check the specifications artificially

    需求規格說明是需求分析階段的產品，我們通常採用的是未使用任何限制非形式化的自然語言進行描述，這種自然語言書寫的需求說明，雖然易於理解和使用，但難以保證其正確性、完整性、無二義性、一致性，驗證過程只能採用不太規范、不太嚴格的人工走查的方法進行檢查，稍微復雜一些軟體的需求規格說明的檢查，實際上已經超出了人工檢查的能力。
  6. 2. the documents involving from requirement analyzing to software testing are written by combining the software engineering with the application requiring of three of our country ' s under - water weapon departments, that is, demonstrating department, designing department and testing department. 3

    二、採用軟體工程化的設計思想，並結合我國水下武器作戰論證、設計、試驗三個部門和單位的應用要求，完成了魚雷武器系統需求分析、設計規格說明、及軟體測試等各階段報告的編寫。
  7. Equal products by other manufacturers, approved by the engineer and owner, will be acceptable in accordance with the substitute equipment requirements in the general conditions section of these specifications

    由其它製造商生產的類似產品，需要經過工程師和業主的認可，並符合本規格說明書運行環境章節中替代產品的相關要求。
  8. Equal products by other manufacturers, approved by the engineer and owner, will be acceptable in accordance with the substitute equipment requirements contained in the general conditions section of these specifications

    由其它製造商生產的類似產品，需要經過工程師和業主的認可，並符合本規格說明書運行環境章節中替代產品的相關要求。
  9. Term project ) perform the requirement workflow for the ophelia ' s oasis project in appendix a

    以學期項目為例，了解用戶需求按軟體工程方法設計軟體，形成需求規格說明文檔。
  10. These two opposing forces result in conflict, and the result is a constantly changing product specification

    這兩股背道而馳的力量導致了沖突，最後結果就是《產品需求規格說明書》不斷的變化。
  11. Deriving operational software specification from system goals. in proc. 10th acm sigsoft symposium on the foundations of software engineering, charleston, south carolina, usa, 2002, pp. 119 - 128

    從環境及其交互的語義模型出發，研究軟體需求的本質含義，試圖建立從需求到軟體規格說明的平滑連續需求工程過程。
  12. Developing applications using the ibm rational unified process is a lot easier if you have the tools to help you throughout the process

    此五部系列的第一部分說明了如何使用rational requisitepro來管理和組織一個新項目的需求規格。
  13. Requirements engineering ( re ) is a branch of software engineering, whose activities involve requirements elicitation, requirements analysis, requirements specification, requirements validation and requirements management

    需求工程是軟體工程的一個分支，其活動包括需求獲取、需求分析、需求規格說明、需求驗證和需求管理。
  14. The main idea of this paper is about the research of the technology of the requirement analysis modelling and model verification. the word " analysis model " refers to the semi - formaliztion of the requirement specification

    本文的主旨是關于需求分析建模和模型驗證技術的研究，文中的「分析模型」是需求規格說明的半形式化表示。
  15. By sharing the information you can track components in the application from their original requirement specification through to testing and release

    通過共享這些信息，您可以跟蹤應用軟體的構件，從他們最初的需求規格說明一直到測試與發布。
  16. We can describe a task of configuring a product from its components according to a required specification and implement a program that does this configuration independent of the products and components themselves ( mcguinness and wright 1998 )

    我們能夠從需求規格說明從產品的組件描述一個配製產品的任務，並實現一個獨立與這些產品和組件的程序來完成配製工作。
  17. After making adequate analysis upon the errors ever occurred in areospace computer system, together with a lot of case data, we can see it distinctly that the software specifications are often the important sources of the errors

    通過對航天計算機系統的軟體所普遍存在著的錯誤進行分析，結合一些實際數據，我們清晰地看到，軟體需求規格說明常常是引起軟體錯誤的重要來源。
  18. Secondly, based on uml, the paper describes the re ' s practicing process and part outcomes of products survey management information system ( psmis ), and emphasizes particularly on requirements elicitation, requirements analysis and requirements specification

    隨后使用uml語言，描述產品檢驗管理信息系統的需求工程的實踐過程和部分結果。側重於需求的獲取、分析建模以及需求規格說明的編寫。
  19. Secondly, based on the uml, the paper describes the re ' s practicing process and part outcomes of a financial central payment management information system ( mis ) of some bureau of finance from diverse view by creating different model and emphasizes particularly on requirements elicitation, requirements analysis and requirements specification

    隨后使用uml語言，通過建立不同的模型，從不同的視角，以不同的詳略程度描述某財政局財政集中支付mis系統的需求工程的實踐過程和部分結果。側重於需求的獲取、分析建模以及需求規格說明的編寫。
  20. The resources include not only programs but also the methods, requirement specification, design construction, development tools and environment, testing and analysis data and maintain information, etc. it has been proved that software reuse is practical and feasible approach to realizing software standardization, raising software productivity, improving software quality, reducing development cost and shorting development cycle

    這些軟體資源不僅包括源代碼，還包括軟體開發方法、需求規格說明、設計結構、開發工具與支撐環境、測試分析數據和維護信息等。實踐已經證明，軟體復用技術不僅可以提高軟體生產率和軟體質量，而且也是降低開發成本、縮短開發周期的重要途徑。
分享友人
分享到 Line

分享到臉書