RUP: Defining roles

Hey Guys,

Today we want to talk about our team, Steven Kovacs and Marco Müller.
In a project it is important to be clear about everyones exercises and tasks next to coding.
Also in our project we want to define roles. We'll use IBM's RUP, a well-known system for business to give different roles to different members. For further information you can look at this site.

In a team with only two people it is really difficult to divorce between each role. But we tried to be as clear as possible, but some roles will be important for both of us. In the following picture you can see our team members and their roles in this project:

Next to our roles, we want to be clear about our technology. We already mentionted that we will use Tensorflow, an Open Source Software developed by researchers from the Google Brain Team. Our structure consists of two main parts (there will be much more parts, but for the explanation of our technology these both are the important ones):

The first part is our AI on a server, programmed in Python with Tensorflow. The other part is our "game", programmed in Java. This includes the game mechanics, the models and the graphical view. Also we want to use the following things:

• We will use the MVC pattern for our Java structure, not only because it keeps our code more organized, but also because structured code is important when using a server-structure.
•  Next to this, clean code is a realy important thing, so we will try to keep our code as simple and clean as possible. This means that we will use clean code patterns.
• One last thing to mention is that we want to develop our porgram test-driven. That means, that every single line of code we will write will be tested before we build our project. To guarantee the functionality of this we use JUnit in combination with Mockito, a Mocking-Framework.

It is a good question to ask why we try to follow these rules. Whoever programmed with clean code patterns and TDD (Test-Driven-Development) knows that it is sometimes really hard to resist the simple way of coding. But this simple way isn't in our opinion a good way. Structure and Overview lack when a project becomes to big and you haven't obey some standards.
Wer know that sometimes it will become really hard, but our goal is to to write good, clean code and resist every single temptation. That's the reason why we program our project this way!

Greets,
TheLearningTriangle-Team