需求分析階段 的英文怎麼說

中文拼音 [xūqiúfēnxījiēduàn]
需求分析階段 英文
ra requirements analysis phase
  • 需 : Ⅰ動詞（需要） need; want; require Ⅱ名詞1. （需用的東西） necessaries; needs 2. （姓氏） a surname
  • 求 : Ⅰ動詞1 （請求; 要求） ask; beg; request; entreat; beseech : 求人幫忙 ask sb a favour; ask a favou...
  • 分 : 分Ⅰ名詞1. （成分） component 2. （職責和權利的限度） what is within one's duty or rights Ⅱ同 「份」Ⅲ動詞[書面語] （料想） judge
  • 析 : Ⅰ動詞1. （分開; 散開） divide; separate 2. （分析） analyse; dissect; resolve Ⅱ名詞（姓氏） a surname
  • 階 : 名詞1. （臺階） steps; stairs 2. （等級） rank 3. [醫學] （耳蝸的三個螺旋管的任一個） scala 4. [數學] order 5. [地質學] stage
  • 段 : Ⅰ量詞（部分） section; segment; part; paragraph; passage Ⅱ名詞（姓氏） a surname
  • 需求 : needs; need; demand; requirement
  • 階段 : stage; phase; period; gradation; bench
  1. On the view of customization theory, the method of information processing for customization is summarized : quality function development and product function architecture, then the need function development ( nfd ) as the design way of implementing sub - system of customization information dealing is proposed based on them. the configuration include three parts : transmission function, need function and developing function. the adapting four steps for implementing are proposed : the collection and classification stage of customization information, the analysis stage of customization information, matching stage and evaluating stage for producing

    尤其是從mc個性化理論出發，總結前人個性化信息處理方法：質量功能配置法和產品族構建法的基礎上，提出基於樹形的兩極需求功能配置法的框架：傳導函數、需求函西安理工大學碩士學位論文數、配置函數，作為個性化信息處理子系統的設計思路，並詳細闡明了該方法的四個實施步驟：個性化信息收集和分類階段、個性化需求分析階段、個性化需求信息配置階段、可製造性評價階段，指明了各個階段的方法在個性化信息處理子系統中的應用，為個性化信息處理于系統的實現奠定了基礎。
  2. Making use of the corba ' s excellent ability of the distributed object handling, fully considering the snmp ' s advantage of being widely supported, the thesis puts forward a kind of network management framework based on corba / snmp gateway. then, according to the framework, combining with itu - t " s recommendation of molding corba system by uml, the thesis models nms interfaces of requirement and analysis stage. the interface requirement is explained, and the static structures and dynamic behaviors are described with uml graphic syntax

    本文分析了傳統網管框架的不足，利用corba優秀的分散式對象處理能力，又充分考慮snmp支持廣泛的優點，提出一種基於corba snmp網關的網管系統框架；然後，結合itu - t使用uml建模corba系統的建議，對網管系統介面進行了需求和分析階段的建模，闡釋了系統的介面需求，並使用uml圖解語法對介面的靜態結構和動態行為進行描述。
  3. Requirement analysis tool is used in the requirement analysis stage of software engineering. its basic function is to assist system analyst to analyze the requirement of the developed system, and to get an intact and accurate software requirement specification which is made up of data flow diagram and data dictionary finally

    需求分析工具用於軟體工程的需求分析階段，它的基本功能是輔助系統分析人員對開發的系統需求進行分析，最終得到由數據流圖和數據字典組成的完整而準確的軟體需求規約。
  4. In order to ensure to process regularly the daily maintenance management, this paper is based on the theory and method of database design and the theory of pavement management system, combining the application environment and operation flow of the expressway maintenance system, bringing forward the four stages of the expressway maintenance system design which are the requirement analysis of consumers, conception framework design, logic framework design and physical framework design, scheming out an optimum database mode applied to all kinds of expressway maintenance systems, and establishing a common database application system, so that the expressway maintenance system can evaluate the pavement performance, forecast the pavement performance and make decisions of the pavement maintenance

    為了保證高速公路日常養護管理正常有序的進行，本文根據數據庫的設計原理、方法及路面管理系統原理，結合高速公路養護管理系統的實際應用環境和操作業務流程，提出了高速公路養護管理系統數據庫設計的4個階段? ?用戶實際需求分析、概念結構設計、邏輯結構設計和物理結構設計，設計出適用於各種高速公路養護管理系統最優的數據庫模式，並建立了通用的數據庫應用系統，使得養護管理系統能夠進行路面性能評價、性能預測和養護維修決策
  5. The waterfall model is a software development model first proposed in 1970, in which development proceeds linearly through the phases of requirements analysis, design, implementation, testing ( validation ), integration and maintenance

    譯文：瀑布模型的軟體開發模式是在1970年首先被提出的，在發展中完善，通過線性階段需求分析、設計、實施、測驗（驗證） 、集成和維護。
  6. The design keeps to the classic life cycle of software engineering ( waterfall model ). according to software analysis, software design, software code and software maintenance, the design is divided into nine processes such as define systematic goal, feasibility analysis, demand analysis, outline design, design, software code, software test in detail, software maintain

    該設計遵循了軟體工程中軟體生命周期法（瀑布模型） ；按照軟體分析、軟體設計、軟體編碼、和軟體維護等過程，系統分為定義系統目標、可行性分析、需求分析、概要設計、詳細設計、軟體編碼、軟體測試、軟體維護等九個階段。
  7. 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

    需求規格說明是需求分析階段的產品，我們通常採用的是未使用任何限制非形式化的自然語言進行描述，這種自然語言書寫的需求說明，雖然易於理解和使用，但難以保證其正確性、完整性、無二義性、一致性，驗證過程只能採用不太規范、不太嚴格的人工走查的方法進行檢查，稍微復雜一些軟體的需求規格說明的檢查，實際上已經超出了人工檢查的能力。
  8. Because of lack of abstraction at the stage of requirement analysis, the traditional management information systems of engineering designing project are not suitable to dynamic recomposition of business management process. this paper will combine workflow technologies with management workflow system of engineering designing project ( edwfms ). by decomposing work into good - definitioned tasks and roles and executing and monitoring them according to rules and processes, we can boost efficiency, reduce cost, enhance level of business management of engineering design department

    傳統的工程設計項目管理信息系統在需求分析階段缺乏高度的抽象性，使得最終的需求模型無法適應管理業務流程的動態重組，本文將結合正在研發的工程設計項目管理信息系統集成工作流技術，將業務處理工作分解成定義良好的任務和角色，並按照一定的規則和過程予以執行和監控，達到提高辦事效率，降低生產成本，改善工程設計單位生產經營管理水平和競爭力的目標。
  9. Surveillance in requirements analysis phase

    軟體工程需求分析階段監理要點
  10. In requirements analysis process, we focus on understanding the requirement documentation and translating the requirements into use cases

    在開發的需求分析階段，主要是理解需求並根據需求形成用例。
  11. At the first half part, the article discussed the two main steps at the earlier preparatory stage, the demand of the security and the risk analysis. thus get the goal and the principle of the security design

    在論文的前半部分，論述了方案設計前期準備的兩個關鍵階段，即安全需求分析階段與風險分析階段，並對如何進行安全需求分析和安全風險分析進行了詳細的闡述。
  12. At last, illustrated by the development of guangzhou telecom facility management, the details of analyzing and design is described, which is the core phase to construct fm, this phase revived the contents and laws of the management of telecom facilities

    以廣州電信設施管理信息系統為例，詳細闡述了運用webgis技術來建設城市設施管理信息系統的核心部分?需求分析階段和系統設計階段，用uml語言對電信設施管理的內容和規律進行了再現和升華。
  13. Accordingly, it is brought out in this article that in the phase of acquirement more method should be used in order to make the requirement of users clear and in the phase of systems analysis systemic method should be used with an eye to material circulation, information circulation, capital circulation and static object of management

    本文就存在於以上兩個階段的問題提出在需求分析階段應採用多種需求分析方法，以求更加準確地反映客戶的需求；在系統分析階段提出應採用系統的方法，具體著眼於物流分析、資金流分析、信息流、和靜態管理對象的分析。
  14. The reason that the ratio of successful mis is low in our country lies in the two phase, one is acquirement of need ; the other is systems analysis

    我國企業的管理信息系統實施的成功率並不高，原因主要出在需求分析階段和系統設計階段。
  15. In the acquirement phase, user is used to put forward their requirement of software and describe their work. what they say is always not systemic and integrated

    在需求分析階段，用戶往往會首先提出敘述自己的業務以及對軟體的要求，這些內容常常會不系統、不完善。
  16. Requirements work is still performed in the requirements phase, design work in the design phase, and so forth, with each of the phases consisting of linear, explicitly defined processes

    需求分析仍然在需求分析階段處理，設計工作仍然在設計階段進行，如此類推，每個階段包含線性的、定義明確的過程。
  17. Most projects have a dedicated requirements phase in which business analysts and consultants talk with end - users and business owners about what they want or need the system to do

    大多數項目有專門的需求分析階段，在這一階段中，業務分析人員和顧問與最終用戶和企業所有者一起探討他們想要或需要系統做什麼。
  18. In the stage of demanding analysis to this system, i have visited the experts and workers who are related to it ; base on oriented - object theory in aspect analyze and design in order to design object layer static state frame layer subject layer attribute layer

    該系統在需求分析階段走訪了有關的專家及工作人員，在分析設計階段應用面向對象的理論詳細的分析並設計其靜態架構的對象層、結構層、主題層和屬性層。
  19. On the basis of the design frame, the main implementation approaches are narrated. tsa was tested during the requirement analysis phase of the software " aerospace distributed unit ( hdu ) ", which verified its usefulness during assisting in analysis modeling and model verification

    Tsa在航天分散式單元（ hdu ）開發的需求分析階段經過初步測試性使用，證實了它在輔助分析建模、模型驗證上所起的作用基本達到了預期的效果。
  20. During the course of software developing ; requirement analysis is a decisive step. the lemma of this article is to discuss uml application on requirement analysis. finally, this thesis builds the model of the products survey management information system ( psmis ) with uml

    軟體系統的開發流程中，需求分析是其中決定性的一步，本文的主旨就在於探討uml如何應用於軟體需求分析階段，並對「產品檢驗管理信息系統」進行了uml建模。
分享友人
分享到 Line

分享到臉書