English
These requirements apply to the actor Business Analyst
| Define functional requirements from L1 | SHALL | Can define functional requirements based on L1 recommendations in terms of health content, decision-support, and scheduling logic.
|
| Define non-functional requirements | SHALL | Can define non-functional requirements including user-friendliness and cybersecurity, informed by implementer best practices.
|
| Link requirements to personas | SHALL | Can link each functional requirement to the correct persona and business process activity.
|
| Verify scenario coverage | SHALL | Can verify that functionalities depicted in user scenarios are captured in the requirements list.
|
French
Ces exigences s'appliquent à l'acteur Business Analyst
| Define functional requirements from L1 | SHALL | Can define functional requirements based on L1 recommendations in terms of health content, decision-support, and scheduling logic.
|
| Define non-functional requirements | SHALL | Can define non-functional requirements including user-friendliness and cybersecurity, informed by implementer best practices.
|
| Link requirements to personas | SHALL | Can link each functional requirement to the correct persona and business process activity.
|
| Verify scenario coverage | SHALL | Can verify that functionalities depicted in user scenarios are captured in the requirements list.
|
Arabic
تنطبق هذه المتطلبات على الممثل Business Analyst
| Define functional requirements from L1 | SHALL | Can define functional requirements based on L1 recommendations in terms of health content, decision-support, and scheduling logic.
|
| Define non-functional requirements | SHALL | Can define non-functional requirements including user-friendliness and cybersecurity, informed by implementer best practices.
|
| Link requirements to personas | SHALL | Can link each functional requirement to the correct persona and business process activity.
|
| Verify scenario coverage | SHALL | Can verify that functionalities depicted in user scenarios are captured in the requirements list.
|
Chinese
These requirements apply to the actor Business Analyst
| Define functional requirements from L1 | SHALL | Can define functional requirements based on L1 recommendations in terms of health content, decision-support, and scheduling logic.
|
| Define non-functional requirements | SHALL | Can define non-functional requirements including user-friendliness and cybersecurity, informed by implementer best practices.
|
| Link requirements to personas | SHALL | Can link each functional requirement to the correct persona and business process activity.
|
| Verify scenario coverage | SHALL | Can verify that functionalities depicted in user scenarios are captured in the requirements list.
|
Russian
Эти требования распространяются и на актера Business Analyst
| Define functional requirements from L1 | SHALL | Can define functional requirements based on L1 recommendations in terms of health content, decision-support, and scheduling logic.
|
| Define non-functional requirements | SHALL | Can define non-functional requirements including user-friendliness and cybersecurity, informed by implementer best practices.
|
| Link requirements to personas | SHALL | Can link each functional requirement to the correct persona and business process activity.
|
| Verify scenario coverage | SHALL | Can verify that functionalities depicted in user scenarios are captured in the requirements list.
|
Spanish
These requirements apply to the actor Business Analyst
| Define functional requirements from L1 | SHALL | Can define functional requirements based on L1 recommendations in terms of health content, decision-support, and scheduling logic.
|
| Define non-functional requirements | SHALL | Can define non-functional requirements including user-friendliness and cybersecurity, informed by implementer best practices.
|
| Link requirements to personas | SHALL | Can link each functional requirement to the correct persona and business process activity.
|
| Verify scenario coverage | SHALL | Can verify that functionalities depicted in user scenarios are captured in the requirements list.
|