Final Handin

Hey guys,

we officially finish our Software Engineering project GottMusIg with this blog post, but we haven’t finished working on it, so look out for more posts on this blog!

Our accumulated work over the 2 Semesters:


Software Requirements Specification

UC-1: DPS Difference

UC-2: Choose Character

UC-3: Show Character

UC-4: Update Database

UC-5: Update Character

Test Cases:

Project Management

Sprint 4 –> link








All blogposts at a glance

What Where
W1: Blog and Vision read
W2: Team/Roles/Technology read
W3: SRS read
W4: UC+Prototype read
W5: Scrum read
W6: Gherkin feature files read
W7: Class diagram read
W8: MVC Tool read
W9: MS Project Gantt read
W11: Midterm Presentation read
W2: Risk Plan/hours spent/new UC read
W3: FP read
W 4: Unit Testing read
W 5: Refactoring read
W 6: Pattern read
W 7: Metrics read
W 8: Test Coverage read
W 9: Deployment CI read
W10: Installation read




CI and Installation

Hey guys,
today we want to show you our continuous integration process. Our projects are build and tested by Jenkins every day and on every change in our master branch.


The generated metrics will be uploaded to Sonar . If there are failures in our tests the team will be notified by email, an issue on our GitHub repository will be opended automatically


and there won’t be a deployment to our artifact repository.

We have several projects and some depend on others. We created a maven repository on GitHub for the project which needs to be included as dependency in the other projects. If the build is successful the artifact will be deployed to our GitHub repository and every project gets the latest changes through the included dependency. So there’s no need to check the project manually out and build it local.

Team GottMusIg



we are now using Metrics to help us develop better software.

The first Metric tool we use is sonarcloud.

Sonarcloud is fully integrated in our Continuous Integration process, it is part of our deployment process on our Jenkins Server.

Sonar has shown us some issues which we tried to improve and are on our way to a reliable software.


Now we’re gonna take a look at a specific Problem SonarQube made us aware of:

When we used the string „class“ several times, sonar suggested to make an own field for this string to avoid many repetitions.


Also sonar warns us if the classes have too many parents:


But we could not fix this problem because of the frameworks we use.

We also use codacy as our second metric tool. It shows us our Code Style, Security, Unused Code and alot of other stuff.

Here is a picture of our Dashboard:




Software Pattern

Hey guys,

last week we looked at some common Software Patterns and how we can implement them into GottMusIg!

We decided to try out the dependency inversion pattern, which wants high-Level modules to depend on low-level modules and both should depend on abstractions.

The abstractions are seen in the picture below:





Other modules of our Software use the abstraction „Entity“ to get the information from the several implementations. So other parts of our software don’t even know that there is an implementation, all they have is the interace where they can interact with the Entity below.




Test Plan / Test Coverage

Hi guys,

this week we created a Test Plan for our project.

We use JUnit and Maven for automated testing.

We already wrote some Unit Tests for our database service as shown here, and added testing in our maven build process.

We are able to start the Unit test via our IDE and have an integrated Coverage tool as shown in the pictures below. (The coverage will go up soon, i promise 😉 ) .

Integrated Coverage Tool
Test successfully run in IDE

Our test dependencies are listed below.



Here the update for week 8 of our Software Engineering Project.

We use Coveralls and SonarQube in our automated test workflow within our Jenkins Server. As of now we have 21% test coverage on our database-service. We also added all the badges! Check them out at our Project repository.

More info on our testing Tools and workflow in our Test Plan



New Scope and Risk Management

Hey guys,

as promised we are continuing our work on GottMusIg.
We redefined our scope and came up with 5 new use cases we want to implement this semester. We are confident we will accomplish our (ambitious) goals to present you an awesome website.



We also came up with some risks that could endanger our project and how to mitigate them. Check it out!


More updates on GottMusIg coming next week!


GottMusIg is back from the Holidays

Hey guys,

we are back on track with our GottMusIg Project and are eager to make progress.

We won’t drastically change our technologies nor architecture, but we do have a little bit of refactoring  to do and we still have to implement a lot of features.

More info regarding our project will be blogged as always so stay tuned.



Midterm Handin


Software Requirements Specification


Software Architecture Document


Choose Character

DPS Difference

Feature Files

DPS Difference Feature

Choose Character Feature

Project Management


YouTrack (we will switch from Jira to YouTrack next Semester)

Gantt Chart

Gantt Chart


all our projects are on our GitHub community GottMusIg.

It’s worth mentioning that the GottMusIg project implements the DPS Calculation with SimulationCraft.

Presentation Slides