FEA03-Customer-Feedback-system 1.0
| Feature ID | FEA03 |
| Subsystem | UX |
| Responsible person | Niko Karvinen |
| Status | Ready for testing |
Description
System that can be used to collect feedback from the users of the service, implemented with doorbell.io. In Doorbell.io, it is possible to save feedback directly as issues, which makes the admin's work easier.
Technical Requirements
- The feedback feature should be integrated into the existing Skill Collector tool.
- The feedback feature should be integrated with the current Skill Collector GitLab repository.
- The feedback should be stored in a secure database that can be accessed by authorized personnel.
- The feedback should be accessible through a user-friendly interface.
Security Requirements
- Access to the feedback feature should be restricted to authorized personnel.
- The feedback data should be protected from unauthorized access, modification, or deletion.
Restrictions, requirements and use cases related to this feature
| Name | Description |
|---|---|
| Use Case 1 | To gather feedback from end users and use that data to improve functionality of the service. |
User Stories
- #81 - Change the account where the feedback goes to Overflow's account
End User UI
Admin interface
User Acceptance
- The feedback feature should meet the requirements and expectations of JAMK university personnel.
- The feedback feature should be tested and validated by JAMK university personnel before being released
Testing
| Test case | Test source | Responsible |
|---|---|---|
| TC-03-001 - Customer feedback | FEA03-Customer-Feedback-system 1.0 | Alena Galysheva |
Acceptance Criteria
| Acceptance Criteria | Notes |
|---|---|
| The feedback system should have an intuitive and user-friendly interface. | |
| It should be easy for users to submit feedback and navigate through the system. | |
| The interface should be responsive and work well on different devices and screen sizes. | Mobile support not needed |
| It should be possible to give feedback in text format. | |
| Users receive a confirmation of their feedback submission. | |
| Feedback can be transferred as an Issue to GitLab | |
| It should be reliable, ensuring that no feedback submissions are lost or corrupted. | |
| The system should have appropriate security measures to protect user data and prevent unauthorized access. |