UniTuebingen-BDVA/TeamprojektSoSe22

Minor Improvements

Opened this issue · 0 comments

s-t-h commented

Description

After the successful deployment of the product, the product owners noticed a number possible improvements for the teaching and gaming component, which should be solved in this user story. The single issues to work on are listed below. As many of the improvements affect both components, the single tasks of this user story may be distributed between the two teams.

Number of assignees: TBD | Estimated Workload: TBD

Acceptance

In order to count as resolved you should have fixed the following issues:

  • For RNA secondary structure representation it would be more appealing if different colors for the single base-types are used. [Marcel]
  • For the gaming component it would be more intuitive, if the currently selected base is highlighted in some way. [Nikolas]
  • The team may want to think of a better name than Serious Game for Nussinov. [Marcel]
  • The team may want to check all texts for grammar and spelling. [Sara]
  • Consider to use an appealing RNA secondary structure visualization on the landing page instead of a random structure (you may want to check ccsb.scripps.edu/illustrate). [Katja]
  • Consider to add a icon that links to the GitHub repository. [Marcel]
  • Consider to choose a license and list all sources of images, third party libraries, etc. in a legal notice panel on the web page (this is considered as Good Scientific Practice by the university). [Kevin]
  • For users it may be more appealing if the browser alert system is exchanged with another alert system, e.g. sweetalert2. [Katja]
  • Implement different difficulty levels for the game component.
  • Adjust tab name for gaming component. [Nikolas]
  • Adjust css file for gaming component or merge css file for both components. [Nikolas]
  • Find more efficient solution to compute all optimal solutions and integrate it into the existing end screen of the teaching component. [Fabian]
  • Fix gaming component end screen (display structures or find an appealing way to display score). [Nikolas]
  • Teaching: Explain wobble pairs and minimal loop size. [Sara]
  • Refactor code.
  • Implement helper for teaching component, i.e. highlight all possible options/cells. [Marcel]
  • Implement stepper for teaching component. [Katja]