KJCKorea
Journal Central

Agile Agile methodologies have gained significant popularity among software development organizations. While agile methodologies minimize formal processes, they still require estimation methodologies for development cost appraisal. In agile software projects, story points are used to estimate development man-hours by comparing the estimated man-hours to the actual man-hours, but they do not provide the size of the software developed, which makes it difficult to compare the productivity achieved in a project, or to compare performance across projects. In this study, we compare the effectiveness of function point-based and story point-based effort estimation from an agile perspective through a case analysis and observe that function point-based estimation is more accurate and allows for function point-based productivity calculations with less deviation than productivity calculated with story points. This led to the improvement of story points as a standard measure in agile software projects.

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

In copyright infringement actions, parts of a work that are not protected creative expressions are excluded from the determination of infringement, especially in the substantial similarity test. With the increasing use of AI in programming, it's crucial to exclude AI-generated parts of a computer program in such disputes. However, third parties cannot accurately identify these AI-generated portions without the active cooperation of the parties involved, which is often difficult to guarantee. Therefore, a procedure requiring parties to identify parts of the program created using AI is necessary. To ensure the effectiveness of this obligation, there should be practical sanctions for non-compliance, such as dismissing the claim against the offending party. This approach considers the benefits that could be gained from violating the specific obligation.