In this blog, we publish articles about current projects and topics regarding IT solutions and software development.
In each project you face the same challenge again: creating a finished product that meets the requirements. In order to do this successfully, there are countless approaches and possibilities. A solution is the use of Redmine, an issue-tracking application that can be simply adapted to meet one’s own individual needs.
This article describes which key figures can be collected by a static analysis and how these can be interpreted. The main focus is on technical debt and complexity.
Security is a difficult topic to control for software projects, as is proven by the constant reports of data leaks in the media. For software developers, it is difficult to oversee the sort of influence that their daily work, which is not directly linked to security issues, has on the security of their applications.
Even though the time for Version 1.x from AngularJS is drawing to a close with the future release of Version 2, its use in combination with Style-Guide from John Papa is still very much worthwhile. In addition to the statement, that the support from AngularJS 1 is only then discontinued when the traffic on angular.io (Angular 2) exceeds that of angularjs.org (Angular 1),
Requirements in agile software development are often described based on “User Stories”. These are short stories which illustrate the use from the users perspective.
Welcome to the World of Statistics – Where Storks Deliver Babies Statistics are encountered in all areas of modern life, but what in fact is the field known as “statistics”? Wikipedia describes statistics this way: “Statistics is the study of methods for handling quantitative information.” In other words, statistics is essentially the clarification of facts based on extensive data sets. As such, statistics makes it easier to read important information for purposes such as making predictions about the future or aiding decision-making.
The first article in this series – “Version names with Maven: Creating the version name” –shows how during the build, and with Maven’s help, a version number, enriched with further information can be written into a manifest, properties or HTML file. Based on the first article, this second one describes how it can be read from within the application. This is helpful in many cases: You can immediately see which version is deployed on which stage, the version information can avoid misunderstandings in error reports, etc.
In many cases, it may be useful to be able to extract the current version number of an application: You can immediately see which version is deployed on which stage, the version information can avoid misunderstandings in error reports, etc.
During the last years it became common to use agile methods in software development. The most widespread ones are Scrum and Kanban. The 2013 “State of Agile” survey found that a vast majority of companies (~60%) uses Scrum or Scrum hybrids. The second place is held by Kanban and “Scrumban” with more than 10%. Compared to the survey from 2012, Kanban experienced the highest increase in usage. That is why we want to compare those two methodologies.
80% of lifetime costs goes to maintenance and hardly any software is maintained for its whole life by the original author. Therefore it is crucial that code is written in a comprehensible manner. Code conventions help to achieve this.
You are interested in making your own guest contribution?
Then please get in touch with us!
