Why is an SRS document also known as black–box specification? What do you understand by requirement gathering? Explain the different requirements gathering techniques that are used by an analyst.
Answer:
An SRS document known as black–box specification because it should only describe what the system must do and refrain from stating how to do these.
It means that the SRS document should specify the system's external behavior and not discuss the implementation issues.
The below questions of our project must be be crystals clearly understood by the analyst to obtain a good vision of the proper problem:
• What is the problem?
• Why is it important to solve the problem?
• What are the possible solutions to the problem?
• What exactly are the data input to the system and what exactly are the data output by the system?
• 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 exactly would the data interchange formats with the external system be?
Comments
Leave a comment