Showing papers in "Journal of Systems and Software in 2014"

TL;DR: An advanced information centric platform for supporting the typical ICT services of a Smart City that can easily embrace all available and upcoming wireless technologies, while enforcing, at the same time, ubiquitous and secure applications in many domains.

TL;DR: This paper shows that there are differences in how the practice of continuous integration is interpreted and implemented from case to case and proposes a descriptive model for documenting and thereby better understanding implementations of the continuous integration practice and their differences.

TL;DR: This research work provides an overview of the state of the art and current techniques that, partially, attempt to face the many challenges of runtime variability mechanisms in the context of Dynamic Software Product Lines, and provides an integrated view of the challenges and solutions that are necessary to support runtime variability mechanism in DSPL models and software architectures.

TL;DR: A solution based on a semantically rich variability model to support the dynamic adaptation of service compositions and its possible configurations are verified at design time using Constraint Programming.

TL;DR: The obtained results support initial considerations about the trustworthiness of recent industrial surveys on agile method usage and suggest a number of recommendations for increasing the quality and value of future survey research in this regard.

TL;DR: This paper presents an automatic method for the verification of UML class diagrams extended with OCL constraints that works by translating the UML/OCL model into a Constraint Satisfaction Problem (CSP) that is evaluated using state-of-the-art constraint solvers to determine the correctness of the initial model.

TL;DR: Findings from a first comprehensive analysis of Open Source projects involving a fork show that Open Source software communities can outlive Open source software projects and that LibreOffice is perceived by its community as supportive, diversified, and independent.

TL;DR: An experimental study on a sufficient number of faulty versions and fault localization techniques shows the high applicability and effectiveness of the novel slice-based statistical fault localization approach to improve fault localization effectiveness.

TL;DR: The results of this SLR can help researchers to obtain an overview of existing web application testing approaches, fault models, tools, metrics and empirical evidence, and subsequently identify areas in the field that require more attention from the research community.

TL;DR: This study presents a secure Boolean-based secret image sharing scheme that uses arandom image generating function to generate a random image from secret images or shared images that efficiently increases the sharing capacity on free of sharing the random image.

TL;DR: This work aimed at systematically reviewing the literature on software architecture visualization to develop a classification of VTs in SA, analyze the level of reported evidence and the use of different VTs for representing SA in different application domains, and identify the gaps for future research in the area.

TL;DR: Overall it is found that models are used primarily as a communication and collaboration mechanism where there is a need to solve problems and/or get a joint understanding of the overall design in a group.

TL;DR: An integrated service engineering method is presented that supports co-existing tenant-specific configurations and that facilitates the development and management of customizable, multi-tenant SaaS applications, without compromising scalability.

TL;DR: There is a lack of conclusive evidence to substantiate the claimed usefulness of SPSM for any of the intended purposes and there is a paramount need for improvement in conducting and reporting simulation studies with an emphasis on evaluation against the intended purpose.

TL;DR: Empirical research methods for scaling up new requirements engineering (RE) technology validation, namely expert opinion, single-case mechanism experiments, technical action research and statistical difference-making experiments, and four kinds of methods for empirical RE technology validation are given.

TL;DR: A review of the research literature is provided and a classification of automated spreadsheet quality assurance approaches is developed, which range from spreadsheet visualization, static analysis and quality reports, over testing and support to model-based spreadsheet development.

TL;DR: A waste identification approach is constructed through which five communication wastes are identified, and solutions to mitigate them, which can help companies identify communication issues that are present in their development efforts.

TL;DR: A checklist for developers to review awareness in collaborative software and the obtained results suggest that the checklist is adequate to provide helpful hints that may be used to improve an application's awareness support.

TL;DR: Analysis of 333 questionnaires indicates that failed projects are associated with low team motivation, and finds unique groupings of team motivational factors for each of the countries investigated, indicating that there are cultural differences that project managers need to consider when working in a global environment.

TL;DR: This study suggests that mandatory pair programming may be less efficient in organizations where solo work could be done and when some interactions are for cooperative activities, and suggests that collaborative backup behavior, which occurred much less often, is close to the formal definition of pair programming.

TL;DR: A Mobile Cloud Middleware framework is developed, which addresses the issues of interoperability across multiple clouds, asynchronous delegation of mobile tasks and dynamic allocation of cloud infrastructure, and helps in maintaining soft-real time responses for mobile cloud applications.

TL;DR: This paper presents a system to create a conceptual model from functional specifications, written in natural language in an automated manner, and concludes with an evaluation of the usefulness of this approach for the requirements analysis.

TL;DR: The findings show that practitioners do not see maturity in agile software development as process definition or quantitative management capabilities, rather, agile maturity means fostering more subjective capabilities, such as collaboration, communication, commitment, care, sharing and self-organization.

TL;DR: This study presents findings on top publications, institutions, and scholars in the agile software development field from 2001 to 2012 based on the publication of such works in Science Citation Index journals.

TL;DR: This paper proposes a novel approach using a hybrid spectrum of full slices and execution slices to improve the effectiveness of fault localization and shows that this approach is more effective in fault localization than other compared approaches, and can reduce almost 2.98-31.79% of the average cost of examined code significantly.

TL;DR: An advanced approach, named SCOTCH+ (Source code and COncept based Test to Code traceability Hunter), to support the developer during the identification of links between unit tests and tested classes and indicates that the accuracy of the proposed approach far exceeds the leading techniques found in the literature.

TL;DR: A formal model of multi-step SPL configuration is presented and it is shown how solutions to these SPL configuration problems can be automatically derived with a constraint solver by mapping them to constraint satisfaction problems (CSPs).

TL;DR: This work proposes a trustworthy two-phase web service discovery mechanism based on QoS and collaborative filtering, which discovers and recommends the needed web services effectively for users in the distributed environment, and also solves the problem of services with incorrect QoS information.

TL;DR: A strategy for automatically fixing faults in a program by combining the ideas of mutation and fault localization, which reveals that a significant fraction of the (fixable) faults can be fixed by examining a small percentage of the program code.

TL;DR: This assessment characterizes the correctness and completeness of the analysis results produced by LINDDUN, as well as the productivity associated with executing the methodology, and looks into aspects such as the ease of use and reliability of LindDUN.