SW 완성도 감정 시 문제점 해결 방법

우균 한국소프트웨어감정평가학회 2023 한국소프트웨어감정평가학회 논문지 Vol.19 No.4

소프트웨어 개발이 활발해짐에 따라 소프트웨어 완성도에 대한 분쟁 사건이 늘어나고 있다. 소프트웨어 완성도에 대한 감정 요구는 늘어나고 있지만, 감정 과정에서는 여러 문제점이 대두되고 있다. 먼저 감정 목적물소프트웨어의 완성도가 현저히 낮을 수 있다. 두 번째로 소프트웨어 모듈의 구조가 매우 복잡할 수 있다. 끝으로 소프트웨어의 실행 환경이 구축되기 힘들 수 있다. 이 논문은 이러한 문제점에 대처하기 위한 몇 가지가능한 방법을 제안한다. 사례 연구를 통해 이들 방법의 적용 가능성을 타진한다. 제안 방법은 소프트웨어 완성도 감정의 부담을 경감시킬 수 있다. With the active developments of software, the cases of disputes on the completeness of software are also increasing. Despite the need for the appraisal of the completeness of software, several problems are encountered during the appraisal process. First of all, the completeness of the target software can be severely low. Secondly, the structure of the software modules can be very complicated. Lastly, the execution environment of the software can be hardly reconstructed. The paper proposes a set of plausible methods to cope with these problems. The applicability of the methods is examined using case studies. The proposed methods can relieve the burden of the appraisal on the completeness of software.

소프트웨어 복제도 감정기법의 표준화 모델에 관한 연구

방효근,차태원,정태명,Bahng, Hyo-Keun,Cha, Tae-Own,Chung, Tai-Myoung 한국정보처리학회 2006 정보처리학회논문지D Vol.13 No.6

소프트웨어(SW) 복제도 감정의 목적은 두 프로그램 사이의 동일 또는 유사성 정도를 판단하는 것으로, 컴퓨터프로그림 저작권 관련 분쟁해결의 주요한 기술적 판단근거를 제시하는 제도라 할 수 있다. SW감정을 진행함에 있어서 중요한 점은 감정인의 주관적 판단에 편중되지 않도록 하고, 신속 객관적인 감정의 수행으로 정확한 감정결과를 도출해내는 것이다. 그러나 현재까지 체계적인 감정기법의 표준화 연구 및 개발은 미비한 상태이며, SW감정 분야별(유형별) 감정기법 조차 전문 감정인들에 따라 그 접근방법이 천차만별이어서 뚜렷한 표준안이 제시되지 못하고 있다. 또한, 기 수행되었던 감정사례에 대한 실증적 분석 결과, 기존 감정 절차 및 기법의 오류 또는 감정인의 전문지식 결여 등의 문제가 잠재하여 일부 감정결과에 대한 객관성 및 정확성에 손상이 있음을 알 수 있다. 본 논문에서는 감정인에 따라 동일한 평가 항목에 대하여 서로 다른 결과가 도출될 수 있는 오차의 허용치를 감소시키기 위한 객관적인 평가 방법과 정형화된 SW복제도 감정기법의 표준화 모델을 제시한다. 특히, 기존 감정기법의 문제점 해결 및 보완 연구를 기반으로 감정범위의 설정, 감정기준 및 방법, 단위작업 프로세스 기준의 감정영역 및 감정항목 설정, 가중치 부여, 논리적 복제도와 물리적 복제도 산출 등에 초점을 맞추어 감정기법을 분석 평가한다. 따라서 SW복제도 감정 기법의 표준화 모델은 감정인의 주관적 판단에 의한 오류의 가능성을 최소화하고, 감정결과의 객관성 및 신뢰성을 한층 제고하기 위한 도구를 제공할 것이다. The Purpose of Similarity(Reproduction) Degree Appraisal is to determine the equality or similarity between two programs and it is a system that presents the technical grounds of judgment which is necessary to support the resolution of software intellectual property rights through expert eyes. The most important things in proceeding software appraisal are not to make too much of expert's own subjective judgment and to acquire the accurate-appraisal results. However, up to now standard research and development for its systematic techniques are not properly made out and as different expert as each one could approach in a thousand different ways, even the techniques for software appraisal types have not exactly been presented yet. Moreover, in the analyzing results of all the appraisal cases finished before, through a practical way, we blow that there are some damages on objectivity and accuracy in some parts of the appraisal results owing to the problems of existing appraisal procedures and techniques or lack of expert's professional knowledge. In this paper we present the model for the standardization of software-similarity-appraisal techniques and objective-evaluation methods for decreasing a tolerance that could make different results according to each expert in the same-evaluation points. Especially, it analyzes and evaluates the techniques from various points of view concerning the standard appraisal process, setting a range of appraisal, setting appraisal domains and items in detail, based on unit processes, setting the weight of each object to be appraised, and the degree of logical and physical similarity, based on effective solutions to practical problems of existing appraisal techniques and their objective and quantitative standardization. Consequently, we believe that the model for the standardization of software-similarity-appraisal techniques will minimizes the possibility of mistakes due to an expert's subjective judgment as well as it will offer a tool for improving objectivity and reliability of the appraisal results.

OSMI 방식으로 개발된 소프트웨어의 형상 관리를 활용한 완성도 감정

김명주 한국소프트웨어감정평가학회 2024 한국소프트웨어감정평가학회 논문지 Vol.20 No.2

동일 업종의 자회사 다수를 보유한 그룹사의 경우, 자회사 간의 업무 일관성과 변화 통일성을 유지하면서도 자회사별 업무 독립성을 보장하기 위하여 단일소스 다중인스턴스(OSMI) 방식을 사용하여 업무 관리 소프트웨어를 공동 개발할 수 있다. 이처럼 다수의 자회사가 동일 개발사와 일괄 계약하여 OSMI 기반의 소프트웨어 개발을 착수했음에도 불구하고 일부 자회사의 인스턴스 개발이 실패하여 법적 소송까지 진행될 경우, 소송 관련 소프트웨어에 한정하여 개발 완성도를 산정해야 하는 감정 과정이 발생한다. 이미 개발이 완료된 자회사는 업무 과정에서 소스 코드를 계속 변경하며 사용하게 되므로 OSMI의 단일소스 특성 때문에 계약 만료일 시점에서의 감정 대상 소스 코드를 특정하기 어렵다. 만일 개발사가 소프트웨어형상 관리(SCM)를 사용하여 OSMI의 소스 코드 변경 로그를 꾸준히 유지해 왔다면, 이 이벤트 데이터를 활용하여 소프트웨어 완성도를 산정할 수 있다. 2개의 자회사가 OSMI 기반의 제조실행시스템(MES)을 함께 개발한 후 발생한 소송에서 SVM이라는 형상 관리를 활용하여 소프트웨어의 완성도를 감정한 사례를 제시한다. A group company with multiple subsidiaries in the same industry may develop business management software using the One Source Multiple Instances (OSMI) methodology. This approach ensures consistency and uniformity of changes across subsidiaries while maintaining each subsidiary's operational independence. Despite several subsidiaries contracting with the same developer to create OSMI-based software, some may face development failures, leading to legal disputes. In such cases, it is necessary to evaluate the completeness of the software specifically related to the lawsuit. Completed subsidiaries continually modify and use the source code, making it challenging to pinpoint the specific code for evaluation at the contract's end due to OSMI's single-source nature. However, if the developer has maintained OSMI source code event logs using Software Configuration Management (SCM), this data can be used to assess the software's completeness. An example is provided where SCM, specifically SVM, was used to evaluate software completeness in a lawsuit following the joint development of an OSMI-based Manufacturing Execution System (MES) by two subsidiaries

소프트웨어 포렌식 : 프로그램 소스코드 유사성 비교 및 분석을 중심으로

방효근,신동명,정태명 한국디지털포렌식학회 2007 디지털 포렌식 연구 Vol.1 No.1

As a sort of the Digital Forensics, Software Forensics are being used as a maeasure to decide disputes concerning the Intellectual Property Rights of software, and also act as important evidences in court. With regard to Software Forensics, we are regulating Software Appraisal syhstem under Computer Program Protection Act to raise the fair resolution of dispute's and operating Similarity Degree Appraisal to determine the equality or similarity between two programs. In this paper we are taking a look at the relation between Software Forensics and Software appraisal, while examining and analysing the trends regarding domestic and foreign matters. Furthermore, we introduce the procedure of Appraisal, an automated Appraisal-tool and finally a realistic example case. The research and basic arrangment in order to raise the reliability and fairness of Software Appraisal Results is proceeding, which is a measure to raise the acceptance of Software Appraisals in court. We also have to continue our research on the development of a tool analysing a huge amount of evidences in an efficient way. 디지털 포렌식의 하나인 소프트웨어 포렌식은 소프트웨어 지적재산권 분쟁의 해결을 위한 기술로 활용되고 있으며 법원의 판결시에도 중요한 증거자료로 활용되고 있다. 소프트웨어 포렌식과 관련하여, 국내에서는 소프트웨어 지적재산권 분쟁의 공정한 해결을 위하여 컴퓨터프로그램보호법에 감정제도를 규정하고 있으며 소프트웨어 관련 증거자료의 분석을 통해 소스코드 및 실행코드의 복제여부 및 복제율 산정 등을 감정하고 있다. 본 논문에서는 소프트웨어 포렌식과 감정제도의 관계를 살펴보고 국내외 동향을 조사 ․ 분석하였다. 또한 소프트웨어 복제도 감정 절차 및 소프트웨어 포렌식을 위한 도구에 대해 소개하고 실제 복제도 감정 사례에 대하여 소개하였다. 법원에 제출한 소프트웨어 감정서의 채택율을 높이기 위한 일환으로 소프트웨어 감정결과에 대한 신뢰성 및 공정성을 높이기 위한 연구 및 기준마련 등이 계속 진행 중이며, 대량의 증거자료를 효율적으로 분석하기 위하여 자동화된 분석 도구의 연구개발 또한 계속되어야 한다.

소프트웨어 완성도 감정과 기성고 감정 분리 필요성에 대한 고찰

김도완 한국소프트웨어감정평가학회 2021 한국소프트웨어감정평가학회 논문지 Vol.17 No.2

In this study, problems of software completeness appraisal are pointed out and their solutions are presented by analyzing appraisal cases and judicial precedents. Completeness appraisal, ready-made appraisal, defect appraisal, and cost appraisal have been classified as and have been evaluated with extant software completeness appraisals. From a legal point of view, and in judicial precedents, however, there is a big difference between the definition of completeness and the completion rate. This is because the degree of completeness is evaluated under the premise that the software’s development is complete, whereas the ready-made appraisal inspects the development progress of unfinished software. Often, in cases involving software completion rate, the total completion level is calculated by weighting each step of the software development process. However, completeness evaluations use the software’s realization-operation as its sole criterion. In addition, another issue not addressed in existing software completeness appraisal cases is that there is no mention of who is responsible for software defects, whereas in case law, the responsible party is determined by finding who caused the dispute. In this paper, we systematically classify these problems, and present a novel evaluation method that separates software completeness evaluations from software completion evaluations.

법정조언자 제도와 소프트웨어감정 제도의 비교 연구

김시열,김민정 한국소프트웨어감정평가학회 2018 한국소프트웨어감정평가학회 논문지 Vol.14 No.2

This study examines the implications of an appraisal system based on Article 119 of Korean Copyright Act, especially the appraisal of computer program works, by reviewing the amicus curiae system of the United States. Although the amicus curiae system is not exactly a target contrasted with the Korean appraisal system, it is meaningful to compare them in various aspects. The amicus curiae system is viewed positively for its function of providing information during litigation, supporting the court’s understanding of specialized fields, and providing opportunities for the socially disadvantaged to participate. As for software appraisal system under the Korean Copyright Act, on the other hand, more active participation is demanded in the dispute resolution process. Thus, through comparison with the amicus curiae system, this study considers the degree of appraisal involvement, the level of activeness in appraisal, the appraisal by expert groups, and the issue of appraisal costs.

소프트웨어 감정의 간이절차 활용 논의에 대한 검토

김시열,강윤수 한국소프트웨어감정평가학회 2019 한국소프트웨어감정평가학회 논문지 Vol.15 No.2

In copyright dispute on software, appraisal procedure is needed, which is regarded as an implementation of the right to fast trial. Considering that, in practice, there has been a long discussion of attempting to operate the software appraisal as a summary procedure. This was done usually by reducing the resources devoted to the summary procedure, however, this way inevitably makes difference in a result obtained through the procedure. Therefore, this research reviewed the previous operation of summary procedure in software appraisal, focusing on intrinsic nature of the summary procedure and role of software appraisal in the trial process.

SW 감정평가에서 디자인 단가산정을 위한 핵심 평가요소 연구

김양훈 한국소프트웨어감정평가학회 2018 한국소프트웨어감정평가학회 논문지 Vol.14 No.2

Typical software is implemented around functional elements, and design elements are considered as additional concepts. However, the design elements of software play an important role in assisting intuitive interpretation of functions in addition to aesthetic functions. In assessment and valuating the current software, it is difficult to derive the objective price because the evaluation criteria for design factors are ambiguous. Therefore, in this study, we derive the key evaluation factor of design factor in software assessment and valuation which can reasonably judge unit price for design effort in software development. As a result, we can indirectly estimate the efforts by distinguishing page design, screen design, main screen and core screen design, and other external icons and design.

민사소송법 개정에 따른 저작권 감정 제도의 실무적대응 방안

김시열 한국소프트웨어감정평가학회 2020 한국소프트웨어감정평가학회 논문지 Vol.16 No.1

The March 29, 2016, amendment to the Civil Procedure Act introduced changes to the appraisal procedures, including new obligations for appraisers, changes in the modes of appraiser testimony, and questioning of appraisers through video conferencing, with all seemingly aimed at procedurally addressing the issues with appraisal in the context of court proceedings. The changes introduced by the amendment also affect the appraisal procedures for copyrights. In light of the above, this article examines how the amendment to the Civil Procedure Act affects the appraisal procedures for copyrights. Specific issuescovered by this paper include: appointment of additional appraisers, prohibition of delegated appraisal,operation of the multiple appraisal system, disclosure of participating experts, proximity of the appraisersystem, and congruence of areas of expertise.

소프트웨어 완성도 감정을 위한 요구사항 완전성 평가

김유경 한국소프트웨어감정평가학회 2023 한국소프트웨어감정평가학회 논문지 Vol.19 No.1

Software requirements are agreed upon after quantifying the work, cost, and duration of a software development project and serve as a contract. It is an essential item for software development because it is derived by understanding the specifications and expectations of the product that both parties, the developer and the customer, want to develop. Most software completeness disputes arise mainly from functional differences between the developer and the customer about the final delivered product. Accordingly, the current software completeness appraisal verifies that the customer's requirements included in the contract are implemented and operated properly. As it is necessary to identify the source of responsibility that causes the dispute, it is very important to examine whether the role of the client as a project participant has been sufficiently fulfilled and complete requirements have been provided. In this paper, we look at the completeness evaluation method of requirements specification and discuss the possibility of using it in software completeness evaluation through the problems of requirements specification revealed in the case of job portal site completeness appraisal.