The requirement gathering is starting point of the user centre design process. Requirements gathering is a very crucial step before you start design or development. Identifying the variation of the requirement needs is the core challenge.Understand the context, focus on the needs & challenges to discover the problem should be the core focus of the requirement gathering method. Real world users requirement gathering is an iterative process facilitates how to gather data and convert this data into system requirements.

About Requirement Gathering

A requirement is a statement about an intended product that specifies what it should do or how to do it. For requirements to be effectively implemented and measured, they must be specific, unambiguous and clear. For example, a requirement may be that a specific button must enable printing of the contents of the current screen.

A great user experience is all about enabling users achieve their objective when using your artifact - be it a website, a software system or anything that you create. Now take a step back. Trying to understand how to make it easy for users to achieve their goals would be pointless if you don't place it within the context of what you know about your users.

Every UX project has its own unique requirements, and research is used to determine what they are. We can divide the requirements into three categories: Business, User, and Technical.

• Business Requirements :

  What the product hopes to accomplish for the company/sponsors. Startups and smaller companies might be able to summarize these in a business model canvas. Larger companies will usually have more requirements, sometimes completed by business analysts or product managers. In either case, these requirements can be better understood through stakeholder interviews.

• User Requirements :

  What the user wants is central to design thinking, so these requirements should have an enormous influence on the UX design. While using your own empathy will help, you shouldn't guess at user requirements - these should be gathered through user interviews, surveys, field or diary studies, etc.

• Technical Requirements :

  We can separate technical requirements into functional and nonfunctional categories. The functional specifications outline what the product should be able to do, such as authentication and administrative functions, and can be organized into a specs document like this one from Product Hunt. Nonfunctional specifications describe how well the product performs, such as usability, performance, data integrity, and maintenance.