Howest
Howest
 

DocSpace at Howest  >
5. Industriële Wetenschappen en Technologie >
5.f Multimedia- en communicatietechnologie >
Multimedia- en communicatietechnologie >
NMCT 2016 >

Please use this identifier to cite or link to this item: http://hdl.handle.net/10046/1394

Title: How big is the impact of a framework change in a large scale application like Bynder
Authors: Hellemans, Jef
Issue Date: 2016
Publisher: Hogeschool West-Vlaanderen
Abstract: Frameworks and libraries are the backbone of any sort of development these days and we could not think of a world without them. But what are the differences between the two and why do we need them so much? I will start off by explaining how a modern web project works and what the different choices are that need some thought before any line of code is typed. All of these decisions are going to have a large impact on the rest of our work. My goal is to illustrate that those early steps are not to be taken lightly as not only the end users’ experience, but also a whole development team can either benefit or detriment from them. More specifically I will aim at the ease of use for a brand new developer who is just joining, seeing as this was my situation at the time of writing. We will focus on general attributes of the most popular frontend frameworks first and then move on to the topics of learning curve and mindset. For the purpose of keeping the content length of this thesis to a maximum I am going to zoom in on only two framework setups. One of them will be the Backbone and Marionette combo as this is the one used by the Bynder frontend team, and the other one is Angular that has my personal preference. From there we will analyse what the impact has been of changing the old codebase to implement the framework setup the frontend team is working with today. We will calculate the amount of code Bynder currently has, the complexity of the modules and the amount of migration that has already been done for each module. Afterwards, we are going to briefly analyse these numbers, take a look at the decisions that were made and also try to have a guess at what the future might possibly bring. Finally, we will come to a conclusion as to whether or not a change like this could be manageable in every application and if so, if it would be worth the time and effort. My goal is that this thesis can not only be a guideline for making a choice at the start of a new project, but also answer some questions when you feel like you have your back against the wall and need a change in your existing one. In a constantly evolving environment where there are multiple good options I aim to help make a smoother transition from one solution to the next, more future proof framework.
URI: http://hdl.handle.net/10046/1394
Appears in Collections:NMCT 2016

Files in This Item:

File Description SizeFormat
jefhellemans.pdf9672KbAdobe PDFView/Open

All items in DSpace are protected by copyright, with all rights reserved.

 

DSpace Software Copyright © 2002-2006 MIT and Hewlett-Packard - Feedback