Write down (Non-) functional requirements

[fgardt]

In GitLab by @Slartibartfass2 on Nov 4, 2022, 13:14

As discussed write down requirements.

We can upload them into GitLab under https://gitlab.uni-ulm.de/se-anwendungsprojekt-22-23/smart-sensing-library-fuer-studienapps/-/requirements_management/requirements. Investigate if this is useful for our cause and if so check that the format complies.

To do:

• [x] determine non functional requirements → ask advisor for any requirements
• [x] upload the requirements to Gitlab (c. f. Documentation Repo)

[fgardt]

In GitLab by @Slartibartfass2 on Nov 4, 2022, 13:14

added to epic &3

[fgardt]

In GitLab by @Slartibartfass2 on Nov 4, 2022, 13:30

changed due date to November 08, 2022

[fgardt]

In GitLab by @Merseleo on Nov 7, 2022, 23:36

Investigation Report:

• needed format: csv file with all requirements, containing two columns: title and description
• requirements must be written down in a requirements document, but theoretically requirements represented in latex code could be exported to csv file (e. g. via python script) and uploaded
• usefulness:
  • don't think so, because you we still need to write them down in extra document (as excepted in old evaluation sheet) and don't have an advantage from having the requirements twice
  • requirements in gitlab don't have any use but only to be written down and visible for the developer / for creating issues
  • only (little) advantage: you can let them close by stakeholder, if they think that the product match the requirement, but only closable via ci script, which seems to be unnecessary complicated

[fgardt]

In GitLab by @Merseleo on Nov 8, 2022, 14:33

changed due date to November 10, 2022

[fgardt]

In GitLab by @Slartibartfass2 on Nov 11, 2022, 24:20

removed due date

[fgardt]

In GitLab by @Slartibartfass2 on Nov 11, 2022, 24:21

moved from smart-sensing-library#14

[fgardt]

In GitLab by @Slartibartfass2 on Nov 11, 2022, 24:49

marked this issue as blocking #6

[fgardt]

In GitLab by @Merseleo on Nov 25, 2022, 16:46

marked the checklist item upload the requirements to Gitlab (c. f. Documentation Repo) as completed

[fgardt]

In GitLab by @Merseleo on Nov 25, 2022, 16:47

created branch 1-write-down-functional-requirements to address this issue

[fgardt]

In GitLab by @Merseleo on Nov 25, 2022, 16:53

created branch docs/1-write-down-non-functional-requirements to address this issue

[fgardt]

In GitLab by @Merseleo on Nov 25, 2022, 16:57

added #16 as child task

[fgardt]

In GitLab by @Merseleo on Nov 25, 2022, 16:59

added #17 as child task

[fgardt]

In GitLab by @Merseleo on Jan 25, 2023, 15:32

mentioned in commit 6e129139c90bfe3943232ec486d0d07fc8d75220

[fgardt]

In GitLab by @mm1398 on Feb 14, 2023, 14:31

marked the checklist item determine non functional requirements → ask advisor for any requirements as completed