• 무역학회지
• /
• 제47권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.

• 통상정보연구
• /
• 제11권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.

• 한국소프트웨어감정평가학회 논문지
• /
• 제17권1호
• /
• pp.1-9
• /
• 2021

도급의 대상이 된 일의 완성 여부는 도급계약에 관한 분쟁에서 어떠한 쟁점을 다루던지 가장 중요한 전제에 해당한다. 일반적으로 도급계약의 형태로 이루어지는 소프트웨어 개발 용역의 경우에도 이는 동일하게 나타난다. 일이 완성된 정도를 완성도라 한다. 소프트웨어 도급계약이 원인이 된 소송에서는 대상 소프트웨어의 완성도를 산출하기 위하여 감정을 주로 활용한다. 다만 그 과정에서 다양한 전문가들이 재량을 가지고 참여하다 보니 객관성 확보에 어려움을 겪는 문제가 있다. 이에 본 논문에서는 그간 소프트웨어 완성도 산출에 관한 여러 사례를 살펴보고 각기 어떠한 산출 방식을 적용하였는지 검토해보았다. 이를 통하여 현재 소송 과정에서 이루어지는 완성도 산출의 객관성을 확보하기 위하여 어떠한 개선점이 필요한지 생각해보았다. 그 결과 부족한 자료에 기반하여 이루어진다는 점, 하자와 미완성을 엄격히 구별하지 않고 감정이 이루어지고 있다는 점, 가중치 적용에 대한 재량이 지나치게 광범위하다는 점 등의 문제가 있어 개선이 필요할 것으로 판단하였다.

• 문화기술의 융합
• /
• 제9권6호
• /
• pp.1017-1029
• /
• 2023

블록체인을 통해 많은 양의 거래가 일어나고 있다. 그중에서도 스마트 계약을 통한 거래의 비중이 커지고 있다. 이에 따라 스마트 계약에 대한 취약점 공격과 스마트 계약을 이용한 사기와 같은 문제점들도 증가한다. 스마트 계약에 대한 보안 감사를 통해 개발자는 취약점을 발견해 해결할 수 있고, 이용자는 스마트 계약의 사기 여부를 구분할 수 있다. 하지만 현재 스마트 계약에 대한 보안 감사에 대한 규정과 표준이 없으므로 보안 감사를 수행하는 서비스들이 불균일하다. 본 논문에서는 스마트 계약에 대한 보안 감사 동향을 분석하고 어떠한 서비스들이 제공되고 있는지 파악한다. 보안 감사 보고서를 중심으로 스마트 계약으로부터 어떠한 요소들을 분석하는지 조사한다. 또한 어떠한 취약점들을 검출할 수 있는지 조사한다. 마지막으로 스마트 계약에 대한 품질 지표와 설계 추출의 가시화 요소를 조사한다. 이를 통해 스마트 계약에 특화된 가시화 요소를 찾을 수 있을 것을 기대한다.

• 반도체디스플레이기술학회지
• /
• 제22권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
• /
• 제7권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.

• 무역상무연구
• /
• 제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
• /
• 제10권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.

• 한국IT서비스학회지
• /
• 제4권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.

• 한국IT서비스학회지
• /
• 제7권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.