mirrors/swt23w23
1
0
Fork 0
mirror of https://github.com/st-tu-dresden-praktikum/swt23w23 synced 2024-07-19 21:04:36 +02:00
Code Issues Packages Projects Releases Wiki Activity
172 commits 56 branches 0 tags 16 MiB
Commit graph

162 commits

Author SHA1 Message Date
Denis Natusch b57ba6687c
Replace “Rechnung” with ”Kostenabrechnung” 
This also affects the acceptance test referring to it.
 2023-10-29 18:15:01 +01:00
Denis Natusch feae26d9da
Add missing functional requirements to use cases 2023-10-29 18:15:01 +01:00
Denis Natusch 82db184184
Replace in the use cases the unregistered user 2023-10-29 18:15:01 +01:00
Denis Natusch e51cf3900f
Make only “Kunden” able to delete their account 2023-10-29 18:15:01 +01:00
Denis Natusch 02f9549df6
Add lifetime to all sequence diagrams 2023-10-29 18:15:01 +01:00
makr912e 9d43a52c49
Add “unauthentifizierter Nutzer” to glossary 2023-10-29 18:15:00 +01:00
Theo Reichert dec96f430e
Change functional dependency F00050 to match UC0501's demands 2023-10-29 18:14:59 +01:00
Denis Natusch 54e98c71fa
Add stereotypes to the use case diagram 2023-10-29 18:14:55 +01:00
erho557e c130482742
Add multiple gui-prototype pages 2023-10-29 18:14:55 +01:00
Denis Natusch 3fa0ff7166
Fix spelling in use case descriptions 2023-10-29 18:14:55 +01:00
Denis Natusch c9e334cb11
Add use case ids to the use case diagram 2023-10-29 18:14:55 +01:00
Denis Natusch f0ee9c7236
Turn use case id into link 
Co-authored-by: Simon Bruder <simon.bruder@mailbox.tu-dresden.de>
 2023-10-29 18:14:55 +01:00
Denis Natusch 504e23ea39
Add sequence diagrams to a few use cases 2023-10-29 18:14:55 +01:00
Denis Natusch 7b19290368
Make use case diagram compatible with new PlantUML 2023-10-29 18:14:55 +01:00
Eren ff62aaafa3
Update acceptance tests 
Co-authored-by: Simon Bruder <simon.bruder@mailbox.tu-dresden.de>
 2023-10-29 18:14:55 +01:00
Simon Bruder 8fa8ea270c
Reflect last meeting’s terminology in domain model 2023-10-29 18:14:54 +01:00
Theo Reichert f4de3bbe22
Improve functional requirements 2023-10-29 18:14:52 +01:00
Denis Natusch 4f41e2bc44
Update use case descriptions 
Co-authored-by: Simon Bruder <simon.bruder@mailbox.tu-dresden.de>
 2023-10-29 18:13:43 +01:00
Denis Natusch 0b32e96eb0
Update use case diagram 2023-10-29 18:13:43 +01:00
Mathis Kral 1ffe3c425f
Fix Login/Registration component in TLA 2023-10-29 18:13:43 +01:00
Mathis Kral ec21e7981a
Update TLA diagram and context diagram 2023-10-29 18:13:43 +01:00
Mathis Kral 1311f1574e
Add new entry in version table 2023-10-29 18:13:43 +01:00
Eren e75f92624e
Change wording of customer removal acceptance test 
Co-authored-by: Simon Bruder <simon.bruder@mailbox.tu-dresden.de>
 2023-10-29 18:13:43 +01:00
Eren 66bbe50dab
Remove acceptance tests 2023-10-29 18:13:43 +01:00
Erik Hohlfeld c9bcf15e4b
Add mockup for GUI prototype 2023-10-29 18:13:43 +01:00
Paul 43173317e9
Update product usage to match task description 
Co-authored-by: Simon Bruder <simon.bruder@mailbox.tu-dresden.de>
Co-authored-by: Mathis Kral <mathis_tiberius.kral@mailbox.tu-dresden.de>
 2023-10-29 18:13:42 +01:00
Paul ded588daab
Use consistent terminology in task description 
Co-authored-by: Simon Bruder <simon.bruder@mailbox.tu-dresden.de>
Co-authored-by: Mathis Kral <mathis_tiberius.kral@mailbox.tu-dresden.de>
 2023-10-29 18:13:42 +01:00
Eren c5be1422cd
Add acceptance tests for edge cases 
Co-authored-by: Simon Bruder <simon.bruder@mailbox.tu-dresden.de>
 2023-10-29 18:13:41 +01:00
Eren 8f54db4327
Add more acceptance tests 2023-10-29 18:13:41 +01:00
Eren 0be0c7fa9a
Translate acceptance tests 2023-10-29 18:13:41 +01:00
Mathis Kral b5eb83026e
Remove template of non-functional requirements 2023-10-29 18:13:41 +01:00
Mathis Kral d9ea093c09
Spell “Cateringservice” consistently 
Co-authored-by: Simon Bruder <simon.bruder@mailbox.tu-dresden.de>
 2023-10-29 18:13:41 +01:00
Theo Reichert 1b7c4e4ecd
Improve functional requirements 2023-10-29 18:13:40 +01:00
Denis Natusch 7a2fa4fea6
Update use case diagram 
The new version takes into account the agreements we made last Friday. However, now i am left with more questions then before - most of the are marked with TODO
 2023-10-29 18:13:37 +01:00
Denis Natusch 9c690183c5
Add “Nutzer” as actor to the use cases 
I added them as an actor, because I wasn’t able to find a nice way to
group certain use cases for the actors Administrator and Kunde.
 2023-10-29 18:13:35 +01:00
Denis Natusch 0123ead10e
Update actor descriptions 
The descriptions of the actors currently only consists of links to the
glossary, because I think any further information would be redundant.
 2023-10-29 18:13:35 +01:00
Denis Natusch 920d59dce7
Add a global reference to the glossary 2023-10-29 18:13:35 +01:00
Simon Bruder 7a8660c89f
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:13:15 +01:00
Denis Natusch f54781cd26
Update use case diagram and add its source code 
I also updated the path to the diagram in the pflichtenheft.
 2023-10-29 18:13:14 +01:00
Mathis Kral 067c1ad273
Update systemContext and topLevelArchitecture 2023-10-29 18:13:14 +01:00
Simon Bruder 57c30c501c
Update domain model to match last meeting’s result 
This also updates the glossary to refer to the domain model, if they
share a term, which is also what is done in videoshop.
 2023-10-29 18:13:14 +01:00
Simon Bruder ed975858a0
Make stakeholders match last meeting’s result 2023-10-29 18:13:13 +01:00
Mathis Kral b93d2d6ba2
Add company_name variable 2023-10-29 18:13:13 +01:00
Mathis Kral 89a30a5c0d
Add toc 2023-10-29 18:13:13 +01:00
Mathis Kral 376e5cff6b
Remove project_name 2023-10-29 18:13:13 +01:00
Mathis Kral 7ca9e923f4
Clarify automation scope in summary 
Co-authored-by: Simon Bruder <simon.bruder@mailbox.tu-dresden.de>
 2023-10-29 18:13:13 +01:00
Mathis Kral 8ec40ea4ca
Add glossary 
Co-authored-by: Erik Hohlfeld <erik.hohlfeld@mailbox.tu-dresden.de>
Co-authored-by: Simon Bruder <simon.bruder@mailbox.tu-dresden.de>
Co-authored-by: Theo Reichert <theo.reichert@mailbox.tu-dresden.de>
Co-authored-by: Paul <heimerp54@gmail.com>
Co-authored-by: Eren <erenasker1537@gmail.com>
Co-authored-by: Denis Natusch <denis.natusch@mailbox.tu-dresden.de>
 2023-10-29 18:13:07 +01:00
Erik Hohlfeld a1dac54060
Add GUI prototype 
Co-authored-by: Mathis Kral <mathis_tiberius.kral@mailbox.tu-dresden.de>
 2023-10-29 18:13:07 +01:00
Theo Reichert 79e7ac3ea4
Add functional requirements 
Co-authored-by: Mathis Kral <mathis_tiberius.kral@mailbox.tu-dresden.de>
 2023-10-29 18:13:05 +01:00
Paul 7caad7c7a0
Add product usage 
Co-authored-by: Mathis Kral <mathis_tiberius.kral@mailbox.tu-dresden.de>
 2023-10-29 18:12:49 +01:00
Mathis Kral d8b2cd26cc
Add task description 
Co-authored-by: Denis Natusch <denis.natusch@mailbox.tu-dresden.de>
 2023-10-29 18:12:48 +01:00
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 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