Merge pull request #38 from sw20-tug/develop

Release 1.0.0

.gitignore

@@ -0,0 +1,113 @@
+# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio, WebStorm and Rider
+# Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839
+
+# User-specific stuff
+.idea/**/workspace.xml
+.idea/**/tasks.xml
+.idea/**/usage.statistics.xml
+.idea/**/dictionaries
+.idea/**/shelf
+
+# Generated files
+.idea/**/contentModel.xml
+
+# Sensitive or high-churn files
+.idea/**/dataSources/
+.idea/**/dataSources.ids
+.idea/**/dataSources.local.xml
+.idea/**/sqlDataSources.xml
+.idea/**/dynamic.xml
+.idea/**/uiDesigner.xml
+.idea/**/dbnavigator.xml
+
+# Gradle
+.idea/**/gradle.xml
+.idea/**/libraries
+
+# Gradle and Maven with auto-import
+# When using Gradle or Maven with auto-import, you should exclude module files,
+# since they will be recreated, and may cause churn.  Uncomment if using
+# auto-import.
+# .idea/artifacts
+# .idea/compiler.xml
+# .idea/jarRepositories.xml
+# .idea/modules.xml
+# .idea/*.iml
+# .idea/modules
+# *.iml
+# *.ipr
+
+# CMake
+cmake-build-*/
+
+# Mongo Explorer plugin
+.idea/**/mongoSettings.xml
+
+# File-based project format
+*.iws
+
+# IntelliJ
+out/
+
+# mpeltonen/sbt-idea plugin
+.idea_modules/
+
+# JIRA plugin
+atlassian-ide-plugin.xml
+
+# Cursive Clojure plugin
+.idea/replstate.xml
+
+# Crashlytics plugin (for Android Studio and IntelliJ)
+com_crashlytics_export_strings.xml
+crashlytics.properties
+crashlytics-build.properties
+fabric.properties
+
+# Editor-based Rest Client
+.idea/httpRequests
+
+# Android studio 3.1+ serialized cache file
+.idea/caches/build_file_checksums.ser
+
+## Import from Spring Initializr Web .gitignore
+
+HELP.md
+target/
+!.mvn/wrapper/maven-wrapper.jar
+!**/src/main/**
+!**/src/test/**
+
+### STS ###
+.apt_generated
+.classpath
+.factorypath
+.project
+.settings
+.springBeans
+.sts4-cache
+
+### IntelliJ IDEA ###
+.idea
+*.iws
+*.iml
+*.ipr
+
+### NetBeans ###
+/nbproject/private/
+/nbbuild/
+/dist/
+/nbdist/
+/.nb-gradle/
+build/
+
+### VS Code ###
+.vscode/
+
+
+# application.properties - depends on settings of the user etc.
+src/main/resources/application.properties
+
+
+# .DS_Store files
+.DS_Store

README.md

@@ -1,3 +1,259 @@
-# ASD: Morning 4
+# Protocol for Agile Meetings: Group ASD-Morning-4
+
+- - - -
+
+# Planning Meeting: Sprint 1
+
+### ASD: Morning 4 - Meeting #1
+
+* Date: 18.03.2020
+* Time: 08:00 - 10:30
+* Type of meeting: Planning, Setup Github Workflow, Label Issues/Sprints
+* Attendees: All
+* Tools used to conduct the meeting: WhatsApp, Slack and Teamspeak
+
+### Purpose
+*	Discussed the tools we’ll use for remote work.
+*	Discussed the technology to use for the project.
+*	Development environment setup for every colleague.
+*	Planning: Labeling and rating all issues and assigning issues for Sprint 1.
+
+### Meeting Protocol
+
+We decided to use the following software/tools:
+
+*	Teamspeak for Voice Calls 
+*	WhatsApp, Slack and Teamspeak chat for messaging
+*	Teamviewer for Pair Programming.
+*	Java Spring Boot with Thymeleaf, Hibernate and MySQL.
+
+### Commitment
+
+* Everyone did a test commit to ensure the workflow is guaranteed and working. 
+
+- - - -
+
+# Sprint 1 Work Progress Meeting 
+
+## ASD Morning 4 - Meeting #2
+
+* Date: 25.03.2020
+* Time: 08:00 - 09:00
+* Type of meeting: Planning
+* Attendees: All
+* Tools used to conduct the meeting: Slack and Teamspeak
+
+### Purpose
+
+*	Helping Teammates with the Framework.
+*	Setting up the Framework for every colleague who had issues.
+*	Creating the user stories and setting the goals for Issues.
+
+### Meeting protocol
+### Troubleshooting
+
+*	Solving common problem with SQL and Springboot.
+
+  * Setting as maven build after pulling.
+  * MySQL: Timezone-problem.
+
+Planning 
+
+*	Setting goals for Sprint 2
+
+  * Issues 003 - 007
+
+*	Organizing pair-programming Teams
+
+  * Teamviewer is used for this point
+
+*	Started implementing next issues
+*	Unit Tests.
+
+Clarification
+
+*	Discussion about Issues.
+
+  * How to rate issues accordingly?
+  * Which issues are related to one and another?
+
+*	Discussion about using branches per issues and git workflow.
+
+### Commitment
+
+* First Prototype implemented, issues closed: LANG_000, LANG_001, LANG_002	
+
+- - - -
+
+# Sprint 1 Review Meeting 
+
+## ASD Morning 4 - Meeting #3
+
+* Date: 01.04.2020
+* Time: 08:00 - 09:50
+* Type of meeting: Sprint Review, The Retrospective
+* Attendees: All
+* Tools used to conduct the meeting: Teamspeak, Teamviewer
+
+### Purpose
+* Asking Questions:
+
+  * What is TODO in next Sprint?
+  *	Are we in time?
+  *	What to Improve?
+
+* Recap of last Sprint
+*	Did the Group communicate enough? (especially given the circumstances of COVID)
+Meeting Protocol
+
+_@Issue 000_
+Development environment is working fine and we think we made a great choice with the technology (Spring Boot, Thymeleaf, Hibernate, Bootstrap, MySQL).
+
+_@Issue 001_
+Database is also running. We can start to implement next Issues (since we are ahead of time):
+
+* things that go well according to all members:
+
+  * all closed issues are working well
+  * Framework is perfect for our implementation
+
+* things to improve:
+
+  * focus more on branches
+  * focus more on the agile workflow
+  * pay attention to naming conventions in GitHub
+  * pay attention to the "coding standard"
+
+Also:
+
+*	code should be easy to read
+* use more comments on parts that are not obvious.
+
+_Agreed deadline for Sprint 2:  29.04.2020 11:00_
+
+Designated Pair Programming Groups:
+
+* Unit Testing      Hieß & Wartinger
+* LANG_003          Loitzenbauer & Ranftl
+* LANG_004          Prüll & Weinhandl
+* LANG_005          Beinhunder & Prüll
+* LANG_006          (open)
+* LANG_007          Felgitscher & Weinhandl
+
+### Commitment
+
+* Sprint 1 was released. 
+* Added LANG_004 implementation of Study Interface. 
+
+- - - -
+
+# Planning Meeting: Sprint 2 
+## ASD Morning 4 - Meeting #4
+
+Date: 22.04.2020
+Time: 08:00 - 11:00
+Type of meeting: Daily Meeting, Code Review
+Attendees: All
+Tools used to conduct the meeting: Slack and Teamspeak
+
+### Purpose
+
+*	Discussions Updates.
+*	How far are the Issues implemented?
+*	Does anyone need help?
+*	Starting to use Code reviews.
+*	Discussing Feedback
+
+### Meeting Protocol
+
+* The Pair programming worked out fine.
+* Issues are almost done.
+* No one needs help for now. 
+* Always Codereview asynchrone for pull requests. (Person not part of the Pair-Programming team)
+* Synchronous reviews are done with Pair-Programming.
+* After every Sprint, critical parts of the Code will be reviewed with the Once-In-A-While code review method.
+* Weinhandl did the first Once-In-A-While code review for the last sprint in retrospective.
+Taking Feedback from Tutors into account.
+More focus on agile events and practices!
+
+### Commitment
+
+* Added Junit and Mockito Tests.
+
+- - - -
+
+# Review Meeting: Sprint 2
+## ASD Morning 4 - Meeting #5
+
+* Review Meeting : Sprint 2 
+* ASD Morning 4 - Meeting #4
+* Date: 29.04.2020
+* Time: 11:30 - 12:00
+* Type of meeting: Review Meeting
+* Attendees: All
+* Tools used to conduct the meeting: Slack and Teamspeak
+
+
+###Purpose
+* Help wanted?
+* How far are the Issues implemented?
+* Are there critical bugs?
+* Ideas for better interaction.
+
+###Meeting Protocol
+* Only minor issues are present.
+* Most Issues are finished.
+* No bugs, we know of yet. 
+* One minor (size 5) Issue was not completed.
+* This gets bigger priority next Sprint
+* Interaction is not highest priority as of now.
+* Code Documentation needs to be updated!
+* Commitment
+* Closed all Issues that we worked on in Sprint 2
+
+
+
+
+
+
+
+
+
+- - - -
+
+# Planning Meeting: Sprint 3
+## ASD Morning 4 - Meeting #6
+
+* Date: 06.05.2020 
+* Time: 08:00 - 08:45
+* Type of meeting: Planning Game
+* Attendees: All
+* Tools used to conduct the meeting: Slack and Teamspeak
+
+###Purpose
+
+* Forming new Pair Programming Groups
+* Declare Issue size
+* distribute Issues
+* Assign Sprint
+* Planning ahead for future Sessions 
 
-This is the repository for the team *ASD: Morning 4*
+###Meeting Protocol
+
+* New Ping-Pong Groups are formed.
+  * Kristiana + Christoph
+  * Alex + Simon
+  * Jan + Andi
+  * Sophie + Carina
+* Issue sizes changed
+* Testing mode got High Priority duo to Issue 8 and 9
+* UnitTesting needs updates!
+
+###Commitment
+
+* Hotfix for ds store!
+
+* Updating some documentation!
+
+* Starting to code Issues.
+