What should the business analyst do to ensure that all requirements meet a quality checklist before the development and testing phase?

• A.Assign a verification method to each requirement.
• B.Negotiate with the client to standardize the requirements.
• C.Obtain approval from engineering for partial testing of the requirements.
• D.Validate the requirements deemed important by the stakeholders.

Comment: *

Name: *

Email: *

Verification: *

A company uses a prioritization range of 1-10. in which 10 represents the highest or best. According to the information from the table, which option should the business * analyst recommend?

• A.2
• B.4
• C.3
• D.1

Comment: *

Name: *

Email: *

Verification: *

A business analyst in organization Y is assigned to elicit requirements in a project within a defined timeline.
The business analyst has identified and invited key stakeholders to a requirements workshop.
However, the stakeholders are not giving clear and concise requirements; their opinions about requirements are changing and conflicting with each other in the meeting. In the end. the business analyst could not elicit and define the requirements and therefore adjourned the meeting.
Which tool or technique could have been used by business analyst to avoid this situation?

• A.Decision tree
• B.Document analysis
• C.Prototyping
• D.Surveys

Comment: *

Name: *

Email: *

Verification: *

Midway through Ihe requirements gathering phase, a stakeholder informs the business analyst that a requested requirement does not address the solution. The stakeholder wants to know who made the request. The business analyst spends hours searching emails to identity the requestor.
What should the business analyst have documented?

• A.The source in the RACI matrix
• B.Sponsor approval in the requirements traceability matrix
• C.The source in the requirements traceability matrix
• D.Roles and responsibilities in the RACI matrix

Comment: *

Name: *

Email: *

Verification: *

A project that was going well for the last few months has encountered a situation-regulatory authorities have deemed that the project does not meet their requirements. Although regulatory requirements were identified during an earlier phase of the project, there is no substantial evidence to prove that the requirements were formally rejected.
This could have been avoided if:

• A.the project team documented customer requests and obtained sign-off.
• B.the customer met with regulatory authorities to verify that their requirements were also considered.
• C.the project manager circulated the meeting minutes after the discussions with all the attendees.
• D.a change control process for requirements and their statuses was followed.

Comment: *

Name: *

Email: *

Verification: *