The paper describes the need for and goals of tool-integration within software development processes. In particular we focus on agile software development but are not limited to. The integration of tools and data between the different domains of the process is essential for an efficient, effective and customized software development. We describe what the next steps in the pursuit of integration are and how major goals can be achieved. Beyond theoretical and architectural considerations we describe the prototypical implementation of an open platform approach. The paper introduces platform apps and a functionality store as general concepts to make apps and their functionalities available to the community. We describe the implementation of the approach and how it can be practically utilized. The description is based on one major use case and further steps are motivated by various other examples.
Arguing for the need of continuing with advancing integration technologies, Seligman @cite_1 determine that existing tools --although already advanced-- are still too costly and labor intensive to build. Their solution is presented in form of a platform. The platform consists of a (vendor) model-independent repository, containing model schemas and a mapping of integrated tools, data importing and exporting components and integration tools using the eclipse platform and its plug-in mechanism. Considering the architecture of Seligman , a platform feature for easy and dynamic usage of integrated functionalities and data is still missing.
@cite_1
160775773 2082624068 1983841261 2171262729
Globally distributed development of complex systems relies on the use of sophisticated development tools but today the tools provide only limited possibilities for integration into seamless tool chains. If development tools could be integrated, development data could be exchanged and tracing across remotely located tools would be possible and would increase the efficiency of globally distributed development. We use a domain specific modeling language to describe tool chains as models on a high level of abstraction. We use model-driven technology to synthesize the implementation of a service-oriented wrapper for each development tool based on OSLC (Open Services for Lifecyle Collaboration) and the orchestration of the services exposed by development tools. The wrapper exposes both tool data and functionality as web services, enabling platform independent tool integration. The orchestration allows us to discover remote tools via their service wrapper, integrate them and check the correctness of the orchestration. Designing and testing distributed applications is still a difficult task that requires in-depth knowledge about networking issues. Eclipse is, among other things, a powerful and widely used IDE for the development of complex applications, in particular modular applications for the OSGi framework. Our R-OSGi middleware supports the seamless distribution of OSGi applications along the boundaries of services. By combining R-OSGi with Eclipse into the R-OSGi Deployment Tool, we give developers a tool that automatically handles distribution in a transparent way and integrates the capabilities of R-OSGi into the Eclipse workflow. With this tool, building, deploying, and monitoring distributed applications is as easy as writing OSGi applications in Eclipse and using a graphical editor to visually create distributed deployments of the modules. The tool can also be used to great effect by researchers to test and benchmark distributed applications and for education purposes. Abstract The need for integrating business and technical information systems, allowing partners to collaborate effectively in creating innovative products, has motivated the design and deployment of a novel integration framework for product lifecycle management. The time is ripe for such an integration framework because of the convergence of three important developments, almost in a perfect storm: (1) maturity of standardized product data and meta-data models, and standardized engineering and business processes; (2) emergence of service-oriented architecture for information sharing; and (3) availability of robust middleware to implement them. These developments allow engineering and business objects and processes to be built or composed as modular pieces of software in the form of services that can communicate with each other and be used across different parts of a business. These modular software pieces can be reused and reconfigured in new ways as business conditions change, thereby saving time and money for companies. This paper describes the business and technical aspects of an integration framework for product lifecycle management using open standards and service-oriented architecture. Data integration systems offer a uniform interface to a set of data sources. Despite recent progress, setting up and maintaining a data integration application still requires significant upfront effort of creating a mediated schema and semantic mappings from the data sources to the mediated schema. Many application contexts involving multiple data sources (e.g., the web, personal information management, enterprise intranets) do not require full integration in order to provide useful services, motivating a pay-as-you-go approach to integration. With that approach, a system starts with very few (or inaccurate) semantic mappings and these mappings are improved over time as deemed necessary. This paper describes the first completely self-configuring data integration system. The goal of our work is to investigate how advanced of a starting point we can provide a pay-as-you-go system. Our system is based on the new concept of a probabilistic mediated schema that is automatically created from the data sources. We automatically create probabilistic schema mappings between the sources and the mediated schema. We describe experiments in multiple domains, including 50-800 data sources, and show that our system is able to produce high-quality answers with no human intervention.