Wyniki wyszukiwania - BazTech

1

Detection of source code in internet texts using automatically generated machine learning models

Badurowicz Marcin

Applied Computer Science

|

2022

|

Vol. 18, no 1

89--98

EN

In the paper, the authors are presenting the outcome of web scraping software allowing for the automated classification of source code. The software system was prepared for a discussion forum for software developers to find fragments of source code that were published without marking them as code snippets. The analyzer software is using a Machine Learning binary classification model for differentiating between a programming language source code and highly technical text about software. The analyzer model was prepared using the AutoML subsystem without human intervention and fine-tuning and its accuracy in a described problem exceeds 95%. The analyzer based on the automatically generated model has been deployed and after the first year of continuous operation, its False Positive Rate is less than 3%. The similar process may be introduced in document management in software development process, where automatic tagging and search for code or pseudo-code may be useful for archiving purposes.

2

2D and 3D numerical simulation of fatigue crack growth path and life predictions of a linear elastic

Bashiri Abdullateef H.

Materials Science Poland

|

2021

|

Vol. 39, No. 2

285--297

EN

This paper describes implementation of the finite element method (FEM) to investigate crack growth problems in linear elastic fracture mechanics and the correlation of results with experimental and numerical data. The approach involved using two different software to compute stress intensity factors (SIFs), the crack propagation trajectory, and fatigue life estimation in two and three dimensions. According to the software, crack modeling might be run in various ways. The first is a developed source code program written in the Visual Fortran language, while the second is the widely used ANSYS Mechanical APDL 19.2 software. The fatigue crack propagation trajectory and the corresponding SIFs were predicted using these two software programs. The crack direction was investigated using the maximum circumferential stress theory, and the finite element (FE) analysis for fatigue crack growth was done for both software based on Paris's law. The predicted results in both software demonstrated the influence of holes on the crack growth trajectory and all associated stresses and strains. The study's findings agree with other experimental and numerical crack propagation studies presented in the literature that reveal similar crack propagation trajectory observations.

3

Comprehension analysis considering programming thinking ability using code puzzle

Ito Hiroki, Shimakawa Hiromitsu, Harada Fumiko

Annals of Computer Science and Information Systems

|

2020

|

Vol. 21

609--618

EN

In programming education, the instructor tries to find out the learners who needs help by grasping the learners' development of understanding using tests that require knowledge. However, in reality, not many learners will acquire the skill of writing source codes. This kind of current situation implies that programming ability of learners cannot be measured by tests that require knowledge. This paper focuses on not only the knowledge items required for programming but also the programming thinking (computational thinking), which is the ability to combine the constituent elements of the program. In this paper, we propose a method to estimate the learner's understanding from the learner's process to solve the code puzzles that require programming thinking as well as knowledge. We developed the interface to realize the proposed method. The experimental result with the interface showed that the proposed method could estimate with the accuracy of 80% or more.

4

Komentarze w kodach wybranych programów

Skhut Sviatoslav, Iholkina Kateryna

Biuletyn Naukowy Wrocławskiej Wyższej Szkoły Informatyki Stosowanej. Informatyka

|

2018

|

vol. 8, nr 1

24--28

EN

Writing comments is as important as writing code. The main purpose of using comments is to improve readability of our code but frequently thoughtless comment writing decrease understandability of source code. Comments must be concise and precise simultaneously. Also, when our code is changed, comments for this code must be changed too. While using comments in our code we must realize that if expressiveness of our programming language allows us to express clearly what we want in code, there is no need to write comments at all. And if we decide to use comments, they must be extremely accurate and understandable, because another person must understand, what we do and most importantly, why we do it. Frequently comments can be replaced with good clear names of variables, functions or classes. Also, we can replace our comments with assertions. Comments should clarify and explain our intentions. Copyrights and an authorship can be implemented using comments too. But our IDE can do these things automatically.

5

ECLogger: Cross-Project Catch-Block Logging Prediction Using Ensemble of Classifiers

Lal S., Sardana N., Sureka A.

e-Informatica Software Engineering Journal

|

2017

|

Vol. 11, nr 1

7--38

EN

Background: Software developers insert log statements in the source code to record program execution information. However, optimizing the number of log statements in the source code is challenging. Machine learning based within-project logging prediction tools, proposed in previous studies, may not be suitable for new or small software projects. For such software projects, we can use cross-project logging prediction. Aim: The aim of the study presented here is to investigate cross-project logging prediction methods and techniques. Method: The proposed method is ECLogger, which is a novel, ensemble-based, cross-project, catch-block logging prediction model. In the research We use 9 base classifiers were used and combined using ensemble techniques. The performance of ECLogger was evaluated on on three open-source Java projects: Tomcat, CloudStack and Hadoop. Results: ECLoggerBagging, ECLoggerAverageVote, and ECLoggerMajorityVote show a considerable improvement in the average Logged F-measure (LF) on 3, 5, and 4 source!target project pairs, respectively, compared to the baseline classifiers. ECLoggerAverageVote performs best and shows improvements of 3.12% (average LF) and 6.08% (average ACC – Accuracy). Conclusion: The classifier based on ensemble techniques, such as bagging, average vote, and majority vote outperforms the baseline classifier. Overall, the ECLoggerAverageVote model performs best. The results show that the CloudStack project is more generalizable than the other projects.

6

Transforming Source Code to Mathematical Relations for Performance Evaluation

Izadkhah H.

Annales Universitatis Mariae Curie-Skłodowska. Sectio AI, Informatica

|

2015

|

Vol. 15, no. 2

7--13

EN

Assessing software quality attributes (such as performance, reliability, and security) from source code is of the utmost importance. The performance of a software system can be improved by its parallel and distributed execution. The aim of the parallel and distributed execution is to speed up by providing the maximum possible concurrency in executing the distributed segments. It is a well known fact that distributing a program cannot be always caused speeding up the execution of it; in some cases, this distribution can have negative effects on the running time of the program. Therefore, before distributing a source code, it should be specified whether its distribution could cause maximum possible concurrency or not. The existing methods and tools cannot achieve this aim from the source code. In this paper, we propose a mathematical relationship for object oriented programs that statically analyze the program by verifying the type of synchronous and asynchronous calls inside the source code. Then, we model the invocations of the software methods by Discrete Time Markov Chains (DTMC). Using the properties of DTMC and the proposed mathematical relationship, we will determine whether or not the source code can be distributed on homogeneous processors. The experimental results showed that we can specify whether the program is distributable or not, before deploying it on the distributed systems.

7

Zaciemnianie kodu jako forma zabezpieczenia kodu źródłowego

Jóźwiak I., Michalski M., Pasieczny M.

Zeszyty Naukowe. Organizacja i Zarządzanie / Politechnika Śląska

|

2012

|

z. 61

159--169

PL

W artykule przedstawiono wprowadzenie do techniki zabezpiecze-nia kodu źródłowego metodą zaciemniania kodu, zwaną obfuskacją. Obfuskacja to technika przekształcania programów, która zachowuje ich semantykę, ale znacząco utrudnia zrozumienie. W artykule zdefiniowano obfuskację, omówiono jej zastoso-wania oraz wady. Przedstawiono przegląd popularnych programów zwanych obfuska-torami, które pozwalają poddać kod źródłowy procesowi zaciemniania kodu dla popu-larnych języków programowania takich jak: języki platformy .NET np. C#, Java, Flash (ActionScript).

EN

In the paper an introduction to the security source code method called obfuscation has been presented. Obfuscation is a technique of converting programs, which retains its semantics, but it is significantly difficult to understand. This article presents definitions of obfuscation, its uses and drawbacks. Paper provides an ove-rview of popular software called obfuscator, that allows the source code subject to the process of code obfuscation, for popular programming languages such as: .NET platform languages eg. C#, Java, Flash (ActionScript).

8

Przegląd systemów do podpisywania kodu

Jóźwiak I., Kozłowski G.

Zeszyty Naukowe. Organizacja i Zarządzanie / Politechnika Śląska

|

2012

|

z. 61

147--158

PL

W artykule przedstawiono wiodące rozwiązania z dziedziny systemów do podpisywania kodu aplikacji. Systemy Microsoft Authenticode, Oracle Java Code Signing oraz Apple Codesign porównane zostały pod kątem ich założeń projektowych, struktury wytwarzanego podpisu cyfrowego, a także sposobu jego generowania oraz weryfikacji. Omówiona została również koncepcja tożsamości kodu źródłowego aplikacji.

EN

This publication discusses the leading solutions for code signing systems such as Microsoft Authenticode, Oracle Java Code Signing and Apple Codesign. All systems were compared to each other in aspects such as digital signature structure, its generation and verification. A special attention was given to an issue of code identity.

9

Wtyczka do środowiska "Eclipse" dla edytora kodów źródłowych VHDL z zaawansowanym systemem formatowania tekstu

Niton B., Poźniak K. T., Romaniuk R. S.

Elektronika : konstrukcje, technologie, zastosowania

|

2011

|

Vol. 52, nr 11

124-127

PL

W artykule opisano koncepcję oraz realizację wtyczki do środowiska Eclipse przeznaczoną do edycji kodów źródłowych w języku opisu sprzętu VHDL. Przedstawiono autorskie rozwiązanie systemu formatującego dla kodów źródłowych VHDL rozszerzające możliwości programu VEditor bazującego na wolnej licencji. Zaprezentowano wynik działania systemu formatującego na wybranych przykładach kodach źródłowych VHDL.

EN

The paper describes an idea and realization of a smart plug-in to the Eclipse software environment. The plug-in is predicted for editing of the VHDL source code. It extend considerably the capabilities of the VEditor program, which bases on the open license. There are presented the results of the formatting procedures performed on chosen examples of the VHDL source codes.

10

Optymalne konstrukcje języka C w programach dla 8-bitowych mikrosterowników PIC

Caban D.

Studia Informatica

|

2010

|

Vol. 31, nr 1

19-27

PL

Zdaniem niektórych osób programy dla mikrosterowników z wewnętrzną pamięcią programu o małej pojemności należy pisać tylko w języku asemblera. Kod wynikowy programu w języku C z reguły zajmuje więcej pamięci. Nie musi być to dużo więcej. Wiele zależy od sposobu zapisania programu źródłowego.

EN

Some person think that software for microcotrollers with small internal program memory should be written in assembly language only. The object code of C program usually occupy more memory space. It is not having to be far more. The way of writing the source code is playing a significant role.

11

Minimalizowanie rozmiaru kodu wynikowego programów w języku C dla mikrosterowników rodziny 8051

Caban D.

Studia Informatica

|

2008

|

Vol. 29, nr 3A

19-37

PL

Kod wynikowy programu napisanego w języku C zajmuje z reguły więcej miejsca w pamięci niż kod wykorzystującego ten sam algorytm programu w języku asemblera. Różnicę tę można zmniejszyć przez stosowanie odpowiednich konstrukcji języka wysokiego poziomu.

EN

The object code of C program usually occupies more memory space than object code of assembly program using the same algorithm. Application of appropriate constructs of the high-level language can decrease this difference.

12

Wzorce projektowe w konstrukcji narzędzi przetwarzania kodu źródłowego

Forczek M., Bartela K., Szmal P.

Prace Naukowe Instytutu Informatyki Stosowanej Politechniki Wrocławskiej. Konferencje

|

2007

371-384

PL

Przedstawione w artykule wzorce projektowe definiują konstrukcję modułów front-end'u taką aby mogły one być wykorzystane w większej liczbie zastosowali związanych z przetwarzaniem kodu źródłowego. Wzorce pomagają uzyskać modularną implementację, pozwalającą na wygodne składanie ścieżki przetwarzania ze skompilowanych bibliotek dynamicznych. Pozwalają oddzielić bloki przetwarzania wstępnego od bloku semantyki. Ich stosowanie daje też korzyści w procesie produkcyjnym samych narzędzi - poprawia architekturę ich konstrukcji, wymusza wyodrębnienie wewnętrznych interfejsów pomiędzy blokami funkcjonalnymi, które stanowią następnie ważne elementy dokumentacji technicznej narzędzia. Wzorce z powodzeniem zastosowano w kilku projektach - zarówno komercyjnych jak i badawczych.

EN

Nowadays, the source code apart from behavioral description - which is essential to generate executable form. -contains also records of its construction assumptions, implementation details notes, testing process requirements, and other information as well. All those data are crucial to achieve good ratings in project supervision, risk minimizing, and product quality. In consequence, there are many purposes of source code processing: compilation, but also documentation generation, refactorizalion, integrity and.correctness verification etc. Design Patterns presented here define front-end modules construction, which gives a possibility of modules reuse. The Patterns enforce modular implementation style, which allows composing code processing path from dynamically linked units in a convenient way. They clearly separate source text processing front-end from semantics units. Also the tools development process can benefit from using these patterns: they improve internal architecture, introduce mid-interfaces between functional blocks that become important form of technical documentation of tool interiors. The design patterns described here have been successfully applied in a few projects - commercial and research ones.