计算机英语教程翻译吕云翔,大学实用计算机英语教程翻译-吕云翔-Unit 2

Section A

Software Requirements(软件需求)

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.

There are three basic activities in the requirements phase. The first is problem or

requirements 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.

There are three main approaches to analyze. Unstructured approaches rely on interaction

between the analyst, customer, and user to reveal all the requirements (which are then documented). The second is the modeling-oriented approach, in which a model of the problem is built based on the available information. The model is useful in

determining if the understanding is correct and in ensuring that all the requirements have been

determined. Modeling may be function-oriented or object-oriented. The third approach is the

prototyping approach in which a prototype is built to

validate the correctness and completeness of