• Title/Summary/Keyword: SW Appraisal

Search Result 8, Processing Time 0.027 seconds

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

A Study on the Research Model for the Standardization of Software-Similarity-Appraisal Techniques (소프트웨어 복제도 감정기법의 표준화 모델에 관한 연구)

  • Bahng, Hyo-Keun;Cha, Tae-Own;Chung, Tai-Myoung
    • 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.

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.

An Overview of Time Estimation in the Appraisal of Completeness for Software

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

A study on the Maturity Appraisal Model of Software Architecture (소프트웨어 아키텍처의 성숙 평가 모델에 관한 연구)

  • Kim Kyung-Hee
    • 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.

  • PDF

Performance Evaluation Study of Solarwall-Photovoltaic Module to Generate Solar Electric Power (SWPV 태양 열-전기 복합생산 모듈 성능평가 연구)

  • Naveed Ahmed T;Kang E. C.;Lee E. J.
    • 한국신재생에너지학회:학술대회논문집
    • /
    • 2005.06a
    • /
    • pp.397-402
    • /
    • 2005
  • Photovoltaic (PV) module can generate electricity using sunlight without causing any environmental degradation. Due to higher fossil fuel prices and environmental awareness, PV applications are becoming more popular as clean source of electricity generation. PV output is sensitive to the operating temperature and can be drastically affected in Building Integrated PV (BIPV) systems. PV Solarwall (SWPV) combination and PV systems have been evaluated in this study for improvement in electrical output and system costs. PV modules under forced ventilation. A 75W polycrystalline silicon PV module was fixed on SW in front of the ventilation fan as it was indicated to be the coolest position on the SW in phoenix simulations. The effectiveness of cooling by means of the forced ventilating air stream has been studied experimentally. The results indicate that there appears to be significant difference in temperature as well as electricity output comparing the SWPV and BIPV options. Electrical output power recovered is about $4\%$ during the typical day of the month of February. RETScreen(R) analysis of a 3kW PV system hypothetically located at Taegu has shown that with typical temperature reduction of $15^{{\circ}C$, it is possible to reduce the simple payback periods by one year. The work described in this paper may be viewed as an appraisal of a SWPV system based on its improved electrical and financial performances due to its ability to operate at relatively lower temperatures.

  • PDF

Computer modeling of crack propagation in concrete retaining walls: A case study

  • Azarafza, Mehdi;Feizi-Derakhshi, Mohammad-Reza;Azarafza, Mohammad
    • Computers and Concrete
    • /
    • v.19 no.5
    • /
    • pp.509-514
    • /
    • 2017
  • Concrete retaining walls are the most common types of geotechnical structures for controlling instable slopes resulting from lateral pressure. In analytical stability, calculation of the concrete retaining walls is regarded as a rigid mass when its safety is required. When cracks in these structures are created, the stability may be enforced and causes to defeat. Therefore, identification, creation and propagation of cracks are among the important steps in control of lacks and stabilization. Using the numerical methods for simulation of crack propagation in concrete retaining walls bodies are among the new aspects of geotechnical analysis. Among the considered analytical methods in geotechnical appraisal, the boundary element method (BEM) for simulation of crack propagation in concrete retaining walls is very convenient. Considered concrete retaining wall of this paper is Pars Power Plant structured in south side in Assalouyeh, SW of Iran. This wall's type is RW6 with 11 m height and 440 m length and endurance of refinery construction lateral forces. To evaluate displacement and stress distributions (${\sigma}_{1,max}/{\sigma}_{3,min}$), the surrounding, especially in tip and its opening crack BEM, is considered an appropriate method. By considering the result of this study, with accurate simulation of crack propagation, it is possible to determine the final status of progressive failure in concrete retaining walls and anticipate the suitable stabilization method.