Hello MEDEN friends and fans,

It’s time to sum up our past work.

GitHub repo:

Project Vision

Project Roles:


Use Cases:




Long-term planning:


This Blog:



To ensure good stability of our code we are using automated testing with unittests. We have formulated a test plan here and you can see the success of our builds and tests on our github page. The green build status tag hopefully indicates that our build is passing 🙂



Function Points

Hi folks,

today we want to show you the function point estimation of our UseCases.

Function points are used for estimating the time that will be spent on certain UCs.
They are calculated in reference on External Inputs, External Ouputs, External Inquiries, Internal Logic Files and External Interface File.

Description of these characteristics:

External Inputs:
How many Input Fields?

External Ouputs:
How many Outputs will be generated for the user to see?
–> number of reports generate, not the number of fields of data on each report

External Inquiries:
How many times the user has to interact with the program without entering any data in?
(buttons, menus or anything the user has to interact with without inputting data)

Internal Logic Files:
How many files that the software you plan to develop will have to access?
–> only includes any data files that your software will have to interact with
–> does not include header files, library files or any files that your compiler will need to compile your software

External Interface File:
How many other systems or software that your software will have to interface with?
(a piece of database software, a web-based server or any other object that your software will have to interface with)

Through Data Element Type, Record Element Type and File Type Reference we identified the complexity which can be LOW, AVERAGE or HIGH. In our UCs these parameters are always “LOW”, because of the simplicity of the UCs.
To estimate how long it will take to implement a Use Case in future, function points of UC that have been already implemented are put in relation to the time we spent on it.

For the calculation of our function points values we used the tool “Tiny Tools”.

For the calculation of FP with TINY TOOL you need to fill in some extra information about the whole application called “Complexity Adjustment Questions”.
This settings are valid for all the UCs and must only defined once.

To calculate the FP values, you have to fill in the “Domain Characteristic Table” for each of the several UCs.

Here you can find the whole table of our FP which contains our already existing UCs and the new UCs we want to implement within this semester:

Based on these data table we created a Function Point Diagram with a trendline. You can see that it fits together pretty good.

Stay tuned.

Regards TheMidnightExpress

Risk Management and new Usecases

Hey folks,

today we want to show you our process.

Here is our risk analysis:

We also have new usecases which are already implemented or will be implemented soon.

You can find all the usecases here:

Keep on rolling.

Greetings TheMidnightExpress

gantt diagram

Hello folks,

finally we have a gantt diagram for our project:

We know it is a little bit wrong and a little bit ugly but we switched vom ZenHub to YouTrack and created all issues again.
The problem is that the exported file from YouTrack doesn’t got the real date we manually modified. It is getting the creation date of the ticket.

That’s the reason why our diagram is not quite correct.


project management has changed

Hello fans of MEDEN,

in the past we had some troubles with ZenHub. It is a nice tool for simple issues and sprints but if you want to track you daily work time it is not really practicable, at least for us.

So we decided to change the tools and enter YouTrack. You can use it as a scrum board and it’s published by the same guys who are publishing IntelliJ.

What a conincidence! We program with IntelliJ.

We hope that now we will have more synergy effects.

Stay tuned for some nice burndown chats xD


architectural documentation

Hello guys,

our Software Architecture Document is proudly released.

It’s a first draft but we think that we checked all the important stuff.

You can see it here:

Some parts are still open because our website is not fully functional so we can’t determine size / performance and some quality issues.

Stay tuned.


class diagram

Hello folks,

a first draft of our class diagram is ready:


This diagram is made by our Software Architect Lorenz.

We know that it could be better but our project is not finished so we don’t know what other classes we need or will be generated.

Stay tuned.