Lukas-Hoernle
commented
2 years ago Dear Team DHBW-Experts, first of all I really enjoyed reading your blog-post. Just out of personal Interest I would be interested if you used draw.io for these diagrams? Regarding the first diagram I don't have much to complain about. Great work! 👍 However the constructor "User()" is there twice. Is there a reason you wrote it twice (once with parameters and once without)? Great idea to separate the getters and setters visually by the way 👍 The connecton "uses" isn't named that pretty. Maybe "validates" could be a more suitable name. I would also exchange the capitalized "N" in the connection between "Tag" and "TagValidation" with an "n". Regarding your data base scheme I was surprised to see how detailed you described the data base already. The scheme is structured and created in a way that makes it simple and clear what your intentions are. What does "Course-ABR" mean? What are you going to save into "Bio"? Is there information that can be split further or is the "bio" just one String? Best regards from team LectureFeed 🌵
07: Class Diagram and DB scheme - DHBW Experts
Hello everyone, this week we will present to you our class diagram, since we already got a db-scheme earlier. Anyway, you can still take a look at it again. Class Diagram We created a class diagram containing five classes with their attributes and methods. Also the data type is always given. While creating theses classes we tried to use our use cases as an orientation. However, the class diagram might change in the future, because we didn’t implement many classes yet. If you have any questions according the content or the structure, let us know! Data base scheme Our data base scheme was already shown in blog post 03. If you haven’t read it already, be sure to check this blog post in order t
https://dhbw-experts.github.io/blog/07/