Collaborative resolution of requirements mismatches when adopting open source components

[Context and motivation] There is considerable flexibility in requirements specifications (both functional and non-functional), as well as in the features of available OSS components. This allows a collaborative matching and negotiation process between stakeholders such as: customers, software contractors and OSS communities, regarding desired requirements versus available and thus reusable OSS components. [Problem] However, inconclusive research exists on such cooperative processes. Not much empirical data exists supporting the conduction of such research based on observation of industrial OSS adoption projects. This paper investigates how functional and non-functional requirement mismatches are handled in practice. [Results] We found two common approaches to handle functional mismatches. The main resolution approach is to get the components changed by the development team, OSS community or commercial vendor. The other resolution approach is to influence requirements, often by postponing requirements. Overall, non-functional requirements are satisfactorily achieved by using OSS components. Last but not least, we found that the customer involvement could enhance functional mismatch resolution while OSS community involvement could improve non-functional mismatch resolution. [Contribution] Our data suggests that the selecting components should be done iteratively with close collaboration with stakeholders. Improvement in requirement mismatch resolution to requirements could be achieved by careful consideration of mismatches size, requirements flexibility and components quality.Peer ReviewedPostprint (author's final draft

OSS integration issues and community support: an integrator perspective

The reuse and integration of Open Source Software (OSS) components provided by OSS communities is becoming an economical and strategic need for today’s organizations. The integration of OSS components provides many benefits, but also risks and challenges. One of the most important risks is the lack of effective and timely OSS community support for dealing with possible integration problems. For gaining an understanding of the common problems that organizations face when integrating OSS components, and the role played by OSS communities, we performed an exploratory study on 25 OSS integration projects from different European organizations. The results show that the main way of reducing integration problems was the use of OSS components from well-established communities; therefore very few integration problems were identified. In most of the cases these problems were successfully solved with the support from the OSS community and/or colleagues. In addition, contrary to the common belief that understanding code from someone else is a hard and undesirable task, some integrators consider OSS code even more understandable than their own code.Peer ReviewedPostprint (author's final draft

Semantically Resolving Type Mismatches in Scientific Workflows

Scientists are increasingly utilizing Grids to manage large data sets and execute scientific experiments on distributed resources. Scientific workflows are used as means for modeling and enacting scientific experiments. Windows Workflow Foundation (WF) is a major component of Microsoft’s .NET technology which offers lightweight support for long-running workflows. It provides a comfortable graphical and programmatic environment for the development of extended BPEL-style workflows. WF’s visual features ease the syntactic composition of Web services into scientific workflows but do nothing to assure that information passed between services has consistent semantic types or representations or that deviant flows, errors and compensations are handled meaningfully. In this paper we introduce SAWSDL-compliant annotations for WF and use them with a semantic reasoner to guarantee semantic type correctness in scientific workflows. Examples from bioinformatics are presented

System requirements-OSS components: matching and mismatch resolution practices – an empirical study

Developing systems by integrating Open Source Software (OSS) is increasingly gaining importance in the software industry. Although the literature claims that this approach highly impacts Requirements Engineering (RE) practices, there is a lack of empirical evidence to demonstrate this statement. To explore and understand problems and challenges of current system requirement–OSS component matching and mismatches resolution practices in software development projects that integrate one or more OSS components into their software products. Semi-structured in-depth interviews with 25 respondents that have performed RE activities in software development projects that integrate OSS components in 25 different software development companies in Spain, Norway, Sweden, and Denmark. The study uncovers 15 observations regarding system requirements-OSS components matching and mismatch resolution practices used in industrial projects that integrate OSS components. The assessed projects focused mainly on pre-release stages of software applications that integrate OSS components in an opportunistic way. The results also provide details of a set of previously unexplored scenarios when solving system requirement–OSS component mismatches; and clarify some challenges and related problems. For instance, although licensing issues and the potential changes in OSS components by their corresponding communities and/or changes in system requirements have been greatly discussed in the RE literature as problems for OSS component integration, they did not appear to be relevant in our assessed projects. Instead, practitioners highlighted the problem of getting suitable OSS component documentation/information.Peer ReviewedPostprint (author's final draft

Lessons learned from the financial crisis for financial stability and banking supervision

The financial crisis that began in 2007 has revealed a need for a new supervisory and regulatory approach aimed at strengthening the system and containing the risk of future financial and economic disruptions. Three ingredients are needed to ensure financial stability: robust analysis, better regulation, and international cooperation. First, financial stability analysis must be improved to take full account of the different sources of systemic risk. Data coverage of the balance sheets of both non-bank financial institutions and the non-financial sectors should be increased. Moreover, to address the problems raised by the interconnections among financial institutions more granular and timely information on their exposures is needed. There must be further integration of macro- and micro-information and an upgrading of financial stability models. The second ingredient is the design of robust regulatory measures. Under the auspices of the G20 and the Financial Stability Board, the Basel Committee on Banking Supervision recently put forward substantial proposals on capital and liquidity. They will result in more robust capital base, lower leverage, less cyclical capital rules and better control of liquidity risk. Finally, the third ingredient is strong international cooperation. Ensuring more effective exchanges of information among supervisors in different jurisdictions and successful common actions is key in preserving financial integration, while avoiding negative cross-border spill-overs. Better resolution regimes are part of the efforts to ensure that the crisis of one institution does not impair the ability of the financial markets to provide essential services to the economy.financial crisis, international cooperation, macroprudential analysis, procyclicality, prudential regulation, stress tests

Final report implementation of relational management

Construction teams and construction organisations have their own distinctive cultures. There also exists an infrastructure, both social and contractual, which ensures that these projects within which the teams operate are completed successfully. It is these issues which this research has addressed. The project was instigated by Queensland Department of Main Roads, Public Works and John Holland Group in order to address how they might better implement relationship management (RM) on their construction projects. The project was devised initially in order to facilitate a change in culture which would allow the project to be run in a relational manner and would lead to effective performance in terms of the KPIs that the organisations set for themselves, described as business better than usual. This report describes the project, its outcomes and deliverable and indicates the changes that were made to the project during the research process. Hence, the initial premise of the project and the problem to investigate was the implementation of relational contracting: • throughout a range of projects; • with a focus on client body staff. The additions that were made to the project, and documented in the variations to the project, included two major additional areas of study: • client management and stakeholder management; • a live case study of an alliancing project. The context within which the research was undertaken is important. The research was driven by main roads with their desire to improve their operations by focusing on the relationship between the major project participants (however, stakeholder and client organisation management became an obvious issue as the research progressed, hence the variations). The context was initially focussed on main roads, public works and John Holland group organisations but it became clear very quickly that this was in fact an industry-wide issue and not an issue specific solely to the project participants. Hence, the context within which this research took place can be described as below: The deliverables from the project are a toolkit for determining RM needs in an organisation, a monograph describing the practical implementation of RM and the outline for a RM CPD and Masters cours

An Ontology-based Collaborative Knowledge Management Network to Enhance the Reusability of Inter-organizational Knowledge

A number of knowledge management (KM) approaches based on individual organizational KM strategies and business requirements have been developed without taking system interoperation into consideration. In this paper, a collaborative inter-organizational KM network is proposed to allow various organizations to access and retrieve inter-organizational knowledge. While knowledge engineers can reuse the inter-organizational knowledge to create and evaluate its own organizational knowledge, general users benefit from the effectiveness and efficiency of searching for relevant inter-organizational knowledge within the networ

A state-of-the-art review on the integration of Building Information Modeling (BIM) and Geographic Information System (GIS)

The integration of Building Information Modeling (BIM) and Geographic Information System (GIS) has been identified as a promising but challenging topic to transform information towards the generation of knowledge and intelligence. Achievement of integrating these two concepts and enabling technologies will have a significant impact on solving problems in the civil, building and infrastructure sectors. However, since GIS and BIM were originally developed for different purposes, numerous challenges are being encountered for the integration. To better understand these two different domains, this paper reviews the development and dissimilarities of GIS and BIM, the existing integration methods, and investigates their potential in various applications. This study shows that the integration methods are developed for various reasons and aim to solve different problems. The parameters influencing the choice can be summarized and named as "EEEF" criteria: effectiveness, extensibility, effort, and flexibility. Compared with other methods, semantic web technologies provide a promising and generalized integration solution. However, the biggest challenges of this method are the large efforts required at early stage and the isolated development of ontologies within one particular domain. The isolation problem also applies to other methods. Therefore, openness is the key of the success of BIM and GIS integration

IRS-III: A broker-based approach to semantic Web services

A factor limiting the take up of Web services is that all tasks associated with the creation of an application, for example, finding, composing, and resolving mismatches between Web services have to be carried out by a software developer. Semantic Web services is a combination of semantic Web and Web service technologies that promise to alleviate these problems. In this paper we describe IRS-III, a framework for creating and executing semantic Web services, which takes a semantic broker based approach to mediating between service requesters and service providers. We describe the overall approach and the components of IRS-III from an ontological and architectural viewpoint. We then illustrate our approach through an application in the eGovernment domain