Ist die Reduktion von Quellcoderedundanz ein Motivator für die Evolution von Programmiersprachen? Das ist die Ausgangsfrage der Untersuchung, die exemplarisch an Sprachfeatures von Java 8 beleuchtet wird. Code Clones und Boilerplate Code werden als Formen von Quellcoderedundanz aufgefasst, beschrieben und definiert. Quellcoderedundanz wird als das Verhältnis der Komplexität des Ausdrucks und der durch diesen transportierte Information definiert und operationalisiert. Zur Messung der Änderung der Quellcoderedundanz durch Java 8 werden Codesegmente von Java 7 auf Java 8 migriert. Bei konstantem Informationsgehalt wird die Ausdruckskomplexität durch Maße der statischen Codeanalyse verglichen. Die Untersuchung zeigt für alle betrachteten Sprachfeatures eine Abnahme der Quellcoderedundanz, die aus einer Reduktion von Boilerplate Code oder dem Wegfall von Code Clones resultiert. Die Ergebnisse deuten darauf hin, dass die Reduktion von Quellcoderedundanz für die mit Java 8 in die Sprache eingeführten Neuerungen zumindest eine notwendige Eigenschaft ist. Um im Ökosystem der Programmiersprachen weiter bestehen zu können, müssen sich Sprachen weiterentwickeln, da ihr technologisches Umfeld stets im Wandel ist. Um seinen Nutzern die Möglichkeit zu geben, qualitativ hochwertigen Quellcode zu verfassen, müssen Sprachmittel zur Verfügung gestellt werden, die eine elegante Ausdrucksform komplexer Sachverhalte erlauben. Eine geringe Quellcoderedundanz kann also als Qualitätsmerkmal für Quellcode gelten und deren Ermöglichung als Evolutionsvorteil für Programmiersprachen angesehen werden.:1 Einleitung 2 Programmiersprachen und Quellcoderedundanz 2.1 Code Clones 2.2 Boilerplate Code 2.3 Quellcoderedundanz 3 Paradigmenwechsel mit Java 8 3.1 Streams API 3.2 Lambda-Ausdrücke 3.3 Die Klasse Optional<T> 3.4 default-Methoden in Interfaces 4 Schluss

Resultatet från utvärderingsintervjuerna pekar mot att Low-code leder till ett antal positiva effekter. Ökad effektivitet, minskat beroende av Angular-kompetens och minskad förekomst av tekniska fel är några. Resultatet indikerar även några utmaningar, såsom en försämrad flexibilitet i validering av input-fält och minskad anpassningsförmåga av komponenter och allmän funktionalitet.  Utilizing semi-structured interviews, some of the organization's requirements were identified. These requirements formed the basis for the development of a prototype and a few test cases. The prototype and the test cases were created in a beta version of a Low-code tool, WebRatio. They were then demonstrated and explained to stakeholders at Kronofogden that evaluated to what extent WebRatio in particular and Low-code in general can fulfill their requirements.    The results from the evaluation-interviews shows that Low-code leads to a number of positive effects. Increased efficiency, decreased dependence on Angular-competence and a decrease in the number of technical mistakes being made. However, the results also point to a number of negative effects, such as an impaired flexibility in validation of input-fields and a reduced adaptability in regard to the usage of components and general functionalities. / The digitalization of today’s society is ongoing at full speed, and the question is not if, but how it will be done. Low-code is an increasingly popular way of building software. Instead of writing code by hand, Low-code allows the user to utilize graphical user interfaces and ready-to-use components, with the intention to increase productivity in the area of software development. This case study whose context is Kronofogdemyndigheten has researched which effects Low-code has on a state-owned organizations software development.   Utilizing semi-structured interviews, some of the organization's requirements were identified. These requirements formed the basis for the development of a prototype and a few test cases. The prototype and the test cases were created in a beta version of a Low-code tool, WebRatio. They were then demonstrated and explained to stakeholders at Kronofogden that evaluated to what extent WebRatio in particular and Low-code in general can fulfill their requirements.    The results from the evaluation-interviews shows that Low-code leads to a number of positive effects. Increased efficiency, decreased dependence on Angular-competence and a decrease in the number of technical mistakes being made. However, the results also point to a number of negative effects, such as an impaired flexibility in validation of input-fields and a reduced adaptability in regard to the usage of components and general functionalities.

Cloud computing is a significant step forward in computer science. It enables customers to use applications on devices such as telephones, tablets, and computers over the internet. However, in the case of some applications, moving to the cloud can be challenging. Enterprise Resource Planning (ERP) is one example of such an application. ERPs need to be configurable since each company is different and has unique use cases. These configurations could be done by manipulating the logic and execution of programs by extending or modifying existing classes, basically writing customized plugins. The customer or the vendor could easily configure traditional offline single-tenant ERPs. Today, however, having this level of customization in a cloud-based multi-tenant ERP system is not an easy task. Since every customer shares the same application, though isolated from each other, changes made for one customer are made for every customer. Therefore, in this paper, we aim to find one or several answers to the question: how can you enable deep customization in multi-tenant SaaS systems in a secure way? A structured literature study is performed to analyze and investigate different solutions. The results gathered from the literature study showed that three solutions could be adapted: microservices, extensible programming, and static analysis tools. However, based on some requirements, extensible programming was found most suitable for the investigated ERP. / configurable, multitenant, SaaS, code,

This report is aim to compared building standard of Chengdu city and Stockholm, as well as find out the suitable energy-saving scenario for two places. To simulate the total energy consumption of logistics building, energy software named design builder will be introduce to calculate. Some of other analysis will be implemented at the same time, including economic analysis, environment analysis and thermal comfort analysis.

During the past years, several tools have been developed to try predicting wheel and rail wear of railway vehicles in an e-cient way. In this MSc thesis a new wear prediction tool developed by I.Persson is studied and compared with another wear prediction tool, developed by T.Jendel, which has been already validated and is in use since several years ago. The advantages that the new model gives are simpler structure, the consideration of wear as a continuous variable and that all the code is integrated in the same software. The two models have the same methodology until the part of the wear calculations and the post-processing. Wheel-rail geometry functions and time domain simulations are performed with the software GENSYS. In the simulation model the track and the vehicle are dened as well as other important properties such as vehicle speed and coe-cient of friction. Three simple tracks are used: tangent track, R=500 m curve with a cant of ht=0.15 m on the outer rail and R=1000 m curve with a cant of ht=0.1 m on the outer rail. The model is assumed to be symmetric so just outer (first and fourth axle) and inner (second and third axles) wheels are considered. During the vehicle-track interaction, the normal and tangential problems are solved. The wheel-rail contact is modelled according to Hertz's theory and Kalker's simplied theory with the help of the algorithm FASTSIM. Then wear calculations are performed according to Archard's wear law. It is applied in dierent ways, obtaining wear depth directly in Jendel's and wear volume rate in Persson's model. Jendel's model is rstly analyzed. Its specifc methodology is briefly explained and modications are performed on the code to make it work as similar as possible to Persson's model. Also parameters regarding the distance in which wear calculations are taken, the discretization of the width of the wheel and the discretization of the contact patch are analyzed. The methodology of Persson's model is also studied, most of all the performance of the post-processing which is one of the keys to the code. The parameters analyzed in this code are the ones regarding a statistical analysis performed during the post-processing and the discretization of the contact patch. Finally the comparisons between the wear depth obtained for both models are carried out. The discrepancies between the models are explained with the parameters analyzed and the dynamic behaviour of both models. Also a theoretical case is used as reference for comparison.

As time passes, more and more code is written, and as companies owna large quantity of code, the importance of readable and easy-to-understand codeincreases. It is well known that a developer's time is spent primarily on reading and understanding source code. This study aims to answer the questions: do students and professionals in software development agree on the current state-of-the-art of source code readability, what inhibits developers from writing code with high readability, and what activities they perceive to help them write code with high readability. In this context, readability is defined as the ease with which a person can read, understand, and comprehend source code, and the effort it takes to understand the logic, relations, cohesion, and ideas behind the code. A survey was distributed by email and social media to people working in the field. The respondents were asked to answer questions about readability and three self-evaluating questions about how they work with code. Responses were analyzed and compared to the state-of-the-art in readability of source code.  A literature study was performed to determine the current state-of-the-art of source code readability.The survey result showed considerable support for the findings of the literature review. The survey results also revealed that the most significant inhibitors for writing code with high readability are connected to lack of time, and the most recognized method of increasing readability is code reviews.

Software engineers need to anticipate unintended consequences, including negative impacts on society, individuals, and the environment. Even developers with the best of intentions can walk into ethical traps. This article includes four suggestions for software engineers during system development to help recognize these traps: (1) Look for humans values in technical decisions. (2) Identify stakeholdersgroups and individuals likely to be affected by the system. (3) Examine how the system will affect the stakeholders' rights and obligations. (4) Review relevant professional standards.

Code obfuscation is a software security technique where transformations are applied to source and/or machine code to make them more difficult to analyze and understand to deter reverse-engineering and tampering. However, in many commercial tools, such as Irdeto's Cloakware product, it is not clear why the end user should believe that the programs that come out the other end are still the same program"! In this thesis, we apply techniques of formal specification and verification, by using the Coq Proof Assistant and IMP (a simple imperative language within it), to formulate what it means for a program's semantics to be preserved by an obfuscating transformation, and give formal machine-checked proofs that these properties hold. We describe our work on opaque predicate and control flow flattening transformations. Along the way, we also employ Hoare logic as an alternative to state equivalence, as well as augment the IMP program with Switch statements. We also define a lower-level flowchart language to wrap around IMP for modelling certain flattening transformations, treating blocks of codes as objects in their own right. We then discuss related work in the literature on formal verification of data obfuscation and layout obfuscation transformations in IMP, and conclude by discussing CompCert, a formally verified C compiler in Coq, along with work that has been done on obfuscation there, and muse on the possibility of implementing formal methods in the next generation of real-world obfuscation tools.

The diploma thesis deals with the study of the process of grinding aggregates of particles of a mixture of powdered lanthanide oxides in the dowanol solvent. The formed dispersions were characterised and used for the preparation of printing inks and subsequently for the printing of labels with chemical codes readable by XRF spectrometry. The aim was to study the milling process, to verify the reliability of reading and recognition of marks with the appropriate codes and to monitor the influence of the additive of the up-conversion powder on the resulting relative intensities of the elements in the chemical code. The statistical significance of the differences in the averages of relative intensities was assessed based on the Student's t test.

No description available.