Charming Waters Portal and Mobile App Development - Non-Functional Requirements

Non-Functional Requirements for Charming Waters Portal and Mobile App Development

Question

A small river cruise company Charming Waters hired you as Power Platform Solution Architect.

The company wants to develop a new portal for the customers and a mobile app for their sales team.

Please select only the non-functional requirements that Charming Waters asks you to implement.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E. F.

Correct Answers: B and E

The project requirements are divided into two groups: functional and non-functional.

The functional requirements define what the system should do and behave like if you push the save button, the system saves the document.

The non-functional requirements describe the system's properties that support system behavior, like saving the document should not take more than 3 seconds on average.

The typical non-functional requirements include regulatory, compliance, privacy, performance specifications, recovery time, availability, etc.

Option B is correct because the requirement for portal content compliance is a non-functional requirement.

Option E is correct because the requirement for mobile app initial load should take not more than 1.5 seconds is a performance non-functional requirement.

Option A is incorrect because the offline capabilities of the mobile app are the app's behavior functional requirement.

Option C is incorrect because the report generation and delivery is the system behavior functional requirement.

Option D is incorrect because the requirement for the OAuth2 authentication is the portal functional requirement.

Option F is incorrect because the requirement to direct the Contact form content from the prospective clients to the sales team is the portal functional requirement.

For more information about non-functional requirements, please visit the below URLs:

As a Power Platform Solution Architect for Charming Waters, the non-functional requirements are the aspects that are not related to the specific features of the portal or mobile app, but rather the quality attributes and constraints that the system must satisfy. Here's a breakdown of each option and whether it's a non-functional requirement:

A. The sales team should see the information about cruise capacity and current occupancy even when they do not have internet access. This requirement is a non-functional requirement as it specifies a performance attribute (i.e., offline access) that the mobile app must provide.

B. The portal content should comply with the latest travel industry regulations This requirement is also a non-functional requirement as it specifies a quality attribute (i.e., compliance with regulations) that the portal must satisfy.

C. Every morning the sales manager should receive a sales report with the previous day results This requirement is not a non-functional requirement as it specifies a specific feature (i.e., sales report generation and delivery) that the system must provide.

D. The portal authentication should be based on the OAuth2 protocol only This requirement is a non-functional requirement as it specifies a technology constraint (i.e., use of OAuth2 for authentication) that the portal must follow.

E. The mobile app initial load should take not more than 1.5 seconds This requirement is also a non-functional requirement as it specifies a performance attribute (i.e., initial load time) that the mobile app must satisfy.

F. Before purchasing a cruise, the customers should contact the sales team directly using the portal's Contact form. This requirement is not a non-functional requirement as it specifies a specific feature (i.e., contact form) that the system must provide.

In summary, the non-functional requirements specified by Charming Waters are:

  • The mobile app should provide offline access to cruise capacity and current occupancy information.
  • The portal content should comply with the latest travel industry regulations.
  • The portal authentication should be based on the OAuth2 protocol only.
  • The mobile app initial load should take not more than 1.5 seconds.