• Title/Summary/Keyword: 소프트웨어 완성도 감정

Search Result 12, Processing Time 0.036 seconds

Software Completeness Evaluation based on ISO/IEC9241.10 (ISO/IEC 9241.10 표준에 기초한 소프트웨어 완성도-하자 감정 기법 연구)

  • Kim, Do-Wan
    • Journal of Software Assessment and Valuation
    • /
    • v.15 no.2
    • /
    • pp.9-16
    • /
    • 2019
  • More than 25% of software copyright evaluations commissioned to the Korea Copyright Commission are software completeness-defective evaluations. Most of the existing software completeness-defective evaluation cases were made to ensure that the requirements contained in the contract or customer's desired requirements were implemented and able to run, limited to the functionality of the software. This paper proposes a more systematic and reasonable maturity-correction technique to meet software completeness definitions. The ISO / IEC 9241.10 standard is a design standard for improving software quality. The ISO / IEC 9241.10 standard specifies seven items that must be complied with and requires functional integrity for work and operational integrity for work efficiency. The software completeness-defective methodology presented in this paper complements the existing function's implementation-functioning methodology with completeness evaluation on the quality of software.

A Study on the Need for Separation of Software Completeness Appraisal and Software Ready-made Appraisal (소프트웨어 완성도 감정과 기성고 감정 분리 필요성에 대한 고찰)

  • Kim, DoWan
    • 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.

Software Project Progress Assessment for Software Appraisal (소프트웨어 감정을 위한 공정율 평가 방안)

  • Kwon, Ho-Yeol
    • 한국IT서비스학회:학술대회논문집
    • /
    • 2010.05a
    • /
    • pp.436-438
    • /
    • 2010
  • 소프트웨어 감정은 분쟁이 발생했을 때 감정신청인의 감정 요청 사항에 대하여 전문가의 입장에서 소프트웨어 내용을 분석하고 감정하여 의견을 제출하게 된다. 특히 분쟁의 내용이 소프트웨어의 완성도 또는 공정율에 관한 경우에는 감정의 대상물인 목표 시스템 및 관련 산출물의 법적인 유효성 검토로 시작하여, 기완성 산출물 및 미완성 산출물에 개발공정의 진척도를 평가한다. 본 연구는 소프트웨어 개발과정에서 발주자와 개발자 사이에서 발생하는 공정율 감정에 대하여 추진 단계 및 세부적인 활동 그리고 현안에 대한 해결의 접근방법을 제시한다.

  • PDF

Improvement of Completeness Determination in Software Development Contract Disputes (소프트웨어 도급계약 분쟁에서 완성도 산출 방식의 한계와 문제점)

  • Kim, Si Yeol
    • 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.

Use Case Points Estimation for the Software Cost Appraisal (소프트웨어 개발비 감정을 위한 유스케이스 점수 추정)

  • Kwon, Ki-Tae
    • 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.

Meaning and Computation of Completeness and Payment in SW Appraisal (SW감정에서 완성도와 기성고의 의미 및 산출 방법)

  • Yun, Young-Sun
    • 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.

A Study on Valuation Method for Dispute Resolution of Software Development (소프트웨어 개발 분쟁해결을 위한 평가방안 연구)

  • Kim, Woo-Sung;Hwang, Jin-Ok;Min, Sung-Gi
    • Proceedings of the Korea Information Processing Society Conference
    • /
    • 2007.05a
    • /
    • pp.560-563
    • /
    • 2007
  • 본 논문은 소프트웨어의 완성도와 관련하여 발주사와 개발사간의 분쟁이 있을 시에 필요한 분쟁조정을 위한 평가방법을 연구하였다. 먼저 소프트웨어 개발 과정에서 발생할 수 있는 분쟁의 유형을 분류하였고, 객관적인 평가를 위한 감정 절차를 분류하였다. 본 연구에서는 분쟁조정의 객관성 확보를 위한 가중치 설정, 각 기능들에 대한 중요도를 설정하여 어느 정도의 완성도를 보였는지를 정량적으로 평가하였다. 또한, 프로그램의 복제 문제를 판단하기 위하여 필요한 감정 항목 설정 및 도용 여부를 판단하기 위한 기본 자료로 활용될 수 있을 것으로 기대한다.

  • PDF

A Study on the Development of Healing VR Content Based on Horticulture (원예 기반 힐링형 VR 콘텐츠 개발 연구)

  • Min-Gyeong Hwang;Jung-Yi Kim
    • The Journal of the Convergence on Culture Technology
    • /
    • v.9 no.4
    • /
    • pp.681-686
    • /
    • 2023
  • The study aims to develop horticulture-based VR content so that users can find rest in their chaotic daily lives. Healing contents that increase user participation, immersion, emotional stability, and creativity and concentration were implemented by using teleports, plant illustrations, inventory, NPC functions, and drawing games. Garden viewing content using VR technology requires technical research and development to overcome the difference from reality, which can increase the reality of the content and the completeness of the experience. The reality of the VR experience will be increased by using high-resolution displays, high-performance processors, and sensors, and user feedback will be collected and continuously improved. Through this, users present new methods by relieving stress, feeling emotional stability, and providing experiences that are impossible in reality.

A Study on the evaluation technique rubric suitable for the characteristics of digital design subject (디지털 디자인 과목의 특성에 적합한 평가기법 루브릭에 관한 연구)

  • Cho, Hyun Kyung
    • The Journal of the Convergence on Culture Technology
    • /
    • v.9 no.6
    • /
    • pp.525-530
    • /
    • 2023
  • Digital drawing subjects require the subdivision of evaluation elements and the graduality of evaluation according to the recent movement of the innovative curriculum. The purpose of this paper is to present the criteria for evaluating the drawing and to propose it as a rubric evaluation. In the text, criteria for beginner evaluation were technical skills such as the accuracy and consistency of the line, the ratio and balance of the picture, and the ability to effectively utilize various brushes and tools at the intermediate levels. In the advanced evaluation section, it is a part of a new perspective or originality centered on creativity and originality, and a unique perspective or interpretation of a given subject. In addition, as an understanding of design principles, the evaluation of completeness was derived focusing on the ability to actively utilize various functions of digital drawing software through design principles such as placement, color, and shape. The importance of introducing rubric evaluation is to allow instructors to make objective and consistent evaluations, and the key to research in rubric evaluation in these art subjects is to help learners clearly grasp their strengths and weaknesses, and learners can identify what needs to be improved and develop better drawing skills accordingly through feedback on each item.

Cortex M3 Based Lightweight Security Protocol for Authentication and Encrypt Communication between Smart Meters and Data Concentrate Unit (스마트미터와 데이터 집중 장치간 인증 및 암호화 통신을 위한 Cortex M3 기반 경량 보안 프로토콜)

  • Shin, Dong-Myung;Ko, Sang-Jun
    • Journal of Software Assessment and Valuation
    • /
    • v.15 no.2
    • /
    • pp.111-119
    • /
    • 2019
  • The existing smart grid device authentication system is concentrated on DCU, meter reading FEP and MDMS, and the authentication system for smart meters is not established. Although some cryptographic chips have been developed at present, it is difficult to complete the PKI authentication scheme because it is at the low level of simple encryption. Unlike existing power grids, smart grids are based on open two-way communication, increasing the risk of accidents as information security vulnerabilities increase. However, PKI is difficult to apply to smart meters, and there is a possibility of accidents such as system shutdown by sending manipulated packets and sending false information to the operating system. Issuing an existing PKI certificate to smart meters with high hardware constraints makes authentication and certificate renewal difficult, so an ultra-lightweight password authentication protocol that can operate even on the poor performance of smart meters (such as non-IP networks, processors, memory, and storage space) was designed and implemented. As a result of the experiment, lightweight cryptographic authentication protocol was able to be executed quickly in the Cortex-M3 environment, and it is expected that it will help to prepare a more secure authentication system in the smart grid industry.