Skip to content

FEA03-Customer-Feedback-system 1.0
Feature ID FEA03
Subsystem the feature is part of e.g. billing
Responsible person Lauri Kosonen
Status e.g. approved

Description

Use-Case: * To gather feedback from end users and use that data to improve functionality of the service.

Technical Requirements: - The feedback feature should be integrated into the existing Skill Collector tool. - The feedback should be stored in a secure database that can be accessed by authorized personnel at JAMK university. - The feedback should be accessible through a user-friendly interface. - The feedback data should be exportable in a standard format (e.g. CSV) for analysis and reporting purposes. - Feedback should show application version.

Security Requirements: - Access to the feedback feature should be restricted to authorized personnel at JAMK university. - The feedback data should be protected from unauthorized access, modification, or deletion.

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.

All relevant issues related to or contributing to the definition of the feature are gathered here
Use Case 1
Use Case 2
Requirement ReqID
Requirement ReqID

Preliminary user stories

  • US108 As a service producer, I want to receive feedback from end users, based on which the product can be developed better (Issue #50)
  • US103 As a service producer, I want to help the end user through a separate support portal without burdening the development team with extra questions (Issue #45)
  • US104 As a service developer, I want to receive development feedback from the end user in the form of an Issue, because it is clearer to process further" (Issue #46)

Testing / possible acceptance criteria

Write down some notions for testing

Testcase Test source Responsible
Testcase 1 T003 Roope Lappalainen