User Story Management
Requirements in agile software development are often described based on “User Stories”. These are short stories which illustrate the use from the users perspective.
In this blog, we publish articles about current projects and topics regarding IT solutions and software development.
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.
Although Apache Shiro includes a powerful and flexible tool for fine-grained allocation of authorizations with its WildcardPermissions, one is faced with its limitations when it comes to complex scenarios. This article shows how any authorization checks can be implemented autonomously using the Permission interface.
In this article, I am going to report on the test framework Gauge from the ThoughtWorks corporation. This is a tool which I met for the first time when I was writing automated end-to-end tests (E2E) for various web applications within a web platform. The purpose of the tests is to progressively check whether certain functions such as single sign-out, appropriate redirection to other pages or access authorisations to certain elements of a selected web application function as they should.
Yeoman – „to boldly go where no man has gone before“ If a survey by Ashley Nolan is to be believed, Yeoman does not yet enjoy widespread use among web developers. Many have indeed already heard of it but almost 50 percent have not yet used it themselves. This really should change! That is why, in this article, I am going to address what this ominous Yeoman is all about, describe the advantages it brings with it and how one can ultimately pull an AngularJS application out of a hat.
People often talk about high quality software products, but what is that? How can you measure or compare the quality of an application? Let’s take a closer look at this topic and discuss what quality is all about and how it can be improved.
You are interested in making your own guest contribution?
Then please get in touch with us!