Implementing Software Product Research Articles

A functionally-oriented approach to digitalization of the activities of competence centers in the field of agricultural cooperation

The publication summarizes the experience of digitalization of the activities of the competence center in the field of agricultural cooperation. The concept of digitalization of the competence center in the field of agricultural cooperation has been formulated and practically implemented, including the use of heterogeneous software products, both author’s and third-party developers. Software products and their functions that will automate the main activities of the competence center in the field of agricultural cooperation are considered. The author’s software product developed for informational and analytical support of the activities of the competence center opened at the Moscow State University of Technology and Management named after K. G. Razumovsky, allows you to automate accounting functions and data mining functions. The main functions of the created and implemented software product are accounting of agricultural producers, established cooperatives and their participation in events organized by the competence center and other organizations, accounting of grantees cooperating with the competence center, implementation of cluster data analysis methods to identify potential members of an agricultural cooperative.

Automatic refactoring of delta-oriented SPLs to remove-free form and replace-free form

Delta-oriented programming (DOP) is a flexible transformational approach to implement software product lines (SPLs). In delta-oriented SPLs, variants are generated by applying operations contained in delta modules to a base program. These operations can add, remove or modify named elements in a program (e.g. classes, methods and fields in a Java program). This paper presents two notions of normal form for delta-oriented SPLs. Both normal forms do not contain the remove operation. Additionally, the second normal form enforces a limitation on the use of the method-modify operation. For each of the proposed normal forms an algorithm for refactoring a delta-oriented SPL into one that satisfies that normal form is described. The algorithms are formalized for a core calculus for delta-oriented SPLs of Java programs.

Fragment-oriented programming: a framework to design and implement software product line domain components

Software product lines facilitate the industrialization of software development. The main goal is to create a set of reusable software components for the rapid production of a software systems family. Many authors have proposed different approaches to design and implement the components of a product line. However, the construction and integration of these components continue to be a complex and time-consuming process. This paper introduces Fragment-oriented programming (FragOP), a framework to design and implement software product line domain components, and derive software products. FragOP is based on: (i) domain components, (ii) fragmentations points and (iii)fragments. FragOP was implemented in the VariaMos tool and using it we created a clothing stores software product line. We derivedfive different products, integrating automatically thousands of lines of code. On average, only three lines of code were manually modified;which provided preliminary evidence that using FragOP reduces manual intervention when integrating domain components.

Implementation of a standardized information management system into activity of scientific and technical library

An effective solution to the tasks of preserving and accessing electronic documentation requires software applications, namely an electronic archive within the information management system of the organization. The information management system is a digital object-control and management system, as well as facilitates the planning and control functions of the enterprise. The object of research is the information management system for the fund of the Scientific and Technical Library ONAFT. The main goal of this project is to create a single electronic resource, namely, an institutional repository for the conservation of scientific works, articles, media, patents, educational objects, annotations and dissertations that are freely available for both HIE employees and for the world the communityAt present, information technology plays a key role in the process of obtaining, storing and disseminating information and knowledge, and is one of the most important tools for strategic development of libraries.Modern software tools such as the IntelliJ IDEA Ultimate Edition development environment, the JavaEE specification, the Java programming language, the Spring framework, the Apache Maven and Apache Ant project assemblies, the Hibernate library, the PostgreSQL database management system, the query language, were used to create the software. SQL To play the institutional repository, the DSpace platform, which is an open source software, was usedThe result of the development is the information and control system for the library fund STL ONAFT, implemented for the purpose of free access to research related to the development of a specific subject area, for further use in the educational process of HIE. The implemented software product is based on the established list of requirements for the functional capabilities of the project. During the development of the information management system for the library fund, the tasks were completed.

Infrastructure support for software import substitution

The purpose of the research is to improve the efficiency of software import substitution processes. In the process of import substitution, we highlight two issues: the issue of retraining a huge number of employees of organizations where it is necessary to carry out import substitution (hundreds of thousands of software users) and the issue of the process of choosing domestic software to replace the imported one. There are a huge number of organizations in which it is necessary to replace foreign software with the Russian one; several hundred large organizations. The number of Russian software products, such as office software, in the registry exceeds 200 copies. Each time the choice involves both the purchase of small licenses, and the deployment and testing of specific software in its entirety, as well as its analysis by experts. This process takes a long time if it is implemented without technical support. The authors put forward a hypothesis that these two problems: choice and retraining – can be effectively solved by the author’s technology of advanced training and instrumental complex that supports this technology. The article analyzes the possibility of using this technology for retraining and examines the beneficial side effects in the form of assessing the quality of interfaces. The types of users in your organization are also analyzed. The authors conclude that the majority of users in the organization belong to the class of mass professional users. In this case, the quality of the interface is crucial when choosing a software product to use. Based on the concepts of mental models and view model proposed by Alan Cooper, the authors have developed a method of selection of the domestic software product. The procedure is based on quantitative indicators obtained by active situational familiarization/training of potential users with the help of a computer training program, which is an accurate (in the sense of Kripke) functional and interface model of the selected software. This procedure ensures the effectiveness of choice of the domestic software due to the introduction of intermediate infrastructure element in the form of the organization of instrumental and methodical support search processes. It is concluded that such an organization of process not only improves the efficiency of the import substitution process, but also makes it possible to make general proposals on the direction of work to improve the quality of the interface of the domestic software. Implementation and development of the proposed methodology, based on the technology of advanced training of mass professional users, in the form of the infrastructure part of the program of transition to the Russian software will provide: confidence in the possibilities of the Russian software to replace painlessly the used foreign products; simplification and acceleration of the process of implementation of the developed software, by reducing the time of user training and minimizing the time of distraction of developers; obtaining objective quantitative results of advanced functional and interface beta testing of the implemented software; obtaining an effective tool to support the implementation and quality assessment of the Russian software by collecting statistical data for the analysis of the implemented software product.

A Dynamic Tracing Model for Agile Software Product Lines Domain Engineering from Features to Structural Elements: An Approach Based on Dynamic Routing

Even if the benefit of implementing Software Product Lines is well established, adopting such a large system is still a complex choice to make: it is hard to implement, needs a good knowledge of market growth and a clear vision of the enterprise objectives for long term. Therefore, many companies remain unwilling to adopt such an approach, unless they gain flexibility and get guarantees. Flexibility can be achieved by adopting an Agile Software Product Line approach, to make sure changes are rapidly implemented and product adapted to market evolution. Guarantees can be acquired by tracing elements and the relations between them. However, tracing in Agile Software Product Line context still needs to gain maturity as it is costly and therefore rarely adopted. In this paper, we discuss the added value of traceability for Agile Software Product Lines, and present our tracing model inspired from dynamic network routing.

Refactoring Delta-Oriented Product Lines to achieve Monotonicity

Delta-oriented programming (DOP) is a flexible transformational approach to implement software product lines. In delta-oriented product lines, variants are generated by applying operations contained in delta modules to a (possibly empty) base program. These operations can add, remove or modify named elements in a program (e.g., classes, methods and fields in a Java program). This paper presents algorithms for refactoring a delta-oriented product line into monotonic form, i.e., either to contain add and modify operations only (monotonic increasing) or to contain remove and modify operations only (monotonic decreasing). Because of their simpler structure, monotonic delta-oriented product lines are easier to analyze. The algorithms are formalized by means of a core calculus for DOP of product lines of Java programs and their correctness and complexity are given.

A geoinformation system of “the hydrocomplexes of Ukraine” as an important part in supporting managerial decisions

Technogenic and environmental safety of hydrocomplexes is an important part in the system of national security, and making prompt managerial decisions in this area is an important factor of a sustainable development of Ukraine. However, the existing problem of subordination of different parts of a hydrocomplex complicates and even impedes a prompt assessment of the actual safety of the complex engineering facilities for future managerial decisions. The study was aimed at working out an effective, representative and easy-to-use geographic information system (GIS) of “The hydrocomplexes of Ukraine” based on the principles of a multicriteria complex assessment of the technogenic and environmental safety of hydrocomplexes of Ukraine as complex environmental, technogenic, geological, engineering, and technical systems. The test objects of the specified GIS comprised 18 major hydrocomplexes of Ukraine, for which we had researched and provided a large volume of data on various aspects of their operation. The designed structure of the GIS and the implemented software product thereof can be useful not only for managers and scientists dealing with the operation of hydraulic structures but also for the general public that may be concerned with environmental issues in the regions of Ukraine.

A novel model-based testing approach for software product lines

Model-based testing relies on a model of the system under test. FineFit is a framework for model-based testing of Java programs. In the FineFit approach, the model is expressed by a set of tables based on Parnas tables. A software product line is a family of programs (the products) with well-defined commonalities and variabilities that are developed by (re)using common artifacts. In this paper, we address the issue of using the FineFit approach to support the development of correct software product lines. We specify a software product line as a specification product line where each product is a FineFit specification of the corresponding software product. The main challenge is to concisely specify the software product line while retaining the readability of the specification of a single system. To address this, we used delta-oriented programming, a recently proposed flexible approach for implementing software product lines, and developed: (1) delta tables as a means to apply the delta-oriented programming idea to the specification of software product lines; and (2) DeltaFineFit as a novel model-based testing approach for software product lines.

Towards correct-by-construction product variants of a software product line: GFML, a formal language for feature modules

Software Product Line Engineering (SPLE) is a software engineering paradigm that focuses on reuse and variability. Although feature-oriented programming (FOP) can implement software product line efficiently, we still need a method to generate and prove correctness of all product variants more efficiently and automatically. In this context, we propose to manipulate feature modules which contain three kinds of artifacts: specification, code and correctness proof. We depict a methodology and a platform that help the user to automatically produce correct-by-construction product variants from the related feature modules. As a first step of this project, we begin by proposing a language, GFML, allowing the developer to write such feature modules. This language is designed so that the artifacts can be easily reused and composed. GFML files contain the different artifacts mentioned above.The idea is to compile them into FoCaLiZe, a language for specification, implementation and formal proof with some object-oriented flavor. In this paper, we define and illustrate this language. We also introduce a way to compose the feature modules on some examples.

A quantitative and qualitative assessment of aspectual feature modules for evolving software product lines

Feature-Oriented Programming (FOP) and Aspect-Oriented Programming (AOP) are programming techniques based on composition mechanisms, called refinements and aspects, respectively. These techniques are assumed to be good variability mechanisms for implementing Software Product Lines (SPLs). Aspectual Feature Modules (AFM) is an approach that combines advantages of feature modules and aspects to increase concern modularity. Some guidelines on how to integrate these techniques have been established in some studies, but these studies do not focus the analysis on how effectively AFM can preserve the modularity and stability facilitating SPL evolution. The main purpose of this paper is to investigate whether the simultaneous use of aspects and features through the AFM approach facilitates the evolution of SPLs. The quantitative data were collected from two SPLs developed using four different variability mechanisms: (1) feature modules, aspects and aspects refinements of AFM, (2) aspects of aspect-oriented programming (AOP), (3) feature modules of feature-oriented programming (FOP), and (4) conditional compilation (CC) with object-oriented programming. Metrics for change propagation and modularity were calculated and the results support the benefits of the AFM option in a context where the product line has been evolved with addition or modification of crosscutting concerns. However a drawback of this approach is that refactoring components' design requires a higher degree of modifications to the SPL structure.

On the use of feature-oriented programming for evolving software product lines — A comparative study

Feature-oriented programming (FOP) is a programming technique based on composition mechanisms, called refinements. It is often assumed that feature-oriented programming is more suitable than other variability mechanisms for implementing Software Product Lines (SPLs). However, there is no empirical evidence to support this claim. In fact, recent research work found out that some composition mechanisms might degenerate the SPL modularity and stability. However, there is no study investigating these properties focusing on the FOP composition mechanisms. This paper presents quantitative and qualitative analysis of how feature modularity and change propagation behave in the context of two evolving SPLs, namely WebStore and MobileMedia. Quantitative data have been collected from the SPLs developed in three different variability mechanisms: FOP refinements, conditional compilation, and object-oriented design patterns. Our results suggest that FOP requires few changes in source code and a balanced number of added modules, providing better support than other techniques for non-intrusive insertions. Therefore, it adheres closer to the Open–Closed principle. Additionally, FOP seems to be more effective tackling modularity degeneration, by avoiding feature tangling and scattering in source code, than conditional compilation and design patterns. These results are based not only on the variability mechanism itself, but also on careful SPL design. However, the aforementioned results are weaker when the design needs to cope with crosscutting and fine-grained features.

Knowledge in Value Creation Process for Increasing Competitive Advantage

The aim of this paper is to compare companies by using value creation model and to determine knowledge in these processes. The framework for the value creation process shows problems of case companies in different phases of this process. Knowledge is compared in each of the individual phases of the process and its role in different types of companies. There is identified role of knowledge for increasing competitive advantage. The methodology involves case study from which data are derived and analyzed. The analysis shows that the framework for the value creation process can be used as an analytical tool for value overview in different phases and there is a need for different approaches to improve business and create new value for customers. Based on the analyzed problems, proposed recommendations for improvement are made. These recommendations are based on providing value innovation for customers (end users of software product). Value innovation of software product is considered as crucial for improvement of the companies in machinery industry. Company A has created new value through remote service. This remote service provides several advantages. Customers can prevent problems in machines by implementing software product which is still analyzing and evaluating data from machines. Company B and C were not able to create major value innovation for several years.

Compositional type checking of delta-oriented software product lines

Delta-oriented programming is a compositional approach to flexibly implementing software product lines. A product line is represented by a code base and a product line declaration. The code base consists of a set of delta modules specifying modifications to object-oriented programs. A particular product in a delta-oriented product line is generated by applying the modifications contained in the suitable delta modules to the empty program. The product-line declaration provides the connection of the delta modules with the product features. This separation increases the reusability of delta modules. In this paper, we provide a foundation for compositional type checking of delta-oriented product lines of Java programs by presenting a minimal core calculus for delta-oriented programming. The calculus is equipped with a constraint-based type system that allows analyzing each delta module in isolation, such that the results of the analysis can be reused. By relying only on the analysis results for the delta modules and on the product line declaration, it is possible to establish whether all the products of the product line are well typed according to the fragment of the Java type system modeled by the calculus.

A formal foundation for dynamic delta-oriented software product lines

Delta-oriented programming (DOP) is a flexible approach for implementing software product lines (SPLs). DOP SPLs are implemented by a code base (a set of delta modules encapsulating changes to object-oriented programs) and a product line declaration (providing the connection of the delta modules with the product features). In this paper, we extend DOP by the capability to switch the implemented product configuration at runtime and present a formal foundation for dynamic DOP. A dynamic DOP SPL is a DOP SPL with a dynamic reconfiguration graph that specifies how to switch between different feature configurations. Dynamic DOP supports (unanticipated) software evolution such that at runtime, the product line declaration, the code base and the dynamic reconfiguration graph can be changed in any (unanticipated) way that preserves the currently running product. The type system of our dynamic DOP core calculus ensures that the dynamic reconfigurations lead to type safe products and do not cause runtime type errors.

Virtual Separation of Concerns: Toward Preprocessors 2.0

Abstract Conditional compilation with preprocessors like cpp is a simple but effective means to implement variability. By annotating code fragments with #ifdef and #endif directives, different program variants with or without these fragments can be created, which can be used (among others) to implement software product lines. Although, preprocessors are frequently used in practice, they are often criticized for their negative effect on code quality and maintainability. We show how simple tool support — views, visualizations, disciplined annotations, and variability-aware type systems — can address these problems and emulate some benefits of modularized implementations. Instead of separating source code into files, we pursue a “virtual separation of concerns”.

Code Generation with the Exemplar Flexibilization Language

Code Generation is an increasing popular technique for implementing Software Product Lines that produces code from abstract specifications written in Domain Specific Languages (DSLs). This paper proposes to take advantage of the similitude among the products in a domain to generate them by analogy. That is, instead of synthesizing the final code from scratch or transforming the DSL specifications, the final products are obtained by adapting a previously developed domain product. The paper also discusses the capabilities and limitations of several currently available tools and languages to implement this kind of generators and introduce a new language to overcome the limitations.

Virtual Separation of Concerns - A Second Chance for Preprocessors.

Conditional compilation with preprocessors like cpp is a simple but eective means to implement variability. By annotating code fragments with #ifdef and #endif directives, dierent program variants with or without these fragments can be created, which can be used (among others) to implement software product lines. Although, preprocessors are frequently used in practice, they are often criticized for their negative eect on code quality and maintainability. In contrast to modularized implementations, for example using components or aspects, preprocessors neglect separation of concerns, are prone to introduce subtle errors, can entirely obfuscate the source code, and limit reuse. Our aim is to rehabilitate the preprocessor by showing how simple tool support can address these problems and emulate some benets of modularized implementations. At the same time we emphasize unique benets of preprocessors, like simplicity and language independence. Although we do not have a denitive answer on how to implement variability, we want highlight opportunities to improve preprocessors and encourage research toward novel preprocessor-based approaches.

GESTIÓN DE INCONSISTENCIA EN ENTORNO MULTIPERSPECTIVA PARA EL DESARROLLO DE SOFTWARE

The development of software systems inevitably involves the detection and handling of inconsistencies. These inconsistencies can arise in system requirements, design specifications and, quite often, in the descriptions that form the final implemented software product. A large proportion of software engineering research has been devoted to consistency maintenance, or geared towards eradicating inconsistencies as soon as they are detected. Software practitioners, on the other hand, live with inconsistency as a matter of course. Depending on the nature of an inconsistency, its causes and its impact, they sometimes choose to tolerate its presence, rather than resolve it immediately, if at all. This paper presents the state of art in inconsistency handling.

Generating text search applications for databases

To develop reusable domain-based assets, the author shows how to connect a domain analysis tool's output to a program generator and then to a domain implementation's input. The generator he built using Java, XML, and Oracle tools can produce code for JSP, PL/SQL, and PSP. This domain engineering research project demonstrated that it is possible to successfully implement software product lines in industrial environments using existing tools.