Which of the following activities is typically involved in requirements validation?

Scenario:

A team is working on a software development project to create a fitness tracker mobile application. The stakeholders include the CEO and the marketing manager of the company. They have different perspectives and priorities for the mobile application.

The CEO wants the application to have a user-friendly interface and support various fitness activities. The marketing manager wants the application to have social media integration and personalized workout recommendations to attract more users. 

Identify the goal of requirements negotiation in this scenario.

Match the three Kano classification properties its description. 

Which of the following elicitation technique matches the description below?

A focused event attended by key stakeholders and subject matter experts (SMEs) for a specific duration. Can be used to generate ideas for new features, to reach a consensus on a requirement, or to review requirements.

Which of the following statements applies benefits of having requirements traceability?

Scenario:

A project was almost finished with requirements elicitation. The following is a conversation between business analyst (BA) and stakeholder(SH) while reviewing

a process flow.

BA: “Are you sure we have the

tax calculation steps correct in this process flow?” 

SH: “Well, I'm not sure. That’s the tax department.” 

The BA team hadn’t talked to anyone in the tax department

over the course of requirements elicitation. 

The BA team had no idea that there was a tax department. As soon as the BA and the tax department met, they found a long

list of missed requirements. 

The project was delayed several months due to this situation. 

What actions should the BA team take prior to the elicitation process?

A typical use case specification template includes the following sections:

Assume you are a Business Analyst responsible for eliciting requirements in a new information system project. 

During initial discussions with different representatives, you discover, among other aspects, the following:

• You do not understand some of the company's terminology.

• It is obvious that the company representatives do not use consistent terminology.

• Your main contact person at the company described their ideas by  telling you the expected interactions between specialists and the information system in the form of different flows of user actions.

Which two of the following approaches are suitable for eliciting and documenting the requirements in this case? 

Requirements documentation can be considered from three different perspectives. 

They are:

Match each core activities of

requirements engineering with its relevant description.