Technical Report
Component-Oriented Redesign of the CASE-Tool AutFocus
Author(s): Klaus Bergner, Franz Huber, Andreas Rausch, Marc Sihling
Year: 1997
Number: TUM-I9752
Editor:
CR Classification: D.1.3, D.1.5, D.1.7, D.2.1, D.2.2, D.2.5, D.2.6, D.2.7, D.2.9, D.2.10, D.2.m
CR General Terms: Design, Documentation, Management
Keywords: Componentware, Object-Oriented Software Engineering, Design, Redesign, Java, CASE, Repository
Abstract:In this paper, we explore how the componentware paradigm can be used to
re-engineer
existing software systems. As a case study, we use the prototype
implementation of
the CASE tool AutoFocus which has been developed using
standard object-oriented
design techniques. Although designed for re-usability
with respectto certain criteria,
AutoFocus did not use a component-based
approach yet. The case study concentrates on
the repository subsystem, as this
part is currently the least modular part of AutoFocus.
We outline essential
concepts of the componentware paradigm, including
a methodology how to carry
out a component-based design process,
introduce the current state of
AutoFocus, and sketch how we derive
a component-based redesign, including a
migration strategy from
purely object-oriented legacy systems to
component-based systems.
Available as compressed Postscript
BibTeX-Entry:
<![CDATA[
@techreport{TUM-I9752,
author = {Klaus Bergner and Franz Huber and Andreas Rausch and Marc Sihling},
title = {Component-Oriented Redesign of the CASE-Tool AutFocus},
number = {TUM-I9752},
institution = {Technische Univerit\"at M\"unchen},
year = {1997},
url = {http://www4.informatik.tu-muenchen.de/reports/TUM-I9752.html},
abstract = {In this paper, we explore how the componentware paradigm can be used to
re-engineer
existing software systems. As a case study, we use the prototype
implementation of
the CASE tool AutoFocus which has been developed using
standard object-oriented
design techniques. Although designed for re-usability
with respectto certain criteria,
AutoFocus did not use a component-based
approach yet. The case study concentrates on
the repository subsystem, as this
part is currently the least modular part of AutoFocus.
We outline essential
concepts of the componentware paradigm, including
a methodology how to carry
out a component-based design process,
introduce the current state of
AutoFocus, and sketch how we derive
a component-based redesign, including a
migration strategy from
purely object-oriented legacy systems to
component-based systems.},
CRClassification = {D.1.3, D.1.5, D.1.7, D.2.1, D.2.2, D.2.5, D.2.6, D.2.7, D.2.9, D.2.10, D.2.m},
CRGenTerms = {Design, Documentation, Management}}
]]>