362 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
Eren	b73327ea6c	Add acceptance tests ... Co-authored-by: Mathis Kral <mathis_tiberius.kral@mailbox.tu-dresden.de>	2023-10-29 18:12:48 +01:00
Denis Natusch	66ef4839e4	Add use-case diagram and general use-cases ... Co-authored-by: Mathis Kral <mathis_tiberius.kral@mailbox.tu-dresden.de>	2023-10-29 18:12:48 +01:00
Simon Bruder	c599e5d072	Add domain model ... Co-authored-by: Mathis Kral <mathis_tiberius.kral@mailbox.tu-dresden.de>	2023-10-29 18:12:48 +01:00
Simon Bruder	9b5bf07132	Add stakeholders ... Co-authored-by: Mathis Kral <mathis_tiberius.kral@mailbox.tu-dresden.de> Co-authored-by: Theo Reichert <theo.reichert@mailbox.tu-dresden.de>	2023-10-29 18:12:34 +01:00
Mathis Kral	36ded44703	Initial commit for scope statement ... Co-authored-by: Simon Bruder <simon.bruder@mailbox.tu-dresden.de>	2023-10-26 15:07:27 +02:00
Simon Bruder	0fe9446ad1	Use Git LFS	2023-10-26 15:06:50 +02:00
Simon Bruder	2c09a8c6fe	Add protocol from 2023-10-20	2023-10-25 17:31:23 +02:00
Simon Bruder	cfe6d65ed3	Use meeting time from protocol for time recording ... This makes it coherent with the protocol, which in the case of the first meeting noted a duration of only 60 minutes. The time tracking obviously should reflect that and not just always assume 90 minutes like I initially did.	2023-10-20 19:19:14 +02:00
Simon Bruder	175f5f106d	Use minutes for time recording ... This is required according to the first paragraph. This also documents in more detail how exactly the weeks are structured. The structuring is not the best way, but considering our team meeting is on Fridays, which especially made the first week start late, it is the best I could think of.	2023-10-20 18:15:28 +02:00
Simon Bruder	cdba75f002	Add time recording for week 1	2023-10-20 16:40:42 +02:00
Simon Bruder	d8b93f5ba4	Add protocol from 2023-10-13 ... Co-authored-by: snd <personal@e1ectron.de>	2023-10-15 12:09:40 +02:00
STlab bot	8a3ee868a9	Initial commit	2023-10-05 11:42:24 +02:00