khairusyaidy / P7-1

0 stars 0 forks source link

2.3.4 Non-Functional Requirements Changes #28

Open khairusyaidy opened 1 year ago

khairusyaidy commented 1 year ago

Task title ID: Non-functional Requirement Changes

What is the task about? Please describe in detail. The task is to address and implement the non-functional requirements (NFRs) listed for the system. These NFRs are crucial for ensuring the overall quality, security, scalability, and usability of the system. They encompass various aspects such as multilingual support, security measures, scalability, accessibility, availability, user interface design, logging, and backup/recovery.

What are the goals of the task? Please describe in detail. To update the requirements in the system POV

Success or completion criteria. Please describe in detail.

Successful implementation of multilingual support with at least three languages supported. The system should handle a 50% increase in users and data load without performance degradation. All data should be encrypted using industry-standard encryption methods, and secure login methods like two-factor authentication should be in place. The system should be accessible and fully functional on common mobile devices and tablets, with responsive design. Achieve at least 99% uptime over a three-month period. Users should find the interface easy to use, with positive feedback in user testing. All changes made within the system should be accurately logged, and logs should be accessible to administrators. Implement regular automated backups with a recovery plan tested successfully.

Allocated time 1 day

Start date and end date of the issue/task Start Date: 28th October 2023 End Date: 28th October 2023

Who is the owner? The owner is the person in-charge of the task and the task should be created and maintained by the owner. Marhakim (mdmarhakim)

The status of the task. This is usually "To-Do" initially To-Do / In-Progress / Completed Completed

What is the Priority of the task? HIGH / MEDIUM / LOW HIGH