早期的频繁的客户接触与简单的需求电子数据表代替了传统的功能规格说明书和复杂的用例图。
Early and frequent customer contact combined with a simple requirements spreadsheet replace traditional functional specifications and sophisticated use case diagrams.
用例图经常被分组来显示涉众们的需求集合（请看图1中的例子）。
Use case diagrams (see Figure 1 for an example) are often grouped to show a collective set of stakeholder needs.
它包括了描述用例模型中所确定的功能需求的逻辑实现的类和序列图。
It consists of class and sequence diagrams that describe the logical implementation of the functional requirements that you identified in the use case model.
您初始的需求是以高层用例的形式获得的，图2中显示了一个实例。
Your initial requirements are captured in the form of high-level use cases, an example of which is shown in Figure 2.
图5B.分析师活动：跟踪到用例的需求或特性。
Figure 5b. Analyst activities: Requirements or features traced to use cases.
Rhapsody是个双向的模型驱动解决方案，可以通过需求图、用例图、序列图、活动图以及状态图捕获项目需求。
Rhapsody is a round-trip model driven solution and supports capturing the project requirements using requirements diagrams, use-case diagrams, sequence diagrams, activity diagrams and state charts.
图四：在假定情节下，用RequisitePro描述需求到业务规则。
Figure 4: Tracing requirements to business rules in RequisitePro with what-if scenario.
图1显示了RationalRequirementsComposer中获得的需求：注意要使ProcessPurchaseOrder业务用例能够满足所有的业务目标。
Figure 1 shows the requirements captured in Rational requirements Composer. Notice that the Process Purchase Order business use case meets all of our business goals.
您可能还想链接到一些工件，例如：多格式文件、用例图、业务模型以及脚本，来继续加工您的需求。
You might also want to continue elaborating your requirements by linking to artifacts, such as: rich text documents, use-case diagrams, business models, and storyboards.
用例文本和关系图描述用户对需求的理解。
Use case text and diagrams describe the users' understanding of the requirements.
序列图的主要用途之一，是把用例表达的需求，转化为进一步、更加正式层次的精细表达。
One of the primary uses of sequence diagrams is in the transition from requirements expressed as use cases to the next and more formal level of refinement.
用例标题上会有一点的变动：需求uc4被删除了，而添加了需求UC5(图15，“对已分支的需求文档所做的修改”)。
Here, there's a modification in the use case title: the requirement UC4 has been removed and the requirement UC5 has been added (Figure 15. Modification on branched requirements document).
从UML 出现之初开始，就一直使用活动关系图 (Activity diagram)来标识和处理描述业务用例的工作流的需求。
Since UML's inception, Activity diagrams have identified and addressed the need for describing the workflow of a business use case.
考虑一下帮助实现可视化的工件的类型，并进一步定义的需求(例如，脚本，用例图，多格式文本文件等等)。
Consider the types of artifacts that would help visualize or further define your requirement (for example, a storyboard, use-case diagrams, rich text documents, and so forth).
图12显示了Rational Software Architect中的业务模型、需求和业务用例uml关系图的集成视图。
Figure 12 shows the integrated view of the business model, requirements, and a business use case UML diagram in Rational Software Architect.
以海上目标监视与打击体系为例，给出利用UML中的用例图、类图、活动图、协作图对体系顶层需求进行描述的方法。
Taking sea target surveillance and hitting system for example, the top-level demands are described using user case diagram, class diagram, activity diagram and collaboration diagram in UML.
本文立足于国产谷物测产系统的需求，用VB开发了谷物产量数据处理和产量分布图生成系统软件。
This paper developed a yield mapping system software based VB for the requirement of national grain yield monitor system.
如果他们用整洁的CAD图给客户展示早期的设计，那么他们的客户很少提出需要大改设计的需求。
If they show clean CAD drawings to their clients in the early design discussions, the clients are less able to discuss needs and requirements that may require radical changes in the design.
概要描述中移基本需求，指明交互的实体名称和相互关系，即角色定义，给出uml用例图。
In the outline description moves the basic demand, indicates the interactive entity name and the reciprocity, namely the role definition, produces UML to use the illustration.
利用UML的用例图、类图、时序图、合作图、组件图和部署图等，定义系统需求，描述系统设计。
The system requirements and design models are defined by UML diagrams such as Use Case diagram, Class diagram, Sequence diagram, Collaboration diagram, Component diagram, and Deployment diagram.
以uml中的用例模型得出了系统的需求模型；以uml中的类图和包图对系统作进一步的分析。
Getting the system requirement model by using use case model in UML, and making further system analysis by using class diagram and package diagram in UML.
用例图保证需求与可测试用例相关。
Use cases diagrams ensure that requirements are related to testable use cases.
论文重点分析了代收费系统的业务需求，并以代收电信资费为例概括出系统用例图，设计出主要业务用例。
Paper focused on analyzing business processes needs of collection charges and generalized systems use case diagram and designed major business cases.
通过对系统总体需求分析，利用具体用例图、用例规约描述对系统功能模块进行功能性需求分析；
Through the analysis of system's specific requirements, use case diagram and use body to describe demand analysis of system function module.
用例包图的读者主要是项目的各种涉众，因此图形的组织必须满足他们的需求。
The primary audience of use-case package diagrams is project stakeholders; therefore, the organization of these diagrams should reflect their needs.
在需求分析阶段运用UML中的用例图分析了系统的主要用例，划分了功能模块并给出了系统中重要的工作流程。
It analyzes the system with the use case picture in UML during the course of requirement analysis and divides the function module and provides the important workflow in the system.
通过应用统一建模语言的用例图展示了系统的功能需求。
Unified Modeling Language(UML) use case diagram was used to denote the function requirements of the system.
家具频道的栏目及首页都是按功能空间划分内容板块，同时支持用户自定义条件搜索，更能满足客户的需求。用大图模板呈现70%的内容，最大程度地提高的用户体验。
Conduct personalized searches is better to meet customers' needs as well. 70% of content is presented in bigger templates, which provides users with a better viewing experience.
家具频道的栏目及首页都是按功能空间划分内容板块，同时支持用户自定义条件搜索，更能满足客户的需求。用大图模板呈现70%的内容，最大程度地提高的用户体验。
Conduct personalized searches is better to meet customers' needs as well. 70% of content is presented in bigger templates, which provides users with a better viewing experience.
应用推荐