Final Presentation

Hi there!

We, Niko, Lars and Avelina, are students at the cooperative university of Karlsruhe.

The semester is now over and here are our results of the project.

Requirements
UC	Overall Use Case Diagram Change Sever Address Choose room, workout or level Create a room Create an exercise Workout activity flow Workout license
SRS	Software Requierements Specification The Blogentry for SRS.
Test Cases	You can see our feature file in the use case documents. On Github: Feature files Add Licence to trainee Workout activity flow Workout license
Test Log Test Coverage	Feature files Add Licence to trainee Workout activity flow Workout license Test Coverage to the blogentry Test with enduser evaluation Test with enduser statistics
Test Plan	RUP Testplan
Functional Test	See feature files in the use case documents. On Github: Feature files Add Licence to trainee Workout activity flow Workout license
Unit Test and Test with enduser	Unit Tests Test with enduser: Test with enduser evaluation Test with enduser statistics Test with enduser survey
Project Management
RUP gantt chart (past) future long-term plan using FP estimation Hours/ team member Team roles	Gantt chart (past)  Function Points  Hours/ team member  RUP Role allocation
Jira / burndown	Jira Burndown: Sprint 2 Sprint 3
FP calculation	Function Points
Ability to Execute
Demo	Demo Download .apk on your smartphone and install it!
Code	Github  Installation
Quality
Architecture SAD document	Architecture to the blogentry  Software Architecture Document  Patterns
Configuration Management/ Environmental Setup	See in SRS part “3.5.2 Technologies”.
Metrics	Metrics
Risk Management	Risk Management
Automated Testing Automatic with deploy	RUP Testplan Automatic Deployment
Pattern	Patterns
Other:
Presentations	Midterm Presentation  Final Presentation
Blog entries	Project – App HW1 – Our Vision HW2 – Team roles and technologies HW3 – SRS and Use-Case-Diagram HW 4 – Use Case HW5 – Jira HW6 – Gherkin .feature HW 7 – ClassDiagram HW8 – Software Architecture HW9: MS Project SE_2_HW2: Risk Management, time estimation and new use cases SE_02_HW3: Function Point Estimation SE2_04_GC_Test SE2_05_GC_Refactoring SE2_06_GC_Pattern SE2_07_GC_Metrics SE2_08_GC_Testing2

Here you can find our blog as PDF with all comments.

And here you can find our all documents as a .zip.

Greetings

WhiteCode!!!

SE2_09_GC_ContinuousIntegration_Installation

Hi there,

today you can install our server and our application.

At first you can see the manual for the server:

Important Requirements:

• Operating system: Windows, Linux (Only with mono)
• Framework: .NET Framework 4.6 (Minimum)

1. Extract the Server.zip file somewhere on your server/computer

2. Check if the port 13001 is open for outside connections

3. Start tbfController.exe

4. Write “/start” without quotations to start the server

5. Finish

 

App Installation:

1. First you have to enable app installation from unknown origin in the settings.
2. Here you can download our .apk to install the app on Android.
3. Then you have to change the server address to your server in the settings of the app

 

I hope you have fun with the application and the server!!!

 

Greetings

WhiteCode

SE2_08_GC_Testing2

Hello Guys!

We did our test coverage with the internal testing function of Visual Studio. You can see our test coverage for our content manager here.

Our test document contains the necessary tests. You can find this here.

 

Have a nice day 🙂

SE2_07_GC_Metrics

Hello out there,
in this week we created the code metrics of our project by using the Sonar C# analyze.
The whole result before corrections you can find here in a excel table.

The first metric we want to show you is Cyclomatic Complexity.

For example in our Activity „ServerAnswer“ the calculated points were 5. As you can see in the picture we got three if statements and one else in a other if statement.

After using a switch case we could reduce the Cyclomatic Complexity. You see this correction in the following screen shot.

Our second metric we used is class clutches.

In the following screen shot we see the class LevelButton with 23 class clutches. Here is nothing to correct because the class is used that often in other classes to generate a level button.

All this information is now also in our Test Plan.
Kind Regards
Niko from WhiteCode

SE2_06_GC_Pattern

Hello Guys!

As you guys might know, we have three code projects. We will show you our server project, to prove you that we developed design patterns.

From the beginning on, we wanted a server application that is able to use MSSQL and MYSQL, so its more flexible for our costumer. So we decided to create a class interface that contains all necessary database functions for the given database (More Here)! At first, here is a small overview of our abstract formation:

Here you can see the functions in our DBInterface:

The next image shows an example usage in the MysqlDataManager, which extends from the DBInterface

And at least, that you get a whole overview of the class construct of our server application:

(Please note, that this image is older and do not contain the actual telegram functions or database interactions. Therefore its more compact for a better overview!)

 

Sincerely,

WhiteCode

SE2_05_GC_Refactoring

Hello,

here you can find our refactoring repositories

1. 4nd3r50n´s repository – Lars Pickelin
2. samslina´s repository – Avelina Ott
3. techniko27´s repository – Niko Scheuermann

We used the tips and tricks in this lecture to refactor the code properly and on point.

Sincerely,

4nd3r50n

SE2_04_GC_Test

This week we wrought our first unit test and begun to create a “master test plan” for test driven development.

Here you can find a draft Version of our master test plan, to get an overview.

In the following screen shot you can see our first unit test “addRoom”.

Our test code can be found here on Github.

Leave a comment
Kind regards
Niko from WhiteCode

SE_02_HW3: Function Point Estimation

Hey guys!

Today we want show you our function point estimations. Function points are used for estimating the time that will be spent on a certain Use Case. They are calculated in reference on External Inputs, Outputs, Inquiries as well as Internal and External Logical Files from the User’s view, thereby they do not depend on the used technology.

To estimate how long it will take to implement a Use Case, function points of UC that have been already implemented are put in relation to the time we spent on it.
We used the calculation for our function points from „TINY TOOL„.

This table shows our Use Cases with the time we needed to implement. The acronyms DET, RET and FTR mean Data Element Type, Record Element Type and File Type Reference. Through these we identified the complexity which can be low, average or high. The part „numbers of“ are the numbers for the measurement parameter of the TINY TOOL.

Here you can see our Complexity Adjustment Table:

Here you can see the Domain Characteristic Table for the Use Case “Choose Room, Workout or Level”:

Below you can see our Use Case:

• Change server address (Completed)
• Choose room, workout, level (New)
• Create a room (New)
• Create an exercise (New)
• Workout activity flow (Old)
• Workout license (Old)

At last you can see the FP calculation and time Estimation diagram:

We have two outliners. “Workout acivity flow” (the blue one on the top) and “Choose room, workout and level” (the right one). Reasons for the the first outliner is the prework, which was very heavy -> Setup network connection, get minor Xamarin problems fixed. The other use cases benefited from this use case. The last outliner is just the complexity of Xamarin, which results in large function points and hours to develop.

Greetings,

WhiteCode 🙂

SE_2_HW2: Risk Management, time estimation and new use cases

Hello folks,

we are back! In this week we did our risk management and use case estaminations!

You can find our risk management here!
You can find our new use case estaminations here!

Our new use cases are:

1. Create a room (Content Manager)
2. Create an exercise (Content Manager)
3. Choose Room/Workout/Level (App)

For a better overview, here you can find our overall UC diagram.

Take a look at it. Feel free to give us some feedback!

Greetings,

4ND3R50N

HW9: MS Project

Hey there,

here you can see our Gantt-Chart as pdf and mpp.

This is the first page of our Gantt-Chart:

Greetings

WhiteCode