scholarly journals GammaPolarSlicer

2011 ◽  
Vol 8 (2) ◽  
pp. 477-499
Author(s):  
Sérgio Areias ◽  
Cruz da ◽  
Rangel Henriques ◽  
Sousa Pinto
Keyword(s):  
Software Development ◽  
Software Industry ◽  
Source Code ◽  
Software Components ◽  
Control Data ◽  
Legacy System ◽  
Textual Representation ◽  
System Dependence Graph ◽  
Under Construction

In software development, it is often desirable to reuse existing software components. This has been recognized since 1968, when Douglas Mcllroy of Bell Laboratories proposed basing the software industry on reuse. Despite the failures in practice, many efforts have been made to make this idea successful. In this context, we address the problem of reusing annotated components as a rigorous way of assuring the quality of the application under construction. We introduce the concept of caller-based slicing as a way to certify that the integration of an annotated component with a contract into a legacy system will preserve the behavior of the former. To complement the efforts done and the benefits of the slicing techniques, there is also a need to find an efficient way to visualize the annotated components and their slices. To take full profit of visualization, it is crucial to combine the visualization of the control/data flow with the textual representation of source code. To attain this objective, we extend the notion of System Dependence Graph and slicing criterion.

scholarly journals General guidelines for biomedical software development

F1000Research ◽  
2017 ◽  
Vol 6 ◽  
pp. 273 ◽  
Author(s):  
Luis Bastiao Silva ◽  
Rafael C. Jimenez ◽  
Niklas Blomberg ◽  
José Luis Oliveira
Keyword(s):  
Software Development ◽  
Biomedical Applications ◽  
Development Process ◽  
Software Components ◽  
Specific Topic ◽  
Software Developers ◽  
Vast Number ◽  
Software Applications ◽  
New Strategies

Most bioinformatics tools available today were not written by professional software developers, but by people that wanted to solve their own problems, using computational solutions and spending the minimum time and effort possible, since these were just the means to an end. Consequently, a vast number of software applications are currently available, hindering the task of identifying the utility and quality of each. At the same time, this situation has hindered regular adoption of these tools in clinical practice. Typically, they are not sufficiently developed to be used by most clinical researchers and practitioners. To address these issues, it is necessary to re-think how biomedical applications are built and adopt new strategies that ensure quality, efficiency, robustness, correctness and reusability of software components. We also need to engage end-users during the development process to ensure that applications fit their needs. In this review, we present a set of guidelines to support biomedical software development, with an explanation of how they can be implemented and what kind of open-source tools can be used for each specific topic.

Requirements to Products and Processes for Software of Safety Important NPP I&C Systems

2022 ◽  
pp. 212-246
Author(s):  
Vladimir Sklyar ◽  
Andriy Volkoviy ◽  
Oleksandr Gordieiev ◽  
Vyacheslav Duzhyi
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Software Verification ◽  
Software Requirements ◽  
Software Components ◽  
Software Life Cycle ◽  
Regulatory Documents ◽  
And Control

Features of software as a component of instrumentation and control (I&C) systems are analyzed. Attention is paid to the importance of functions performed by software and hazards of such software. Requirements for characteristics of software as a component of I&C systems are analyzed. Different regulatory documents are considered in order to disclose common approaches to the use of dedicated software and off-the-shelf software components. Classification of software, as well as classification of requirements, is described. Criteria of selection and structuring of requirements, as well as criteria for software verification, are defined. As long as the characteristics of software components directly depend on the quality of the processes of software development and verification, requirements for software life cycle processes are considered.

scholarly journals Making the Evolution of Graphical Models Visible

10.29007/fqc6 ◽  
2018 ◽  
Author(s):  
Thomas Baar ◽  
Issam Bendaas
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Graphical Models ◽  
Software Industry ◽  
Source Code ◽  
Version Control ◽  
Software Projects ◽  
History Of ◽  
Development Practice ◽  
Uml Models

With adoption of the UML and other graphical languages by software industry,graphical models became a cornerstone in today's software development practice.As other artefacts such as program source code, graphical models evolve overtime and are, thus, put regularily under version control.In order to deeply understand the role an artefact plays within a project, it issometimes helpful to review the history of this artefact. While there arenumerous tools available that make it easy for a user to grasp the evolution oftextual files (or even portions of it), an adequate support for graphical fileshas remained to be an area of niche products.In this paper, we argue that a better support for reviewing the version historyof graphical files can facilitate the work with graphical models. In order tosupport this claim, we implemented a prototypcical tool that can extract anddisplay the version history of any graphical file stored in a GitHub-repository.In addition, users can annotate each version of a file with comments, whatturns our tool into a review tool for software projects. Recently, we started touse the tool is a software engineering course to give students better feedbackon complex UML models they have to develop iteratively.

Software of Safety Important I&C Systems

2014 ◽  
pp. 146-177
Author(s):  
Vyacheslav Kharchenko ◽  
Vladimir Sklyar ◽  
Andriy Volkoviy
Keyword(s):  
Software Development ◽  
Nuclear Power ◽  
Software Verification ◽  
Software Requirements ◽  
Software Components ◽  
Software Life Cycle ◽  
Regulatory Documents ◽  
And Control

Features of software as a component of Instrumentation and Control (I&C) systems are analyzed. Attention is paid to the importance of functions performed by software and hazards of such software. Requirements for characteristics of software as a component of I&C systems are analyzed. Different regulatory documents are considered in order to disclose common approaches to the use of dedicated software and off-the-shelf software components. Classification of software, as well as classification of requirements, is described. Criteria of selection and structuring of requirements, as well as criteria for software verification, are defined. As long as the characteristics of software components directly depend on the quality of the processes of software development and verification, requirements for software life cycle processes are considered. The second part of this chapter is dedicated to evaluation of software for nuclear power plant I&C system. Criteria and principles of evaluation are observed. Evaluation of the characteristic of software as a product and software development and verification processes are considered.

Requirements to Products and Processes for Software of Safety Important NPP I&C Systems

2020 ◽  
pp. 97-131
Author(s):  
Vladimir Sklyar ◽  
Andriy Volkoviy ◽  
Oleksandr Gordieiev ◽  
Vyacheslav Duzhyi
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Software Verification ◽  
Software Requirements ◽  
Software Components ◽  
Software Life Cycle ◽  
Regulatory Documents ◽  
And Control

Features of software as a component of instrumentation and control (I&C) systems are analyzed. Attention is paid to the importance of functions performed by software and hazards of such software. Requirements for characteristics of software as a component of I&C systems are analyzed. Different regulatory documents are considered in order to disclose common approaches to the use of dedicated software and off-the-shelf software components. Classification of software, as well as classification of requirements, is described. Criteria of selection and structuring of requirements, as well as criteria for software verification, are defined. As long as the characteristics of software components directly depend on the quality of the processes of software development and verification, requirements for software life cycle processes are considered.

scholarly journals Recognizing lines of code violating company-specific coding guidelines using machine learning

2019 ◽  
Vol 25 (1) ◽  
pp. 220-265 ◽  
Author(s):  
Miroslaw Ochodek ◽  
Regina Hebig ◽  
Wilhelm Meding ◽  
Gert Frost ◽  
Miroslaw Staron
Keyword(s):  
Machine Learning ◽  
Action Research ◽  
Software Development ◽  
Source Code ◽  
Design Guidelines ◽  
Code Design ◽  
Action Research Project ◽  
Software Developers ◽  
Code Analysis

AbstractSoftware developers in big and medium-size companies are working with millions of lines of code in their codebases. Assuring the quality of this code has shifted from simple defect management to proactive assurance of internal code quality. Although static code analysis and code reviews have been at the forefront of research and practice in this area, code reviews are still an effort-intensive and interpretation-prone activity. The aim of this research is to support code reviews by automatically recognizing company-specific code guidelines violations in large-scale, industrial source code. In our action research project, we constructed a machine-learning-based tool for code analysis where software developers and architects in big and medium-sized companies can use a few examples of source code lines violating code/design guidelines (up to 700 lines of code) to train decision-tree classifiers to find similar violations in their codebases (up to 3 million lines of code). Our action research project consisted of (i) understanding the challenges of two large software development companies, (ii) applying the machine-learning-based tool to detect violations of Sun’s and Google’s coding conventions in the code of three large open source projects implemented in Java, (iii) evaluating the tool on evolving industrial codebase, and (iv) finding the best learning strategies to reduce the cost of training the classifiers. We were able to achieve the average accuracy of over 99% and the average F-score of 0.80 for open source projects when using ca. 40K lines for training the tool. We obtained a similar average F-score of 0.78 for the industrial code but this time using only up to 700 lines of code as a training dataset. Finally, we observed the tool performed visibly better for the rules requiring to understand a single line of code or the context of a few lines (often allowing to reach the F-score of 0.90 or higher). Based on these results, we could observe that this approach can provide modern software development companies with the ability to use examples to teach an algorithm to recognize violations of code/design guidelines and thus increase the number of reviews conducted before the product release. This, in turn, leads to the increased quality of the final software.

scholarly journals Development of E-learning Software Based Multiplatform Components

2017 ◽  
Vol 6 (3) ◽  
pp. 228-234
Author(s):  
Irma Salamah ◽  
M. Aris Ganiardi
Keyword(s):  
Software Development ◽  
Web Applications ◽  
Electronic Device ◽  
Cost Effective ◽  
Software Components ◽  
High Quality ◽  
Information And Communication ◽  
E Learning ◽  
Learning Software

E-learning software is a product of information and communication technology used to help dynamic and flexible learning process between teacher and student. The software technology was first used in the development of e-learning software in the form of web applications. The advantages of this technology because of the ease in the development, installation, and distribution of data. Along with advances in mobile/wireless electronics technology, e-learning software is adapted to this technology known as mobile learning. The ability of this electronic device is the same as a single computer even though it is simpler than a single computer. The problem that arises when e-learning software operates on multiple platforms is that computer programs are made repeatedly depending on the platform being used. This situation will obviously affect the quality of e-learning software. To overcome these problems, in this study developed component-based software that is a modern paradigm for software development that produces reusable software components, high quality, and cost-effective. In software development, software components will be assembled in the software in need. The result of this research is high quality e-learning software based multiplatform component.

scholarly journals General guidelines for biomedical software development

F1000Research ◽  
2017 ◽  
Vol 6 ◽  
pp. 273 ◽  
Author(s):  
Luis Bastiao Silva ◽  
Rafael C. Jiménez ◽  
Niklas Blomberg ◽  
José Luis Oliveira
Keyword(s):  
Software Development ◽  
Biomedical Applications ◽  
Development Process ◽  
Software Components ◽  
Specific Topic ◽  
Software Developers ◽  
Vast Number ◽  
Software Applications ◽  
New Strategies

Most bioinformatics tools available today were not written by professional software developers, but by people that wanted to solve their own problems, using computational solutions and spending the minimum time and effort possible, since these were just the means to an end. Consequently, a vast number of software applications are currently available, hindering the task of identifying the utility and quality of each. At the same time, this situation has hindered regular adoption of these tools in clinical practice. Typically, they are not sufficiently developed to be used by most clinical researchers and practitioners. To address these issues, it is necessary to re-think how biomedical applications are built and adopt new strategies that ensure quality, efficiency, robustness, correctness and reusability of software components. We also need to engage end-users during the development process to ensure that applications fit their needs. In this review, we present a set of guidelines to support biomedical software development, with an explanation of how they can be implemented and what kind of open-source tools can be used for each specific topic.

Recent trends in Component Based software development and Efficiency analysis of Semantic search based component retrieval Technique

2018 ◽  
pp. 105-113 ◽  
Author(s):  
Vishnu Sharma ◽  
Vijay Singh Rathore
Keyword(s):  
Software Development ◽  
Efficiency Analysis ◽  
Software Components ◽  
High Demand ◽  
Component Retrieval ◽  
Software Developer ◽  
Software Libraries ◽  
Retrieval Technique ◽  
Executable File ◽  
Recent Trends

In these days most of the software development uses preexisting software components. This approach provides plenty of benefits over the traditional development. Most of the software industries uses their own domain based software libraries where components resides in the form of modules, codes, executable file, documentations, test plans which may be used as it is or with minor changes. Due to shrinking time and high demand of software development it is necessary to use pre tested software components to ensure high functionality in software developed. Software components can be used very easily and without having the worries of errors and bugs because these are developed under expert supervision and well tested. What we have to do is just embed these components in our project. In this paper a survey got conducted over 112 software developer,testers and freelancers. In survey several issues in CBSD were identified. An efficient repository along with a component search engine is developed. All the component retrieval techniques were evaluated and compared with precise and recall method.

JAVASCRIPT ASYNCHRONOUS PROGRAMMING

2019 ◽  
Vol 128 (2B) ◽  
pp. 5-16
Author(s):  
Tran Thanh Luong ◽  
Le My Canh
Keyword(s):  
Design Patterns ◽  
Source Code ◽  
Object Oriented ◽  
Exception Handling ◽  
Code Smells ◽  
Asynchronous Programming ◽  
Event Driven ◽  
Programming Patterns ◽  
The Impact

JavaScript has become more and more popular in recent years because its wealthy features as being dynamic, interpreted and object-oriented with first-class functions. Furthermore, JavaScript is designed with event-driven and I/O non-blocking model that boosts the performance of overall application especially in the case of Node.js. To take advantage of these characteristics, many design patterns that implement asynchronous programming for JavaScript were proposed. However, choosing a right pattern and implementing a good asynchronous source code is a challenge and thus easily lead into less robust application and low quality source code. Extended from our previous works on exception handling code smells in JavaScript and exception handling code smells in JavaScript asynchronous programming with promise, this research aims at studying the impact of three JavaScript asynchronous programming patterns on quality of source code and application.

Sign in / Sign up

Export Citation Format

Share Document