Are We Ready for SDN? Implementation Challenges for Software-Defined Networks

Cloud services are exploding, and organizations are converging their data centers in order to take advantage of the predictability, continuity, and quality of service delivered by virtualization technologies. In parallel, energy-efficient and high-security networking is of increasing importance. Network operators, and service and product providers require a new network solution to efficiently tackle the increasing demands of this changing network landscape. Software-defined networking has emerged as an efficient network technology capable of supporting the dynamic nature of future network functions and intelligent applications while lowering operating costs through simplified hardware, software, and management. In this article, the question of how to achieve a successful carrier grade network with software-defined networking is raised. Specific focus is placed on the challenges of network performance, scalability, security, and interoperability with the proposal of potential solution directions.

An exploration of seniors’ motivation to use mobile brain-exercise software

This article reports on the development of an iPhone-based brain-exercise tool for seniors involving a series of focus groups (FGs) and field trials (FTs). Four FGs with 34 participants were conducted aimed at understanding the underlying motivational and de-motivational factors influencing seniors’ engagement with mobile brain-exercise software. As part of the FGs, participants had approximately 40 minutes hands-on experience with commercially available brain-exercise software. A content analysis was conducted on the data resulting in a ranking of 19 motivational factors, of which the top three were challenge, usefulness and familiarity and 15 de-motivational factors, of which the top-three were usability issues, poor communication and games that were too fast. Findings were used to inform the design of three prototype brain-exercise games for the iPhone contained within one overall application, named Brain jog. Subsequently, two FTs were conducted using Brain jog to investigate the part that time exposure has to play in shaping the factors influencing engagement. New factors arose with respect to the initial FGs including the motivational factor feedback and the de-motivational factor boring. The results of this research provide valuable guidelines for the design and evaluation of mobile brain-exercise software for seniors.

Towards optimal software engineering: learning from agile practice

In essence, optimal software engineering means creating the right product, through the right process, to the overall satisfaction of everyone involved. Adopting the agile approach to software development appears to have helped many companies make substantial progress towards that goal. The purpose of this paper is to clarify that contribution from comparative survey information gathered in 2010 and 2012. The surveys were undertaken in software development companies across Northern Ireland. The paper describes the design of the surveys and discusses optimality in relation to the results obtained. Both surveys aimed to achieve comprehensive coverage of a single region rather than rely on a voluntary sample. The main outcome from the work is a collection of insights into the nature and advantages of agile development, suggesting how further progress towards optimality might be achieved.

The Maturation of Agile Software Development Principles and Practice: Observations on Successive Industrial Studies in 2010 and 2012

The agile model of software development has been mainstream for several years, and is now in a phase where its principles and practices are maturing. The purpose of this paper is to describe the results of an industry survey aimed at understanding how maturation is progressing. The survey was taken across 40 software development companies in Northern Ireland at the beginning of 2012. The paper describes the design of the survey and examines maturity by comparing the results obtained in 2012 with those from a study of agile adoption in the same region in 2010. Both surveys aimed to achieve comprehensive coverage of a single area rather than rely on a voluntary sample. The main outcome from the work is a collection of ‘insights’ into the nature and practice of agile development, the main two of which are reported in this paper.

Software Patents and the Digital Environment

Software is patentable in Europe so long as there is sufficient ‘technical contribution’ under the decades-long interpretation of the European Patent Convention made by the Boards of Appeal of the European Patent Office. Despite the failure of the proposed Directive on Computer Implemented Inventions, opponents of software patents have failed to have any affect upon this technical contrivance. Yet, while national courts find the Boards of Appeal decisions persuasive, ‘technical contribution’ remains a difficult test for these various courts to apply. In this article I outline that the test is difficult to utilise in national litigation (it is an engineering approach, rather than a legal one) and suggest that as the Boards of Appeal become less important (and thus less persuasive) should the proposed Unified Patent Court come to fruition, the ‘technical contribution’ test is unlikely to last. This may again make the whole issue of what/whether/how software should be patentable open to debate, hopefully in a less aggressive environment than has existed to date.

Relational architecture description language for software families

Software Product-Line Engineering has emerged in recent years, as an important strategy for maximising reuse within the context of a family of related products. In current approaches to software product-lines, there is general agreement that the definition of a reference-architecture for the product-line is an important step in the software engineering process. In this paper we introduce ADLARS, a new form of architecture Description language that places emphasis on the capture of architectural relationships. ADLARS is designed for use within a product-line engineering process. The language supports both the definition of architectural structure, and of important architectural relationships. In particular it supports capture of the relationships between product features, component and task architectures, interfaces and parameter requirements.