Modularizing and Specifying Protocols among Threads

We identify three problems with current techniques for implementing protocols among threads, which complicate and impair the scalability of multicore software development: implementing synchronization, implementing coordination, and modularizing protocols. To mend these deficiencies, we argue for the use of domain-specific languages (DSL) based on existing models of concurrency. To demonstrate the feasibility of this proposal, we explain how to use the model of concurrency Reo as a high-level protocol DSL, which offers appropriate abstractions and a natural separation of protocols and computations. We describe a Reo-to-Java compiler and illustrate its use through examples.Comment: In Proceedings PLACES 2012, arXiv:1302.579

Feature modeling: An extended perspective to design IT infrastructure

Feature modeling is a widely used method in systems engineering. Feature models help to communicate the requirements and architecture of IT systems. Applying feature models to IT infrastructure is a rare explored field in system development. We advocate using feature modeling for designing IT infrastructure to give an additional perspective on systems architecture and implement functions and properties of IT infrastructure. In this research-inprogress paper we present the idea of combining feature modeling and IT infrastructures and propose an exemplified feature model in context of IT infrastructure and its corresponding research questions. The discussion leads to functional and non-functional-requirements, feature-oriented description of architecture, and scope of IT infrastructure

CONFIGEN: A tool for managing configuration options

This paper introduces CONFIGEN, a tool that helps modularizing software. CONFIGEN allows the developer to select a set of elementary components for his software through an interactive interface. Configuration files for use by C/assembly code and Makefiles are then automatically generated, and we successfully used it as a helper tool for complex system software refactoring. CONFIGEN is based on propositional logic, and its implementation faces hard theoretical problems.Comment: In Proceedings LoCoCo 2010, arXiv:1007.083

A Model-Driven Engineering Approach for ROS using Ontological Semantics

This paper presents a novel ontology-driven software engineering approach for the development of industrial robotics control software. It introduces the ReApp architecture that synthesizes model-driven engineering with semantic technologies to facilitate the development and reuse of ROS-based components and applications. In ReApp, we show how different ontological classification systems for hardware, software, and capabilities help developers in discovering suitable software components for their tasks and in applying them correctly. The proposed model-driven tooling enables developers to work at higher abstraction levels and fosters automatic code generation. It is underpinned by ontologies to minimize discontinuities in the development workflow, with an integrated development environment presenting a seamless interface to the user. First results show the viability and synergy of the selected approach when searching for or developing software with reuse in mind.Comment: Presented at DSLRob 2015 (arXiv:1601.00877), Stefan Zander, Georg Heppner, Georg Neugschwandtner, Ramez Awad, Marc Essinger and Nadia Ahmed: A Model-Driven Engineering Approach for ROS using Ontological Semantic

Next generation software environments : principles, problems, and research directions

The past decade has seen a burgeoning of research and development in software environments. Conferences have been devoted to the topic of practical environments, journal papers produced, and commercial systems sold. Given all the activity, one might expect a great deal of consensus on issues, approaches, and techniques. This is not the case, however. Indeed, the term "environment" is still used in a variety of conflicting ways. Nevertheless substantial progress has been made and we are at least nearing consensus on many critical issues.The purpose of this paper is to characterize environments, describe several important principles that have emerged in the last decade or so, note current open problems, and describe some approaches to these problems, with particular emphasis on the activities of one large-scale research program, the Arcadia project. Consideration is also given to two related topics: empirical evaluation and technology transition. That is, how can environments and their constituents be evaluated, and how can new developments be moved effectively into the production sector

Adopting Architectural Event Modules for Modular Coordination of Multiple Applications

Nowadays, large-scale software systems consist of multiple applications, which interact with each other to fulfill desired system-level requirements. It is usually required to coordinate the interactions of the constituent applications to ensure that the system-level requirements are fulfilled. In this paper, we outline a set of requirements that must be fulfilled to facilitate the modular composition of multiple applications. We introduce the concept of architectural event modules, which are abstractions to represent constituent applications and their coordination logic in a modular and uniform way. We explain the implementation of this concept in the EventReactor language, and define their formal semantics in processing events using the UPPAAL toolset. We illustrate the suitability of architectural event modules in achieving modularity and loose coupling in the composition of multiple applications by means of a case study in the domain of energy-efficient computing

A Study on Platform's New Strategy in Media 2.0 Era - Based on “Keystone” concept & Google case

The purpose of this paper is to suggest a new strategy of the platform in Media 2.0 era. This goal is approached by firstly examining conceptual change of the platform strategy from mass media world (Media 1.0) to micro media world (Media 2.0). Then, it will discuss "Keystone" strategy by Iansiti & Levien (2004) who introduced four different types of platform and will give an example, Google. The data shows, how Google's keystone strategy could be successfully accomplished with three sources for value creation, revelation, aggregation and plasticity, and how healthy it is in terms of productivity, robustness, and niche creation. Finally, an applicable framework to Media 2.0 will be constructed on the basis sources for value creation and "Keystone" capabilities of ecosystem management. Three main parts of the keystone strategy are the openness, synchronization, and mass customization focus. --Media platform,Keystone,ecosystem