Software Analysis, Evolution, Maintenance and Visualization

A special issue of Software (ISSN 2674-113X).

Deadline for manuscript submissions: 1 May 2024 | Viewed by 1870

Special Issue Editor


E-Mail Website
Guest Editor
School of Computer Engineering, Costa Rica Institute of Technology, Cartago 159-7050, Costa Rica
Interests: software engineering; software analysis, evolution, and maintenance; visual analytics; computational thinking

Special Issue Information

Dear Colleagues,

The development and maintenance of software systems involve a large number of complex processes that extend over long periods of time and may involve many software engineers in different locations and countries. These complex processes are cyclic and conform to the basis of software evolution: software changes are based on the current state of the software project, which is the accumulation of previous changes made by several software engineers. In this context, several tools, such as logs, communication systems and defect-tracking systems keep records with dates, comments, changes made to software elements and details of the associated programmers.

Software development and maintenance usually expands over several years, generating thousands and even millions of lines of source code (LOC), hundreds of software components and thousands of commits, variables, constants, programming structures, methods and intricate relationships among software items.

Topics of interest include, but are not limited to, the following:

  • Methods to monitor the evolution of the quality of software elements (i.e., classes, packages and modules), taking into account the use of software quality metrics.
  • Mechanisms for the measurement and analysis of task execution, progress analysis and performance prediction.
  • Methods to assist in risk management and to control the size and complexity of the software product.
  • Instruments to keep project managers informed on collaboration patterns between developers.
  • Approaches to study synchronous and asynchronous changes, as well as their implications (in terms of quality and functionality).
  • Methods to understand and comprehend software systems and their recent changes and evolution.
  • Comprehension of the sociotechnical relationships derived from the development process.
  • Software tools for software analysis, evolution and maintenance.
  • Software analysis, parsing and fact extraction.
  • Software evolution analysis.
  • Mining software repositories, software analytics and software visualization.

Dr. Antonio González-Torres
Guest Editor

Manuscript Submission Information

Manuscripts should be submitted online at www.mdpi.com by registering and logging in to this website. Once you are registered, click here to go to the submission form. Manuscripts can be submitted until the deadline. All submissions that pass pre-check are peer-reviewed. Accepted papers will be published continuously in the journal (as soon as accepted) and will be listed together on the special issue website. Research articles, review articles as well as short communications are invited. For planned papers, a title and short abstract (about 100 words) can be sent to the Editorial Office for announcement on this website.

Submitted manuscripts should not have been published previously, nor be under consideration for publication elsewhere (except conference proceedings papers). All manuscripts are thoroughly refereed through a single-blind peer-review process. A guide for authors and other relevant information for submission of manuscripts is available on the Instructions for Authors page. Software is an international peer-reviewed open access quarterly journal published by MDPI.

Please visit the Instructions for Authors page before submitting a manuscript. The Article Processing Charge (APC) for publication in this open access journal is 1000 CHF (Swiss Francs). Submitted papers should be well formatted and use good English. Authors may use MDPI's English editing service prior to publication or during author revisions.

Keywords

  • software analysis, evolution, and maintenance
  • software visualization
  • visual software analytics
  • quality assurance in software systems
  • software reengineering
  • software metrics
  • mining software repositories

Published Papers (1 paper)

Order results
Result details
Select all
Export citation of selected articles as:

Research

28 pages, 7911 KiB  
Article
Beam Transmission (BTR) Software for Efficient Neutral Beam Injector Design and Tokamak Operation
by Eugenia Dlougach and Margarita Kichik
Software 2023, 2(4), 476-503; https://doi.org/10.3390/software2040022 - 24 Oct 2023
Cited by 1 | Viewed by 1066
Abstract
BTR code (originally—“Beam Transmission and Re-ionization”, 1995) is used for Neutral Beam Injection (NBI) design; it is also applied to the injector system of ITER. In 2008, the BTR model was extended to include the beam interaction with plasmas and direct beam losses [...] Read more.
BTR code (originally—“Beam Transmission and Re-ionization”, 1995) is used for Neutral Beam Injection (NBI) design; it is also applied to the injector system of ITER. In 2008, the BTR model was extended to include the beam interaction with plasmas and direct beam losses in tokamak. For many years, BTR has been widely used for various NBI designs for efficient heating and current drive in nuclear fusion devices for plasma scenario control and diagnostics. BTR analysis is especially important for ‘beam-driven’ fusion devices, such as fusion neutron source (FNS) tokamaks, since their operation depends on a high NBI input in non-inductive current drive and fusion yield. BTR calculates detailed power deposition maps and particle losses with an account of ionized beam fractions and background electromagnetic fields; these results are used for the overall NBI performance analysis. BTR code is open for public usage; it is fully interactive and supplied with an intuitive graphical user interface (GUI). The input configuration is flexibly adapted to any specific NBI geometry. High running speed and full control over the running options allow the user to perform multiple parametric runs on the fly. The paper describes the detailed physics of BTR, numerical methods, graphical user interface, and examples of BTR application. The code is still in evolution; basic support is available to all BTR users. Full article
(This article belongs to the Special Issue Software Analysis, Evolution, Maintenance and Visualization)
Show Figures

Figure 1

Back to TopTop