A food delivery company plans to develop a new Power Platform solution.
The company asks you, as a Solution Architect, to help.
The company prepared preliminary requirements.
What are the functional requirements on the company's list?
Click on the arrows to vote for the correct answer
A. B. C. D. E. F.Correct Answers: A, C, D and F
As a Solution Architect, you need to lead the process of collecting the requirements.
The project requirements are divided into two groups: functional and non-functional.
The functional requirements define what the system should do and behave like users should create an account to use the food delivery service.
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 A is correct because creating an account to use the food delivery service is the app's functional requirement.
Option C is correct because monitoring the position of the delivery vehicles on the dashboard map all the time is a functional requirement.
Option D is correct because the requirement to provide a list of the restaurants that users can order food from is the system's functional requirement.
Option F is correct because the requirement to text the customer with an estimated delivery time is the system's functional requirement.
Option B is incorrect because the requirement for the disclaimer about food delivery time compliance is a non-functional requirement.
Option E is incorrect because the requirement for restoration of the operation within 2 hours is a non-functional requirement.
For more information about functional requirements, please visit the below URLs:
Sure, I'd be happy to provide a detailed explanation of the functional requirements listed for the food delivery company's new Power Platform solution.
Functional requirements describe what the system or software is supposed to do, in terms of specific features and functions that are required to meet the needs of the users and the business. These requirements are typically expressed as user stories or use cases, which describe the desired behavior or interaction of the system from the perspective of the user.
Let's go through each of the requirements listed and explain what they mean:
A. The users should create an account to use the food delivery service This requirement specifies that the solution should have a user authentication and registration feature, where users can create an account with their personal information such as name, email, and phone number. This is a common requirement for many online services and is important for security and personalization.
B. The disclaimer about food delivery time should comply with city regulations This requirement specifies that the solution should include a disclaimer or notice about food delivery time that is compliant with the regulations of the city in which the service is being offered. This is important to ensure that the company is following local laws and regulations.
C. The manager should see the position of the delivery vehicles on the dashboard map all the time This requirement specifies that the solution should include a real-time tracking feature for delivery vehicles, where the manager can see the current location of each vehicle on a map displayed on a dashboard. This is important for efficient management of delivery operations, enabling the manager to quickly identify any issues or delays and take appropriate action.
D. The app should have a list of the restaurants that users can order food from This requirement specifies that the solution should have a database or directory of restaurants that are available for food delivery, which users can browse and select from. This is a key feature of a food delivery service and is necessary to provide users with a selection of options to choose from.
E. If the system fails, the solution operations should be restored within 2 hours This requirement specifies that the solution should have a robust and reliable system architecture, such that if the system were to fail or experience downtime, it would be restored within 2 hours. This is important to minimize disruption to the service and ensure that users can continue to place orders and receive deliveries.
F. The app must send a text to the customer with an estimated delivery time after the order is placed. This requirement specifies that the solution should include an automated notification feature, where customers receive a text message with an estimated delivery time after they have placed an order. This is an important feature for providing customers with up-to-date information about the status of their order and when they can expect to receive their food.
Overall, these functional requirements provide a good starting point for designing and developing a food delivery service using the Power Platform. By meeting these requirements, the solution should be able to provide users with a seamless and convenient experience for ordering food and managing deliveries, while also complying with local regulations and providing the necessary features for effective management and maintenance of the system.