What are the issues of requriment analysis?
In the traditional waterfall model of software development, the first phase of conditions analysis is also the most important bone . This is the phase which involves gathering information about the client’s requirements and defining, in the clearest possible terms according to client, the problem that the product is anticipated to break.
This analysis includes understanding the client’s business environment and constraints, the functions the product must perform, the performance situations it must cleave to, and the external systems it must be compatible with. ways used to gain this understanding include client interviews, use cases, and “ shopping lists ” of software features.
The results of the analysis are generally captured in a formal conditions specification, which serves as input to the coming step.
1 Ambiguous Demands: Guests don’t( really) know what they want Conceivably the most common problem in the conditions analysis phase is that guests have only a vague idea of what they need, and it’s up to you to ask the right questions and perform the analysis necessary to turn this unformed vision into a formally- proved software conditions specification that can, in turn, be used as the base for both a design plan and an engineering armature.
2 Change Requests: Conditions change during the course of the design The alternate most common problem with software systems is that the conditions defined in the first phase change as the design progresses. This may do because as development progresses and prototypes are developed, guests are suitable to more easily see problems with the original plan and make necessary course corrections; it may also do because changes in the external terrain bear reshaping of the original business problem and hence necessitates a different result than the one firstly proposed. Good design directors are apprehensive of these possibilities and generally formerly have backup plans in place to deal with these changes.
3 Undue Timelines: Guests have unreasonable timelines It’s quite common to hear a client say commodity like “ it’s an exigency job and we need this design completed in X weeks ”. A common mistake is to agree to similar timelines before actually performing a detailed analysis and understanding both of the compass of the design and the coffers necessary to execute it. In accepting an unreasonable timeline without discussion, you are, in fact, doing your client a injustice it’s relatively likely that the design will either get delayed( because it was n’t possible to execute it in time) or suffer from quality blights( because it was rushed through without proper examination).
4 Communication gaps: Communication gaps live between guests, masterminds and design directors frequently, guests and Masterminds fail to communicate easily with each other because they come from different worlds and don’t understand specialized terms in the same way. This can lead to confusion and severe miscommunication, and an important task of a design director, especially during the conditions analysis phase, is to Insure that both parties have a precise understanding of the deliverable and the tasks demanded to achieve it.