Requirements gathering is not as tough as the name sounds. In fact it is a job that needs some or none technical knowledge and a reasonable business knowledge with good communication skills (Both written and Oral). When it comes to requirements, simply think about a builder that you hired to build your new house. What does the builder do when he first approach you?
He will ask you several questions such as ‘How many bed rooms you need?’, ‘How many bath rooms you need?’ etc… these are nothing but requirements for the new house.
In the same way, a Business Analyst or Requirements Analyst will talk to the business owner and ask him several questions or simply take the notes of his requirements for the new business or some modification to the existing business etc..
These requirements can be taken as a rough copy in a note book or computer while the business is speaking. After the meeting, the requirement Analyst will make them into a fair copy by adding some detail explanation so that every one in the organization can understand them. We will see more about the sample documentation of Requirements template in next session.
Requirements and Business Requirements are two very common words that are often used interchangeable in an organization. Being said that, ‘Requirements’ are the first and foremost step in the software life cycle management.
What any one can do with out requirements? If some one ask a tester to create test cases with out giving them requirements, is not it foolishness? I have seen in some websites as one of the most popular interview question for a tester position is “How can you write test cases when there are no requirements? “.
Well, If you seriously thinking about a quality product, then never ask this question. Ok, lets come back to the topic again. Requirements are the first step that the business takes into consideration before they have decided to built a new product/piece of application, or a change in the current application or product.
There is some one called ‘Requirements analyst’ whose responsibility is to prepare requirements document based on the business needs. These requirements are further classified into two types such as ‘Functional requirements’, and ‘Technical requirements’.
Functional Requirements give the over view of the current business and also gives a over all view on future business. This document does talk about what is needed in future or what changes are required now in a simplistic language that a common man can understand.
Technical requirements give the more detailed specifics of the problem and how to solve the problem in a technical front so the dev leads and technical folks can clearly understand.
Please ask questions below if you have any questions?