What is the classification for each requirement?

DRAG DROP

A company plans to implement Dynamics 365 Supply Chain Management.

You are a solution architect and need to prepare a Solution Blueprint document for this implementation.

You need to classify the requirements by type.

What is the classification for each requirement? To answer, drag the appropriate classifications to the correct requirements. Each classification may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.

View Answer

Answer:

Explanation:

Box 1: Non-functional

Requirements are commonly referred to as either functional or non-functional. Functional requirements describe what the solution needs to do or its behaviors, and non-functional requirements commonly describe non-behavior aspects of the solution such as performance requirements.

The following examples are of well-composed non-functional requirements:

Average screen load time for internal users that are not mobile will be less than three seconds.

External portal must be able to handle 100 concurrent users who are performing case submission.

Any credit card number that is used cannot be stored in Common Data Service environment.

Box 2: Functional

Example functional requirements

The following scenarios describe simple examples of functional requirements:

As a sales user, I need to be able to close an opportunity as lost and then capture why it was lost so that we can improve our sales tactics in the future.

As a sales manager, I need to be able to approve a discount on a quote so that I can reduce the total price and give a discount to the customer.

As a staff accountant, I want to be prevented from closing a batch that has pending items so that I do not have to reopen it later.

Box 3: Non-functional

Examples of common non-functional requirement types include:

Availability

Compliance/regulatory

* -> Data retention/residency

Performance (response time, and so on)

Privacy

Recovery time

Security

Scalability