Once specified, those use cases contain the software requirements.
一旦具体化,这些用例就会包含软件需求。
Figure 1: Relationships between software requirements and business rules.
图一:软件需求和业务规则之间的关系。
Figure 2 shows some of the software requirements for the products discussed above.
图2显示了上面讨论的产品的一些软件需求。
Assuming we develop an ATM system, we look at two different software requirements, SR1 and sr2.
假定我们开发一个自动取款机系统,我们看到两种不同的软件需求,SR1和sr2。
Note that you can specify functional software requirements in one of two formats: declarative and use case.
注意你可以用两种格式之一指定功能性软件需求:声明形式和用例形式。
Simulation execution is an important check method of software requirements specifications (SRS).
模拟执行是一种重要的需求规格说明书(SRS)的检测方法。
However, when detailed software requirements are embedded in contracts, odds are your team has trust issues.
然而,当软件需求的细节嵌入到合同中时,你的组织可能有信任问题。
Based on the research of chaos and software requirements complexity theory, a theory model was proposed.
在基于混沌理论和软件需求复杂性理论研究的基础上,提出一种理论模型。
Setup a software-centric requirements tool to give a clear picture of the software requirements for projects.
设置一个以软件为中心的需求工具,为项目提供一幅软件需求的清晰图像。
There are system and software requirements you have to consider before deploying IBM Mashup Center and DB2 database.
在部署IBMMashupCenter和DB 2数据库之前,必须考虑系统和软件需求。
For information about hardware, software, and supported platforms, see CM Server hardware and software requirements.
如果您想得到关于硬件、软件以及支持平台的信息,您可以查看CMServer硬件和软件需求。
There are unclear software requirements because there is miscommunication as to what the software should or shouldn't do.
软件需求不清晰,原因是就软件应否实现的功能缺乏有效的沟通。
Dissecting business rules from software requirements is a good technique for depicting, analyzing, and validating requirements.
将业务规则从软件需求中剥离出来是对于描述、分析和确认需求都很有好处的一项技术。
As we saw earlier, requirement types might include business needs, features, and functional and non-functional software requirements.
正如我们前面看到的,需求类型可能包括业务需要、特性以及功能性和非功能性的软件需求。
For example, if you decide to specify software requirements with use cases, then your guidelines should tell you how to write the flows of events.
例如,你如果决定用用例来规约软件需求,你的指南就应该告诉你如何写出事件流程。
Similar to the discussion about software requirements and their association to business rules, business rules could be linked to a particular use-case step.
同有关软件需求及与其关联的业务规则的讨论类似,业务规则也可以同特定的用例步骤相联系。
His interest in software development best practices led him to develop the concept of use cases as a way to better identify and specify software requirements.
他最感兴趣的是软件开发最佳实践引导他开发用例概念,从而更好地识别和描述软件需求。
If you already know some of the background of the WTP and want to get started downloading all of the required software, skip to the section software requirements.
如果您已经知道WTP的一些背景,并且想直接开始下载所有必需的软件,那么请略过软件需求小节。
Traditional software development method is difficult to support software requirements validation at early stage, which often leads to project uncontrollable.
传统软件开发方法因难以支持需求的早期验证而易导致项目失控。
If the domain (in this case, the hotel industry) is well understood among requirements engineers, the primary focus of their work is software requirements and business rules.
如果这个领域(比如酒店业)为需求工程师所了解,那么首要的工作要点就是软件需求和业务规则。
The initial deliverable to be evaluated is the software requirements. Subsequently, the majority of the evaluation and test is based on the validated software requirements.
最开始进行评价的交付产品是软件需求,随后,大部分评价和测试是基于被确认的软件需求。
Before we discuss use cases, let's consider some of the principles of traditional requirements analysis regarding business requirements, software requirements, and business rules.
在讨论用例之前,让我们先来考虑一些关于业务需求、软件需求和业务规则的传统需求分析的原则。
This section should state the purpose of the document. It could also specify the intended audience. Identify the product whose software requirements are specified in this document.
这部分要描述文档的目的。应该指明读者。说明本需求文档描述了哪个产品的软件需求。
Once the analyst identifies a solution as the most optimal "to-be" BPM, he or she defines the business requirements and refines them into software requirements in the form of use cases.
分析人员将解决方案标识为最优的“将来”BPM 后,他/她需要定义业务需求,并将其细化为软件需求(用例)。
It enables stakeholders to collaborate in context to define requirements by using various visual and textual techniques to capture business objectives and elaborate software requirements.
它使得涉众可以使用各种可视化及基于文本的技术来进行同一语境协作,以捕捉商业目标并精确化软件需求。
If you're installing GAWK from source, consult the README file in the GAWK source distribution, which lists any additional software requirements for successful compilation and installation.
如果您使用源代码安装GAWK,请参考gawk源代码分发版中的README文件,其中列出了进行成功的编译和安装所需的任何附加软件。
The product releases we announced last month (to be generally available in December 2004) are helping to redefine the software requirements, analysis, design, and implementation experience.
上个月我们声明的产品(2004年12月就将投入市场)能够帮助重新定义软件需求、分析、设计和实现经验。
Although these requirements aren't directly related to the story line, they'll have an impact on the final result — just as nonfunctional software requirements must have on a computer system.
尽管这些需求并不直接与故事情节相关,它们还是对最终的结果有着潜在的影响——正如计算机系统上必须有非功能性软件需求一样。
The same is true when we're exploring ambiguous software requirements to meet ambiguous business needs: the business needs change as we move toward them and our understanding of them increases.
研究不确定的软件需求以满足不确定的业务需求也是如此:业务需求会随着我们接近它们以及对它们的理解加深而变化。
By looking carefully at the activities of actors in business use cases and identifying which activities can be replaced by information technology, new software requirements are likely to appear.
通过仔细观察业务用例中使用者的活动以及确定哪一种活动能够被信息技术所取代,新的软件需求就会呈现出来。
应用推荐