Feature-Oriented Re-engineering of Legacy Systems into Product Line Assets – a Case Study

Kang, Kyo C.; Kim, Moonzoo; Lee, Jaejoon; Kim, Byungkil

doi:10.1007/11554844_6

Cited by 44 publications

(29 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This redundancy problem comes from the legacy design of earlier CAS and has not been fixed yet due to risk of a large scale revision. 3 Features corresponding to business processes are not shown in this paper. Table 1, there are frequent revisions due to newly added affiliated stores and changes of affiliated services.…”

Section: A Feature Model Of Casmentioning

confidence: 94%

“…First, we reviewed the existing CAS code and the revision history with help of domain experts and extracted the legacy design. Then, we constructed a feature model of the CAS domain that captures variabilities of CAS from the revision history and a market analysis [1][2] [3]. Based on the recovered legacy design and the feature model, we could re-design components of CAS to preplan adoption of future evolution, which enhanced system maintainability.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Re-engineering a Credit Card Authorization System for Maintainability and Reusability of Components – A Case Study

Kang

Lee

Kim

et al. 2006

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract.A credit card authorization system (CAS) is a large information system performing diverse activities such as purchase authentication, balance transfer, cash advances, etc. One characteristic of CAS is its frequent update to satisfy the needs of customers and newly enforced governmental laws. Thus, CAS should be designed to minimize the effects of updates, for which high reusability of the CAS components is desired. In this paper, we present our experience of re-engineering CAS based on a feature model for improved reusability of components, which alleviates the difficulty of system maintenance. The result of this project has been successfully transferred to the company.

show abstract

Section: A Feature Model Of Casmentioning

confidence: 94%

Section: Introductionmentioning

confidence: 99%

Re-engineering a Credit Card Authorization System for Maintainability and Reusability of Components – A Case Study

Kang

Lee

Kim

et al. 2006

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…[18], [19], [20]). Some of these focus on the design of SPLs for mature and stable domains of industrial robotics (e.g.…”

Section: B Robotics Software Product Linesmentioning

confidence: 99%

A Software Product Line Approach for Configuring Cloud Robotics Applications

Gherardi

Hunziker

Mohanarajah

2014

2014 IEEE 7th International Conference on Cloud Computing

View full text Add to dashboard Cite

Abstract-The computational requirements of the increasingly sophisticated algorithms used in today's robotics software applications have outpaced the onboard processors of the average robot. Furthermore, the development and configuration of these applications are difficult tasks that require expertise in diverse domains, including software engineering, control engineering, and computer vision. As a solution to these problems, this paper extends and integrates our previous works, which are based on two promising techniques: Cloud Robotics and Software Product Lines. Cloud Robotics provides a powerful and scalable environment to offload the computationally expensive algorithms resulting in low-cost processors and light-weight robots. Software Product Lines allow the end user to deploy and configure complex robotics applications without dealing with low-level problems such as configuring algorithms and designing architectures. This paper discusses the proposed method in depth, and demonstrates its advantages with a case study.

show abstract

“…This case study is based on the problem statement of the prototype of a Home Service Robot (HSR) for daily services provided in [22], [23]. The case study has been chosen because the details about the problem statement are very clear, it is simple enough to be analysed and understood in the context of a paper, and also because mobile robots are commonly used in software architecture examples [26].…”

Section: The Home Service Robot Case Studymentioning

confidence: 99%

“…Therefore, the generation of alternatives is based on the use of architectural patterns [6] and the evaluation of alternatives is done by applying structural metrics [14] over the produced models. In order to show the applicability of our approach, we apply the proposed steps and guidelines to the Home Service Robot case study as presented in [22], [23].…”

Section: Introductionmentioning

confidence: 99%

A Goal-Oriented Approach for the Generation and Evaluation of Alternative Architectures

Grau

Franch

Software Architecture

View full text Add to dashboard Cite

Abstract. There is a recognized gap between requirements and architectures. There is also evidence that architecture evaluation, when done at the early phases of the development lifecycle, is an effective way to ensure the quality attributes of the final system. As quality attributes may be satisfied at a different extent by different alternative architectural solutions, an exploration and evaluation of alternatives is often needed. In order to address this issue at the requirements level, we propose to model architectures using the i* framework, a goal-oriented modelling language that allows to represent the functional and non-functional requirements of an architecture using actors and dependencies instead of components and connectors. Once the architectures are modelled, we propose guidelines for the generation of alternative architectures based upon existing architectural patterns, and for the definition of structural metrics for the evaluation of the resulting alternative models. The applicability of the approach is shown with the Home Service Robot case study.

show abstract

Feature-Oriented Re-engineering of Legacy Systems into Product Line Assets – a Case Study

Cited by 44 publications

References 11 publications

Re-engineering a Credit Card Authorization System for Maintainability and Reusability of Components – A Case Study

Re-engineering a Credit Card Authorization System for Maintainability and Reusability of Components – A Case Study

A Software Product Line Approach for Configuring Cloud Robotics Applications

A Goal-Oriented Approach for the Generation and Evaluation of Alternative Architectures

Contact Info

Product

Resources

About