Functional requirements outline the tasks that the ADF is expected to perform. These tasks can be visualized through use cases or other specific functionalities that illustrate the ADF’s intended achievements.
These functional requirements encompass detailed descriptions of the ADF, with the required functionality being as precise as possible, including any restrictions that are specific to the ODD.
On the other hand, non-functional requirements describe the manner in which the ADF should operate. These are primarily conceptualized through performance requirements, design limitations, and quality attributes.
Non-functional requirements typically provide details on constraints, goals, or control mechanisms associated with the ADF’s qualities and its success. They specify the level of quality or standard to which an ADF should adhere. In general, these requirements are challenging to measure and test. As a result, the user experience, including the ADF’s look-and-feel, as well as safety, security, and privacy requirements, play a significant role.
Main Question
Are the requirements classified as functional and non-functional?
Sub-Questions
- Is there a detailed description of the ADF including a defintion of the expected target?
- Are the specific tasks the ADF expected to perform described?
- Are the restrictions that are specific to the ODD identified?
- Is the level of quality or standard is the ADF expected to adhere to defined?
- Are the aspects of user experience, safety, security and privacy considered?