Automatic Transactions Identification in Use Cases

  • Mirosław Ochodek
  • Jerzy Nawrocki
Part of the Lecture Notes in Computer Science book series (LNCS, volume 5082)

Abstract

Since the early 90’s of the previous century, use cases have became informal industry standard for presenting functional requirements. The rapid popularity growth stimulated many different approaches for their presentation and writing styles. Unfortunately, this variability makes automatic processing of use cases very difficult. This problem might be mitigated by the use of transaction concept, which is defined as an atomic part of the use case scenario. In this paper we present approach to the automatic transaction discovery in the textual use cases, through the NLP analysis. The proposed solution was implemented as a prototype tool UCTD and preliminarily verified in a case study.

Keywords

Use cases Use-cases transactions Use Case Points Requirements engineering Effort estimation Natural language processing 

References

  1. 1.
    Adolph, S., Bramble, P., Cockburn, A., Pols, A.: Patterns for Effective Use Cases. Addison-Wesley, Reading (2002)Google Scholar
  2. 2.
    Albrecht, A.J., Gaffney Jr., J.E.: Software function, source lines of code and envelopment effort prediction: a software science validation. Mcgraw-Hill International Series In Software Engineering, pp. 137–154 (1993)Google Scholar
  3. 3.
    Anda, B., Sjøberg, D.I.K.: Towards an inspection technique for use case models. In: Proceedings of the 14th international conference on Software engineering and knowledge engineering, pp. 127–134 (2002)Google Scholar
  4. 4.
    Arnold, M., Pedross, P.: Software Size Measurement and Productivity Rating in a Large-Scale Software Development Department. In: Proc. of the 20th ICSE, pp. 490–493 (1998)Google Scholar
  5. 5.
    Banerjee, G., Production, A.: Use Case Estimation Framework.Google Scholar
  6. 6.
    Beck, K., Fowler, M.: Planning Extreme Programming. Addison-Wesley, Reading (2000)Google Scholar
  7. 7.
    Ciemniewska, A., Jurkiewicz, J., Nawrocki, J., Olek, Ł.: Supporting use-case reviews. In: Abramowicz, W. (ed.) BIS 2007. LNCS, vol. 4439, pp. 424—437. Springer, Heidelberg (2007)Google Scholar
  8. 8.
    Clemmons, R.K.: Project Estimation With Use Case Points. CrossTalk–The Journal of Defense Software Engineering (February 2006)Google Scholar
  9. 9.
    Cockburn, A.: Writing effective use cases. Addison-Wesley, Boston (2001)Google Scholar
  10. 10.
    Cunningham, H., Maynard, D., Bontcheva, K., Tablan, V.: GATE: A framework and graphical development environment for robust NLP tools and applications. In: Proceedings of the 40th Anniversary Meeting of the Association for Computational Linguistics (2002)Google Scholar
  11. 11.
    Diev, S.: Software estimation in the maintenance context. ACM SIGSOFT Software Engineering Notes 31(2), 1–8 (2006)CrossRefGoogle Scholar
  12. 12.
    Dutoit, A.H., Paech, B.: Rationale-Based Use Case Specification. Requirements Engineering 7(1), 3–19 (2002)CrossRefMATHGoogle Scholar
  13. 13.
    Endres, A., Rombach, H.D.: A Handbook of Software and Systems Engineering: Empirical Observations, Laws, and Theories. Addison-Wesley, Reading (2003)Google Scholar
  14. 14.
    Fantechi, A., Gnesi, S., Lami, G., Maccari, A.: Applications of linguistic techniques for use case analysis. Requirements Engineering 8(3), 161–170 (2003)CrossRefGoogle Scholar
  15. 15.
    Fellbaum, C.: Wordnet: an electronic lexical database. Mit Pr (1998)Google Scholar
  16. 16.
    Harel, D.: Statecharts: A visual formalism for complex systems. Technical report, Weizmann Institute of Science, Dept. of Computer Science (1986)Google Scholar
  17. 17.
    Harry, A.: Formal Methods Fact File: VDM and Z. Wiley, Chichester (1996)Google Scholar
  18. 18.
    Jacobson, I.: Object-oriented development in an industrial environment. ACM SIGPLAN Notices 22(12), 183–191 (1987)CrossRefGoogle Scholar
  19. 19.
    Jacobson, I., Christerson, M., Jonsson, P., Overgaard, G.: Object-oriented software engineering: A use case driven approach (1992)Google Scholar
  20. 20.
    Karner, G.: Resource Estimation for Objectory Projects. Objective Systems SF AB (copyright owned by Rational Software) (1993)Google Scholar
  21. 21.
    Klein, D., Manning, C.D.: Accurate unlexicalized parsing. In: Proceedings of the 41st Annual Meeting of the Association for Computational Linguistics, pp. 423–430 (2003)Google Scholar
  22. 22.
    Kusumoto, S., Matukawa, F., Inoue, K., Hanabusa, S., Maegawa, Y.: Estimating effort by use case points: method, tool and case study. In: Proceedings. 10th International Symposium on Software Metrics, pp. 292–299 (2004)Google Scholar
  23. 23.
    Reif, W.: Formale methoden fur sicherheitskritische software - der kiv-ansatz. Informatik - Forschung und Entwicklung 14, 193–202 (1999)Google Scholar
  24. 24.
    Reisig, W.: Petri nets, an introduction. In: Salomaa, A., Brauer, W., Rozenberg, G. (eds.) EATCS, Monographs on Theoretical Computer Science, Berlin, Springer, Heidelberg (1985)Google Scholar
  25. 25.
    Ribu, K.: Estimating object-oriented software projects with use cases. Master’s thesis, University of Oslo, Department of Informatics (2001)Google Scholar
  26. 26.
    Rolland, C., Achour, C.B.: Guiding the construction of textual use case specifications. Data Know Eng. 25(1), 125–160 (1998)CrossRefMATHGoogle Scholar
  27. 27.
    Schneider, G., Winters, J.P.: Applying use cases: a practical guide. Addison-Wesley Longman Publishing Co., Inc., Boston (1998)Google Scholar

Copyright information

© IFIP International Federation for Information Processing 2008

Authors and Affiliations

  • Mirosław Ochodek
    • 1
  • Jerzy Nawrocki
    • 1
  1. 1.Institute of Computing SciencePoznań University of TechnologyPoznańPoland

Personalised recommendations