A Storytest-Driven Approach to the Migration of Legacy Systems

Abbattista, Fabio; Bianchi, Alessandro; Lanubile, Filippo

doi:10.1007/978-3-642-01853-4_19

Cited by 5 publications

(4 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A robust and high-quality test suite supports refactoring, providing confidence in the system new version's correctness. [18][19][20] Tests are defined and verified against the system's legacy version. Still, their goal is to validate the next versions, yet to be developed.…”

Section: Importance Of Assessing the Quality Of Individual Test Methodsmentioning

confidence: 99%

“…Finally, tests developed and verified on legacy systems can play the role of requirements during the reengineering phases. A robust and high‐quality test suite supports refactoring, providing confidence in the system new version's correctness 18‐20 . Tests are defined and verified against the system's legacy version.…”

Section: Approaches For Assessing Test Artifacts Qualitymentioning

confidence: 99%

See 1 more Smart Citation

Fight silent horror unit test methods by consulting a TestWizard

Cerioli

Lagorio

Leotta

et al. 2021

J Software Evolu Process

View full text Add to dashboard Cite

Tests, when not correctly implemented, can pass on incorrect system implementations rather than fail. In this case, they are named silent horrors or false‐negative tests. They make releasing low‐quality (buggy) versions of the software system more probable. Furthermore, faithfully implementing test specifications is crucial when they play the role of documentation, like when documenting components or services or driving legacy systems' re‐engineering. This paper presents TestWizard, a novel approach and tool for automatically assessing individual tests' quality from the point of view of their coherence to specifications. TestWizard automatically assesses the quality of each individual test case w.r.t. its specification, providing detailed reports on why a single test is a false negative, hence helping testers fix them. Thus, TestWizard can help to automate the test code review process, which is still mainly manual today. The analysis of 1012 test implementations, developed by 123 students in three experiments, shows that TestWizard is (1) by far more accurate than code review performed by multiple students, (2) slightly better than code review performed by three senior experts, and (3) always able to detect a significant percentage of false‐negative test methods (up to 21.22%).

show abstract

Section: Importance Of Assessing the Quality Of Individual Test Methodsmentioning

confidence: 99%

Section: Approaches For Assessing Test Artifacts Qualitymentioning

confidence: 99%

Fight silent horror unit test methods by consulting a TestWizard

Cerioli

Lagorio

Leotta

et al. 2021

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…XP is a new software development methodology that advocates frequent ‘releases’ of a working software in short development cycles to improve productivity in response to changing customer requirements. Much of the work in this area begins to focus on various ways to automate the iterative and incremental process, with some emphasis on acceptance testing . Hennessy and Power's work in is the most relevant to ours.…”

Section: Related Workmentioning

confidence: 99%

KLONOS: Similarity‐based planning tool support for porting scientific applications

Ding

Hsu

Hernández

et al. 2012

Concurrency and Computation

View full text Add to dashboard Cite

In this paper, we propose a methodology to address an important aspect of software porting that receives little attention, namely planning support. When a scientific application consisting of many subroutines is to be ported, the selection of key subroutines greatly impacts the productivity and overall porting strategy because these subroutines may represent a significant feature of the code in terms of functionality, code structure, or performance. They may as well serve as indicators of the difficulty and amount of effort involved in porting a code to a new platform. The proposed methodology is based on the idea that a set of similar subroutines can be ported with similar strategies and result in a similar-quality porting. By viewing subroutines as data and operator sequences, analogous to DNA sequences, we are able to use various bioinformatics techniques to conduct the similarity analysis of subroutines while mitigating NP-complete challenges of other approaches. To the best of our knowledge, we are one of the first to explore this bioinspired view of program to target the porting planning problem. In this paper, we describe our methodology and present a tool called Klonos to facilitate the execution of the methodology, which integrates to well known bioinformatics tools. As a proof of concept, we use Klonos to conduct experiments to find strategies for porting of several scientific benchmarks and applications. We also have identified some of the advantages and limitations of the bio-inspired view of a program code and the future work. 1073Besides these challenges faced by the application developers, many scientific applications tend to be long lived and comprise large code bases developed by a team of people and often outlive the involvement of any single developer. To maintain those applications is not an easy task, let alone to port them to the new system while the efficiency and correctness have to be guaranteed. To rewrite the entire application is too expensive and seems unrealistic. On the other hand, simulation platforms emerge at a frequency much higher than the lifetime of such application code bases, requiring at times fairly intrusive changes to fully benefit from the capabilities such platforms provide, which take years to develop. These changes are often made manually because of the lack of tool support. Automation of the process is rather impractical given its complexity, the level of tool support, and the lack of tool integration that automates user-driven porting strategies. Thus, the porting of scientific applications is both time consuming, labor intensive, and erroneous. Even an 'expert team' needs to start somewhere, this team will initiate the effort to restructure the code in order to exploit the new systems features, a very challenging error-prone process; the quality of the results will depend critically on the experience of the experts involved.In order to ease the effort for the software porting, we present a methodology to address an important aspect of software porting that receiv...

show abstract

“…During that period their adoption has span from small development projects with low risk and criticality to large distributed projects in critical application domains such as banking and automotive industry. Recently, a number of studies on the applicability of agile methods and techniques in the areas of Model-Driven Development, Software Modernization, Service-Oriented Architecture and Cloud Computing have been published (Qumer and Henderson-Sellers 2007, Abbattista et al 2009, Picek 2009, Prakash 2010, Zhang and Patel 2011, Matinnejad 2011. This paper further enlarges the existing body of research by answering the following research questions:…”

Section: Introductionmentioning

confidence: 99%

Challenges of Model-driven Modernization - An Agile Perspective

Stavru

Krasteva

Ilieva

2013

Proceedings of the 1st International Conference on Model-Driven Engineering and Software Development

View full text Add to dashboard Cite

Software organizations are nowadays facing increased demand for modernizing their legacy software systems using up-to-date technologies. The combination of Model-Driven Development and delivery models like Cloud and Software as a Service have become a very promising approach for software modernization that possesses a lot of advantages, including great deal of automation and reuse of system functionality. However, the use of such new and immature technologies is very challenging and requires a comprehensive methodology for their seamless application within the software modernization projects. When developing such methodology, questions on whether agile methods and techniques should be incorporated and what could be the benefits and implications from that become of particular interest. To help answering these questions, the paper evaluates the potential of agile methods and techniques to address the challenges of Model-Driven Modernization. The challenges are extracted through a systematic review of the existing body of literature on Model-Driven Development and Software Modernization, and the evaluation is conducted through the Delphi technique. As a result, a ranked list of applicable agile techniques is proposed and suggestions for their use in Model-Driven Modernization are made.

show abstract

A Storytest-Driven Approach to the Migration of Legacy Systems

Cited by 5 publications

References 6 publications

Fight silent horror unit test methods by consulting a TestWizard

Fight silent horror unit test methods by consulting a TestWizard

KLONOS: Similarity‐based planning tool support for porting scientific applications

Challenges of Model-driven Modernization - An Agile Perspective

Contact Info

Product

Resources

About