全部

1·Requirements elicitation is continuous.

需求抽取是连续的。

2·Does this requirements elicitation scenario look familiar to you?

下面这种启发用户说出需求的场景您是否感觉很熟悉呢？

3·Research and Application of Use-Case Driven Analysis Method on Software Requirements Elicitation;

用例驱动技术从行为者的角度建立用例，旨在减少软件开发的复杂度。

4·Requirements engineering consists of activities like requirements elicitation, specification and validation.

需求工程包括的活动有需求捕获，需求定义和需求验证。

5·The main purpose of this document is to aid the Requirements Elicitation in a software development life cycle.

这份文档的主要目的是帮助增强软件开发生命周期中的需求捕获过程。

6·They are requirements elicitation, requirements analysis, requirements specification, requirements validation and requirements management.

它们分别是需求获取、需求分析、需求规格说明编写、需求验证、需求管理。

7·We've seen Systems Engineers responsible for everything from planning, to requirements elicitation, to architecture capture, to integration and testing.

我们看到“系统工程师”会对一切事情负责，从计划到需求获取，到架构获取，到集成再到测试。

8·Requirements elicitation is a process whereby a software designer or engineer attempts to identify all the capabilities and features of a specific application.

需求诱导(requirements elicitation)这个过程让软件设计师或工程师可以尝试发现特定应用程序的所有功能和特性。

9·How could testers remain involved in the requirements elicitation activity while immersed in system, integration, and user acceptance test, all at the same time?

测试人员如何能够仍旧参与需求启发活动，同时又浸入系统、集成，和用户体验测试？

10·Due to the criticality and impact of this phase, it is very important to perform the requirements elicitation is performed in no less than a perfect manner.

因为这个阶段的困难性和影响力，按一个理想的模式来完成需求捕获过程就非常重要。