Software Configuration Management Tools Research Articles

Improved Data Security in Cloud Environment for Test Automation Framework and Access Control for Industry 4.0

In analyzing project regressions, automation has emerged as a major agenda in managing changes in software which requires minimum manual intervention. For rapid testing environment, software development processes such as Agile, Scrum, and XP processes depend on continuous integration tools. There is no single tool to handle the project automation, and the main challenge is dependency on multiple tools. The proposed automation tool should support configuration, execution, and debugging facility. Integrating the project automation works such as software configuration management tools Mercurial and Git, job scheduling tools like Jenkins and Apache Continuum, test management tools like TestNG and Selenium need tight integration which is a challenge. The existing PKI infrastructure for access control does not share data among the software tools and processes increasing the complexity when an organization needs to leverage the existing cloud services. The proposed approach optimizes the execution time by taking single CSV with input test case and metadata information and efficiently group and executes the tests automatically. The proposed method includes implementation of security access control mechanism for the jobs execution platform in cloud environment.

S-SCMM: A Simplified Software Configuration Management Model for Software Services in Public University

Software Configuration Management (SCM) is a process that supports Software Development Life Cycle (SDLC), which benefits project management, development activities, maintenance activities, quality assurance activities, and the end users of the software product. However, findings from series of interviews have proven that SCM is difficult to operate and to be implemented by the practitioners in public universities specifically in Malaysia. Some of the SCM activities could be aided by using the SCM automated tools, however not all practitioners opted that due to inflexibility of the tools. Theoretical and empirical study have identified and revealed the current practices, success factors, essential elements, and components of SCM that were used frequently and beneficial among software practitioners. The empirical study also found that the main components of s-SCMM are process, SCM tool, and human. The s-SCMM was proposed and developed by considering the main components: process, tools, human, and success factors. The s-SCMM model was validated through expert review. As the result, a Simplified SCM Model (or s-SCMM) was proposed and developed to help the execution and implementation of SCM in public university environment. The s-SCMM model is simplified by focusing on change management, version control, system building, and release management. Therefore, s-SCMM will become a platform to assist total implementation of SCM in organization. By using this model, the preparation and usage of SCM artefacts could become more effective, efficient, and systematic.

A State of the Art: Software Configuration Management Tools for Global Software Development

Global Software Development (GSD) has emerged widely in today’s software development environment. The emergence of GSD has create difficulty to several technical areas such as Requirement Engineering, Validation and Verification; not to mention Software Configuration Management (SCM) practices. To date, many SCM tools has been proposed by the researchers to reduce the difficulties faced by GSD project developers when dealing with SCM practices. Therefore, there is a need to update on the current trend of SCM tools in GSD context in order to assist practitioners in selecting the best tools for their project. To perform the study, Systematic Mapping Studies (SMS) has been used to identify and provide an overview of the SCM tools which has been developed specifically for GSD environment. This paper contributes the following: 1) This paper synthesized the SCM tools in GSD and 2) Current trend of SCM tools in today’s software development environment also is identified.

Replication of empirical studies in software engineering research: a systematic mapping study

In this article, we present a systematic mapping study of replications in software engineering. The goal is to plot the landscape of current published replications of empirical studies in software engineering research. We applied the systematic review method to search and select published articles, and to extract and synthesize data from the selected articles that reported replications. Our search retrieved more than 16,000 articles, from which we selected 96 articles, reporting 133 replications performed between 1994 and 2010, of 72 original studies. Nearly 70 % of the replications were published after 2004 and 70 % of these studies were internal replications. The topics of software requirements, software construction, and software quality concentrated over 55 % of the replications, while software design, configuration management, and software tools and methods were the topics with the smallest number of replications. We conclude that the number of replications has grown in the last few years, but the absolute number of replications is still small, in particular considering the breadth of topics in software engineering. We still need incentives to perform external replications, better standards to report empirical studies and their replications, and collaborative research agendas that could speed up development and publication of replications.

웹 기반 로봇 소프트웨어 공학 도구 설계 및 구현

As the requirement of user for robot functionality, the function and interface for controlling the robot system is more sophisticated and complicated. Accordingly development process of robot is more complicated and it takes much longer time to develop a robot system. Software development using project management tool is more important in software engineering because of the complexity of software, especially robot system. This paper proposes SEED (Software Engineering Equipment for Development), which is a web-based and integrated software engineering tool to provide independent tools for robot software development. SEED includes the document management tool, the software configuration management tool, the software testing tool on developing robot software and provide a functionality of collaborated and remote development due to WEB-based operations.

Component-based software version management based on a Component-Interface Dependency Matrix

As much component-based software is developed, a software configuration management (SCM) tool for component-based software is necessary. In this paper, we propose a version management mechanism for impact analysis while components are upgraded. We separately version the components and interfaces based on a Component-Interface Dependency Matrix (CIDM), and analyze impacts according to their dependency relationship. The result of our simulation shows that CIDM is capable of managing large numbers of components without impedance mismatch. In addition, in a well-designed software system, using CIDM to analyze impacts can save resources in the software development phase.

Improving change management in software development: Integrating traceability and software configuration management

Software configuration management (SCM) and traceability are two prominent practices that support change management in software development. While SCM helps manage the evolution of software artifacts and their documentation, traceability helps manage knowledge about the process of the development of software artifacts. In this paper, we present the integration of traceability and SCM to help change management during the development and evolution of software artifacts. We developed a traceability model using a case study conducted in a software development organization. This model represents knowledge elements that are essential to comprehensively manage changes tracked within the change management function of SCM tools. A tool that supports the integrated practice of SCM and traceability is also presented. We illustrate the usefulness of our model and tool using a change management scenario that was drawn from our case study. We also present a qualitative study towards empirically evaluating the usefulness of our approach.

The wonderful world of wiki benefits students and instructors

In order to educate students on the software engineering process, the University of Alabama in Huntsville requires computer engineering students to work as a group on a mock project. Along with the final source code, the group is expected to turn in all relevant requirements, design, and test documents along with their revision histories, tracked by the method of our choice. Based on experience with past classes, we had found that managing a single report across a group without a master repository involves many different versions being moved around via e-mail messages, thumb drives, and project notebooks. Combining this disorganization with limited meeting time outside of class and the chances of easily completing this heavily documented project began to look slim. We needed a better solution. Our answer was a wiki combined with software configuration management (SCM) and source browsing tools. This article not only explains the advantages of using our solution but also shows how to set up our development platform from scratch.

Odyssey-SCM: An integrated software configuration management infrastructure for UML models

Model-driven development is becoming a reality. Different CASE tool vendors support this paradigm, allowing developers to define high-level models and helping to transform them into refined models or source code. However, current software configuration management tools use a file-based data model that is barely sufficient to manipulate source code. This file-based data model is not adequate to provide versioning capabilities for software modeling environments, which are strongly focused on analysis and architectural design artifacts. The existence of a versioned repository of high-level artifacts integrated with a customized change control process could help in the development and maintenance of such model-based systems. In this work, we introduce Odyssey-SCM, an integrated software configuration management infrastructure for UML models. This infrastructure is composed of a flexible version control system for fine-grained UML model elements, named Odyssey-VCS, and two complementary components: a customizable change control system tightly integrated with the version control system, and a traceability link detection tool that uses data mining to discover change traces among versioned UML model elements and provides the rationale of change traces, automatically collected from the integrated software configuration management infrastructure.

SubCM: a tool for improved visibility of software change in an industrial setting

Software configuration management is the discipline of managing large collections of software development artefacts from which software products are built. Software configuration management tools typically deal with artefacts at fine levels of granularity - such as individual source code files - and assist with coordination of changes to such artefacts. This paper describes a lightweight tool, designed to be used on top of a traditional file-based configuration management system. The add-on tool support enables users to flexibly define new hierarchical views of product structure, independent of the underlying artefact-repository structure. The tool extracts configuration and change data with respect to the user-defined hierarchy, leading to improved visibility of how individual subsystems have changed. The approach yields a range of new capabilities for build managers, and verification and validation teams. The paper includes a description of our experience using the tool in an organization that builds large embedded software systems.

An approach for managing the evolution of web-based educational applications

The management of the infrastructure and content of the World Wide Web is a growing problem for the development of web-based educational applications (WbEA) and is hidden beneath the tremendous benefits of the web. Moreover, such systems undergo more frequent and quite extensive changes in their development and operational period because the client's perception (either the learner, the teacher or institutional organisation) of the complete end product is a moving target. So, there is a need for a disciplined approach to managing the evolution of web-based educational applications. Such a disciplined approach as applied throughout the software engineering process is called software configuration management (SCM). This paper begins a discussion of how the development of web-based educational applications could benefit from SCM techniques and tools and proposes a model for the management of the evolution of such systems. The model couples the development and evolution process of WbEA configurations into one framework, which seems promising for the implementation of a configuration management process. Also, the model focuses on the development of the web-based educational content, defining the configurations of the items involved in the underlying process. Finally, an example is given to demonstrate the benefits of the use of this approach.

Managing the verification trajectory

In this paper we take a closer look at the automated analysis of designs, in particular of verification by model checking. Model checking tools are increasingly being used for the verification of real-life systems in an industrial context. In addition to ongoing research aimed at curbing the complexity of dealing with the inherent state space explosion problem - which allows us to apply these techniques to ever larger systems - attention must now also be paid to the methodology of model checking, to decide how to use these techniques to their best advantage. Model checking "in the large" causes a substantial proliferation of interrelated models and model checking sessions that must be carefully managed in order to control the overall verification process. We show that in order to do this well both notational and tool support are required. We discuss the use of software configuration management techniques and tools to manage and control the verification trajectory. We present Xspin/Project, an extension to Xspin, which automatically controls and manages the validation trajectory when using the model checker Spin.

Industrial Requirements for Distributed SCM Tool

As software development comes to be viewed more and more as an engineering discipline, Software Configuration Management is increasingly recognised as a key technology in the development of software. The Esprit VISCOUNT project^1 aim is to implement an innovative Software Configuration Management (SCM) tool to use in a geographically distributed software development environment, a Virtual Software Corporation (VSC). The features implemented by the tool will be the following: ·Configurable process modelling ·Inter-working capabilities with COTS SCM tools ·Selective replication of archives ·Open to include plug-in applications (security mechanism, encryption, etc) This paper is based on the work undertaken as part of the VISCOUNT project, partially funded by European Union's Esprit Programme, and it describes the SIA (Societa' Italiana Avionica) requirements defined in the framework of VISCOUNT.

Unified versioning through feature logic

Software configuration management (SCM) suffers from tight coupling between SCM version-ing models and the imposed SCM processes. In order to adapt SCM tools to SCM processes, rather than vice versa, we propose a unified versioning model, the version set model . Version sets denote versions, components, and configurations by feature terms , that is, Boolean terms over ( feature : value )-attributions. Through feature logic , we deduce consistency of abstract configurations as well as features of derived components and describe how features propagate in the SCM process; using feature implications , we integrate change-oriented and version-oriented SCM models. We have implemented the version set model in an SCM system called ICE, for Incremental Configuration Environment . ICE is based on a featured file system (FFS) , where version sets are accessed as virtual files and directories. Using the well-known C preprocessor (CPP) representation, users can view and edit multiple versions simultaneously, while only the differences between versions are stored. It turns out that all major SCM models can be realized and integrated efficiently on top of the FFS, demonstrating the flexible and unifying nature of the version set model.