Importance of Needs Analysis We all know that the requirements are collected before any software development project. This is what truly understand the importance of ....
Getting the requirements right at the beginning of your project, you can save a third or more of its overall budget.
You save money by getting the requirements right to start. Why? Because of the requirements to correct the errors represent 70% to 80% cost recovery .
The quality requirements will be captured to define a large extent, if your project is a success or a failure. Sometimes you may be asked to reduce the requirement to capture time of my argument is: "If you can invest in getting the requirements done right the first time, how you will pay the cost and time needed to be a resource it would be much more than they have to invest today. "
Requirement analysis advice and analysis requirements capture processes should be reflected in the documentation which shall include the following:
Define the problem and the high level description of the solution. The analyst must understand the problem and the need for a solution. The questions that need answering here are
What problems will be solved is the solution?
What benefits the company will make the solution?
The requirements?
In addition to answering questions about a high level description of the solution to be developed and operational requirements to meet the needs to be documented.
Meeting the needs of all stakeholders and users of the solution.
You must ensure that the needs of all stakeholders are well understood. You must also understand the needs of people who are ultimately going to use the solution / system. This is very important so that the solution meets all counts.This also help identify conflicting needs you.
Define what the solution should and should not do.
You must not only define what the solution should be, but also define what the solution will not do. The requirements should be established so that nothing is left to the imagination or create doubts.
Define the characteristics required.
Provide details of the characteristics required in the software package. In technical terms, define the functional and nonfunctional requirements. Trying to capture the "what" and not "how."
Capture all the supporting information.
Include details of the proceedings, workflow, information flow, hierarchies, etc. Record any other information that may be relevant to the studied solution. Identify the source of all requirements and be documented in such a way that is manageable.
Once you have completed all the above tips, it is feasible, non-conflicting requirements unambiguous, traceable and verifiable.
Benefits of Good Needs Analysis
Cost Savings
Shorten your development cycle
A product that meets your needs
Improve team productivity
Reduce rework and disputes arising from the requirements clear and unambiguous
