Requirement Analysis

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 1

Requirement Analysis.

1. Eliciting requirements.

This is the process of communicating with clients and users in order to determine their
needs. This is sometimes referred to requirements gathering. By this we will conduct a
customer’s feedback surveys and organize email feedback. This system allows you to
keep track of requests and the people who made them, as well as ideas you've already
shared. Employees can use the procedure to provide a clear roadmap for future customer
interactions. We know that customer feedback is major because it serves as a guiding
resource for the growth for our project.

2. Functional requirements.

Functional requirements assist in keeping our team on track. A poorly specified scope
causes the schedule to be extended and the expense to rise. a functional requirement will
describe a particular behaviour of function of the system when certain conditions are met,
for example authentication of a user when he/she tries to log into our website.

3. Usability requirements.

Usability requirements are a set of documented expectations and requirements intended to


make a product, service, process, or environment simple to use. In our project, for
example, we will include customization and personalization as a necessity to customise or
personalise items for consumers. In our websites, users can search any state in Malaysia
and we will provide a list where to go and quick info about the place. We will also
provide a recommendation from our teams about the spots that they choose.

You might also like