• Korea Trade Review
• /
• v.47 no.1
• /
• pp.163-180
• /
• 2022

The purpose of this study is to examine the extent to which smart contracts can be applied to the software export business and to find out the legislative issues to activate smart contracts. A smart contract is a computer program that automatically executes a contract when conditions are fulfilled. Smart contracts can play a pivotal role in the field that requires immediate execution of contract or in a highly standardized field with multiple parties involved. In the software export business, it is desirable to apply the smart contract partially rather than applying the smart contract to the entire process because various parties are involved and the process is very complicated. The business model of exporting packaged software, a completed software that is mainly licensed for use, rather than the business model of exporting customized software is suitable for using smart contracts because the project for implementing customized software is mainly focused in the development stage. When smart contracts are used in processes such as contract signing, payment, and project management, work efficiency can be increased. In addition, smart contracts can be used when conditions can be quantified, such as error penalties, in areas that previously required contracts with third parties such as banks, guarantors. In order for smart contracts to be actively used in practice, legal reviews on various issues are necessary including the legality of a smart contract and the validity as an electronic document of NFT (non-fungible token) certificate. Also, for the system stability preventing hacking, etc, the periodic verification or inspection by a third party is essential. To activate smart contracts in international transactions the international treaty regarding smart contracts is also necessary.

• International Commerce and Information Review
• /
• v.11 no.1
• /
• pp.333-351
• /
• 2009

The American Law Institute(ALI) has presented drafts of "Principles of the law of software contracts" to clarify and unify the law of software transactions. These principles apply to agreements for the transfer of or access to software. Providing these principles means something in software contracts. First of all, these principles seek to limit the scope to cover only contracts involving software exchanged or accessed for consideration, while UCITA includes a wide variety of "computer information". Secondly, this project is "Principles" instead of "Restatement" which means that these principles are not the law unless a court adopts it. This is for flexibility not to hinder law's adoptability of new legal issues that might be created in the future since the software industry has developed. Third, the project seek to balance between software transferor's interest and transferees to permit the use of remote disablement in limited circumstances. These principles, however, should be considered some concerns in the future work. For example, not to be a unconscionable agreement, it is better to suggest the specific click-wrap procedure and be more illustrative about what types of browser-wrap language are acceptable and what types are not.

• Journal of Software Assessment and Valuation
• /
• v.17 no.1
• /
• pp.1-9
• /
• 2021

In disputes involving contracts for work, most issues boil down a single, most crucial, underlying question: whether the agreed work was completed. The same applies to software development services, which are usually usually provided under contracts for work. In disputes arising from software development contracts, appraisal is commonly used to determine the completeness of the software in question. However, it is often difficult to ensure the objectivity of the appraisal. This study examines past cases involving the determination of software completeness to identify the method used in each case. Then, based on the findings, this study identifies issues requiring improvements to ensure objective determination of completeness.

• The Journal of the Convergence on Culture Technology
• /
• v.9 no.6
• /
• pp.1017-1029
• /
• 2023

A large amount of transactions are taking place through Blockchain. Among them, the proportion of transactions through smart contracts is increasing. Accordingly, problems such as vulnerability attacks on smart contracts and fraud using smart contracts are increasing. Through security audits of smart contracts, developers can discover and resolve vulnerabilities, and users can distinguish whether smart contracts are fraudulent. However, there are currently no regulations and standards for security auditing of smart contracts, so services that perform security auditing are uneven. In this paper, we analyze security audit trends for smart contracts and identify what services are being provided. We investigate what elements are analyzed from smart contracts, focusing on security audit reports. Also, investigate what vulnerabilities can be detected. Finally, we investigate quality indicators for smart contracts and visualization elements of design extraction. Through this, we hope to be able to find visualization elements specialized for smart contracts.

• Journal of the Semiconductor & Display Technology
• /
• v.22 no.3
• /
• pp.73-77
• /
• 2023

As the DeFi market continues to expand, fraudulent activities using smart contracts have also increased. HoneyPot and Ponzi schemes are well-known frauds that exploit smart contracts. While several studies have demonstrated the potential to detect smart contracts implementing these scams, there has been a lack of research focusing on simultaneously detecting both types of fraud. This paper addresses this gap by harnessing artificial intelligence to conduct experiments for the detection of both HoneyPot and Ponzi schemes. The study employs the CNN (Convolutional Neural Network) model, commonly used for malware detection. To effectively utilize CNN, the bytecode of smart contracts is transformed into visual representations. The experimental results showcase a recall rate of 0.89 and an F1 score of 0.85, indicating promising detection capabilities.

• Journal of Computing Science and Engineering
• /
• v.7 no.4
• /
• pp.251-262
• /
• 2013

Bad smells are usually related to program source code, arising from bad design and programming practices. Refactoring activities are often motivated by the detection of bad smells. With the increasing adoption of Design-by-Contract (DBC) methodologies in formal software development, evidence of bad design practices can similarly be found in programs that combine actual production code with interface contracts. These contracts can be written in languages, such as the Java Modeling Language (JML), an extension to the Java syntax. This paper presents a catalog of bad smells that appear during DBC practice, considering JML as the language for specifying contracts. These smells are described over JML constructs, although several can appear in other DBC languages. The catalog contains 6 DBC smells. We evaluate the recurrence of DBC smells in two ways: first by describing a small study with graduate student projects, and second by counting occurrences of smells in contracts from the JML models application programming interface (API). This API contains classes with more than 1,600 lines in contracts. Along with the documented smells, suggestions are provided for minimizing the impact or even removing a bad smell. It is believed that initiatives towards the cataloging of bad smells are useful for establishing good design practices in DBC.

• THE INTERNATIONAL COMMERCE & LAW REVIEW
• /
• v.19
• /
• pp.169-190
• /
• 2003

Uniform Computer Information Transactions Act (UCITA) for e-commerce in non-UCC and non-UETA transactions, promulgated in 1999. The Act Drafted by the National Conference of Commissioners on Uniform State Laws. UCITA applies to contracts to license or buy software, contracts to create computer programs, contracts for on-line access to databases and contracts to distribute information over the Internet. UCITA does not apply to goods such as television sets, stereo equipment, airplanes or traditional books and publications. Goods generally remain subject to UCC Article 2 or Article 2A. Many transactions may include more than computer information. If that transaction covers non-goods subject matter, UCITA applies only to the part of the transaction which is computer information and other law applies to the other subject matter. In the event the other subject matter is goods, UCC Article 2 or 2A applies to the goods subject matter and UCITA applies to the computer information part. UCITA is coordinated with existing Articles 2 and 2A, so coverage of each to part of the transaction will be facilitated. With respect to other subject matter (primarily services) UCC Articles 2 and 2A have worked in mixed transactions with the common law applicable to the services.

• International journal of advanced smart convergence
• /
• v.10 no.3
• /
• pp.89-96
• /
• 2021

In various areas of the 4th industry, a big issue is software quality enhancement for stability and reliability of the smart software systems. After revising software promotion law at 2020, we must clearly define requirements and separate design parts and implementation parts of an all public software development contracts. In this study, we need to validate whether the final implementation of software is followed by the original design or not. To do this, we consider the design restoration through software visualization based on reverse engineering. Therefore we propose an UML design extraction and visualization method based on reverse engineering. Based on this, we may validate whether it is implemented according to the original design, and how much visualizes and includes the code the internal complexity for improvement of software quality.

• Journal of Information Technology Services
• /
• v.4 no.2
• /
• pp.33-46
• /
• 2005

Small/medium software businesses are often at a disadvantage when trying to win government contracts. Rather, most of small/medium software companies work with larger companies in the form of subcontracting. In its broadest meaning, subcontracting refers to the purchase of a part of a product or process from a different company. Appropriate subcontracting system helps both large and small software firms keep in healthy. However, many problems regarding subcontracting have been reported and recognized as one of major obstacles impeding advancement of the software industry. This paper examines the current problems in subcontracting system by conducting a field survey and proposes directions to improve the system for software project. It suggests revision of 'Software Industry Promotion Act' to induce fair relationship among software firms.

• Journal of Information Technology Services
• /
• v.7 no.3
• /
• pp.129-144
• /
• 2008

The uncertainty of software projects makes a big gap between the initial schedule/expense and the final one. Moreover, it is difficult for a project manager to reschedule and re-budget for reflecting the effects of changes in the software development. In this paper, we suggest EVM (Earned Value Management) to control the schedule and the expenses of an on-going software development project. In order to apply EVM to a software project, we consider turnkey contracts and propose the way to calculate the earned value for the software development. Finally, we illustrate our method with the case of N-company. We expect our EVM help to analyze and to predict the final schedule and the expense of a software development project.