img
Question:
Published on: 21 November, 2024

Briefly Discuss about Requirements Analysis

Answer:

After requirements gathering is complete, the analyst analyses the gathered requirements to form a clear understanding of the exact customer requirements and to weed out any problems in the gathered requirements.

For carrying out requirements analysis effectively, the analyst first needs to develop a clear understanding of the problem. The following basic questions pertaining to the project should be clearly understood by the analyst before carrying out analysis:

What is the problem?

*Why is it important to solve the problem?

*What exactly are the data input to the system and what exactly are the data output by the system?

*What are the possible procedures that need to be followed to solve the problem?

*What are the likely complexities that might arise while solving the problem?

*If there are external software or hardware with which the developed software has to interface, then what should be the data interchange formats with the external systems?

During requirements analysis,the analyst needs to identify and resolve three main types of problems in the requirements:

• Anomaly - an anomaly is an ambiguity in a requirement. When a requirement is anomalous, several interpretations of that requirement are possible. Any anomaly in any of the requirements can lead to the development of an incorrect system, since an anomalous requirement can be interpreted in the several ways during development.

• Inconsistency - Two requirements are said to be inconsistent, if one of the requirements contradicts the other

• Incompleteness - An incomplete set of requirements is one in which some requirements have been overlooked. The lack of these features would be felt by the customer much later, possibly while using the software. Often, incompleteness is caused by the inability of the customer to visualise the system that is to be developed and to anticipate all the features that would be required.

Random questions