• Journal of KIISE:Computing Practices and Letters
• /
• v.16 no.5
• /
• pp.566-570
• /
• 2010

Use Case Point(UCP) is a measure of a software project size for software effort estimation based on use case. UCP measures the size of the software project based on the use case model. Because UCP is based on the use case model, it is intuitive and easy to obtain. Also, it does not require extra artifacts. On the other hand, UCP has some problems. UCP assumes every transaction has the same complexity. But, the number of operations and complexity of operations may affect complexity of transaction. In addition, UCP uses simple rating scale of complexity, but it may be inadequate for detailed estimates. To solve these problems, we suggest "Transaction Point(TP)", a size measure based on use case transaction. TP considers actors and operations in transaction. Complexity of transaction is based on the number of operations and complexity of operation, so it can support detailed estimation.

• Journal of KIISE
• /
• v.42 no.9
• /
• pp.1117-1123
• /
• 2015

Use The Use Case Points method is a software estimation method that is based on user requirements. When requirement analysts elicit user requirements, they obtain different use cases because different levels of detail are possible for the Use Case, and this affects the Use Case Points. In this paper, we suggest a method to refine the level of detail of the Use Case by using the concept of an elementary function. This refinement method achieves the desired reliability for the Use Case Points because it produces less of a deviation in the Use Case Points for different requirement analysts than other methods that are based on the step, transaction, and narrative of the Use Case.

• The KIPS Transactions:PartD
• /
• v.12D no.1 s.97
• /
• pp.103-110
• /
• 2005

Software Development is converting from structural to object oriented method. The later software development prefers the iterative process applications, not aterfall process and based on use case model, the requirements are expressed and based on this, analysis, design and coding are accomplished. Therefore, size of the software to be developed is estimated basing on use case and it is only possible to maintain the project success by estimating development effort, cost and development period. Even though development effort estimation models related current use case point. there is no appropriate development effort estimating. This paper shows, as a result of applying the development effort estimating model about UCP to the growth curve, a superior performance improvement to current statistical models. Therefore, estimation of development effort by applying this model, project development maintenance can be appropriately carried out.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2019.10a
• /
• pp.701-703
• /
• 2019

현재의 소프트웨어는 매우 크고 복잡하다. 고품질 소프트웨어는 요구사항 단계부터 정확하게 분석해야 한다. 그러나 자연어 요구사항은 부정확하기 때문에 유스케이스 식별이 어렵다. 게다가, 기존 요구 사항 분석 방법은 객체와 용어 식별에 대한 정확한 기준이 없다. 따라서 분석 결과는 분석가마다 다르다. 본 논문에서는 자연어 요구사항으로부터 유스케이스 추출 및 소프트웨어 공수 산정 방법을 제안한다. 제안한 방법에서는 Goal Modeling과 Fillmore의 Case 메커니즘을 개선했다. 이 방법은 자연어 요구 사항을 단계별로 분석하여 유스케이스를 모델링한다. 또한 유스케이스 점수(Use Case Point)를 이용하여 소프트웨어의 공수를 산정(Effort Estimation)한다. 제안한 방법은 고품질 소프트웨어 개발을 위해 자연어 요구사항의 변경 없이 유스케이스 추출이 가능하다. 또한 추출된 유스케이스를 통해 UCP 기반의 공수 산정을 평가할 수 있다. 본 논문에서는 우체국 시스템의 사례에 적용하였다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2012.11a
• /
• pp.1497-1499
• /
• 2012

전통적인 소프트웨어 개발에서는 초기 요구사항을 정확히 판단하고 분석하는 것이 중요하다. 이를 위해 B.Boehm은 가치혁신 요구공학을 제안하지만, 이는 기존의 개발 방법 기반이다. 본 논문에서는 가치 혁신 요구공학 개선을 위해, 유스케이스 기반의 요구공학 방법을 제시와, 요구사항과 유스케이스의 우선순위 도출 방법을 제안한다. 이를 위해 어려운 시스템 요소(하드웨어와 소프트웨어)를 기본 단위인 유스케이스 요소와, 유스케이스 점수(Use Case Point) 개념을 적용하여 유스케이스 중요도를 도출한다. 그 기본 단위 내의 분석을 통해 쉽게 요구사항 추출 및 우선순위화를 한다. 이는 테스트 단계에서 우선순위화된 테스트 케이스를 적용이 가능한다고 본다.

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

• The KIPS Transactions:PartD
• /
• v.11D no.3
• /
• pp.597-604
• /
• 2004

Accurate software cost estimation is essential to both developers and customers. Most of the cost estimating models based on the size measure methods, such as LOC and FP, are obtained through size estimation. The accuracy of size estimation directly influences the accuracy of cost estimation. As a result, the overall structure of regression-based cost models applies the power function based on software size. Many growth phenomenon in nature such as the growth in living organism, performance of technology, and learning capability of human show an S-shaped curve. This paper proposes a model which estimates the developing effort by using the growth curve. The presented model assumes that the relation cost and size follows the growth curve. The appropriateness of the growth curve model based on Function Point, Full-Function Point and Use-Case Point, which are the general methods in estimating the software size have been confirmed. The proposed growth curve model shows similar performance with power function model. In conclusion, the growth curve model can be applied in the estimation of the software cost.

• The KIPS Transactions:PartD
• /
• v.15D no.3
• /
• pp.375-386
• /
• 2008

Recently, development paradigm of information system is turning into object oriented and component based, and this methodology is leading the software industry. To acclimatize aptly to this trend, users demand the assessment of software expenses to change with the appropriate model of computing costs of the environment, and some people are actually studying the concept of Object Oriented Function Point and UCP method. Especially, Object Oriented Function Point Measurement Process has good points in overcoming the bound of LOC and the existing the Function Point Measurement Process because Object Oriented Function Point Measurement Process is applicable to the early stage of development project mainly with the used cases, and valid to the life long period as the each stage of software products develops, and always understandable to communicate with users by the UML mark rules. Accordingly, this research is to measure Functional Point at ROFP and AOFP in accordance with the development project of information system by the national defense CBD methodology procedures and UML Interrelation Analysis that are recently and widely used in the developmental environment of object oriented information system. Furthermore, this study suggests the measurement method to obtain Functional Point, and identifies service function and object/class function in the correlation analysis of use case and class based on the products and UML modeling via traditional FPA model and object oriented FPA model. Above all, this study is to demonstrate the improvement of traditional Function Point Measurement Process, IFPUG-CPM and software cost basis, and reveal Function Point Measurement Process, which is appropriate to the development of object oriented information system, and suggest the evaluation results of the compatibility through case studies.