Agile programming – Introduction and current legal challenges

Within the realms of software development, customers must specify the requirements of their new software before the start of the project. Today, this leads to considerable delays with respect to the start of the project. In addition, the integration of new requirements into a system already developed in parts is becoming increasingly time-consuming and cost-intensive. Yet the specifically necessitated functions of a software are often only revealed through the process of development. By means of agile programming, changes in the requirements of a software product can be handled flexibly in shorter development cycles. In the following, the framework of agile software development projects as it applies under German law is described and current legal problems of such projects – in particular, the issue of contract type and the new building contract law – are considered. The unplanned project design appears contrary to the legal approach. The article shows, however, that agile software products development provides customers with dynamic and quickly scalable products and that customers can leave the project after individual project steps. The new development of building contract law, which focuses on subunits and approvals, is also very much in line with the above-mentioned programming.     

Ending the War with Al Qaeda

As long as we conceive of the fight with al Qaeda as a war, the fight will remain unwinnable and the goal of effective destruction will remain beyond our reach, according to the author. Historically speaking, modern wars require negotiated conclusions or the complete eradication of present and future threats. The former is politically impossible and the latter is historically unachievable.     

The state of the art in privacy impact assessment

There is growing interest in Europe in privacy impact assessment (PIA). The UK introduced the first PIA methodology in Europe in 2007, and Ireland followed in 2010. PIAs provide a way to detect potential privacy problems, take precautions and build tailored safeguards before, not after, the organisation makes heavy investments in the development of a new technology, service or product. This paper presents some findings from the Privacy Impact Assessment Framework (PIAF) project and, in particular, the project's first deliverable, which analyses the similarities and differences between PIA methodologies in Australia, Canada, Hong Kong, Ireland, New Zealand, the United Kingdom and the United States, with a view to picking out the best elements which could be used in constructing an optimised PIA methodology for Europe. The project, which began in January 2011, is being undertaken for the European Commission's Directorate General Justice. The first deliverable was completed in September. The paper provides some background on privacy impact assessment, identifies some of its benefits and discusses elements that can be used in construction of a state-of-the-art PIA methodology.