• Title/Summary/Keyword: 유스케이스 트랜잭션

Search Result 2, Processing Time 0.016 seconds

Software Effort Estimation based on Use Case Transaction (유스케이스 트랜잭션 기반의 소프트웨어 공수 예측 기법)

  • Lee, Sun-Kyung;Kang, Dong-Won;Bae, Doo-Hwan
    • 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.

An Elementary-Function-Based Refinement Method for Use Cases to Improve Reliability of Use Case Points (유스케이스 점수 측정의 신뢰도 향상을 위한 단위기능 중심의 유스케이스 정제 방법)

  • Heo, Ryoung;Seo, Young-Duk;Baik, Doo-Kwon
    • 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.