The main goal of the requirements phase is to produce the Software Requirements Specification (SRS), which accurately captures_the client's requirements and which forms the basis of software development and validation. The basic reason for the difficulty in specifying software requirements comes from the fact that there are three interested parties - the client, the end users, and the software developer. The requirements document has to be such that the client and users can understand it easily and the developers can use it as a basis for software development. Due to the diverse parties involved in software requirements specification, a communication gap exists. This makes the task of requirements specification difficult (Figure 2-1).
There are three basic activities in the requirements phase. The first is problem or requirement analysis. The goal of this activity is to understand such different aspects as the requirements of the problem, its context, and how it fits within the client's organization. The second activity is requirements specification, during which the understood problem is specified or written, producing the SRS. And the third activity is requirements validation, which is done to ensure that the requirements specified in the SRS are indeed what are desired.
需求阶段的主要目标是制定软件需求规范(SRS),该规范准确地捕捉了客户的需求,并构成了软件开发和验证的基础。指定软件需求困难的基本原因是有三个相关方——客户端、最终用户和软件开发人员。需求文档必须使得客户端和用户能够容易地理解它,并且开发人员能够将其用作软件开发的基础。由于软件需求规范涉及的各方不同,因此存在沟通差距。这使得需求规范的任务变得困难(图2-1)。
需求阶段有三个基本活动。第一个是问题或需求分析。此活动的目标是了解问题的不同方面,如问题的要求、上下文以及它如何适应客户的组织。第二个活动是需求规范,在此过程中指定或编写已理解的问题,生成SRS。第三项活动是需求验证,这是为了确保SRS中规定的需求确实是所需的。
Software Requirements
最新推荐文章于 2024-08-26 10:30:00 发布