Week 7 | Requirements

Every product has requirements. It's no different in this field. 

A search on the definition of requirement on the internet will turn up as

- a nessecitate

- To call for as obligatory or appropriate

In this case, it is a statement about an intended product that specifies what it should or how it should perform. It should be specific, ambiguous and as clean as possible.

To gather a set of reliable and stable requirements, one should first set themselves to do data gathering.

Data which is sufficient, relevant and appropriate has to be collected to proceed. There are many ways such as to do this. Interviews, focus groups, creating questionnaires and various kinds of observations are just a few of the methods that can be used to collect date from potential users. They all are useful in different ways and the best ones can be custom selected to best fit the needed aim.

• Interviews -->  These are effective in getting people to explore the issues, they can be customized to be structured, semi structured or completely unstructured. 
• Focus groups --> Important in the meeting of future or current stakeholders.
• Questionnaires --> Best at gaining an agreement ad highlighting problematic areas and disagreements during the requirements activity. 

These are just some of the methods and many more can be used to their full advantage to get the most data out of the activities. These are all of course influences by other factors such as the nature of the task, participants and the available resources.