• The KIPS Transactions:PartD
• /
• v.13D no.6 s.109
• /
• pp.823-832
• /
• 2006

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.

• Journal of Software Assessment and Valuation
• /
• v.17 no.2
• /
• pp.11-17
• /
• 2021

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.

• Journal of Software Assessment and Valuation
• /
• v.15 no.2
• /
• pp.25-33
• /
• 2019

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.

• Journal of Software Assessment and Valuation
• /
• v.16 no.1
• /
• pp.21-26
• /
• 2020

The completeness appraisal of software is performed in various forms, such as assessing the completion level in the development process, calculating the defect rate, estimating the development cost, and calculating the redevelopment cost. Along with this, the problem that is often dealt with is estimation of the development time. Even in a dispute over completeness due to delays in software development, issues of calculating an appropriate development time required to develop a delivery software or a development time required for change requests are often included in the appraisal request. In this paper, we introduce the procedure and method for estimating the appropriate project time of software development so that the appraiser can be applied to the appraisal work for determining the completeness. The method is based on the manual for calculating the appropriate project period of software development project.

• Journal of the Korea Society of Computer and Information
• /
• v.10 no.6 s.38
• /
• pp.167-176
• /
• 2005

The software architecture is an essential part of a software-intensive system. In addition, the architecture evaluation is a very important process and a cheap way to avoid a software disaster. This article introduces a new method to evaluate architecture by maturity levels. Maturity Models which are about software and software process, have gained wide scale acceptance over the last decade. We are applying these techniques to the software architecture and propose SW(Software Architecture Maturity appraisal Model). SAMM consists of six-levels. We expect that our maturity model SAMM describe the requirements that any architecture must have in order to improve its software architecture design and constitute a proven architecture within which to manage the improvement efforts. We can reduce our effort to design architecture, have a guideline to construct the high qualify architecture with SAMM, and evaluate architecture and make architecture level.

• Journal of Software Assessment and Valuation
• /
• v.16 no.1
• /
• pp.27-36
• /
• 2020

The software development cost appraisal is treated as a part of the program completion appraisal, and the software engineering methodology is applied. In particular, software cost estimation techniques have been actively applied. For more information about the software development costs calculation, we can refer to the "SW cost estimation guide". Although successful appraisal of a number of development costs based on the guide has been processed, but a number of cases requiring discussion of appraisal results have been discovered. In this study, we propose a use case-based size estimation method to maintain the accuracy and consistency of size estimation. As a result of performing performance evaluation of the proposed method in an environment similar to the development cost appraisal case, it was proved that the accuracy was improved over the existing function points method.

• Journal of Software Assessment and Valuation
• /
• v.16 no.1
• /
• pp.1-11
• /
• 2020

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 issues covered 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 appraiser system, and congruence of areas of expertise.

• Journal of Software Assessment and Valuation
• /
• v.15 no.2
• /
• pp.35-42
• /
• 2019

In this study, we reviewed the definition of completeness and payment in SW appraisal along to being complicated requirements of the appraisal, and we also presented their meaning and computation method. The completeness in SW appraisals means the degree of functional completion of the final product, and the payment refers cost spent to develop the product. Therefore, the completeness is evaluated based on the functions or interfaces of the final product, while the payment is calculated on the outputs or expenses of development steps. Recently, SW appraisal is complicated and the requirements for completeness and payment are changing. In this paper, we review the meanings and objectives of completeness and payment and present the evaluation methods for those.

• 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.

• Journal of Software Assessment and Valuation
• /
• v.16 no.2
• /
• pp.37-44
• /
• 2020

As the information society develops, various cases of copyright infringement have occurred. In many disputes between companies, software similarity appraisal is dominated. This thesis is a study on the method of calculating the similarity of the standards subject to appraisal. In other words, it is a study to calculate the amount of revision and addition of the specification to be assessed. The analysis method compares the table of contents of both specifications and finds the same or similar part. The similarity weight is determined according to the degree of similarity. Weights identify and assign the degree of similarity between the expert's expertise and the specification. If it is completely newly added, the similarity weight is 1, if it is partially modified, the similarity weight is 0.4, and if it is almost the same as before, it is calculated by giving a weight of 0.05. Through this paper, it was found that the result of calculating the similarity to the specification is 21.2 pages.