Orion-re: A component-based software reengineering environment (original) (raw)

Component-Oriented Software Reengineering using Transformations

2002

This article presents a strategy of Component-Oriented Software Reengineering using Transformations, to rebuild legacy systems. Components are used to facilitate the reuse and maintenance of the rebuilt system. The strategy is a result of several researches

Re-Engineering for Reuse: Integrating Reuse Techniques into the Reengineering Process

1998

In this report, we present an overview of the existing software re-engineering process and its related concepts.We also classify existing software reuse techniques and we propose how to integrate such techniques into thesoftware re-engineering process by following a component-based approach. In addition, we demonstrate how ourmethodology can be applied on a client-server legacy system.Keywords: Re-engineering, Reverse Engineering, Reuse, Components, Software Engineering.1 Introduction...

Towards reuse reengineering of old software

Proceedings Fourth International Conference on Software Engineering and Knowledge Engineering, 1992

With reference to the setting up of reuse reengineering processes this paper describes the high level organizational paradigm adopted in the reuse reengineering project RE2. In particular the paper outlines: ( i ) the k e y role of reverse engineering in a reuse reengineering process: (ii) the need to &fine a module 'Template' in order to implement reusable modules in languages which do not have an ad hoc comtruct. Finally, with reference to TurboPmcal the paper describes the templa& adopted in RE2.

A Component-Based Software Engineering Environment

The Journal of Object Technology, 2004

Software Engineering Environments (SEEs) have been extensively studied, aiming to provide help in software development. Component-Based Software Engineering (CBSE) arises as an approach for constructing software through reusable components, reducing development costs and time, among other benefits. This paper identifies the main requirements for Component-Based Software Engineering Environments (CBSEEs), and presents Orion, a CBSEE which integrates different works from our research group, involving development tools, a repository, a process model and a middleware platform.

A Component-Based Framework for Software Reusability

Component-based development allows us to develop and integrate product components which facilitate software reusability, high quality and simplification for testing. Component-Based Software Engineering makes use of approaches which are based on architecture definition languages, object oriented design and software architecture. These strategies assist in the development of both domain-specific and generic software products. Reusability approach speeds up software development by using already developed components, thus software development cost and time is substantially reduced. I this paper, we present a Component-Based Software Engineering framework for software reusability

Creating Reusable Software Component from Object-Oriented Legacy System through Reverse Engineering

Journal of Object Technology, 2009

Due to the constant change in technology, lack of standardization, difficulties of changes and absence of distributed architecture, the business value of legacy systems have become weaker. We cannot undermine the importance of legacy systems because some of their functions are too valuable to be discarded and too expensive to reproduce. The software industry and researchers have recently paid more

Reengineering Techniques for Object Oriented Legacy Systems

Today’s software development is defined by continuous evolution of software products. These products are regularly updated during their usage. In most of the cases systems grow inevitably by adding new features or by changing the system architecture due to new technologies or business plans. It is more than a decade; objects oriented paradigm is adopted as the most efficient passage to build flexible software, and promptly supported by industry. Though, the benefits of object oriented paradigm are supported by many, but its usage does not necessarily result in general, adaptable systems. These huge systems are often suffering from improper use of object oriented techniques, like inheritance and the lack of object oriented methods being regulated towards the building of families of systems instead of developing single applications. These growing technologies make the systems more difficult to maintain and improve. So, there is growing demand for reengineering of object-based systems. The main intention of this paper is to discover important research directions in the area of reengineering of object oriented legacy systems, which necessitate further attention in order to build more effective and efficient reengineering technique for these systems. The paper first discusses the state of art in reengineering of legacy system and its need. Paper also discuss the benefits of component based system over object oriented system and later outlines the techniques for reengineering of object oriented legacy system. In this paper we presented statistical analysis based on more than a decade data.

Software Reengineering at the Architectural Level: Transformation of Legacy Systems

Bericht, Department of Computer Science, University of Leicester, UK, 2006

In this paper, we put forward a methodology for reengineering the architecture of a legacy software system. The proposed approach is not restricted to any specific source and target architectures, or programming language. It consists in (1) achieving a representation of the source code through its categorization and structuring,(2) transforming it into the new intended architecture, and (3) generating the code for the target platform. First, the code is categorized according to its purpose by pre-defined rules and represented as a model that ...

Software engineering with reusable components

1997

Software is rarely built completely from scratch. To a great extent, existing software documents source code, design documents, etc. are copied and adapted to t new requirements. Yet we are far from the goal of making reuse the standard approach to software development.

Object-Oriented Reengineering Patterns - An Overview

2005

Successful software systems must be prepared to evolve or they will die. Although object-oriented software systems are built to last, over time they degrade as much as any legacy software system. As a consequence, one must invest in reengineering efforts to keep further development costs down. Even though software systems and their business contexts may differ in countless ways, the techniques one uses to understand, analyze and transform these systems tend to be very similar. As a consequence, one may identify various reengineering patterns that capture best practice in reverse- and re-engineering object-oriented legacy systems. We present a brief outline of a large collection of these patterns that have been mined over several years of experience with object-oriented legacy systems, and we indicate how some of these patterns can be supported by appropriate tools.