Feature Wiki
Schede
Improve Usability 360° Feedback Survey
Panoramica della pagina
[Nascondi]1 Initial Problem
The survey should allow capturing workplace-based performance appraisals over time. For example, upon completing the internship, students get a detailed feedback on their performance from their supervisors. The appraisal feedbacks serve as a bond between theory and practice and encourage the development of practical skills.
Both internal (ILIAS-Access) and external raters should be considered for appraisal feedback.
- Usability: Apraisees typically lack guidance to work with selecting raters
- Closing the survey: Apraisees must close the survey to view results, results are aggregated and names of the raters are not visible
2 Conceptual Summary
3 User Interface Modifications
3.1 List of Affected Views
3.2 User Interface Details
3.3 New User Interface Concepts
None.
4 Technical Information
Technical
Supporting multiple survey runs will require a major refactoring of a number of survey tables and classes. Code quality should be improved, e.g. Repository classes should be introduced.
Security
There are not any security implications.
Privacy
No additional privacy implications.
5 Contact
- Author of the Request: Tödt, Alexandra [atoedt];
- Maintainer: Killing, Alexander [alex]
- Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}
6 Funding
- …
7 Discussion
- When are raters able to fill in the survey again? Directly after they finished it? After the survey has been closed? After a time period?
- Why not simply add an option to allow multiple survey runs (Default is 1)?
- The add raters dialog would be changed for 360 surveys as well. Should the "Search Users" option be abandoned?
- When will competence entries be written exacly, if multiple runs are allowed?
- How will all the result screens change, if multiple runs are allowed?
, 10.11.2020: Thank You Alex for your reasonable questions. We have answered the questions by modifying this feature request.
8 Implementation
{The maintainer has to give a description of the final implementation and add screenshots if possible.}
Test Cases
- {Test case number linked to Testrail} : {test case title}
Approval
Approved at {date} by {user}.
Ultima modifica: 16. Feb 2021, 14:40, Non rivelato