All in one

Final Post. End of Transmission.

Use Cases:
General:

Register: 

Activate:

Add-Movie:

Edit-Settings:

Generate-Reccomendations: 

Like-Movie:

Movie-Details: 

Testing:

Test-Plan: 

Feature-Files: 

Auto-Complete-Proof (One of them): 

Unit-Tests: 

Code-Coverage: 

Stress-Test: See Test-Plan up top

Installation on other groups device/server: 

Projectmanagement

GANTT-Chart: 

JIRA-Scrum-Board: 

Function-Point-Estimaten Part 1: 
And calculated Function-Points on a graph where the axis are switchedd (Mea Culpa, Mea Maxima Culpa):

Complexity Adjustment Table:

Riskmanagement:

https://github.com/WowItsSoftwareEngineering/TINF15B4-LSMF/blob/master/docs/Risks/Risks.md

Architecture:

SAD: 

Codacy-Dashboard: 

How we use MVC: 

Class Diagram with Patterns: (Builder and Adapter Pattern)

Source and Binary:
Source is right here: 
Binary can be downloaded here: 

Deployment:

Travis:

Other Docs:

SRS: 

Midterm-Presentation: 

Final Presentation:

Blog as PDF: It’s… not pretty. But that’s what realistically can be done without spending 30 bucks on the right to install plugins on this “”great”” website.

Other things that might be of interest:
DB-Schema: 

Two Healthy JIRA Sprints:  <- Two Links

Fowler-Refactoring we did: <- Two links

Thank you for your time.

See You Space Cowboy..

P.S.:
Props to Razor1911, FAiRLiGHT, SKIDROW and my mother for buying me an Amiga 500 back in the day. That thing was dope.

Advertisements

Code Deodorant

ayyyyyy,

giphy

This week we started using code metrics. We are using codacy which automatically is triggered via a webhook when we commit on our repo, so it does not require Travis at all.

 

Example for a codesmell we fixed:

smell1

This makes sense cause the comparison could throw an exception when sortingOrder null is. To fix this we simply switched the literal with the variable.

Example for a codesmell we will not fix:

smell2

You simply can not delete this method since the OnScrollListener requires this method to be implemented.

When you wanna take a look at our metrics, just stare at the glorious codacy badge on our git repo https://github.com/WowItsSoftwareEngineering/TINF15B4-LSMF/

In our commit history you can see we already removed some of dem smells:

smell3

gReEtZ,

TiNf15B4lSmF

“Everything is design. Everything!”

 

designAt least that’s what Paul Rand said.design

Even adding gif-animations (Please don’t pronounce it as dschiff) is design.

Anyway.

Design Patterns. Android already uses a lot of them, so we’re going to talk about those.

First, how about the adapter pattern?
This design pattern allows an interface of an existing class to be used as another interface. In our case, this is to make our movies compatible with the list-view interface provided by android.

If you wonder what else there might be: we’re also using the builder pattern for a small work-around in our program to disable SSL-Checks (Was used when we did not have a valid cert, will be removed before production.) Can be found in the SSLTool class and its method.

The intent of the Builder design pattern is to separate the construction of a complex object from its representation. By doing so the same construction process can create different representations.

The two patterns are marked on the following diagram.

https://cduc.su/diagram2.png

 

Check the github if you want to see the code.

Buh-bye.

TambangDesignLogoAnimation2AwardWebDesignkoko_pebble_md_whtkoko_pebble_md_whtTambangDesignLogoAnimation2

Unit Testing

Hi Guys,

this week we prepared some amazing JUnit test.

Here is a screenshot from our gradle file, which should prove to you that we are using JUnit (Because the screenshot from a testresult may be faked of course).

Screenshot from 2017-05-03 08-56-45

Here is the Test-Screenshot:

Screenshot from 2017-05-03 09-02-34

Link to Test-Code (Click on the turtle): turtle1dancing

And this fellow link will lead you to our testing plan